Comment 4 for bug 1617630

Hello.

I'm having the same problem with mousepad. Yesterday, I've choosed "menu/logout/halt" option instead of "menu/logout/shutdown". And problems started to happen: I could not even reboot or shutdown computer, because every time when I wanted to do this, there was a window to unblock session (I have had to enter my user password and there was not internet connection - it could not be connected via NetworkManager! etc.) The only one working solution to shutdown computer was: press "RESET" and next "POWER" buttons.

I've decided to try shytdown system via shutdown(8) command but it did not work:

[~]$ shutdown now
Failed to power off system via logind: There's already a shutdown or sleep operation in progress

Anyway, there is not LightDM now! I have to login via "unblock" window mentioned above. And when I want to edit some file, there is a WARNING message:

[~]$ mousepad /lib/systemd/system/rtkit-daemon.service

** (mousepad:2869): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*: Connection refused

It happens with every file, that I want to edit etc. Log files contains many entries related to the 'rtkit-daemon'. For example:

rtkit-daemon[1383]: Supervising 0 threads of 0 processes of 1 users.
rtkit-daemon[1383]: Failed to look up client: No such file or directory

I apologize for such a long comment, but mousepad issues, started to happen after described situation. I have no idea if it's important, but it started to happen when I choosed - by accident - 'halt' option instead of 'shutdown' during logout.

Thanks.