[systemd-bugs] [Bug 72759] Systemd user manager interferes with ecryptfs - private directory not being unmounted

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=72759

W Unruh <unruh at physics.ubc.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOTOURBUG                   |---

--- Comment #2 from W Unruh <unruh at physics.ubc.ca> ---
The answer referred to the symptoms, not the bug. The bug is that systemd
leaves
something about the user "logged in" even after the user logs out. Thus in my 
system the SYMPTOM is that when I try to run reboot as user after I have logged
out as root, I get an error message saying that user root is still logged in
and this blocks the reboot. 
Another symptom is that systemd --user and (sd-pam) are left running for that
logged out user even after that user (in my case aboove root) has logged out. 

So running in runlevel 3 on Mageia 4.1 newly updated, if I first log in as root
immediately log out as root (so I get another login request on the runlevel 3
terminal) and log in as unruh ( user 500) and then try to run reboot, I get an
error message from systemd saying

User root is logged in on tty1
Please retry operation after closing inhibitors and logging out other users. 

The other users ARE logged out. 

As another SYMPTOM, if I log in as user, run poweroff or reboot, I get, after a
number of messages, a timeout of 90 sec on User Manager failing. 90 sec
completely defeats the stated purpose of systemd to speed up boots and halts.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141128/218892da/attachment.html>