Support elogind as an alterantive session tracker for systemd-logind.

Yamakuzure Support elogind as an alterantive session tracker for systemd-logind.

For users who do not want to run the full systemd suite, but do not
want to patch sddm to use ck-launch-session either, elogind can be
used as an alternative session tracker via its PAM module.


sddm requires systemd to log errors

See #11018: sddm upgrade: missing logs and missing maui theme
for an example of an error that was not properly logged.
Upstream says that logging errors requires systemd :(

OpenRC GLEP proposal


There has been some serious concerns expressed in the Gentoo forums about the recent development of OpenRC. This blog entry tries to address them in a constructive, positive way. Should my personal opinion, expressed below, gain favourable reviews by the Gentoo community and by the OpenRC user community, this blog entry could be turned into a Gentoo Linux Enhancement Proposals (GLEP). If there is enough support for such a motion, the entire text below could be copied into the gentoo wiki, reformatted to fit the GLEP guidelines, and, of course, edited, amended and completed in which ever way the community sees fit in view of starting the official GLEP submission procedure. On the other hand, shouldn't there be any sufficient active support for such a motion, this blog entry will simply remain here, as a record of my opinion on the subject.

udev as unmet requirements for kdelibs

While working on #9109: How to replace udev with eudev?, I added -systemd -udev USE flags in make.conf, but got:

$ emerge -uDNat @world

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!

!!! The ebuild selected to satisfy ">=kde-base/kdelibs-4.14.22:4[aqua=]" has unmet requirements.

How to replace udev with eudev?

I am experiencing troubles with replacing udev with eudev. I encounter all kinds of conflicts, etc.

KDE and systemd


logind depends on systemd.
The bug below shows that KDE developers fully expect users to use logind and systemd:

Bug 360489 -  kscreenlocker suggests running "loginctl unlock-sessions" even though I don't use systemd  

A reply from a KDE developer says that they won't fix this for users not using systemd:

Martin Gräßlin 2016-03-14 :

Syndicate content