February 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 864142] New: Console login prompt appears briefly during shutdown of system when using nouveau driver
by bugzilla_noreply＠novell.com 18 Feb '14

18 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=864142 https://bugzilla.novell.com/show_bug.cgi?id=864142#c0 Summary: Console login prompt appears briefly during shutdown of system when using nouveau driver Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rb03884(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 When shutting down my system the console login prompt appears briefly when using the nouveau driver. However, after blacklisting nouveau and setting NO_KMS_IN_INITRD with the /etc/sysconfig/kernel module. The Nvidia driver was then installed causing the login prompt to disappear during shutdown or if restart selected. Reproducible: Always Steps to Reproduce: 1. Start up the default installation with KDE4 with nouveau driver 2. Once at desktop, select Kickoff Geeko -->Leave -->Shut down or Restart 3. Notice the login prompt briefly during shutdown and/or restart Actual Results: Login prompt appears briefly during shutdown/restart while using nouveau driver Expected Results: Login prompt does not appear and is replaced with shutdown graphics while using nouveau driver only. I believe this problem is related to systemd shutdown. Patch required. -- 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 7

[Bug 864126] New: add a new printer window never shows system ppd files.
by bugzilla_noreply＠novell.com 18 Feb '14

18 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=864126 https://bugzilla.novell.com/show_bug.cgi?id=864126#c0 Summary: add a new printer window never shows system ppd files. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: illumilore(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 In system settings> printers> add a new printer, After inputting the url of an lpt printer, when it gets to the pick a driver part, the list of system ppd files is never populated. A small loading icon is shown to the lower left, but it never goes away. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 4

[Bug 864128] New: add a new printer has inconsistent prefill data between lpd and ipp
by bugzilla_noreply＠novell.com 18 Feb '14

18 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=864128 https://bugzilla.novell.com/show_bug.cgi?id=864128#c0 Summary: add a new printer has inconsistent prefill data between lpd and ipp Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: illumilore(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 When going to systemsettings> printers> add a new printer, the window that shows up, when clicking lpd/lpr the address entry box is prefilled with "lpd", while the internet printing protocal entry box is prefilled with "ipp://". Given that lpd requires the same :// otherwise you get an error, it should have the same :// prefill added that ipp has. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 4

[Bug 862961] New: Prompt for encrypted partition password not visible (off screen) when external monitor plugged in
by bugzilla_noreply＠novell.com 18 Feb '14

18 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=862961 https://bugzilla.novell.com/show_bug.cgi?id=862961#c0 Summary: Prompt for encrypted partition password not visible (off screen) when external monitor plugged in Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bdimm(a)hotneuron.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 Booting a laptop with an encrypted partition. When no external monitor is attached, the prompt for the password for the encrypted partition is positioned along the bottom edge of the screen. When an external monitor is attached, the password prompt is either partially or entirely off the bottom of the screen, depending on the monitor. I'm talking here about the graphical password prompt (I don't know if it is part of KDE or something else that starts before KDE), not the text prompt you see if you hit ESC to escape the graphical overlay and see the plain text boot messages. Probably related: The laptop seems to be driving the external monitor at the laptop screen's native resolution rather than at the external monitor's resolution (even when the laptop is in a docking station and the screen is closed [but still seems to be on?]). Maybe the positioning of the password dialog is being computed from the external monitor's native resolution even though that is not the resolution being displayed. Even if this is just a side-effect of some other problem causing the monitor to be driven at the wrong resolution, trying to position the password input along the bottom edge of the screen (rather than the center) seems like a risky and odd choice. Reproducible: Always Steps to Reproduce: 1. Configure laptop to have an encrypted partition. 2. Plug in an external monitor (probably needs to have more vertical pixels than laptop screen). 3. Boot and wait for the password prompt for the encrypted partition. Actual Results: Password prompt is partially or completely off the bottom of the screen, possibly leaving the user completely unaware that there is a prompt and thinking that the system is stuck. Expected Results: Password prompt should be on the screen. -- 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 7

[Bug 845475] New: No systemd unit file fount for nfs-kernel-server
by bugzilla_noreply＠novell.com 18 Feb '14

18 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=845475 https://bugzilla.novell.com/show_bug.cgi?id=845475#c0 Summary: No systemd unit file fount for nfs-kernel-server Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bugs(a)vdm-design.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0 On a System with following patterns installed: x11 kde4 yast2_basis kde4_basis enhanced_base base fonts After installing nfs-kernel-server the systemd nfsserver.service file can not be found. Which should be clear, as the nfs server should be started with fallback to the sysvinit script. test-vm:/etc/sysconfig/network # zypper in nfs-kernel-server Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: nfs-kernel-server 1 new package to install. Overall download size: 112.0 KiB. After the operation, additional 429.7 KiB will be used. Continue? [y/n/?] (y): Retrieving package nfs-kernel-server-1.2.8-4.1.2.i586 (1/1), 112.0 KiB (429.7 KiB unpacked) Retrieving: nfs-kernel-server-1.2.8-4.1.2.i586.rpm .......................................................................................................................................................................................................[done (312.7 KiB/s)] (1/1) Installing: nfs-kernel-server-1.2.8-4.1.2 ........................................................................................................................................................................................................................[done] test-vm:/etc/sysconfig/network # systemctl start nfsserver.service Failed to issue method call: Unit nfsserver.service failed to load: No such file or directory. See system logs and 'systemctl status nfsserver.service' for details. test-vm:/etc/sysconfig/network # systemctl status nfsserver.service nfsserver.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) test-vm:/etc/sysconfig/network # /etc/init.d/nfsserver status Checking for kernel based NFS server: idmapd unused mountd unused statd unused nfsd unused nfsserver.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) test-vm:/etc/sysconfig/network # /etc/init.d/nfsserver start redirecting to systemctl start nfsserver Failed to issue method call: Unit nfsserver.service failed to load: No such file or directory. See system logs and 'systemctl status nfsserver.service' for details. Reproducible: Always Steps to Reproduce: 1. Install nfs-kernel-server 2. Start nfsserver with rcnfsserver start, /etc/init.d/nfsserver start or systemctl start nfsserver.service Actual Results: /etc/init.d/nfsserver start redirecting to systemctl start nfsserver Failed to issue method call: Unit nfsserver.service failed to load: No such file or directory. See system logs and 'systemctl status nfsserver.service' for details. Expected Results: The NFS server should start The installation was done from the openSUSE_13.1 online repository 11. Oct 2013 08:00 UTC -- 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 12

[Bug 849387] New: NFS file systems unmounted 15 minutes after reboot
by bugzilla_noreply＠novell.com 18 Feb '14

18 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=849387 https://bugzilla.novell.com/show_bug.cgi?id=849387#c0 Summary: NFS file systems unmounted 15 minutes after reboot Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: R.Vickers(a)cs.rhul.ac.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 We have a server which is both an NFS server and NFS client. After booting all the NFS file systems in fstab successfully mount, but 15 minutes later an sm-notify failure causes them to be unmounted again. This has happened after at least 2 reboots. So there are 2 mysteries here: (1) Why does sm-notify fail? (2) Why does this failure cause systemd to tear down the NFS client services? The key messages in the log are 2013-11-07T08:31:59.117550+00:00 teaching sm-notify[1953]: Version 1.2.7 starting 2013-11-07T08:31:59.284828+00:00 teaching sm-notify[1953]: Backgrounding to notify hosts... 2013-11-07T08:31:59.296556+00:00 teaching nfs[1899]: Starting NFS client services: sm-notify idmapd..done 2013-11-07T08:32:04.435916+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec572] RPC status 1 2013-11-07T08:32:04.528118+00:00 teaching sm-notify[2022]: Version 1.2.7 starting 2013-11-07T08:32:04.528564+00:00 teaching sm-notify[2022]: Already notifying clients; Exiting! 2013-11-07T08:32:04.529097+00:00 teaching nfsserver[1900]: Starting kernel based NFS server: idmapd mountd statd nfsd sm-notify..done 2013-11-07T08:32:11.616881+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec573] RPC status 1 2013-11-07T08:32:15.621965+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec574] RPC status 1 2013-11-07T08:32:23.632100+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec575] RPC status 1 2013-11-07T08:32:39.644970+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec576] RPC status 1 2013-11-07T08:33:11.658055+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec577] RPC status 1 2013-11-07T08:34:15.724413+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec578] RPC status 1 2013-11-07T08:36:15.826645+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec579] RPC status 1 2013-11-07T08:38:15.919664+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec57a] RPC status 1 2013-11-07T08:40:15.960524+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec57b] RPC status 1 2013-11-07T08:42:16.062979+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec57c] RPC status 1 2013-11-07T08:44:16.165623+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec57d] RPC status 1 2013-11-07T08:46:16.253668+00:00 teaching sm-notify[1960]: nsm_parse_reply: [0x527ec57e] RPC status 1 2013-11-07T08:48:16.353764+00:00 teaching sm-notify[1960]: Unable to notify mailhost.cs.rhul.ac.uk, giving up 2013-11-07T08:48:16.465687+00:00 teaching nfs[7573]: Shutting down NFS client services:umount.nfs4: /rmt/csfiles/pgrads: device is busy 2013-11-07T08:48:16.497619+00:00 teaching nfs[7573]: umount.nfs4: /rmt/csfiles/staff: device is busy 2013-11-07T08:48:16.567285+00:00 teaching nfs[7573]: umount: /var/lib/nfs/rpc_pipefs: target is busy. 2013-11-07T08:48:16.568078+00:00 teaching nfs[7573]: (In some cases useful info about processes that use 2013-11-07T08:48:16.568571+00:00 teaching nfs[7573]: the device is found by lsof(8) or fuser(1)) 2013-11-07T08:48:16.569186+00:00 teaching nfs[7573]: ..failed 2013-11-07T08:48:16.569418+00:00 teaching systemd[1]: nfs.service: control process exited, code=exited status=1 2013-11-07T08:48:16.581167+00:00 teaching systemd[1]: Unit nfs.service entered failed state There is only one host which sm-notify is failing to contact. It is an NFS client and the corresponding file in /var/lib/nfs is -rw------- 1 statd nogroup 94 Jul 31 13:20 /var/lib/nfs/sm.bak/mailhost.cs.rhul.ac.uk and its contents are 0100007f 000186b5 00000003 00000010 cbb2ce7f5dc6110000c869900388ffff 134.219.205.131 teaching If I run sm-notify by hand I get: teaching# sm-notify -df -m 1 sm-notify: Version 1.2.7 starting sm-notify: Added host mailhost.cs.rhul.ac.uk to notify list sm-notify: Effective UID, GID: 103, 65534 sm-notify: Sending PMAP_GETPORT for 100024, 1, udp sm-notify: Added host mailhost.cs.rhul.ac.uk to notify list sm-notify: Host mailhost.cs.rhul.ac.uk due in 2 seconds sm-notify: Received packet... sm-notify: nsm_parse_reply: [0x527306d7] RPC status 1 sm-notify: Host mailhost.cs.rhul.ac.uk due in 2 seconds sm-notify: Sending PMAP_GETPORT for 100024, 1, udp sm-notify: Added host mailhost.cs.rhul.ac.uk to notify list sm-notify: Host mailhost.cs.rhul.ac.uk due in 4 seconds sm-notify: Received packet... sm-notify: nsm_parse_reply: [0x527306d8] RPC status 1 sm-notify: Host mailhost.cs.rhul.ac.uk due in 4 seconds sm-notify: Sending PMAP_GETPORT for 100024, 1, udp sm-notify: Added host mailhost.cs.rhul.ac.uk to notify list sm-notify: Host mailhost.cs.rhul.ac.uk due in 8 seconds sm-notify: Received packet... sm-notify: nsm_parse_reply: [0x527306d9] RPC status 1 sm-notify: Host mailhost.cs.rhul.ac.uk due in 8 seconds sm-notify: Sending PMAP_GETPORT for 100024, 1, udp sm-notify: Added host mailhost.cs.rhul.ac.uk to notify list sm-notify: Host mailhost.cs.rhul.ac.uk due in 16 seconds sm-notify: Received packet... sm-notify: nsm_parse_reply: [0x527306da] RPC status 1 sm-notify: Host mailhost.cs.rhul.ac.uk due in 16 seconds sm-notify: Sending PMAP_GETPORT for 100024, 1, udp sm-notify: Added host mailhost.cs.rhul.ac.uk to notify list sm-notify: Host mailhost.cs.rhul.ac.uk due in 32 seconds sm-notify: Received packet... sm-notify: nsm_parse_reply: [0x527306db] RPC status 1 sm-notify: Host mailhost.cs.rhul.ac.uk due in 32 seconds sm-notify: Unable to notify mailhost.cs.rhul.ac.uk, giving up Reproducible: Always Steps to Reproduce: It is reproducable on my server, but I don't know how to reproduce it on other machines. Both server and client are running opensuse 12.3 -- 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 10

[Bug 849476] New: /etc/init.d/nfsserver fails to start because -nfs-version needs 2 hyphens
by bugzilla_noreply＠novell.com 18 Feb '14

18 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=849476 https://bugzilla.novell.com/show_bug.cgi?id=849476#c0 Summary: /etc/init.d/nfsserver fails to start because -nfs-version needs 2 hyphens Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jimc(a)math.ucla.edu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Package: nfs-kernel-server-1.2.8-4.2.1.x86_64 When you do /etc/init.d/nfsserver start, rpc.mountd exits printing its usage message. The reason is that VERSION_PARAMS is set to -nfs-version 4 where it should be --nfs-version 4 (2 hyphens). Patch coming. Also, if NFS4_SERVER_MINOR_VERSION != '0', i.e. if it is unset (as it was in my case due to copying /etc/sysconfig/nfs from v12.3), the option -nfs-version 4. (four dot) will be appended. rpc.mountd does not care, but rpc.nfsd chokes on it, "unsupported minor version". May I suggest a case statement such as: case "$NFS4_SERVER_MINOR_VERSION" in [1-9]* ) (append the minor version option) esac -- 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 11

[Bug 859221] New: nfs init script prints error message
by bugzilla_noreply＠novell.com 18 Feb '14

18 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=859221 https://bugzilla.novell.com/show_bug.cgi?id=859221#c0 Summary: nfs init script prints error message Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: okir(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- On openSUSE 13.1, if I do this # /etc/init.d/nfs force-start Starting NFS client services: sm-notify gssd/etc/init.d/nfs: line 225: /run/nfs/nfs-rpc.gssd: No such file or directory idmapd..done This is because the script fails to create /run/fs prior to starting gssd. -- 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 849523] New: mdadmd running superfluously
by bugzilla_noreply＠novell.com 18 Feb '14

18 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=849523 https://bugzilla.novell.com/show_bug.cgi?id=849523#c0 Summary: mdadmd running superfluously Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 On a system newly upgraded to 13.1rc2, I noticed mdadmd was running despite /etc/mdadm.conf being non-existent and no RAID arrays being present. It seems pretty odd for it to be started to monitor nothing. When I asked on opensuse-factory, this was part of the answer: > Package mdadmd is installed as a dependency of package libstorage4, > which is dependency by autoyast and yast-backup I don't know if this is a YaST issue, but I'll start with you guys. Reproducible: Always -- 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 12

[Bug 864114] New: kde does not autostart script
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=864114 https://bugzilla.novell.com/show_bug.cgi?id=864114#c0 Summary: kde does not autostart script Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: illumilore(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 I have a test script that is "touch /home/user/1", and I have set it to autostart using systemsettings> startup and shutdown. It also shows up in ~/.kde4/Autostart/, however, it never actually runs at system startup or after the user is logged in. The script itself works, but kde is not actually starting it when it should. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 3