Bug 728731 - Autologin issue: Cannot open ConsoleKit session: Connection was disconnected before a reply was received
Summary: Autologin issue: Cannot open ConsoleKit session: Connection was disconnected ...
Status: RESOLVED WORKSFORME
: 741556 (view as bug list)
Alias: None
Product: openSUSE 12.1
Classification: openSUSE
Component: KDE4 Workspace (show other bugs)
Version: Factory
Hardware: x86 Other
: P3 - Medium : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-07 19:05 UTC by Jürgen Mathwich
Modified: 2013-01-19 20:08 UTC (History)
10 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
error message screenshot (19.84 KB, image/jpeg)
2011-11-22 10:10 UTC, robert spitzenpfeil
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jürgen Mathwich 2011-11-07 19:05:28 UTC
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13

On a freshly Installed openSUSE 12.1 RC2 this message happens when enabling KDM AutoLogin 

"Warning: Cannot open ConsoleKit session: Unable to open session: Connection was disconnected before a reply was received".

The logon continues after clicking "Ok".





Reproducible: Always

Steps to Reproduce:
I can reproduce this by doing the following steps

1.) add a new user (maybe it also works with the first standard, non-root user) 
2.) enable Auto-Login for this user via /etc/sysconfig/displaymanager/ DISPLAYMANAGER_AUTOLOGIN
3.) init 3 --> init 5 --> error occurs (also after reboot)

After removing the user logon string from DISPLAYMANAGER_AUTOLOGIN and rebooting the message is gone again.
Comment 1 Stefan Dirsch 2011-11-07 20:23:25 UTC
KDM issue?
Comment 2 robert spitzenpfeil 2011-11-17 10:32:00 UTC
I see this as well, but it works after a cold reboot.

Currently I only see it when doing 'init 3 --> init 5'. Starting console-kit-daemon manually 'solves it'. I took as quick look at the systemd files and to me it seems console-kit-daemon should be started in 'graphical.target' / 'default.target'.
Comment 3 Will Stephenson 2011-11-21 20:46:17 UTC
So this is only on a fresh installation that was booted to runlevel 3 on first boot, instead of 5, correct?

Robert, was this with RC2 or final?

CCing Frederic as this is probably a systemd thing that consolekit is not started.
Comment 4 robert spitzenpfeil 2011-11-22 10:10:24 UTC
Created attachment 463371 [details]
error message screenshot

I'm using the final release version of 12.1 - this error message showed up after the update from 11.4 to 12.1 was done. Since then a couple of updates were pulled.

I _used_ to get this error message when I started up my system, did some work and chose to go to runlevel 3, do some work and go back to runlevel 5. I observed that the console kit daemon was not started, did it by hand and the next login would succeed.

As of _now_ the behaviour has changed a bit:

Going to runlevel 3 still terminates console kit daemon, going back to 5 initially doesn't start it. A login succeeds partially (I get a black screen and some plasma apps seem to be there, but invisible) and the console kit daemon gets started. After killing the X-server the next login works as it should.
Comment 5 patrick shanahan 2011-11-29 13:55:35 UTC
I see the same warning going from init 3 to init 5.  I boot into runlevel 3 so I always see the warning.

Bug is marked "Need info" but no request.  What info is needed?  I will attempt to supply.

System is x86_64 upgraded from 11.4 via zypper/tumbleweed.

note:  I do not see the warning on a laptop upgraded continuously from b1.
Comment 6 Axel Martens 2012-01-06 08:04:18 UTC
I get the same message when logging into KDM after switching from runlevel 3 to 5. The problem is that afterwards, I have trouble with sound and I am not able to mount any USB device.

After rebooting everything works properly (my standard runlevel is 5). But once I change to runlevel 3 and then back to 5, or boot into runlevel 3 and then go up to 5, I have those problems.

As with Robert and Patrick, the issue has come into being after I upgraded from 11.4 to 12.1 via zypper.

If any information will be needed to fix the problem, please let me know.
Comment 7 Jon Nelson 2012-02-02 02:53:50 UTC
Possibly related: bug #732642, bug #739772, bug#715467, bug #736695
Comment 8 Winfried Dobbe 2012-02-20 11:39:26 UTC
Same message here when going from runlevel 3 to 5. When doing a cold reboot message does not appear.

System was installed from final openSuse 12.1 DVD.

What info is needed?
Comment 9 Christian Trippe 2012-03-25 17:35:48 UTC
*** Bug 741556 has been marked as a duplicate of this bug. ***
Comment 10 Juraj Václavík 2012-05-06 07:19:06 UTC
I installed 12.1 64bit (AMD Ilano) from DVD, I updated into 4.8.2 - OK, and now updated into 4.8.3 - and I cannot log due "Cannot open ConsoleKit session: Connection was disconnected before a reply was received".
Comment 11 Christian Trippe 2013-01-19 20:08:50 UTC
Sorry that this bug did not really get any attention. However I have never seen this bug with openSUSE 12.2. So I'll close it as worksforme. If you can reporduce it with 12.2 or Factory please reopen.