This is interesting.

They called it ConsoleKit2

Nice changelog:

Already a good thing to try out.

Even better.

The other cabal already "broke" it, so I guess no harm tweaking it. I'll take a look at what was in mind here and how it would affect the desktop code.


Of course this won't stop the deprecation attempts all over the place.

I'm glad, and not just because of Slackware. XFCE has always been good for portability, I'm glad they're keeping this up.

Whatever you might think of the relative merits of systemd, the comments on this Reddit thread about this particular act of apostasy are actually blowing my mind.

I took the link from there but I still didn't read the comments.

I'm a Xfce user and I see it like a really mature, non-bullshit DE.

But I fail to see how this kind of task has to be done by a small DE dev team like the Xfce one.

It's not like migrating to GTK3 was a higher priority or anything...

I was having the same thoughts.
If we dissect the post a little we can see this:

It seems this may be temporary until openbsd systemd-thingy work is complete (I think it was openbsd any way). I have a feeling other people will need to step up and help wit this over time - possibly not something xfce's small dev team can manage alone if we look over to the next few years rather than initial energy to create this.

I was browsing his changes, and it does seem to be done with the purpose to fix long broken things on BSD. (Right, BSD users?)

Curious why ConsoleKit was chosen--maybe it already has better support on BSD. Stop gap, he describes, but maybe he should give himself a bit more credit. I doubt logind actually contains anything to support BSD. ConsoleKit, with its flaws, can be a standard, if it is just finished up for BSD. And even better if Xfce wants to stay multiplatform.

The *BSDs are particularly fond of it.

I'm glad somebody is going to the trouble. Between this and KDE making encouraging noises it's been nice to have some news that isn't gloom about kampfgruppe Poettering.

2 members found this post helpful.

I read the comments up until:
So we are now at the point of actively discouraging people from developing free and open source software in their free time, if they are not employed by and pushing the agenda of some large Linux corporation? That would be a very sad state for the Linux community to be in.

5 members found this post helpful.

When I see how Lennart talks down to the eudev team by calling them "amateurs", I'm coming to the same conclusion as you.

3 members found this post helpful.

Nice example for quoting out of context. The context was Which means nothing more than "XFCE lacks manpower already and increasing the workload will make that situation worse."
Nothing about corporations here or about discouraging open source development, just a statement about project management.

2 members found this post helpful.

open source devs are allowed to do anything they want
based on how good and stable xfce is, i'd say they are doing a great job

all in all they are probably not paid to work on xfce

I have it built and working on my own system, and it seems to work well. Here's a sampler SlackBuild script I edited from Patrick's. For testing purposes, the patches normally used by Slackware are commented out. There is a note I added into the SlackBuild file for usage if you have Linux-PAM built for Slackware.

You will need the same ConsoleKit Slackware packages from /slackware-*/source/l/ConsoleKit plus the ConsoleKit2 sources from here for the current version of 0.9.2 found here: https://github.com/ConsoleKit2/Conso...-0.9.2.tar.bz2

The dependencies are the same, for now apparently, but for completion purposes, you should probably have pm-utils installed to allow ConsoleKit access to the power management systems to perform suspend/hibernation.

Attached Files

ConsoleKit2.SlackBuild.txt (5.5 KB, 24 views)

2 members found this post helpful.

In Xfce, do you still have shutdown/reboot/suspend/hibernate capability?

I still have them Robby.