On miercuri, 11 ianuarie 2017 10:12:00 EET Felipe Sateler wrote: > Control: tags -1 moreinfo unreproducible > > On 11 January 2017 at 04:59, Bogdan Vatra <bogdan.va...@kdab.com> wrote: > > On miercuri, 11 ianuarie 2017 09:48:16 EET Bogdan Vatra wrote: > >> On marți, 10 ianuarie 2017 17:20:28 EET Felipe Sateler wrote: > >> > Hi, > >> > > >> > On 10 January 2017 at 16:05, Bogdan Vatra <bogdan.va...@kdab.com> wrote: > >> > > Package: rtkit > >> > > Version: 0.11-4 > >> > > Severity: important > >> > > > >> > > --- Please enter the report below this line. --- > >> > > > >> > > This bug is pretty annoying because it makes pulseaudio unusable (see > >> > > #850806). > >> > > >> > > Here are the logs: > >> > <snip> > >> > > >> > > -- Unit rtkit-daemon.service has begun starting up. > >> > > ian 10 21:00:32 zmeu rtkit-daemon[19342]: Failed to connect to system > >> > > bus: > >> > > Failed to connect to socket /var/run/dbus/system_bus_socket: No su > >> > > >> > This suggests that dbus is not running. Could that be the case? Do > >> > other dbus-interacting apps misbehave? > >> > >> I think that's a wrong message ... because : > >> > >> $ ls -l /var/run/dbus/system_bus_socket > >> srw-rw-rw- 1 root root 0 ian 10 09:42 /var/run/dbus/system_bus_socket > >> > >> That file exists and dbus works fine (all my KDE/Qt apps works ok). > > > > If I manually run "/usr/lib/rtkit/rtkit-daemon" it works just fine... > > The only problem is when I start it with "systemctl start rtkit- > > daemon.service". > > Weird. Could you repeat the same with the daemon as started by systemd? > > Use `systemctl edit --full rtkit-daemon` to edit the ExecStart line.
It is the same thing ... : [...] ExecStart=/usr/lib/rtkit/rtkit-daemon [...] Actually I was inspired from that file to exec "/usr/lib/rtkit/rtkit-daemon" manually :). It there any way to debug it ?