February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 908798] New: systemd re-adds itself to pam-config with every update
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=908798 Bug ID: 908798 Summary: systemd re-adds itself to pam-config with every update Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I got rid of the useless pam_systemd by running "pam-config --delete --systemd". (See http://seifesrants.blogspot.de/2014/11/pamsystemd-on-server-wtf.html) However, today I found that it magically reappeared and is spamming my system logs for no good reason. Checking, I noticed that systemd was updated lately. Looking into the postinstall stuff, I found the following "gem": postinstall scriptlet (using /bin/sh): /usr/sbin/pam-config -a --systemd || : /sbin/ldconfig [...] This unconditional adding is not really a good idea IMNSHO, if it is done at all, it should only be done at initial install of systemd. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 886065] multiseat: not generate the seat1
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=886065 http://bugzilla.opensuse.org/show_bug.cgi?id=886065#c5 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |fbui(a)suse.com Resolution|--- |WONTFIX --- Comment #5 from Franck Bui <fbui(a)suse.com> --- 13.1 has reached EOL and is not supported anymore. Feel free to open a new bug report if this still can be reproduced on a newer/supported distro such as Leap or Tumbleweed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 879521] Mount timeout hangs boot process
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=879521 http://bugzilla.opensuse.org/show_bug.cgi?id=879521#c4 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |fbui(a)suse.com Resolution|--- |WONTFIX --- Comment #4 from Franck Bui <fbui(a)suse.com> --- 13.1 has reached EOL and is not supported anymore. Feel free to open a new bug report if this still can be reproduced on a newer/supported distro such as Leap or Tumbleweed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 858429] do not restart libvirt-guests during libvirt updates!
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=858429 http://bugzilla.opensuse.org/show_bug.cgi?id=858429#c16 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |fbui(a)suse.com Resolution|--- |WONTFIX --- Comment #16 from Franck Bui <fbui(a)suse.com> --- 13.1 has reached EOL and is not supported anymore. Feel free to open a new bug report if this still can be reproduced on a newer/supported distro such as Leap or Tumbleweed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 845649] 70-persistent-net.rules is empty
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=845649 http://bugzilla.opensuse.org/show_bug.cgi?id=845649#c16 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |fbui(a)suse.com Resolution|--- |WONTFIX --- Comment #16 from Franck Bui <fbui(a)suse.com> --- 13.1 has reached EOL and is not supported anymore. Feel free to open a new bug report if this still can be reproduced on a newer/supported distro such as Leap or Tumbleweed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 877634] systemd rescue mode doesn't work
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=877634 http://bugzilla.opensuse.org/show_bug.cgi?id=877634#c3 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fbui(a)suse.com Resolution|--- |WONTFIX --- Comment #3 from Franck Bui <fbui(a)suse.com> --- 13.1 has reached EOL and is not supported anymore. Feel free to open a new bug report if this still can be reproduced on a newer/supported distro such as Leap or Tumbleweed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 972015] New: change systemd-journald MaxLevelSyslog default to stop excessive logging
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=972015 Bug ID: 972015 Summary: change systemd-journald MaxLevelSyslog default to stop excessive logging Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: erbenton(a)comcast.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- By default, journald logs debug level info in /var/log/messages. This results in excessive logging which in the long run is harmful to SSD's The default logging level for journald needs to be MaxLevelSyslog=warning in /etc/systemd/journald.conf with the current setting my /var/log messages fills up with useless drivel like this once each minute 2016-03-21T10:41:01.848060-07:00 xxxx systemd[15769]: Starting Paths. 2016-03-21T10:41:01.848883-07:00 xxxx systemd[15769]: Reached target Paths. 2016-03-21T10:41:01.849128-07:00 xxxx systemd[15769]: Starting Timers. 2016-03-21T10:41:01.849843-07:00 xxxx systemd[15769]: Reached target Timers. 2016-03-21T10:41:01.850085-07:00 xxxx systemd[15769]: Starting Sockets. 2016-03-21T10:41:01.850800-07:00 xxxx systemd[15769]: Reached target Sockets. 2016-03-21T10:41:01.851044-07:00 xxxx systemd[15769]: Starting Basic System. 2016-03-21T10:41:01.851770-07:00 xxxx systemd[15769]: Reached target Basic System. 2016-03-21T10:41:01.852085-07:00 xxxx systemd[15769]: Starting Default. 2016-03-21T10:41:01.852853-07:00 xxxx systemd[15769]: Reached target Default. 2016-03-21T10:41:01.853076-07:00 xxxx systemd[15769]: Startup finished in 85ms. 2016-03-21T10:41:01.902440-07:00 xxxx systemd[15769]: Stopping Default. 2016-03-21T10:41:01.903696-07:00 xxxx systemd[15769]: Stopped target Default. 2016-03-21T10:41:01.904160-07:00 xxxx systemd[15769]: Stopping Basic System. 2016-03-21T10:41:01.905147-07:00 xxxx systemd[15769]: Stopped target Basic System. 2016-03-21T10:41:01.905372-07:00 xxxx systemd[15769]: Stopping Paths. 2016-03-21T10:41:01.905985-07:00 xxxx systemd[15769]: Stopped target Paths. 2016-03-21T10:41:01.906201-07:00 xxxx systemd[15769]: Stopping Timers. 2016-03-21T10:41:01.978831-07:00 xxxx systemd[15769]: Stopped target Timers. 2016-03-21T10:41:01.979434-07:00 xxxx systemd[15769]: Stopping Sockets. 2016-03-21T10:41:01.980530-07:00 xxxx systemd[15769]: Stopped target Sockets. 2016-03-21T10:41:01.981060-07:00 xxxx systemd[15769]: Starting Shutdown. 2016-03-21T10:41:01.982096-07:00 xxxx systemd[15769]: Reached target Shutdown. 2016-03-21T10:41:01.982430-07:00 xxxx systemd[15769]: Starting Exit the Session... -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 965492] New: oS 13.1: systemd in patch 2016-137 booting directly into maintenance mode
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=965492 Bug ID: 965492 Summary: oS 13.1: systemd in patch 2016-137 booting directly into maintenance mode Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pi.ro(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 664678 --> http://bugzilla.opensuse.org/attachment.cgi?id=664678&action=edit 'journalctl -xb' Output in Maintenance Mode. openSuse 13.1 on Thinkpad: /home with own encrypted /dev/sda7 (/tmp and /var bound to /home/tmp and /home/var) After applying recommended update 2016-137 for systemd (208-35.1 to 210-40.1) next reboot directly went into maintenance mode without asking for home-password (or any pause). Manual 'cryptsetup luksOpen /dev/sda7 cr_home' was possible, /home then automatically mounted. As dev-mapper-cr_home.device timed out (?), I set a keyfile for /dev/sda7 and changed crypttab accordingly. System booted still into maintenance mode, this time with /home mounted properly. 'journalctl -xb' output attached. 'systemctl isolate graphical.target' was possible, so I changed systemd & systemd-sysvinit from 210-40.1 back to 208-35-1 in yast: booted without any flaw like before the update. libgudev-1_0-0, libudev1 and udev from patch 2016-137 could stay at 210-40.1 without any harm. May be similar to Bug 960258. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 924488] [evergreen 13.1] fstab entry prevents booting no emergency shell
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=924488 http://bugzilla.opensuse.org/show_bug.cgi?id=924488#c23 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fbui(a)suse.com Resolution|--- |WONTFIX --- Comment #23 from Franck Bui <fbui(a)suse.com> --- 13.1 has reached EOL and is not supported anymore. Feel free to open a new bug report if this still can be reproduced on a newer/supported distro such as Leap or Tumbleweed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 908567] New: init 3, kdm and X does not stop
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=908567 Bug ID: 908567 Summary: init 3, kdm and X does not stop Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sweet_f_a(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Somehow my X was chrashed (running at 100% CPU). That's why I issued "init 3". Firstly I noticed that "init 3" took about 2 minutes to finish, which I find odd. After runlevel change X and kdm is still running. Another try gives me $ rckdm stop redirecting to systemctl stop rcxdm.service Failed to issue method call: Unit rcxdm.service not loaded. BTW what is the right systemctl command to stop kdm? Don't see any rcxdm.service... This is the log of "init 3" 2014-12-05T12:35:30.309597+01:00 bart systemd[1]: Stopping Daemon for power management... 2014-12-05T12:35:30.310007+01:00 bart systemd[1]: Stopping Disk Manager... 2014-12-05T12:35:30.310316+01:00 bart systemd[1]: Stopping Authorization Manager... 2014-12-05T12:35:30.310604+01:00 bart systemd[1]: Stopping User Manager for 1001... 2014-12-05T12:35:30.310891+01:00 bart systemd[1]: Stopping Execution Queue Daemon... 2014-12-05T12:35:30.311222+01:00 bart systemd[1]: Stopping User Manager for 1102... 2014-12-05T12:35:30.311514+01:00 bart systemd[1]: Stopping user-1000.slice. 2014-12-05T12:35:30.311800+01:00 bart systemd[1]: Removed slice user-1000.slice. 2014-12-05T12:35:30.314391+01:00 bart systemd[1]: Stopping user-1006.slice. 2014-12-05T12:35:30.314872+01:00 bart systemd[1]: Removed slice user-1006.slice. 2014-12-05T12:35:30.315258+01:00 bart systemd[1]: Stopping user-0.slice. 2014-12-05T12:35:30.315648+01:00 bart systemd[1]: Removed slice user-0.slice. 2014-12-05T12:35:30.315993+01:00 bart systemd[1]: Stopping LVM2 metadata daemon... 2014-12-05T12:35:30.316437+01:00 bart systemd[1]: Stopping Stop Read-Ahead Data Collection 10s After Completed Startup. 2014-12-05T12:35:30.316795+01:00 bart systemd[1]: Stopped Stop Read-Ahead Data Collection 10s After Completed Startup. 2014-12-05T12:35:30.317139+01:00 bart systemd[1]: Stopping Cleanup of Temporary Directories... 2014-12-05T12:35:30.317513+01:00 bart systemd[1]: Stopping Graphical Interface. 2014-12-05T12:35:30.317850+01:00 bart systemd[1]: Stopped target Graphical Interface. 2014-12-05T12:35:30.318206+01:00 bart systemd[1]: Stopping LSB: X Display Manager... 2014-12-05T12:35:30.527111+01:00 bart systemd[1]: Started Purge old kernels. 2014-12-05T12:35:30.527509+01:00 bart systemd[1]: Started Manage Sound Card State (restore and store). 2014-12-05T12:35:30.527847+01:00 bart systemd[1]: Starting Restore Sound Card State... 2014-12-05T12:35:30.610220+01:00 bart systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... 2014-12-05T12:35:30.610647+01:00 bart systemd[1]: Mounted Configuration File System. 2014-12-05T12:35:30.610954+01:00 bart systemd[1]: Starting Show Plymouth Boot Screen... 2014-12-05T12:35:30.611266+01:00 bart systemd[1]: Mounted FUSE Control File System. 2014-12-05T12:35:30.611607+01:00 bart systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... 2014-12-05T12:35:31.879886+01:00 bart systemd[19793]: Stopping Default. 2014-12-05T12:35:32.124898+01:00 bart systemd[19793]: Stopped target Default. 2014-12-05T12:35:32.125265+01:00 bart systemd[19793]: Starting Shutdown. 2014-12-05T12:35:32.125617+01:00 bart systemd[19793]: Reached target Shutdown. 2014-12-05T12:35:32.125951+01:00 bart systemd[19793]: Starting Exit the Session... 2014-12-05T12:35:32.126294+01:00 bart systemd[1]: Stopped LVM2 metadata daemon. 2014-12-05T12:35:32.126618+01:00 bart systemd[1]: Stopped Execution Queue Daemon. 2014-12-05T12:35:32.126940+01:00 bart systemd[1]: Stopped Authorization Manager. 2014-12-05T12:35:32.129139+01:00 bart systemd[1]: Stopped Disk Manager. 2014-12-05T12:35:32.129564+01:00 bart systemd[1]: Stopped Daemon for power management. 2014-12-05T12:35:32.129951+01:00 bart systemd[1]: Started Tell Plymouth To Write Out Runtime Data. 2014-12-05T12:35:32.130346+01:00 bart systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. 2014-12-05T12:35:32.697776+01:00 bart systemd[19575]: Stopping Default. 2014-12-05T12:35:32.698270+01:00 bart systemd[19575]: Stopped target Default. 2014-12-05T12:35:32.717529+01:00 bart systemd[19575]: Starting Shutdown. 2014-12-05T12:35:32.717997+01:00 bart systemd[19575]: Reached target Shutdown. 2014-12-05T12:35:32.718387+01:00 bart systemd[19575]: Starting Exit the Session... 2014-12-05T12:35:35.062984+01:00 bart systemd[1]: Stopped User Manager for 1001. 2014-12-05T12:35:35.063411+01:00 bart systemd[1]: Stopping user-1001.slice. 2014-12-05T12:35:35.063717+01:00 bart systemd[1]: Removed slice user-1001.slice. 2014-12-05T12:35:35.734627+01:00 bart systemd[1]: Stopped User Manager for 1102. 2014-12-05T12:35:35.735046+01:00 bart systemd[1]: Stopping user-1102.slice. 2014-12-05T12:35:35.735400+01:00 bart systemd[1]: Removed slice user-1102.slice. 2014-12-05T12:35:43.478476+01:00 bart kdm: :0[17392]: pam_unix(xdm:session): session closed for user wiesing 2014-12-05T12:35:47.420488+01:00 bart xdm[21427]: Shutting down service kdm..done 2014-12-05T12:35:47.422104+01:00 bart systemd[1]: Stopped LSB: X Display Manager. 2014-12-05T12:36:02.082804+01:00 bart /usr/sbin/cron[24007]: pam_unix(crond:session): session opened for user freundt by (uid=0) 2014-12-05T12:36:06.015422+01:00 bart systemd[1]: Stopped Cleanup of Temporary Directories. 2014-12-05T12:36:06.015851+01:00 bart systemd[1]: Stopping Replay Read-Ahead Data... 2014-12-05T12:36:06.016165+01:00 bart systemd[1]: Stopped Replay Read-Ahead Data. 2014-12-05T12:36:06.016456+01:00 bart systemd[1]: Starting File System Quota Check... 2014-12-05T12:36:06.376098+01:00 bart systemd[1]: Started Set Up Additional Binary Formats. 2014-12-05T12:36:06.376513+01:00 bart systemd[1]: Started File System Check on Root Device. 2014-12-05T12:36:06.376828+01:00 bart systemd[1]: Started File System Quota Check. 2014-12-05T12:36:06.379674+01:00 bart systemd[1]: Starting Enable File System Quotas... 2014-12-05T12:36:06.854571+01:00 bart systemd[1]: Stopped User Manager for 1102. 2014-12-05T12:36:06.855940+01:00 bart systemd[1]: Removed slice user-1102.slice. 2014-12-05T12:36:06.897699+01:00 bart systemd[1]: Started Restore Sound Card State. 2014-12-05T12:36:06.902554+01:00 bart systemd[1]: Starting user-1006.slice. 2014-12-05T12:36:06.902936+01:00 bart systemd[1]: Created slice user-1006.slice. 2014-12-05T12:36:06.903247+01:00 bart systemd[1]: Starting Session 121762 of user freundt. 2014-12-05T12:36:06.903550+01:00 bart systemd[1]: Started Session 121762 of user freundt. 2014-12-05T12:36:07.610356+01:00 bart /USR/SBIN/CRON[24007]: pam_unix(crond:session): session closed for user freundt 2014-12-05T12:36:18.354363+01:00 bart quotaon[24562]: quotaon: using /mnt/tmpdirs/aquota.group on /dev/mapper/vg0-tmpdirs [/mnt/tmpdirs]: Device or resource busy 2014-12-05T12:36:22.120689+01:00 bart quotaon[24562]: quotaon: using /mnt/tmpdirs/aquota.user on /dev/mapper/vg0-tmpdirs [/mnt/tmpdirs]: Device or resource busy 2014-12-05T12:36:22.121061+01:00 bart systemd[1]: quotaon.service: main process exited, code=exited, status=2/INVALIDARGUMENT 2014-12-05T12:36:22.121439+01:00 bart systemd[1]: Failed to start Enable File System Quotas. 2014-12-05T12:36:22.121792+01:00 bart systemd[1]: Unit quotaon.service entered failed state. 2014-12-05T12:36:36.446772+01:00 bart sudo: rudi : TTY=pts/17 ; PWD=/home/rudi ; USER=root ; COMMAND=/usr/bin/su 2014-12-05T12:36:36.447238+01:00 bart sudo: pam_unix(sudo:session): session opened for user root by rudi(uid=0) 2014-12-05T12:36:36.447977+01:00 bart sudo: pam_systemd(sudo:session): pam_putenv: delete non-existent entry; XDG_RUNTIME_DIR 2014-12-05T12:36:36.491023+01:00 bart su: (to root) rudi on none 2014-12-05T12:36:36.494087+01:00 bart su: pam_unix(su:session): session opened for user root by rudi(uid=0) 2014-12-05T12:36:36.494459+01:00 bart su: pam_systemd(su:session): pam_putenv: delete non-existent entry; XDG_RUNTIME_DIR 2014-12-05T12:37:01.618555+01:00 bart /usr/sbin/cron[29439]: pam_unix(crond:session): session opened for user freundt by (uid=0) 2014-12-05T12:37:01.623809+01:00 bart systemd[1]: Starting Session 121763 of user freundt. 2014-12-05T12:37:01.624823+01:00 bart systemd[1]: Started Session 121763 of user freundt. 2014-12-05T12:37:02.092316+01:00 bart /USR/SBIN/CRON[29439]: pam_unix(crond:session): session closed for user freundt 2014-12-05T12:37:06.818431+01:00 bart systemd[1]: Started Show Plymouth Boot Screen. 2014-12-05T12:37:06.819204+01:00 bart systemd[1]: Started Dispatch Password Requests to Console Directory Watch. 2014-12-05T12:37:06.821258+01:00 bart systemd[1]: Starting Wait for Plymouth Boot Screen to Quit... 2014-12-05T12:37:06.821596+01:00 bart systemd[1]: Starting Terminate Plymouth Boot Screen... 2014-12-05T12:37:06.847800+01:00 bart systemd[1]: Started Wait for Plymouth Boot Screen to Quit. 2014-12-05T12:37:06.848209+01:00 bart systemd[1]: Started Terminate Plymouth Boot Screen. 2014-12-05T12:37:06.848528+01:00 bart systemd[1]: Reached target Multi-User System. 2014-12-05T12:37:06.848831+01:00 bart systemd[1]: Starting Update UTMP about System Runlevel Changes... 2014-12-05T12:37:07.330171+01:00 bart systemd[1]: Started Update UTMP about System Runlevel Changes. -- You are receiving this mail because: You are on the CC list for the bug.

1 2