I have the same problem in 12.1 with most logins, using KDE. When this happens networkmanager is not available and I have to restart it, with a crash of plasma as a result. So the only way is to log out, restart networkmanager and log in as user again.
On another computer I had the same error but then they disappeared, have seen it there only once more. But on the other one it happens 2 out of 3 boots. This really needs fixing, please.

Why I've been asigned to this bug? If below sysvinit is a service not
started this belongs to the service.

For the postfix problem below systemd: do the commands

     systemctl enable postfix.service
     systemctl start postfix.service

help?

For me the postfix is not the problem, I can not use systemd because it doesn't work with an encrypted /tmp.

But this bug is, for me, about a crashing consolekit, as it appears, and in my case appears to be the result of something with network manager, although I am not sure which one is cause or result.

This sounds like a race condition. I am not able to reproduce this here, never got this error. Does this also happen with gdm? Could someone test that (setting /etc/sysconfig/displaymanager:DISPLAYMANAGER="gdm")?

Assuming gdm means Gnome? I installed Gnome in the same system, logged in once using systemd, no problem, rebooted with sytem V, logged in into Gnome, same error.
But then in Gnome a message appears that something went wrong with the option to log out, which I did. Retried to log in and now was ok. So it seems to usually be once, this error, and loggin in the 2nd time solves the problem somehow. Hope this helps.

Sorry , too late to select needed info thingy

When I do "service network restart" I see after the networkmanager starts that it counts to 30. When I boot my system I think it is this that causes the error of consolekit because when I wait this time before I try to login it works, when I login immediately I get the error.
On my wife's netbook I usually don't get the error because it is much slower so the count down is already over when I can log in. I would really appreciate it if this bug got fixed.

IMHO, this sounds like a systemd related issue and no ConsoleKit problem. More concrete, I don't think systemd is directly responsible but rather the sequence in which the services are started. However, I don't know how to debug systemd, so assigning to the systemd maintainer.

should like bnc#728731 ?

It would be nice to get this fixed for those using sys v. For me systemd is now fixed so I switched to systemd, where this bug does not happen.

(In reply to comment #8)

Holger? Are you aware that the problem occurs with SysVinit booted?
That is that one of the boot scripts used for ConsoleKit will not
work.

Ok, I mixed things up, so this is no systemd issue, thanks for the pointer. A couple of questions, though:

1. After installing GNOME, did you also set gdm as login manager? More preciecly, is /etc/sysconfig/displaymanager:DISPLAYMANAGER="gdm" set? (if not, set it and run SuSECconfig)

2. This only happens with automatic login, right? To test, and without disabling automatic login, you can boot with a '3' appended to the grub command line. Once booted, login as root and enter 'init 5' to bring X up. Also happening?

3. There is nothing obviously changed with the ConsoleKit package, at least nothing I think is related. Could you also give the output of 'rpm -qa | grep ConsoleKit'?

Thanks.

1. Tried it again with gnome, set as you told, and then the error does NOT appear.

2. I do not auto log in since I have an encrypted home

3. ConsoleKit-x11-0.4.5-6.2.2.x86_64
ConsoleKit-32bit-0.4.5-6.2.2.x86_64
ConsoleKit-0.4.5-6.2.2.x86_64

(In reply to comment #12)
> Ok, I mixed things up, so this is no systemd issue, thanks for the pointer. A
> couple of questions, though:
> 
> 1. After installing GNOME, did you also set gdm as login manager? More
> preciecly, is /etc/sysconfig/displaymanager:DISPLAYMANAGER="gdm" set? (if not,
> set it and run SuSECconfig)

I did not "install" gnome (neither I do use it): 

I updated from 11.4 to 12.1 with all of KDE/GNOME/XFCE being installed.
I *use* xfce4 at login, not gnome, and I don't use gdm:

$ grep DISPLAYMANAGER= /etc/sysconfig/displaymanager
DISPLAYMANAGER="kdm4"

using gdm is not really an option -- and right now I don't want to kill my session, so the gdm test might take some time (sometimes after Xmas is always a good 1st estimate;)

> 2. This only happens with automatic login, right?

no. I *never* use automatic logins!
this happens with normal login from kdm4 to xfce4, but only when booting with sysvinit (not really needed anymore right now since most systemd issues are solved or workarounds exist, but still sysvinit should work without errors and complains too).

> 3. There is nothing obviously changed with the ConsoleKit package, at least
> nothing I think is related. Could you also give the output of 'rpm -qa | grep
> ConsoleKit'?


ConsoleKit-devel-0.4.5-6.2.2.x86_64
ConsoleKit-x11-0.4.5-6.2.2.x86_64
ConsoleKit-0.4.5-6.2.2.x86_64
ConsoleKit-32bit-0.4.5-6.2.2.x86_64

(In reply to comment #13)
> 1. Tried it again with gnome, set as you told, and then the error does NOT
> appear.

Ok, interesting to hear that both of you are using kdm4 as login manager. Can you please attach /var/log/boot.log and /var/log/messages to this bug? Thanks.

> 2. I do not auto log in since I have an encrypted home

Ok, the reason I'm asking is that I suspect this error to happen if you boot and log in very fast. So, for clarification, does it also happen if you boot (includes entering password for encrypted home) and afterwards stay at the login prompt for about, let's say, one whole minute? 

> 3. ConsoleKit-x11-0.4.5-6.2.2.x86_64
> ConsoleKit-32bit-0.4.5-6.2.2.x86_64
> ConsoleKit-0.4.5-6.2.2.x86_64

I use only kde, but installed gnome for this bug to try. Afterwards I overwrote everything with partimage to be back at my own system, so I am afraid I have no log files anymore. On my wife's netbook with a C50 CPU, which is much slower than my duo2core, I had the problem only a few times, and I think it is because I can log in much later, so I also had the feeling it had to do with time. But when I tried it on mine, it didn't make much of a difference. But when the error kept appearing, in the end I tried the following: I killed X, and retried, and usually the 2nd or 3rd time everything was ok.

btw the password for the encrypted home is entered during log in. I couldn't log in into my encrypted home using gdm, complained about not being able to write some .Ice...  Then I tried a non encrypted home login and that worked well. Rebooted and tried again, same thing.

What kind of crypto setup do you have? The one I know (might have changed meanwhile) asks for the password of the encrypted home partition during boot, not during login. Did you manage your encryption through YaST or manually?

I actually have no idea how to find out which kind of crypto setup I have, all I did was set it up using Yast. And yes, I am asked at login, not during boot, which makes sense since I have more users on the same system using encrypted home.

(In reply to comment #17)
> What kind of crypto setup do you have? The one I know (might have changed
> meanwhile) asks for the password of the encrypted home partition during boot,

correct, crypt-startup with passphrase happens at boot time in 
/etc/init.d/boot.crypto


> not during login. Did you manage your encryption through YaST or manually?

plain yast setup (from opensuse 11.0 (installed June 2008) upgraded through all versions though, no new 12.1 installation).

I have the same problem.
KDE4, check.
autologin? check.
encrypted boot? check. (root device on encrypted partition)
using systemd "solves" the problem? check.

Ok, systemd seems to work fine for everybody now, and if not, we should fix the bugs there. Sorry, it's not realistic that I will find the time to look into this for systemV, so closing sooner than later.