Bug#562026: kdm cannot open ConsoleKit session on first login attempt
reassign 562026 libck-connector0 0.4.1-2
thanks
On Thu, Dec 24, 2009 at 2:02 PM, George Kiagiadakis
<kiagiadakis.george@gmail.com> wrote:
> On Tue, Dec 22, 2009 at 1:08 AM, Sergiy Yegorov <prapor@unixzone.org.ua> wrote:
>> Messages in /var/log/daemon.log
>> Dec 22 00:59:25 excelsior kdm: :0[2294]: Cannot open ConsoleKit session: Unable to open session: Method "OpenSessionWithParameters" with signature "a(sv)" on interface "org.freedesktop.ConsoleKit.Manager" doesn't exist
>> Dec 22 00:59:25 excelsior kdm: :0[2294]: Client start failed
>> Dec 22 00:59:25 excelsior kdm: :0[2294]: Cannot close ConsoleKit session: Unable to close session: no session open
>>
>> On second login attempt - no problems.
>> Bug reproduced on 3 different installations.
>
>
> I can reliably reproduce this bug on my laptop. Looks like consolekit
> has changed its dbus interface, as the service
> "org.freedesktop.ConsoleKit.Manager" doesn't exist indeed. There is
> only "org.freedesktop.ConsoleKit". I will investigate further...
>
After investigation, it seems that the dbus interface is ok.
org.freedesktop.ConsoleKit.Manager is an interface, not a service, and
the mentioned method with that signature exists.
Facts:
- It only happens right after boot.
- If you login to a tty prior to logging in with kdm, kdm works from
the first time.
- Running ps auxf from the kdm init script, I can see that consolekit
is not running right before kdm starts, so it must be kdm that first
uses it and activates the daemon. (I suspect the error has to do with
first-time activation)
- kdm does not use dbus directly, it uses the libck-connector library,
so the problem is obviously not kdm's fault. Thus, I am reassigning
this bug to libck-connector0.
- I am also using linux 2.6.32
The related code is here:
http://websvn.kde.org/branches/KDE/4.3/kdebase/workspace/kdm/backend/client.c?revision=986143&view=markup
(line 1325)
Reply to: