Arch Linux

Do you get any output in your syslog (/var/log/*)? Is the system fully up-to-date (with the newest udev)?

Hi Tom. I'm getting the same bug (I see you closed mine, as it's the same as this one). My system is fully up to date: udev 182-1 (base). I haven't found much info on X logs on /var/log, but I get the following on ~/.xsession-errors:


[cassio@arch ~]$ grep -i signal .xsession-errors
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Object::connect: No such signal QDBusAbstractInterface::Changed()
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Object::connect: No such signal QDBusAbstractInterface::Changed()
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Object::connect: No such signal QDBusAbstractInterface::StateChanged(uint)
"Cannot create unix session: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5"
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)


It's basically the same error KDM is throwing up on login.
signal 5 is SIGTRAP. Why dbus-daemon-launch-helper is getting it though I have no idea :-/

Yes, my system is up to date, udev 182-1.
The related log entries are:

Apr 12 11:14:03 localhost dbus[1550]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Apr 12 11:14:03 localhost kernel: [ 33.009028] console-kit-dae[2648] trap int3 ip:7f8fdf20f143 sp:7fffc8043040 error:0
Apr 12 11:14:03 localhost dbus[1550]: [system] Activated service 'org.freedesktop.ConsoleKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5
Apr 12 11:14:03 localhost kdm: :0[2635]: Cannot open ConsoleKit session: Unable to open session: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5

Could you guys try installing dbus-core and dbus from testing? I might have messed up the build and built against the testing versions rather than the versions in core/extra.

This might be related: https://bugs.archlinux.org/task/29407

Tested with
dbus 1.4.20-1
dbus-core 1.4.20-2
consolekit 0.4.6-1

The same error occurs.

Same problem, but with Gnome3.

dbus 1.4.16-1
dbus-core 1.4.16-1
dbus-glib 0.98-1
dbus-python 0.84.0-1
consolekit 0.4.6-1

After the system loads up, gnome 3 can not start (it launches old-style gnom2 version).

Here is /var/log/messages:

Apr 12 13:15:46 localhost dbus[558]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Apr 12 13:15:46 localhost dbus[558]: [system] Activating service name='org.freedesktop.Accounts' (using servicehelper)
Apr 12 13:15:46 localhost dbus[558]: [system] Successfully activated service 'org.freedesktop.Accounts'
Apr 12 13:15:46 localhost accounts-daemon[791]: started daemon version 0.6.15
Apr 12 13:15:46 localhost dbus[558]: [system] Activated service 'org.freedesktop.ConsoleKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-
launch-helper received signal 5
Apr 12 13:15:46 localhost kernel: [ 18.030950] console-kit-dae[792] trap int3 ip:7f2ce819c143 sp:7fff8d53c0b0 error:0
Apr 12 13:15:47 localhost dbus[558]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Apr 12 13:15:47 localhost dbus[558]: [system] Activated service 'org.freedesktop.ConsoleKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-
launch-helper received signal 5
Apr 12 13:15:47 localhost gdm-welcome][788]: WARNING: Unable to open session: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received
signal 5
Apr 12 13:15:47 localhost kernel: [ 18.859138] console-kit-dae[795] trap int3 ip:7f9e54d8a143 sp:7ffff34ff220 error:0


Any ideas?

The daemon itself crashes, that's odd, there should have been no changes to it. I'll have to sort this out when I get back to my computer, and can figure out why I'm not seeing this. (only thing I can think of us that I use "testing").

Not sure what is going on, but I get:

[cassio@arch ~]$ ps aux | grep -i dbus
dbus 2028 0.0 0.0 3292 1024 ? Ss 14:12 0:00 /usr/bin/dbus-daemon --system
cassio 2109 0.0 0.0 3728 224 ? S 14:13 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
cassio 2110 0.0 0.0 4040 1024 ? Ss 14:13 0:01 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

despite the error at login.

I get the same problem here with Gnome 3 on a fully upgraded system (not using testing versions), just like strizhov user reported above, even if I can succesfully log into gnome session. Don't know if may be relevant but another effect I observed is that "suspend/shutdown" voice disappeared from gnome 3 session menu. Downgrading to 0.4.5-2 (without downgrading udev) works fine.

just to be sure, you guys can downgrade consolekit without downgrading udev as well?

@Ionut: yes

but it won't work because udev-acl is missing and udev-acl is the one that allows authorized users to consolekit to access devices.

Old consolekit 0.4.5-2 with dbus packages from testing works for me.

consolekit 0.4.5-2 with udev 182-1 works for me.

I'm using xdm with xfce4 and had this problem when I simulatneously upgraded udev and consolekit. I downgraded consolkit back to 0.4.5-2 and kept udev updated to 182-1 and it works ok now

i guess it works for you guys with newer udev because your user is in video,audio, etc groups

I get the following output in /var/log/xdm.log:

xdm error (pid 1344): Dbus error: Unable to open session: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 5
xdm error (pid 1344): console-kit-daemon not running?
xdm error (pid 1344): session start failed
xdm info (pid 1344): sourcing /etc/X11/xdm/arch-xdm/Xreset
xdm info (pid 1339): Starting X server on :0
1 XSELINUXs still allocated at reset
SCREEN: 0 objects of 152 bytes = 0 total bytes 0 private allocs
COLORMAP: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DEVICE: 0 objects of 64 bytes = 0 total bytes 0 private allocs
CLIENT: 0 objects of 104 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 44 bytes = 0 total bytes 0 private allocs
PIXMAP: 1 objects of 76 bytes = 76 total bytes 0 private allocs
GC: 0 objects of 56 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
GLYPH: 0 objects of 12 bytes = 0 total bytes 0 private allocs
SYNC_FENCE: 0 objects of 4 bytes = 0 total bytes 0 private allocs
TOTAL: 1 objects, 76 bytes, 0 allocs
1 PIXMAPs still allocated at reset
PIXMAP: 1 objects of 76 bytes = 76 total bytes 0 private allocs
GC: 0 objects of 56 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
GLYPH: 0 objects of 12 bytes = 0 total bytes 0 private allocs
SYNC_FENCE: 0 objects of 4 bytes = 0 total bytes 0 private allocs
TOTAL: 1 objects, 76 bytes, 0 allocs

Please try with consolekit-0.4.6-2, I hope it is fixed now.

I have the same xdm.log output as Rob (different PID of course, but...)

I tried 0.4.6-2, it works like a charm

0.4.6-2 works for me too, thank you very much

Awesome :-)