On Thu, 11 Sep 2014 02:42:52 +0200 Michael Biebl <bi...@debian.org>
wrote:
> reopen 756076
> thanks
>
>
> While the error message is gone, the actual cleanup doesn't seem to
work
> properly.
>
> When logging out, the logind session persists and remains in state
> "closing":
While this is true, it seems that device permissions are actually
removed correctly. I determined this by:
Logging in on tty6.
Successfully using the sound card (with aplay, if that matters).
Logging out from tty6.
Logging in with the same user via ssh.
Unsuccessfully using the sound card (aplay errors, saying that it can
not find the card).
Using start-stop-daemon to change to the user in question (does not go
through PAM)
Same error as with ssh
I did not log in with that user at all before that time, and no open
sessions existed on the system for that user except for those
specified. Is there anything wrong with that method, and can you
reproduce my results Michael?
So what other risks are there if it is stuck in this "closing" state
(assuming that I did not make a mistake in my above determination)?
On the subject of fixing the issue, my only guess is that since the
user@.service start failed, it might be getting hung up on shutdown,
you know? I can not come up with anything better, since nothing stuck
out on a short peruse of systemd/src/login/, and logind is not emitting
any other error messages for me (are you getting anything else,
Michael).
So again, I would appreciate if we determined for sure if this bug is
causing security issues or other large concerns.
Thanks a ton,
--
Cameron
