Re: [gentoo-user] Mysterious failure of ConsoleKit

[Helmut Jarausch <jarausch@igpm.rwth-aachen.de>]

On 12/23/10 02:41:44, Mark Knecht wrote:
> On Wed, Dec 22, 2010 at 9:39 AM, Peter Humphrey
> <peter@humphrey.ukfsn.org> wrote:
> > On Wednesday 22 December 2010 17:28:09 Mark Knecht wrote:
> >> On Wed, Dec 22, 2010 at 9:09 AM, Peter Humphrey
> >> <peter@humphrey.ukfsn.org> wrote:
> >> <SNIP>
> >>
> >> > Can anyone see anything else I could check?
> >> >
> >> > --
> >> > Rgds
> >> > Peter.          Linux Counter 5290, 1994-04-23.
> >>
> >> Disk space?
> >
> > Seems not. I copied a 150M ISO into /var with no problem. This is a
> 20GB
> > ext4 partition with default mkfs options, 58% full. Good idea 
> though
> -
> > thanks.
> 
> Yeah, that would be too easy.
> 
> OK, so I don't know much about what consolekit even does. It's on 
> this
> system and was touched (I guess) when the system booted, but it's not
> running:
> 
> - Mark
> 
> 
> k2 ~ # ls -la /var/run/ConsoleKit/pid
> -rw-r--r-- 1 root root 5 Dec 22 16:31 /var/run/ConsoleKit/pid
> 
> k2 ~ # /etc/init.d/consolekit status
>  * status:  stopped
> 
> k2 ~ # rc-update show --verbose
>            alsasound |      default
>              apcupsd |      default
>             bootmisc | boot
>              checkfs | boot
>            checkroot | boot
>                clock | boot
>          consolefont | boot
>           consolekit |
>          crypto-loop |
>                 dbus |      default
>        device-mapper |
>             dmeventd |
>           git-daemon |
>                  gpm |
>               hdparm |
>             hostname | boot
>              keymaps | boot
>                local |      default nonetwork
>           localmount | boot
>                  lvm |
>       lvm-monitoring |
>                mdadm |      default
>               mdraid |
>              modules | boot
>                mysql |
>         mysqlmanager |
>             net.eth0 |      default
>               net.lo | boot
>             netmount |      default
>                 nscd |
>           ntp-client |      default
>                 ntpd |      default
>              numlock |
>              pciparm |
>              pwcheck |
>            pydoc-2.6 |
>            pydoc-3.1 |
>            rmnologin | boot
>               rsyncd |
>            saslauthd |
>                 slpd |
>               smartd |
>                 sshd |      default
>             svnserve |
>            syslog-ng |      default
>                 udev |
>     udev-dev-tarball |
>           udev-mount |
>       udev-postmount |      default
>              urandom | boot
>           vixie-cron |      default
>                  xdm |      default
>            xdm-setup |
> k2 ~ #
> 
> 


I'm having the same problem (as do others).
 ps auxw | grep -i console
shows, that console-kit-daemon is actually running.
And killall console-kit-daemon, /etc/init.d/consolekit start
fixes the problems.

It looks as if something has started consolekit earlier but not by
using /etc/init.d/consolekit .

Unfortunately, I don't know how to debug which is starting consolekit.
Furthermore, I'd like to know where the source of the start-stop-daemon 
is.

Helmut.