Hello.
I'm having the same problem with 'rtkit' and log files flooding.
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 even 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 shutdown 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 e.g. 'rtkit-daemon.service'
file via 'mousepad', there is a WARNING message (** (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. But this is not important here. 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
✗✗ rtkit-daemon[1364]: message repeated 10 times: [ Failed to look up client:
No such file or directory]
There is about 30. such entries in '/var/log/syslog/' file etc. Anyway,
here are informations gathered via systemd's systemctl(1) command:
[~]$ systemctl status rtkit-daemon.service
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; disabled; vendor
preset: enabled)
Active: active (running) since sun 2018-03-25 11:44:47 CEST; 1h 26min ago
Main PID: 1383
CGroup: /system.slice/rtkit-daemon.service
└─1383 n/a
mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No
such file or directory
mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No
such file or directory
mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No
such file or directory
mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No
such file or directory
mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No
such file or directory
mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No
such file or directory
mar 25 11:45:07 greendragon rtkit-daemon[1383]: Failed to look up client: No
such file or directory
I apologize for such a long comment, but 'rtkit' 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.
● Release: 16.04.4 LTS
● rtkit: 0.11-4
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547589
Title:
rtkit-daemon flooding syslog
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1547589/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
