December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 877685] New: smartmontools can not read information from MegaRaid controller
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=877685 https://bugzilla.novell.com/show_bug.cgi?id=877685#c0 Summary: smartmontools can not read information from MegaRaid controller Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: svalx(a)svalx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 smartmontools-6.2-2.1.2.x86_64 I have a single MegaRaid 9240-8i controller with 8 disks on 2 RAID's. and want to get info about this disks. Reproducible: Always Steps to Reproduce: ---------- # smartctl -i /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14.3-26.g2a280a3-desktop] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Smartctl open device: /dev/sdd failed: DELL or MegaRaid controller, please try adding '-d megaraid,N' --------- # smartctl -i -d megaraid,0 /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14.3-26.g2a280a3-desktop] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Smartctl open device: /dev/sdd [megaraid_disk_00] failed: INQUIRY failed --------- $ man smartctl ... megaraid,N - [Linux only] the device consists of one or more SCSI/SAS disks connected to a MegaRAID controller. The non-negative integer N (in the range of 0 to 127 inclusive) denotes which disk on the controller is monitored. Use syntax such as: smartctl -a -d megaraid,2 /dev/sda smartctl -a -d megaraid,0 /dev/sdb smartctl -a -d megaraid,0 /dev/bus/0 The following entry in /proc/devices must exist: For PERC2/3/4 controllers: megadevN For PERC5/6 controllers: megaraid_sas_ioctlN ... --------- $ grep mega /proc/devices 250 megaraid_sas_ioctl --------- So I have megaraid_sas_ioctl instead megaraid_sas_ioctl0 and probably it case of failed inquiry. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 929899] New: something is wrong with ruby requires in YaST packages
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=929899 Bug ID: 929899 Summary: something is wrong with ruby requires in YaST packages Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: aschnell(a)suse.com Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- See discussion on yast-devel mailing list today and PBI https://trello.com/c/UdOTBSOZ/178-1-fix-rubygem-dependencies-for-ruby-2-2. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 908451] New: GRUB update removes custom themes
by bugzilla_noreply＠novell.com 11 Mar '18

11 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=908451 Bug ID: 908451 Summary: GRUB update removes custom themes Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jon(a)grossart.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I'm using Tumbleweed, and I've seen this happen across multiple installs. 1. create an optional theme in /boot/grub2/themes (not installed via the package manager) 2. set the theme via YaST2 > Boot loader 3. reboot 4. theme shows up 5. have a system update for grub (not sure if just the update grub command will clobber it or if it's a package upgrade) 6. reboot 7. theme is back to the default theme and custom theme has been removed from /boot/grub2/themes -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 956755] New: yast lan: Can't setup network using yast after manual configuration
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=956755 Bug ID: 956755 Summary: yast lan: Can't setup network using yast after manual configuration Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: gsanso(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The issue happens the following way: 1) I setup network some network interfaces by using a script (See attached ifcfg files > in Files dir) 2) I start yast: # yast lan 3) An error message is displayed and I can't continue: Error Internal error. Please report a bug report with logs. Details: undefined method `[]' for nil:NilClass Caller: /usr/share/YaST2/modules/LanItems.rb:1319:in `block in BuildLanOverview' 4) For more info see logs > in attached Logs dir -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 939745] New: sprof: Inconsistency detected by ld.so: dl-open.c: 707
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=939745 Bug ID: 939745 Summary: sprof: Inconsistency detected by ld.so: dl-open.c: 707 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I am running openSUSE 13.2, glibc-devel-2.19-16.15.1.x86_64 and trying to run sprof as the following. 1. compile my shared object with -g 2. export LD_PROFILE_OUTPUT=`pwd` 3. export LD_PROFILE=libmylib.so 4. run my app 5. sprof libmylib.so libmylib.so.profile Then I see Inconsistency detected by ld.so: dl-open.c: 707: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed and sprof terminates. It reproduces always. How can I provide additional info? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 926792] New: release-notes-openSUSE requires google-opensans-fonts
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=926792 Bug ID: 926792 Summary: release-notes-openSUSE requires google-opensans-fonts Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: ke(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: coolo(a)suse.com CC: rsalevsky(a)suse.de Found By: --- Blocker: --- Mailing list discussion: http://lists.opensuse.org/opensuse-packaging/2015-04/msg00069.html Specimens of fonts at issue: https://www.google.com/fonts/specimen/Open+Sans Trying to zypper rm google-opensans-fonts wants to remove opensuse-release-notes. Unless google-opensans-fonts contains *necessary* fonts unavailable elsewhere, fonts that if unavailable would break functionality, suggests or recommends for google-opensans-fonts is OK, but not requires. Theming does not create necessity or functionality. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 958884] New: Update yast and lcn packages for 42.1
by bugzilla_noreply＠novell.com 06 Mar '18

06 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=958884 Bug ID: 958884 Summary: Update yast and lcn packages for 42.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: medipas(a)gmail.com QA Contact: ke(a)suse.com Found By: --- Blocker: --- For instance, zypper dup's list of changes don't appear localized. Suse's search page is not showing all available finished translations. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 918654] New: ndpmon stops silently to work
by bugzilla_noreply＠novell.com 04 Mar '18

04 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=918654 Bug ID: 918654 Summary: ndpmon stops silently to work Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tschaefer(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using the following paket: rpm -qi ndpmon Name : ndpmon Version : 1.4.0 Release : 8.1 Architecture: x86_64 Install Date: Do 11 Dez 2014 11:11:33 CET Group : Productivity/Networking/Diagnostic Size : 1304023 License : LGPL-2.1+ Signature : DSA/SHA1, Mi 15 Okt 2014 17:26:58 CEST, Key ID ff9db4771bce05ef Source RPM : ndpmon-1.4.0-8.1.src.rpm Build Date : Mi 15 Okt 2014 17:26:32 CEST Build Host : cloud118 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/home:gregfreemyer:Tools-for-forensic-boot-cd URL : http://ndpmon.sourceforge.net/ Summary : IPv6 Neighbor Discovery Protocol Monitor Description : NDPMon, Neighbor Discovery Protocol Monitor, is a tool working with ICMPv6 packets. NDPMon observes the local network to see if nodes using neighbor discovery messages behave properly. When it detects a suspicious Neighbor Discovery message, it notifies the administrator by writing in the syslog and in some cases by sending an email report. Distribution: home:gregfreemyer:Tools-for-forensic-boot-cd / openSUSE_13.2 ndpmon starts and is running for a while: systemctl status ndpmon.service ndpmon.service - LSB: IPv6 Neighbor Discovery Protocol Monitor Loaded: loaded (/etc/init.d/ndpmon) Active: active (running) since Do 2015-02-19 15:58:57 CET; 44s ago Process: 19017 ExecStop=/etc/init.d/ndpmon stop (code=exited, status=0/SUCCESS) Process: 19028 ExecStart=/etc/init.d/ndpmon start (code=exited, status=0/SUCCESS) CGroup: /system.slice/ndpmon.service └─19035 /usr/sbin/ndpmon Feb 19 15:59:32 pflaume ndpmon[19028]: ------------------ Feb 19 15:59:32 pflaume ndpmon[19028]: ----- ND_NEIGHBOR_ADVERT ----- Feb 19 15:59:32 pflaume ndpmon[19028]: Reset timer for 0:19:99:f3:0:42 fe80:0:0:0:219:99ff:fef3:42 Feb 19 15:59:32 pflaume ndpmon[19028]: ------------------ Feb 19 15:59:33 pflaume ndpmon[19028]: ----- ND_NEIGHBOR_SOLICIT ----- Feb 19 15:59:33 pflaume ndpmon[19028]: Reset timer for b4:b5:2f:f3:b5:ac fe80:0:0:0:b6b5:2fff:fef3:b5ac Feb 19 15:59:33 pflaume ndpmon[19028]: ------------------ Feb 19 15:59:33 pflaume ndpmon[19028]: ----- ND_NEIGHBOR_ADVERT ----- Feb 19 15:59:33 pflaume ndpmon[19028]: Reset timer for 0:19:99:f3:0:42 fe80:0:0:0:219:99ff:fef3:42 Feb 19 15:59:33 pflaume ndpmon[19028]: ------------------ But after some time/days: there are no mails and the state is: systemctl status ndpmon.service ndpmon.service - LSB: IPv6 Neighbor Discovery Protocol Monitor Loaded: loaded (/etc/init.d/ndpmon) Active: active (running) since Mo 2015-02-09 16:22:46 CET; 1 weeks 2 days ago Process: 762 ExecStart=/etc/init.d/ndpmon start (code=exited, status=0/SUCCESS) CGroup: /system.slice/ndpmon.service └─809 /usr/sbin/ndpmon Feb 19 15:58:31 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:31 pflaume ndpmon[762]: ------------------ Feb 19 15:58:31 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:31 pflaume ndpmon[762]: ------------------ Feb 19 15:58:32 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:32 pflaume ndpmon[762]: ------------------ Feb 19 15:58:32 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:32 pflaume ndpmon[762]: ------------------ Feb 19 15:58:44 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:44 pflaume ndpmon[762]: ------------------ I don't know, what is going wrong here. I have seen that there is a complete new version at http://ndpmon.sourceforge.net/ Or can somebody recommend alternatives? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 942795] New: Mute microphone button/led do not work on Lenovo T410
by bugzilla_noreply＠novell.com 04 Mar '18

04 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=942795 Bug ID: 942795 Summary: Mute microphone button/led do not work on Lenovo T410 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: makripodis(a)techgr.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello I have installed Opensuse 13.2 x86_64, default KDE installation, on a Lenovo T410 laptop The mute microphone button does not work. I list some system information as follows. Thanks haris@atlas:~> uname -ior 3.16.7-24-desktop x86_64 GNU/Linux haris@atlas:~> lsmod | egrep -i 'sound|acpi|think|audio|snd' snd_usb_audio 174132 0 snd_usbmidi_lib 29779 1 snd_usb_audio snd_rawmidi 34923 1 snd_usbmidi_lib snd_seq_device 14497 1 snd_rawmidi snd_hda_codec_hdmi 55740 4 snd_hda_codec_conexant 19013 1 snd_hda_codec_generic 77203 2 snd_hda_codec_conexant snd_hda_intel 34475 5 snd_hda_controller 35103 1 snd_hda_intel snd_hda_codec 156066 5 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller snd_hwdep 13602 2 snd_usb_audio,snd_hda_codec snd_pcm 116857 5 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller thinkpad_acpi 87443 1 snd_timer 33609 1 snd_pcm snd 87947 23 snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_rawmidi,snd_hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device rfkill 26772 5 cfg80211,thinkpad_acpi,bluetooth acpi_cpufreq 19433 1 soundcore 15047 2 snd,snd_hda_codec processor 40484 1 acpi_cpufreq haris@atlas:~> haris@atlas:~> cat /etc/issue Welcome to openSUSE 13.2 "Harlequin" - Kernel \r (\l). haris@atlas:~> rpm -qa | egrep -i 'sound|mix|audio' libasound2-1.0.28-6.1.4.x86_64 pulseaudio-utils-5.0-4.21.1.x86_64 pulseaudio-module-lirc-5.0-4.21.1.x86_64 libwebrtc_audio_processing0-0.1-11.1.2.x86_64 pulseaudio-5.0-4.21.1.x86_64 kio_audiocd-14.12.3-16.1.x86_64 libgstaudio-1_0-0-1.4.3-1.5.x86_64 pulseaudio-module-bluetooth-5.0-4.21.1.x86_64 esound-daemon-0.2.41-28.1.2.x86_64 pulseaudio-module-zeroconf-5.0-4.21.1.x86_64 kmix-14.12.3-16.1.x86_64 pulseaudio-module-x11-5.0-4.21.1.x86_64 yast2-sound-3.1.4-2.1.10.x86_64 pulseaudio-module-jack-5.0-4.21.1.x86_64 sound-theme-freedesktop-0.8-7.1.2.noarch libaudiofile1-0.3.6-6.1.2.x86_64 haris@atlas:~> haris@atlas:~> cat /etc/modprobe.d/50-sound.conf /etc/modprobe.d/50-alsa.conf options snd slots=snd-hda-intel,snd-hda-intel # u1Nb.WiEkMfkoYv9:5 Series/3400 Series Chipset High Definition Audio alias snd-card-0 snd-hda-intel # NXNs.H_iCoShyb69:High Definition Audio Controller alias snd-card-1 snd-hda-intel install snd /sbin/install-snd-module snd $CMDLINE_OPTS install snd-pcm /sbin/install-snd-module snd-pcm $CMDLINE_OPTS install snd-seq /sbin/install-snd-module snd-seq $CMDLINE_OPTS haris@atlas:~> -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 960456] New: Firefox freezes on AccuWeather extended forecast webpage
by bugzilla_noreply＠novell.com 04 Mar '18

04 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=960456 Bug ID: 960456 Summary: Firefox freezes on AccuWeather extended forecast webpage Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: tandrewjohnson(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Recently I've had problems with Firefox freezing (requiring me to forcibly terminate it), and pinpointed it to the AccuWeather extended forecast webpage. Firefox works fine with every other webpage I've browsed, including on AccuWeather.com. The extended forecast page loads fine in Firefox on Fedora 23, Windows 7, and Windows 8.1, but not in openSUSE 13.2. I've tried everything I could think of to find the cause of this problem. I restarted Firefox in safe mode, but the problem still exists. I reinstalled openSUSE completely, after which the problem was fixed until I installed the ~400 updates recommended by the software applet. This caused the problem to return, so I temporarily solved it by installing the ESR version of Firefox which works. I checked the Web Console and didn't see any unusual error messages. When the Developer Tools pane is open though, the problem seemed to disappear. However, when I scrolled down, then Firefox froze, so it seems like the source of the problem is an element that's about halfway down the page. I think this might be a duplicate of bug 942817, which sounds very similar. I asked about this problem on the openSUSE forum: https://forums.opensuse.org/showthread.php/512291-Firefox-freezes-on-AccuWe… and was told that the problem might be related to the Intel graphics drivers in the kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 3