GNOME Bugzilla – Bug 554140
gdm should take care of dbus and ck prefix
Last modified: 2013-11-18 14:47:34 UTC
Steps to reproduce: if gdm install path is /usr/local, the it considers that dbus & ck are installed in it's path.... wrong: in my case: dbus-launch path is /usr/bin ck libexec dir is /usr/lib/ConsoleKit... Hal take care of this... Stack trace: Other information:
So we probably need to have console kit advertise advertise the location of ck-get-x11-display device before we can fix it. For dbus we can just rely on dbus-launch being in the path. Note though, it's a little strange because if we run the system dbus-launch then it won't know to look for service files and bus policy in the non-system prefix (not sure if that will be a problem)
Is there something I can try, as a workaround? Or, is there any other logs or information that is required to hep troubleshoot this? I'm having various other problems, and I want to make sure they are not related to this issue before digging any deeper. Thanks.
a workaround that may work (not sure) is creating symlinks from where dbus-launch and ck-get-x11-display-device are to where gdm expects them to be. Another workaround would be to install those packages into the same prefix as gdm.
Almost there now. That finally got GDM to launch, and present a newer looking login box, however it always says "Can not authenticate user" when clicking on my user. I watched the logfiles while launching GDM, and I no longer see the "Could not run helper: Failed to execute child process "/opt/gnome/lib/gdm/ck-get-x11-display-device" (No such file or directory)" errors, but I'm still not able to login via GDM.
do you have a pam file for gdm in /etc/pam.d/gdm ?
Yes, I have two: $> cat /etc/pam.d/gdm #%PAM-1.0 auth include system-auth account include system-auth password include system-auth session include system-auth $> cat /etc/pam.d/gdm-autologin #%PAM-1.0 auth required pam_permit.so
Just updated to Gnome-2.24.1, and although the gdm version didn't change...making the symlinks as mentioned above, did allow be to get logged in correctly.
Is it a good idea to be depending on a libexec executable from another package? I would think that if ck-get-x11-display-device and ck-get-x11-server-pid are usable external ABI for CK, then they should be somewhere in $PATH. Alternatively, I was wondering why the functionality of ck-get-x11-display-device and ck-get-x11-server-pid aren't put into a library, say, libck-util? Jon/Ray, any thoughts on that?
i tend to agree with you.
About putting the executables in $PATH or making a library?
library. I don't think it's a very big issue either way though. The number of programs that consume that interface is small, so a minor wart in the architecture isn't a huge deal in my eyes.
Well, I would work on some patches to make libck-util, but I wouldn't want to waste my time if they wouldn't be applied.
Ah, need mccann to chime in I guess. I don't maintain consolekit. Maybe should be discussed on ConsoleKit's bugzilla?
OK. Filed fdo bug 18427. https://bugs.freedesktop.org/show_bug.cgi?id=18427
Requested, at very least that libexecdir be added to the pc file in next release of ConsoleKit. Attachment depends on both https://bugs.freedesktop.org/show_bug.cgi?id=18427 (same as above comment by Dan) and https://bugzilla.gnome.org/show_bug.cgi?id=596388 are resolved as proposed.
Created attachment 144091 [details] [review] Allows GDM to detect libexec directories for GSD and CK, also fixes dbus_datadir.
i believe this is obsolete now.