https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c1 --- Comment #1 from Drazenko Djuricic 2014-02-24 20:04:52 UTC --- I think this is related too? "systemd" also prevents your home directory from getting properly unmounted if you used "ecryptfs" to encrypt it. This bug was NOT present in openSUSE 12.3. But in openSUSE 13.1 you get the phenomenon that "systemd" seems to keep a PAM session open for your user even after you logout (the home directory remains decrypted and readable!); hence the command "ecryptfs-umount-private" fails to work properly; instead it tells me that the directory is mounted in another session. Another user already tried to report this to the "systemd" folks, but the response there was "not our bug" ...? https://bugs.freedesktop.org/show_bug.cgi?id=72759#c1 http://nwrickert2.wordpress.com/2013/12/16/systemd-user-manager-ecryptfs-and... The root cause here seems to be that even after a user logs out, "systemd" keeps running a "/usr/lib/systemd/systemd --user" process under the ID of the user and also a "(sd-pam)" (= systemd-PAM component?) session; also under the ID of the user. So ... even after logout a user's session never really ends and thus causes numerous side-effects in KDE, sudo, ecryptfs, yast and many other places ...? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c Xiyuan Liu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c4 --- Comment #4 from Stakanov Schufter 2014-02-25 08:21:54 UTC --- Thank you for your suggestion. I will try, but not on this machine (as it is my "production" machine and uttermost key). Beginning next week I can try this on a 32 bit 13.1 machine that may be "scarified" in case things go wrong. AFAIK the 32 bit behaves exactly as the 64 bit in this regard. I will let you know around Monday next week reporting here if that is O.K. for you. Greets. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c6 Drazenko Djuricic changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |djuricicd@gawnet.ch --- Comment #6 from Drazenko Djuricic 2014-03-05 21:34:58 UTC --- (In reply to comment #3)

You may give the latest systemd-208 a try and report if this works for you:

http://download.opensuse.org/repositories/Base:/System/openSUSE_13.1/

Sorry, openSUSE-noob here ... How do I apply this patch? Do I need to add the above URL in "yast" as repository? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c8 --- Comment #8 from Drazenko Djuricic 2014-03-05 23:27:35 UTC --- (In reply to comment #7)

I avoided to do experiments on my production system...

Yes, I have test systems for that. What dependency issues did you run into? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c10 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |stakanov@freenet.de --- Comment #10 from Dr. Werner Fink 2014-03-24 13:33:49 UTC --- Test out latest systemd from http://download.opensuse.org/repositories/Base:/System/openSUSE_13.1/ and report -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c12 Achim Mildenberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |admin@fph.physik.uni-karlsr | |uhe.de --- Comment #12 from Achim Mildenberger 2014-04-09 08:17:40 UTC --- I'm also encountering two hanging processes after user-logins. /usr/lib/systemd/systemd --user (sd-pam) on openSuSE 13.1. Since these are hosts which have a lot of different users logging in, I'm somewhat concerned about the consequences. In http://nwrickert2.wordpress.com/2013/12/16/systemd-user-manager-ecryptfs-and... I read, that pam-config -d --systemd might be a workaround, but has side-effects. If anyone here knows the list of side-effects, I'd be glad. As far as I understand, systemd --user is started via pam at logins/ssh-access. Which mechanism is supposed to stop these processes after a logout? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c14 --- Comment #14 from Achim Mildenberger 2014-04-09 09:55:32 UTC --- Thank you very much, Werner! Upgrading to systemd-210-619.1.x86_64.rpm systemd-sysvinit-210-619.1.x86_64.rpm from your repository helps a lot. As it seems, there is still a (smaller) issue: systemd --user (sd-pam) remain if there is an open mount (e.g. a USB-stick). Maybe this is being discussed here: https://bugs.freedesktop.org/show_bug.cgi?id=70214 Anyway, are you planning to release an update of systemd for 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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c16 --- Comment #16 from Drazenko Djuricic 2014-04-27 10:09:28 UTC --- (In reply to comment #15)

(In reply to comment #14)

...

Anyway, are you planning to release an update of systemd for 13.1?

I've burned my fingers with such updates

Sorry if I ask ... but what will happen now? Will this annoying bug ever be fixed in 13.1? Or can we expect a fix in 13.2? Regards. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c18 --- Comment #18 from Dr. Werner Fink 2014-04-28 13:06:20 UTC --- (In reply to comment #17) I do not find the time to port all those changes back to 13.1 as this not only requires a lot of backporting but also a lot of testing andin fact I can not test all those fixes as I do not have all the test scenarios around. Nevertheless you're welcome to test out http://download.opensuse.org/repositories/Base:/System/openSUSE_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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c20 --- Comment #20 from Dr. Werner Fink 2014-04-28 14:12:43 UTC --- (In reply to comment #19) One major problem is that in fact there are several other packages which sould also updated if systemd will be updated. E.g. multipath-tools and many others. It is perfect for you that 34 desktops are running but I had burned my fingers in past with systemd updates (compare with bug #854884) and I'm aware that not all users are able to debug such problems into its fully deep as they are not software engineers and/or familiar with how to do software engineering. Indeed some of the bug reports requires a crystal ball and a lot of time from my side and both I do not have :( -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865337 https://bugzilla.novell.com/show_bug.cgi?id=865337#c21 Stakanov Schufter changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|stakanov@freenet.de | --- Comment #21 from Stakanov Schufter 2014-05-06 16:26:39 UTC --- Hello Werner, I have good news for you. Your work was (at least on a 32 bit with standard KDE system) absolutely fruitful. I did try to open several user, to use SUID, to log out from that user, not respecting the order of opening. De facto a few processes stay open for about 10-15 seconds after log out but after that magically close and the system is like you would expect it. No process of logged out user seems to stay open. The only adverse effect currently was a request to install by hand a dbus package with a higher version than that of the systemd repo. This resolved the conflict and the dbus patch of today installed smoothly. If I would have chosen the primary conflict solving proposed by yast I would have uninstalled 149 packages. So you may look on the last dbus patch to see if some dependency has to be adapted. I will now use the system extensively for about a week doing whatever comes to my mind may be shitty for systemd to handle. :-) After that I will report back a last time. My feeling: good, I think you made it. But to be dead sure, I wish to test further. What to say...I am delighted up to now. Kind regards, thank you and compliments. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=865337 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joschibrauchle@gmx.de --- Comment #23 from Joschi Brauchle --- We are having the same problem at our institute in combination with NFSv4 and Kerberos mounts. The user mounts its home from an NFSv4 server via autofs. Unfortunately, due to systemd leaving an "(sd-pam)" process hanging around which accesses the user home even after user logout, the NFSv4 share cannot be unmounted. After a while, the user kerberos tickets for the nfsv4 mount expires and things are in a big mess, as the user is not even aware of the situation as he has logged out long before. The "(sd-pam)" processes and now inaccessible nfs4 mounts keep sticking around forever until the machine is rebooted. We currently refrain to automatically kill all "(sd-pam)" processes after user logout to prevent this scenario. Not nice... -- You are receiving this mail because: You are on the CC list for the bug.