February 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 860574] New: Some loginctl actions don't work
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=860574 https://bugzilla.novell.com/show_bug.cgi?id=860574#c0 Summary: Some loginctl actions don't work Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i686 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: acc-id(a)yandex.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:26.0) Gecko/20100101 Firefox/26.0 same as: "Robert Marcano 2013-12-29 17:01:38 EST "loginctl kill-session" and "loginctl kill-user" commands always returns with an error message: Failed to issue method call: Input/output error" from https://bugzilla.redhat.com/show_bug.cgi?id=1047186 Reproducible: Always Steps to Reproduce: loginctl kill-user UserName Actual Results: Failed to issue method call: Input/output error Expected Results: systemd kills all UserName processes -- 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 8

[Bug 859365] New: systemd-analyze set-log-level: free(): invalid pointer
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=859365 https://bugzilla.novell.com/show_bug.cgi?id=859365#c0 Summary: systemd-analyze set-log-level: free(): invalid pointer Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: fcrozat(a)suse.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- # systemd-analyze set-log-level This command expects one argument only. *** Error in `systemd-analyze': free(): invalid pointer: 0x00007f195454b6e0 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x7410f)[0x7f1953da810f] /lib64/libc.so.6(+0x7996e)[0x7f1953dad96e] /lib64/libc.so.6(+0x7a647)[0x7f1953dae647] /lib64/libdbus-1.so.3(dbus_error_free+0x31)[0x7f19540f55d1] systemd-analyze[0x402b72] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f1953d55be5] systemd-analyze[0x40313d] ======= Memory map: ======== [...] Needless to say that the expected result is just the message "This command expects one argument only." without the "free(): invalid pointer" part ;-) My system is Factory, last updated 2013-11-29 and systemd-208-6.1.x86_64. I can also reproduce this bug on 13.1. -- 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 8

[Bug 859072] New: systemd-analyze, broken TAB completion
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=859072 https://bugzilla.novell.com/show_bug.cgi?id=859072#c0 Summary: systemd-analyze, broken TAB completion Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sweet_f_a(a)gmx.de 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 $ systemd-analyze <TAB> bash: _init_completion: command not found If you have command-not-found installed then it will look even more silly ... There are even more completions broken that way. openSUSE default bash config gets more and more broken. How can we get rid of all those completion scripts? Please don't install them per default or is there an easy way to disable them? 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 23

[Bug 856858] New: systemd-analyze command completion script broken
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=856858 https://bugzilla.novell.com/show_bug.cgi?id=856858#c0 Summary: systemd-analyze command completion script broken Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Yarny(a)public-files.de 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 The command completion mechanism for systemd-analyze is apparently broken: It yields an error message instead of suggested commands. Reproducible: Always Steps to Reproduce: 1. type "systemd-analyze " at command prompt 2. press tab key Actual Results: > linux-2zh8:~ # systemd-analyze If '_init_completion' is not a typo you can use command-not-found to lookup the package that contains it, like this: > cnf _init_completion -- 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 13

[Bug 856392] New: systemd - point grub at the right entry before hibernating
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=856392 https://bugzilla.novell.com/show_bug.cgi?id=856392#c0 Summary: systemd - point grub at the right entry before hibernating Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: All OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: systemd-maintainers(a)suse.de ReportedBy: vdziewiecki(a)suse.com QAContact: qa-bugs(a)suse.de CC: fcrozat(a)suse.com Found By: Development Blocker: --- Created an attachment (id=572623) --> (http://bugzilla.novell.com/attachment.cgi?id=572623) grub.sh, should go to /usr/lib/systemd/system-sleep Hi, I believe this functionality has to be added before switching from pm-utils to systemd suspend/hibernate. When a computer is turned on after hibernating, grub must chose the right entry automatically, and not let the user chose. If the user would choose to boot into another OS, bad things could happen. To fix this, just put the attached script to /usr/lib/systemd/system-sleep. Thanks, Wojtek -- 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 21

[Bug 856389] New: systemd - stop hibernation when there is no resume parameter on kernel cmdline
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=856389 https://bugzilla.novell.com/show_bug.cgi?id=856389#c0 Summary: systemd - stop hibernation when there is no resume parameter on kernel cmdline Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: All OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: systemd-maintainers(a)suse.de ReportedBy: vdziewiecki(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- Created an attachment (id=572622) --> (http://bugzilla.novell.com/attachment.cgi?id=572622) Proposed patch. Hi, I believe this functionality has to be added before switching from pm-utils to systemd suspend/hibernate. If there's no resume parameter on kernel command line, then there is no point in hibernating since the system won't resume. I propose this patch. Please check if it's ok, I wrote it myself and I'm not a particularly experienced programmer. Thanks. -- 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 853293] New: boot hang after 12.3 -> 13.1 upgrade adds libpcre dependency to udevadm
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=853293 https://bugzilla.novell.com/show_bug.cgi?id=853293#c0 Summary: boot hang after 12.3 -> 13.1 upgrade adds libpcre dependency to udevadm Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ar16(a)imapmail.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 in opensuse 12.3 ldd /sbin/udevadm linux-vdso.so.1 (0x00007fffe3d44000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fa23e9a2000) libblkid.so.1 => /usr/lib64/libblkid.so.1 (0x00007fa23e77a000) libkmod.so.2 => /lib64/libkmod.so.2 (0x00007fa23e565000) libacl.so.1 => /lib64/libacl.so.1 (0x00007fa23e35c000) librt.so.1 => /lib64/librt.so.1 (0x00007fa23e154000) libc.so.6 => /lib64/libc.so.6 (0x00007fa23dda6000) /lib64/ld-linux-x86-64.so.2 (0x00007fa23ebc2000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fa23dba2000) libuuid.so.1 => /usr/lib64/libuuid.so.1 (0x00007fa23d99d000) liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007fa23d777000) libz.so.1 => /lib64/libz.so.1 (0x00007fa23d561000) libattr.so.1 => /lib64/libattr.so.1 (0x00007fa23d35c000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa23d140000) with my usual (for a long time) ld.so.conf, cat /etc/ld.so.conf /usr/local/lib64 /usr/local/lib include /etc/ld.so.conf.d/*.conf # /lib64, /lib, /usr/lib64 and /usr/lib gets added # automatically by ldconfig after parsing this file. # So, they do not need to be listed. and a locally installed pcre I use for dev in, ls -al /usr/local/lib64/*pcre* -rwxr-xr-x 1 root root 965 Nov 27 14:10 /usr/local/lib64/libpcrecpp.la* lrwxrwxrwx 1 root root 19 Nov 27 14:10 /usr/local/lib64/libpcrecpp.so -> libpcrecpp.so.0.0.0* lrwxrwxrwx 1 root root 19 Nov 27 14:10 /usr/local/lib64/libpcrecpp.so.0 -> libpcrecpp.so.0.0.0* -rwxr-xr-x 1 root root 47K Nov 27 14:10 /usr/local/lib64/libpcrecpp.so.0.0.0* -rwxr-xr-x 1 root root 919 Nov 27 14:10 /usr/local/lib64/libpcre.la* -rwxr-xr-x 1 root root 977 Nov 27 14:10 /usr/local/lib64/libpcreposix.la* lrwxrwxrwx 1 root root 21 Nov 27 14:10 /usr/local/lib64/libpcreposix.so -> libpcreposix.so.0.0.2* lrwxrwxrwx 1 root root 21 Nov 27 14:10 /usr/local/lib64/libpcreposix.so.0 -> libpcreposix.so.0.0.2* -rwxr-xr-x 1 root root 14K Nov 27 14:10 /usr/local/lib64/libpcreposix.so.0.0.2* lrwxrwxrwx 1 root root 16 Nov 27 14:10 /usr/local/lib64/libpcre.so -> libpcre.so.1.2.2* lrwxrwxrwx 1 root root 16 Nov 27 14:10 /usr/local/lib64/libpcre.so.1 -> libpcre.so.1.2.2* -rwxr-xr-x 1 root root 425K Nov 27 14:10 /usr/local/lib64/libpcre.so.1.2.2* after rm -f /etc/ld.so.cache ldconfig mkinitrd 12.3 boots OK. but, after upgrade to 13.1, the system hangs on boot, streaming (to serial console) messages about a missing "libpcre.so.1" apparently, in opensuse 13.1, a dependency on libpcre.so.1 has been added if I boot from LiveKDE, chroot to 13.1, and vi /etc/ld.so.conf + /lib64 /usr/local/lib64 /usr/local/lib include /etc/ld.so.conf.d/*.conf # /lib64, /lib, /usr/lib64 and /usr/lib gets added # automatically by ldconfig after parsing this file. # So, they do not need to be listed. ln -sf /usr/lib64/*pcre* /lib64 rm -f /etc/ld.so.cache ldconfig mkinitrd then reboot ... boot to 13.1 is OK again. noting on the booted 13.1 system, ldd /sbin/udevadm linux-vdso.so.1 (0x00007fff77ffe000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fe54b5d6000) librt.so.1 => /lib64/librt.so.1 (0x00007fe54b3ce000) libblkid.so.1 => /usr/lib64/libblkid.so.1 (0x00007fe54b193000) libkmod.so.2 => /lib64/libkmod.so.2 (0x00007fe54af7d000) libacl.so.1 => /lib64/libacl.so.1 (0x00007fe54ad74000) libc.so.6 => /lib64/libc.so.6 (0x00007fe54a9c5000) /lib64/ld-linux-x86-64.so.2 (0x00007fe54b7fa000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fe54a7c1000) !!! libpcre.so.1 => /lib64/libpcre.so.1 (0x00007fe54a55b000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fe54a33d000) libuuid.so.1 => /usr/lib64/libuuid.so.1 (0x00007fe54a138000) liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007fe549f12000) libz.so.1 => /lib64/libz.so.1 (0x00007fe549cfc000) libattr.so.1 => /lib64/libattr.so.1 (0x00007fe549af7000) There's clearly a conflict, or missing dep, re: pcre. The workaround I've used above is likely not the best approach. Not sure what is. 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 29

[Bug 852232] New: some non fatal failure during boot results in an endless loop due to defect emergency mode
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=852232 https://bugzilla.novell.com/show_bug.cgi?id=852232#c0 Summary: some non fatal failure during boot results in an endless loop due to defect emergency mode Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hpj(a)urpla.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=569041) --> (http://bugzilla.novell.com/attachment.cgi?id=569041) screenshot: error loop User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 On a fresh installation, yast failed to create a fstab (#852027). While creating one myself, I also added some nfs mounts. For some reason, these mounts don't work correctly (due to a missing rpcbind, nfs service tries to access /etc/init.d/rpcbind, but that isn't available, hence it fails). Now the whole system is installed in /, so emergency should work, but it spits out some errors in an endless loop. Scrrenshot attached. Reproducible: Always Steps to Reproduce: 1. add some mount target, that does not exist or results in some other failure 2. reboot Actual Results: results in error loop Expected Results: enter emergency mode -- 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 25

[Bug 852021] New: rsyslog.service cancels emergency.target making it impossible to enter emergency shell
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=852021 https://bugzilla.novell.com/show_bug.cgi?id=852021#c0 Summary: rsyslog.service cancels emergency.target making it impossible to enter emergency shell Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: arvidjaar(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=568839) --> (http://bugzilla.novell.com/attachment.cgi?id=568839) systemd debug log entering emeregency shell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 As was found in bnc#851993, if rsyslog service is active it may be impossible to enter emergency shell. The reason is, rsyslog.service requires basic.target which requires sysinit.target which conflicts with emergency.{target,service}. So if syslog.service is triggered by connection to syslog.socket it tries to start basic.target which cancels pending emergency shell. Nov 23 23:20:05 server systemd[1]: Started Emergency Shell. Nov 23 23:20:05 server systemd[1]: Starting Emergency Mode. Nov 23 23:20:05 server systemd[1]: emergency.target changed dead -> active Nov 23 23:20:05 server systemd[1]: Job emergency.target/start finished, result=done Nov 23 23:20:05 server systemd[1]: Reached target Emergency Mode. .. Nov 23 23:20:05 server systemd[1]: Incoming traffic on syslog.socket Nov 23 23:20:05 server systemd[1]: Trying to enqueue job rsyslog.service/start/replace Nov 23 23:20:05 server systemd[1]: Installed new job rsyslog.service/start as 541 Nov 23 23:20:05 server systemd[1]: Installed new job basic.target/start as 549 Nov 23 23:20:05 server systemd[1]: Installed new job sysinit.target/start as 550 .. Nov 23 23:20:05 server systemd[1]: Stopping Emergency Mode. Nov 23 23:20:05 server systemd[1]: emergency.target changed active -> dead Nov 23 23:20:05 server systemd[1]: Job emergency.target/stop finished, result=done Nov 23 23:20:05 server systemd[1]: Stopped target Emergency Mode. Nov 23 23:20:05 server systemd[1]: Stopping Emergency Shell... Full log in attachment. 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 23

[Bug 852015] New: Pulseaudio fails to start after running yast or other xdg-su programs
by bugzilla_noreply＠novell.com 03 Feb '16

03 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=852015 https://bugzilla.novell.com/show_bug.cgi?id=852015#c0 Summary: Pulseaudio fails to start after running yast or other xdg-su programs Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Sound AssignedTo: tiwai(a)suse.com ReportedBy: johan(a)illwinter.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 running some programs e.g. yast - through xdg-su changes the owner of /run/user/1000/pulse to root. This causes pulseaudio to fail with the message: "Failed to create secure directory (/run/user/1000/pulse): Permission denied" Application that use pulseaudio do not work when this has happened and output the message above. This occurs in the xfce environment after installing pulseaudio, no settings changed. This is the same problem as Bug 829076 in opensuse 12.3. Reproducible: Always Steps to Reproduce: 1. install pulseaudio in the xfce DE 2. run yast 3. try to run pulseaudio volume control Actual Results: Connection to pulseaudio failed message displayed Expected Results: Application working -- 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 37