What | Removed | Added |
---|---|---|
Priority | P5 - None | P3 - Medium |
Status | RESOLVED | REOPENED |
CC | lmb@suse.com | |
Resolution | FIXED | --- |
Hey, I don't mean to be a killjoy, and I may have missed something in the rather long discussion of this bug - but with tumbleweed, updating xdm *still* terminates the user's session. May 02 09:33:35 hermes [RPM][1966]: install xdm-1.1.11-19.2.x86_64: success May 02 09:33:35 hermes systemd[1]: Reloading. May 02 09:33:35 hermes systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped May 02 09:33:35 hermes systemd[1]: Started CUPS Scheduler. May 02 09:33:35 hermes [RPM][1966]: erase xdm-1.1.11-19.1.x86_64: success May 02 09:33:35 hermes systemd[1]: Reloading. May 02 09:33:35 hermes systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped May 02 09:33:35 hermes systemd[1]: Started CUPS Scheduler. May 02 09:33:35 hermes systemd[1]: Stopping X Display Manager... May 02 09:33:35 hermes org.gtk.vfs.Daemon[2740]: A connection to the bus can't be made May 02 09:33:35 hermes su[2902]: pam_unix(su-l:session): session closed for user root May 02 09:33:35 hermes kdm[2689]: :0[2689]: pam_unix(xdm:session): session closed for user lmb ... May 02 09:33:37 hermes systemd[1]: Stopped X Display Manager. May 02 09:33:37 hermes systemd[1]: Starting X Display Manager... This is rather consistently annoying ;-) Is there any chance to avoid this without modifying /etc/sysconfig/services globally?