You are not logged in.
Pages: 1
With GNOME 3.6, polkit and networkmanager moving to [extra], ConsoleKit has now been removed from the repositories. Any package that previously depended on it now relies on systemd-logind instead. That means that the system must be booted with systemd to be fully functional.
Could someone explain this to me? I've still got ConsoleKit installed, so whats the problem?
Last edited by nuc (2013-02-07 18:15:48)
Offline
It means nothing uses consolekit anymore, everything is built against logind instead. You can keep consolekit installed, but nothing will be using it unless you make it.
Offline
So now I am forced to to use Systemd. Hm, what happens if I just restart without configuring anything?
Offline
If you do a:
pacman -QmYou will see consolekit there. That means it is not in the repositories - it is in manually tracked packages - anymore. What you should do now is:
sudo pacman -R consolekitTo get rid of it completely. Then if any issues arise - they shouldn't - post back again.
Edit: and if you aren't systemd right now then you really should get around to switching over..
Last edited by headkase (2012-11-02 01:50:19)
Offline
So now I am forced to to use Systemd. Hm, what happens if I just restart without configuring anything?
You will probably join the list of people posting about how their systems don't work properly today.
Offline
@headkase: Yes, I was just hoping that only the dependencies in the PKGBUILDs changed, but that Applications can still use ConsoleKit internally
Last edited by nuc (2012-11-02 01:53:07)
Offline
Nope. Most of the apps will use one or the other as a build time dependency. When you're using a binary distribution, you get what the devs decide.
Offline
@headkase: Yes, I was just hoping that only the dependencies in the PKGBUILDs changed, but that Applications can still use ConsoleKit internally
Yeah, switch over to systemd. As I understand it: the functionality that used to be provided by consolekit is now provided by logind - part of systemd. I didn't find it too difficult to switch over to systemd and as a bonus my boot time drastically improved once I did. Also, once you are pure systemd it is brain-dead simple to manage the boot process - like saying "enable" or "disable" simple - in a command.
Edit: redundant department of redundancy brings you a delightfully redundant statement about redundant logind explanations.
![]()
Last edited by headkase (2012-11-02 02:04:32)
Offline
nuc wrote:@headkase: Yes, I was just hoping that only the dependencies in the PKGBUILDs changed, but that Applications can still use ConsoleKit internally
Yeah, switch over to systemd. As I understand it: the functionality that used to be provided by consolekit is now provided by logind - part of systemd.
Except now it actually works... ![]()
Offline
lol, must needs get my Login Manager to work ![]()
EDIT: Done, I think ![]()
EDIT2:
You are advised to move to netcfg or NetworkManager before embarking to systemd.
What about wicd? EDIT: There is a wicd.service, so I suppose it works.
EDIT3: This is what it sais when I do:
"sudo systemctl enable dbus.service"
The unit files have no [Install] section. They are not meant to be enabled using systemctl.What does that mean? Is that normal?
----->>> Moved to new topic: https://bbs.archlinux.org/viewtopic.php … 2#p1186052
Last edited by nuc (2012-11-02 02:35:46)
Offline
I have not used consolekit in ages and I am yet to miss a single feature. This entire fuzz puzzles me.
Offline
Pages: 1