May 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 815322] New: device of "$PWD" not in output of mount if on 'root' (/dev/rootfs not in mount output)
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=815322 https://bugzilla.novell.com/show_bug.cgi?id=815322#c0 Summary: device of "$PWD" not in output of mount if on 'root' (/dev/rootfs not in mount output) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)tlinx.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 I have a simple util program that has worked until recently -- I'm not sure if it went into 12.3 (I think so), or if it is in factory. These 3 lines demonstrate the problem: dev=$(df /bin |tail -1|cut -d\ -f1) mountline=$(mount|grep "$dev"); [[ -z ${mountline:-} ]] && mountline=ERROR echo "mounted with /etc/fstab line: '$mountline'" For some reason, the devices shown by 'mount' don't seem to be the devices shown in 'df' nor in /etc/fstab, yet both are documented to use /etc/mtab. Reproducible: Always Steps to Reproduce: 1. Try above script lines -- note that dev for root = /dev/root 2. But note that output of mount doesn't show /dev/root -- (only rootfs). 3. mount doesn't recognize 'rootfs' as a block device or special type: # mount rootfs /mnt mount: special device rootfs does not exist Ishtar:/bin# mount rootfs /mnt -t rootfs mount: wrong fs type, bad option, bad superblock on rootfs, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Actual Results: mount claims root is on a non-existent device. Expected Results: mount should list values in mtab that show existing devices, not non-existent device aliases. -- 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 15

[Bug 852036] New: incorrect work of command _login_
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=852036 https://bugzilla.novell.com/show_bug.cgi?id=852036#c0 Summary: incorrect work of command _login_ 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: Microsoft-SUXX(a)mail.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 login by standart way in system type in console $login "username" 1) result in X - nothing 2) in console Alt-[F1-F6] result of this comman is LOGOUT but if username already loggeid in one of the other console - then rasult is also nothing Reproducible: Always Steps to Reproduce: 1. Add 2 or more user account in system 2. Get in X (graphic mode) console (terminal window) or 2A. Go to clear terminal in Alt-F1...Alt-F6 3. Type: login username Actual Results: In case 2. Nothing In case 2A. result of this command is LOGOUT. but if username already loggeid in one of the other console - then result is nothing Expected Results: Login with username account. -- 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 856765] New: glmatrix process does not exit when xdcreensaver stops.
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=856765 https://bugzilla.novell.com/show_bug.cgi?id=856765#c0 Summary: glmatrix process does not exit when xdcreensaver stops. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: carlos.e.r(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Situation: 13.1 system with XFCE desktop, freshly installed with all mandatory updates, nvidia proprietary driver (obviously, because it needs 3D to run this app) installed via rpm. Xscreensaver is configured to run GLmatrix screensaver. When the screensaver triggers, and I use the machine again, I see this in top: top - 11:40:06 up 2 days, 12:52, 10 users, load average: 0.10, 0.13, 0.14 Tasks: 249 total, 2 running, 247 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.5 us, 0.9 sy, 0.6 ni, 97.0 id, 1.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 8193444 total, 3444632 used, 4748812 free, 474056 buffers KiB Swap: 22017008 total, 334780 used, 21682228 free, 1524108 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7613 cer 39 19 128488 37036 22104 S 4.318 0.452 0:32.43 glmatrix 31774 root 20 0 344936 216676 35976 S 1.661 2.645 39:55.93 X 5105 cer 20 0 1598580 249768 42852 S 0.332 3.048 8:29.26 thunderbird-bin A process named 'glmatrix' is still running, using more CPU than any - which is why I noticed. It can not be killed normally, it has to be killed 9. See: cer@Elessar:~> killall glmatrix cer@Elessar:~> killall -9 glmatrix cer@Elessar:~> killall glmatrix cer@Elessar:~> killall glmatrix cer@Elessar:~> killall -9 glmatrix cer@Elessar:~> killall -9 glmatrix glmatrix: no process found cer@Elessar:~> -- 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 6

[Bug 858493] New: mount-by-device ceased to work properly in 13.1
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=858493 https://bugzilla.novell.com/show_bug.cgi?id=858493#c0 Summary: mount-by-device ceased to work properly in 13.1 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: mario.natiello(a)math.lth.se QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 The following fstab entries [CODE] /dev/sdb1 /mount/usbdisk vfat user,rw,noauto 0 0 remuser@IP:. /localuser/target fuse.sshfs users,allow_other,reconnect, follow_symlinks,rw, noauto,_netdev,idmap=user,uid=1000,gid=100, IdentityFile=/localuser/.ssh/id_rsa,ServerAliveInterval=60 0 0 [/CODE] should allow to mount the filesystems just by stating EITHER the device OR the mountpoint as in, e.g., [CODE] > mount /dev/sdb1 > mount /mount/usbdisk > mount /localuser/target [/CODE] All these work ok. However the following one does not work: [CODE] > mount remuser@IP:. mount: remuser@IP:.: No such file or directory > mount --source remuser@IP:. mount: remuser@IP:.: No such file or directory[/CODE] [/CODE] despite the fact that the syntax is supported by the man pages of fstab, mount and sshfs, and despite the fact that it did work in 12.2 and it currently works in other distros (I tried in ubuntu 13.04). Reproducible: Always Steps to Reproduce: 1. Put in fstab a remote device that is mounted by sshfs 2. mount the device by stating "mount device" or "mount --source device" 3. mount fails while "mount mountpoint" does not fail. Actual Results: [/CODE] > mount remuser@IP:. mount: remuser@IP:.: No such file or directory > mount --source remuser@IP:. mount: remuser@IP:.: No such file or directory [/CODE] [/CODE] Expected Results: Remote file system properly mounted -- 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 5

[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 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 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 907387] New: nut systemd service file (nut-driver.service) has wrong ExecStart/Stop entry.
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=907387 Bug ID: 907387 Summary: nut systemd service file (nut-driver.service) has wrong ExecStart/Stop entry. Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ivar_nikolaisen(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: The nut-driver service file (/usr/lib/systemd/system/nut-driver.service) does not work because the service file is incorrect. It currently has the following settings under [Service]: ExecStart=/upsdrvctl start ExecStop=/upsdrvctl stop These are obviously not correct full paths to the upsdrvctl executable. On my machine, I have found the executable located at /usr/lib/ups/driver/upsdrvctl, and nut seems to work correctly if I change to this path (that is, after doing systemctl start nut-server.service, my UPS is identified correctly and I can query it using the upsc utility). Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 18