Page 1 of 1
Consolekit
Posted: 20. Dec 2011, 23:52
by GJones
Is it just me or are Slackware and its descendants the only distros on which Consolekit works properly?
- Debian Squeeze and Debian Testing: broken
- Arch Linux: broken
- Ubuntu: broken
- Fedora: broken (or rather systemd appears not to handle CLI logins properly)
- Gentoo: broken, if all the forum posts are any indication
- Slackware (and Salix, etc.): ck-launch-session works with no problems.
I guess Mr. Volkerding is doing something right...
Re: Consolekit
Posted: 21. Dec 2011, 00:27
by Shador
In what regard is it broken with the others?
Re: Consolekit
Posted: 21. Dec 2011, 03:33
by GJones
ck-launch-session never creates an active session when used in .xinitrc, thus automount and power management don't work properly. Or, in some cases, creates an active session but somehow screws it up so that power management doesn't work. The only way to get a working consolekit session is to log in through one of the various bloaty display managers.
But wait a minute... The version of KDE on Slackware/Salix uses HAL, not consolekit/udisks. And pcmanfm-mod uses HAL too. Maybe it doesn't work on Slackware either, and I'm just not noticing because everything uses HAL. Hmm.
Re: Consolekit
Posted: 21. Dec 2011, 09:01
by thenktor
From my Openbox xinitrc:
Code: Select all
# start the openbox session, if possible attached to consolekit
if [ -e /usr/bin/ck-launch-session ]; then
exec /usr/bin/ck-launch-session /usr/bin/openbox-session
else
exec /usr/bin/ck-launch-session
fi
ck-launch-session is needed for my upower based logout tool (wm-logout)and it works.
PS: Who else can see the major bug in this xinitrc?
Re: Consolekit
Posted: 21. Dec 2011, 09:05
by gapan
Re: Consolekit
Posted: 21. Dec 2011, 10:04
by JRD
Lol thenktor !
About Systemd: it seems all the recent effort of freedesktop.org improvements for the desktop are merging using systemd. This is a problem in my opinion as systemd seems to be focused on Linux only (BSD and the like may have difficulties implementing it) and other thing, I don't think Patrick will ever switch to systemd one day...
Re: Consolekit
Posted: 21. Dec 2011, 10:05
by mimosa
Shouldn't it be like this:
Code: Select all
# start the openbox session, if possible attached to consolekit
if [ -e /usr/bin/ck-launch-session ]; then
exec /usr/bin/ck-launch-session /usr/bin/openbox-session
else
exec /usr/bin/openbox-session
fi
Incidentally, I discovered that locate in the Openbox beta hadn't set up its initial cache. I didn't rummage around to see if regular updates are scheduled, but I imagine not, either.
Re: Consolekit
Posted: 21. Dec 2011, 10:08
by thenktor
Yep mimosa, that's how it should be. Nobody complained about this, so probably every Salix Openbox user has ConsoleKit installed
Re: Consolekit
Posted: 21. Dec 2011, 10:19
by mimosa
I don't remember installing it, but it works. Just have a look ... yes it looks as though it came preinstalled:
Code: Select all
vanilla[disk-1]$ ls -l usr/bin | grep ck-launch-session
-rwxr-xr-x 1 root root 4308 Dec 19 2010 ck-launch-session*
Re: Consolekit
Posted: 21. Dec 2011, 13:08
by Shador
JRD wrote:Lol thenktor !
About Systemd: it seems all the recent effort of freedesktop.org improvements for the desktop are merging using systemd. This is a problem in my opinion as systemd seems to be focused on Linux only (BSD and the like may have difficulties implementing it) and other thing, I don't think Patrick will ever switch to systemd one day...
There are so many solutions for this. Patching/forking systemd, developing a version for BSD, continuing/forking console-kit, ...
IMO systemd seems a really worthwile development, as it simplifies daemon startup a lot. The current solution with the init scripts by keeping track of PIDs is very hackish and opposoed to the script solution systemd is much more robust an reliable. Probably the software has bugs as of now, but in the long run with those bugs eliminated, it can get up to a level of robustness and reliability init scripts just cannot reach by design.
