Hello everybody, the current ebuilds for elogind are - sys-auth/elogind_225.9999::kde and - sys-auth/elogind-226.4::gentoo The following updates are there from upstream: - sys-auth/elogind_225.9999::kde The relevant branch was fully merged and thus deleted. The current live ebuild is: + sys-auth/elogind_228.9999::seden The current releases are: + sys-auth/elogind_227.4::seden (Used in Void Linux) + sys-auth/elogind_228.1::seden (Current testing) Cheers Sven
After all the cleanup and many hours of hard work, the first stable release of elogind is out: 229.3 This one has select patches from systemd/systemd-stable, and was the first major goal of development of elogind. Older possible releases to use are 227.4 and 228.3, but I reckon it is best to just bump to 229.3.
Sorry for the double post. I forgot to mention, that the next major goal is to update elogind further until it reaches v233-stable, as that is the current stable version of sys-apps/systemd.
Totally semi-random question (sorry) - does elogind work properly for CanGraphical seat property as will be needed for solving bug 613222? https://www.freedesktop.org/wiki/Software/systemd/writing-display-managers/
(In reply to Mart Raudsepp from comment #3) > Totally semi-random question (sorry) - does elogind work properly for > CanGraphical seat property as will be needed for solving bug 613222? > https://www.freedesktop.org/wiki/Software/systemd/writing-display-managers/ If systemd-login can, it should. Currently elogind-229.3 shows: ~ $ loginctl show-seat seat0 Id=seat0 ActiveSession=4 CanMultiSession=yes CanTTY=yes CanGraphical=yes Sessions=4 IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 However, I have to check whether all bits to give the correct answers via dbus are in place. (SeatAdded, SeatRemoved, PropertyChanges) The important piece seems to be: "Most prominently this is actually seat0 which comes up in text mode, and where the graphics driver is then loaded and probed during boot. This means display managers must watch PropertyChanged events on all seats, to see if they gain (or lose) the CanGraphical field."
Yeah, the property change is the key part here, so that once gdm learns to listen for it when it's not CanGraphical yet, it would all work nicely once the kernel driver init is done. Feel free to report the result of further findings on this in bug 613222 instead to be on a more on-topic bug than my interjection here, with a note saying "leio asked me to report logind behavior here" or something :D
Thanks, added 229.3 in git commit 45bdafa706c09957b864d3d22fe19edce88d4940
Works, thank you very much!
