Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-20 Thread Felipe Sateler 
Control: tags -1 - unreproducible moreinfo
Control: reassign -1 systemd
Control: affects -1 rtkit
Control: retitle -1 Units with PrivateTmp fail when /var is a symlink
Control: severity -1 normal

On 12 January 2017 at 04:46, Bogdan Vatra  wrote:
> Hi,
>
>  I have an update, some time ago (~1year) I run out of space on my system
> partition and I decide to move /var folder to another partition and symlink it
> back to / partition. Today I just moved back my var folder and rtkit daemon
> started to work ... :)

This is a bug in systemd. A related issue is
https://github.com/systemd/systemd/issues/3867 , but that is
supposedly fixed in 232. BogDan, do you have version 232 installed? It
may be that the issue is not fully fixed yet.

-- 

Saludos,
Felipe Sateler

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Processed: Re: Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-20 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 - unreproducible moreinfo
Bug #850855 [rtkit] [rtkit] rtkit daemon fails to start
Removed tag(s) unreproducible and moreinfo.
> reassign -1 systemd
Bug #850855 [rtkit] [rtkit] rtkit daemon fails to start
Bug reassigned from package 'rtkit' to 'systemd'.
No longer marked as found in versions rtkit/0.11-4.
Ignoring request to alter fixed versions of bug #850855 to the same values 
previously set
> affects -1 rtkit
Bug #850855 [systemd] [rtkit] rtkit daemon fails to start
Added indication that 850855 affects rtkit
> retitle -1 Units with PrivateTmp fail when /var is a symlink
Bug #850855 [systemd] [rtkit] rtkit daemon fails to start
Changed Bug title to 'Units with PrivateTmp fail when /var is a symlink' from 
'[rtkit] rtkit daemon fails to start'.
> severity -1 normal
Bug #850855 [systemd] Units with PrivateTmp fail when /var is a symlink
Severity set to 'normal' from 'important'

-- 
850855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-12 Thread Bogdan Vatra 
Hi,

 I have an update, some time ago (~1year) I run out of space on my system 
partition and I decide to move /var folder to another partition and symlink it 
back to / partition. Today I just moved back my var folder and rtkit daemon 
started to work ... :)

Cheers,
BogDan.

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-11 Thread Bogdan Vatra 
On miercuri, 11 ianuarie 2017 13:11:07 EET Felipe Sateler wrote:
> On 11 January 2017 at 13:05, Bogdan Vatra  wrote:
> > On miercuri, 11 ianuarie 2017 12:40:23 EET Felipe Sateler wrote:
> >> On 11 January 2017 at 12:37, Bogdan Vatra  wrote:
> >> > 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  
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 
> >> > 
> >> > 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:
> >> >> >> > 
> >> >> >> > 
> >> >> >> > > -- 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 :).
> >> 
> >> Sorry, I was not clear. I meant stracing the daemon.
> > 
> > Attached the log.
> 
> Hmm. I guess it's not my day, I can't explain myself :(
> 
> Please run the rtkit-daemon under strace, with systemd: edit the
> systemd service like so:
> 
> ExecStart=/usr/bin/strace -o /tmp/strace.log -ff /usr/lib/rtkit/rtkit-daemon
> 
> then do a `systemctl daemon-reload` and a restart of the rtkit-daemon.
> Then please attach the /tmp/strace.log.$PID file.

Ah, sorry probably is me not you.
I edit as you requested but there is not /tmp/strace.log file, this is the 
commands I used:

bogdan@zmeu:~$ sudo systemctl daemon-reload 
bogdan@zmeu:~$ sudo systemctl start rtkit-daemon
Job for rtkit-daemon.service failed because the control process exited with 
error code.
See "systemctl status rtkit-daemon.service" and "journalctl -xe" for details.
bogdan@zmeu:~$ systemctl status rtkit-daemon.service
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
   Loaded: loaded (/etc/systemd/system/rtkit-daemon.service; disabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2017-01-11 18:42:42 EET; 6s 
ago
  Process: 26573 ExecStart=/usr/bin/strace -o /tmp/strace.log -ff /usr/lib/
rtkit/rtkit-daemon (code=exited, status=1/FAILURE)
 Main PID: 26573 (code=exited, status=1/FAILURE)



What "Loaded: loaded (/etc/systemd/system/rtkit-daemon.service; disabled; 
vendor preset: enabled)" *disabled means in the log?

BogDan.

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-11 Thread Felipe Sateler 
On 11 January 2017 at 13:05, Bogdan Vatra  wrote:
> On miercuri, 11 ianuarie 2017 12:40:23 EET Felipe Sateler wrote:
>> On 11 January 2017 at 12:37, Bogdan Vatra  wrote:
>> > 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  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 
>> >
>> > 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:
>> >> >> > 
>> >> >> >
>> >> >> > > -- 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 :).
>>
>> Sorry, I was not clear. I meant stracing the daemon.
>
> Attached the log.

Hmm. I guess it's not my day, I can't explain myself :(

Please run the rtkit-daemon under strace, with systemd: edit the
systemd service like so:

ExecStart=/usr/bin/strace -o /tmp/strace.log -ff /usr/lib/rtkit/rtkit-daemon

then do a `systemctl daemon-reload` and a restart of the rtkit-daemon.
Then please attach the /tmp/strace.log.$PID file.



-- 

Saludos,
Felipe Sateler

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-11 Thread Bogdan Vatra 
On miercuri, 11 ianuarie 2017 12:40:23 EET Felipe Sateler wrote:
> On 11 January 2017 at 12:37, Bogdan Vatra  wrote:
> > 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  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 
> > 
> > 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:
> >> >> > 
> >> >> > 
> >> >> > > -- 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 :).
> 
> Sorry, I was not clear. I meant stracing the daemon.

Attached the log.

$ sudo strace /usr/lib/rtkit/rtkit-daemon
[sudo] password for bogdan: 
execve("/usr/lib/rtkit/rtkit-daemon", ["/usr/lib/rtkit/rtkit-daemon"], [/* 18 vars */]) = 0
brk(NULL)   = 0x1cc3000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f156c6be000
access("/etc/ld.so.preload", R_OK)  = 0
open("/etc/ld.so.preload", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
close(3)= 0
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=245391, ...}) = 0
mmap(NULL, 245391, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f156c682000
close(3)= 0  
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)  
open("/lib/x86_64-linux-gnu/libdbus-1.so.3", O_RDONLY|O_CLOEXEC) = 3 
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300\323\0\0\0\0\0\0"..., 832) = 832  
fstat(3, {st_mode=S_IFREG|0644, st_size=321680, ...}) = 0
mmap(NULL, 2417328, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f156c25   
mprotect(0x7f156c29d000, 2093056, PROT_NONE) = 0 
mmap(0x7f156c49c000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4c000) = 0x7f156c49c000  
close(3)= 0  
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)  
open("/lib/x86_64-linux-gnu/libcap.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300\30\0\0\0\0\0\0"..., 832) = 832   
fstat(3, {st_mode=S_IFREG|0644, st_size=22768, ...}) = 0 
mmap(NULL, 2117976, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-11 Thread Felipe Sateler 
On 11 January 2017 at 12:37, Bogdan Vatra  wrote:
> 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  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 
> 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:
>> >> > 
>> >> >
>> >> > > -- 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 :).

Sorry, I was not clear. I meant stracing the daemon.

-- 

Saludos,
Felipe Sateler

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-11 Thread Bogdan Vatra 
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  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  
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:
> >> > 
> >> > 
> >> > > -- 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 ?

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Processed: Re: Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-11 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 moreinfo unreproducible
Bug #850855 [rtkit] [rtkit] rtkit daemon fails to start
Added tag(s) unreproducible and moreinfo.

-- 
850855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-11 Thread Felipe Sateler 
Control: tags -1 moreinfo unreproducible

On 11 January 2017 at 04:59, Bogdan Vatra  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  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:
>> > 
>> >
>> > > -- 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.

-- 

Saludos,
Felipe Sateler

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-11 Thread Bogdan Vatra 
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  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:
> > 
> > 
> > > -- 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".
I strace it and from the log it seems it succeeds to open dbus socket:
[...]
connect(3, {sa_family=AF_UNIX, sun_path="/var/run/dbus/system_bus_socket"}, 
33) = 0
getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0
fstat(3, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0
getsockopt(3, SOL_SOCKET, SO_ACCEPTCONN, [0], [4]) = 0
getsockname(3, {sa_family=AF_UNIX}, [128->2]) = 0
geteuid()   = 1000
sendmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0AUTH EXTERNAL 
", iov_len=15}, {iov_base="31303030", iov_len=8}, {iov_base="\r
\nNEGOTIATE_UNIX_FD\r\nBEGIN\r\n", iov_len=28}], msg_iovlen=3, 
msg_controllen=0, msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 51
[...]

BogDan.$ strace systemctl start rtkit-daemon.service
execve("/bin/systemctl", ["systemctl", "start", "rtkit-daemon.service"], [/* 66 vars */]) = 0
brk(NULL)   = 0x55654252d000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fce6f2d
access("/etc/ld.so.preload", R_OK)  = 0
open("/etc/ld.so.preload", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
close(3)= 0
open("/lib/systemd/tls/x86_64/libsystemd-shared-232.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/systemd/tls/x86_64", 0x7ffe76d74760) = -1 ENOENT (No such file or directory)
open("/lib/systemd/tls/libsystemd-shared-232.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/systemd/tls", 0x7ffe76d74760) = -1 ENOENT (No such file or directory)
open("/lib/systemd/x86_64/libsystemd-shared-232.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/systemd/x86_64", 0x7ffe76d74760) = -1 ENOENT (No such file or directory)
open("/lib/systemd/libsystemd-shared-232.so", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=2200704, ...}) = 0
mmap(NULL, 2205104, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fce6ee96000
mmap(0x7fce6f025000, 569344, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x18e000) = 0x7fce6f025000
mmap(0x7fce6f0b, 1456, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fce6f0b
close(3)= 0
open("/lib/systemd/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=245391, ...}) = 0
mmap(NULL, 245391, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fce6f294000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340`\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=135448, ...}) = 0
mmap(NULL, 2212904, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fce6ec79000
mprotect(0x7fce6ec91000, 2093056, PROT_NONE) = 0
mmap(0x7fce6ee9, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x17000) = 0x7fce6ee9
mmap(0x7fce6ee92000, 13352, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fce6ee92000
close(3)= 0
open("/lib/systemd/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-10 Thread Bogdan Vatra 
On marți, 10 ianuarie 2017 17:20:28 EET Felipe Sateler wrote:
> Hi,
> 
> On 10 January 2017 at 16:05, Bogdan Vatra  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:
> 
> 
> > -- 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).

BogDan.

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-10 Thread Felipe Sateler 
Hi,

On 10 January 2017 at 16:05, Bogdan Vatra  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:

> -- 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?

-- 

Saludos,
Felipe Sateler

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#850855: [rtkit] rtkit daemon fails to start

2017-01-10 Thread Bogdan Vatra 
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:
bogdan@zmeu:~$ sudo 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: failed (Result: exit-code) since Tue 2017-01-10 20:54:59 EET; 5min 
ago
 Main PID: 17917 (code=exited, status=203/EXEC)

ian 10 20:54:59 zmeu systemd[1]: Starting RealtimeKit Scheduling Policy 
Service...
ian 10 20:54:59 zmeu systemd[1]: rtkit-daemon.service: Main process exited, 
code=exited, status=203/EXEC
ian 10 20:54:59 zmeu systemd[1]: Failed to start RealtimeKit Scheduling Policy 
Service.
ian 10 20:54:59 zmeu systemd[1]: rtkit-daemon.service: Unit entered failed 
state.
ian 10 20:54:59 zmeu systemd[1]: rtkit-daemon.service: Failed with result 
'exit-code'.
bogdan@zmeu:~$ sudo systemctl start rtkit-daemon.service 
Job for rtkit-daemon.service failed because the control process exited with 
error code.
See "systemctl status rtkit-daemon.service" and "journalctl -xe" for details.
bogdan@zmeu:~$ sudo 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: failed (Result: exit-code) since Tue 2017-01-10 21:00:32 EET; 10s 
ago
  Process: 19342 ExecStart=/usr/lib/rtkit/rtkit-daemon (code=exited, status=1/
FAILURE)
 Main PID: 19342 (code=exited, status=1/FAILURE)

ian 10 21:00:32 zmeu systemd[1]: Starting RealtimeKit Scheduling Policy 
Service...
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Main process exited, 
code=exited, status=1/FAILURE
ian 10 21:00:32 zmeu systemd[1]: Failed to start RealtimeKit Scheduling Policy 
Service.
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Unit entered failed 
state.
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Failed with result 
'exit-code'.
bogdan@zmeu:~$ sudo journalctl -xe
ian 10 21:00:16 zmeu systemd[1]: Reloading.
ian 10 21:00:16 zmeu systemd[1]: apt-daily.timer: Adding 5h 21min 32.698921s 
random time.
ian 10 21:00:16 zmeu sudo[19309]: pam_unix(sudo:session): session closed for 
user root
ian 10 21:00:23 zmeu sudo[19328]:   bogdan : TTY=pts/10 ; PWD=/home/bogdan ; 
USER=root ; COMMAND=/bin/systemctl status rtkit-daemon.service
ian 10 21:00:23 zmeu sudo[19328]: pam_unix(sudo:session): session opened for 
user root by bogdan(uid=0)
ian 10 21:00:23 zmeu sudo[19328]: pam_unix(sudo:session): session closed for 
user root
ian 10 21:00:27 zmeu sudo[19331]:   bogdan : TTY=pts/10 ; PWD=/home/bogdan ; 
USER=root ; COMMAND=/bin/systemctl stop rtkit-daemon.service
ian 10 21:00:27 zmeu sudo[19331]: pam_unix(sudo:session): session opened for 
user root by bogdan(uid=0)
ian 10 21:00:27 zmeu sudo[19331]: pam_unix(sudo:session): session closed for 
user root
ian 10 21:00:28 zmeu sudo[19334]:   bogdan : TTY=pts/10 ; PWD=/home/bogdan ; 
USER=root ; COMMAND=/bin/systemctl status rtkit-daemon.service
ian 10 21:00:28 zmeu sudo[19334]: pam_unix(sudo:session): session opened for 
user root by bogdan(uid=0)
ian 10 21:00:28 zmeu sudo[19334]: pam_unix(sudo:session): session closed for 
user root
ian 10 21:00:32 zmeu sudo[19339]:   bogdan : TTY=pts/10 ; PWD=/home/bogdan ; 
USER=root ; COMMAND=/bin/systemctl start rtkit-daemon.service
ian 10 21:00:32 zmeu sudo[19339]: pam_unix(sudo:session): session opened for 
user root by bogdan(uid=0)
ian 10 21:00:32 zmeu systemd[1]: Starting RealtimeKit Scheduling Policy 
Service...
-- Subject: Unit rtkit-daemon.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- 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
ian 10 21:00:32 zmeu rtkit-daemon[19342]: Demoting known real-time threads.
ian 10 21:00:32 zmeu rtkit-daemon[19342]: Demoted 0 threads.
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Main process exited, 
code=exited, status=1/FAILURE
ian 10 21:00:32 zmeu systemd[1]: Failed to start RealtimeKit Scheduling Policy 
Service.
-- Subject: Unit rtkit-daemon.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit rtkit-daemon.service has failed.
-- 
-- The result is failed.
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Unit entered failed 
state.
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Failed with result 
'exit-code'.
ian 10 21:00:32 zmeu sudo[19339]: pam_unix(sudo:session): session closed for 
user root
ian 10 21:00:43 zmeu sudo[19348]:   bogdan : TTY=pts/10 ; PWD=/home/bogdan ; 
USER=root ; COMMAND=/bin/systemctl status rtkit-daemon.service
ian 10 21:00:43 zmeu sudo[19348]: