[SOLVED] Problem with consolekit 0.4.6-1

EvilRobot · 2012-04-12 20:13:29

After doing an update today I was unable to poweroff/reboot my machine from Gnome's Shutdown menu and the network indicator in the panel was showing that I was not connected to the internet (even though I was, wired connection) and when I went to network settings I received a message complaining that I did not have compatible software to manage the network interface. The only way I was able to shutdown or reboot my system was from the command line.

I was able to get correct those issues by downgrading from consolekit 0.4.6-1 and udev 182-1. Steps listed below for anyone else having this issue:

First downgrade from consolekit 0.4.6-1

# pacman -U /var/cache/pacman/pkg/consolekit-0.4.5-2-x86_64.pkg.tar.xz

Then downgrade from udev 182-1

# pacman -U /var/cache/pacman/pkg/udev-181-9-x86_64.pkg.tar.xz

Now run

# mkinitcpio -p linux

Then reboot

I was wondering if anyone else is having this issue and if they have a better solution?

Edit: It turns out udev is not the problem as it can be upgraded without reproducing these issues and since this does not appear to be confined to Gnome I've updated the thread title to reflect these developments.

Solution: upgrade to consolekit 0.4.6-2

Last edited by EvilRobot (2012-04-13 16:02:36)

mcloaked · 2012-04-12 20:27:51

I had the same problem running i686 with kde - I followed the same workaround as you did and the problem has gone away for now.

I presume there is a problem with either consolekit or udev but I don't know which one. Hopefully a fixed package set will be available before too long.

gondsman · 2012-04-12 20:30:35

I had the same problem, KDE here. I only downgraded consolekit and now everything is fine. I don't think it's related to udev at all.

Painless · 2012-04-12 20:36:42

I use Xdm, which refuses to log me in (standalone Compiz) with the latest consolekit and udev, it just loops back to the Xdm login screen. Downgrading consolekit (0.4.6-1 -> 0.4.5-2) and udev (182-1 -> 181-9) fixed that. Here are the errors I was getting while Xdm was looping (from /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

mcloaked · 2012-04-12 20:40:19

gondsman: I updated udev to 182-1 and rebooted - the problem was not there so I confirm that this looks like consolekit 0.4.6-1 is the cause of the problem.

mcloaked · 2012-04-12 20:56:04

This is related https://bugs.archlinux.org/task/29408

EvilRobot · 2012-04-12 21:03:00

I can confirm with gondsman and mcloaked that udev 182-1 does not appear to be the issue. The reason I initially thought udev was part of the problem was because of issues with network settings but it's fine now.

Thanks for the link mcloaked.

Last edited by EvilRobot (2012-04-12 21:07:17)

gondsman · 2012-04-13 06:50:55

consolekit 0.4.6-2 has been released, it solved the problem for me. If other people confirm, we can mark this as [solved].

bernarcher · 2012-04-13 07:05:45

Confirmed. 0.4.6-2 appears to work.

Painless · 2012-04-13 10:23:48

Yes new consolekit works with Xdm. Thanks to all.

EvilRobot · 2012-04-13 15:59:29

The update to consolekit 0.4.6-2 works here with Gnome, thread marked as solved.

Arch Linux

#1 2012-04-12 20:13:29

[SOLVED] Problem with consolekit 0.4.6-1

#2 2012-04-12 20:27:51

Re: [SOLVED] Problem with consolekit 0.4.6-1

#3 2012-04-12 20:30:35

Re: [SOLVED] Problem with consolekit 0.4.6-1

#4 2012-04-12 20:36:42

Re: [SOLVED] Problem with consolekit 0.4.6-1

#5 2012-04-12 20:40:19

Re: [SOLVED] Problem with consolekit 0.4.6-1

#6 2012-04-12 20:56:04

Re: [SOLVED] Problem with consolekit 0.4.6-1

#7 2012-04-12 21:03:00

Re: [SOLVED] Problem with consolekit 0.4.6-1

#8 2012-04-13 06:50:55

Re: [SOLVED] Problem with consolekit 0.4.6-1

#9 2012-04-13 07:05:45

Re: [SOLVED] Problem with consolekit 0.4.6-1

#10 2012-04-13 10:23:48

Re: [SOLVED] Problem with consolekit 0.4.6-1

#11 2012-04-13 15:59:29

Re: [SOLVED] Problem with consolekit 0.4.6-1

Board footer