| 1 |
One last RFC before this will be implemented. News will be displayed to anyone |
| 2 |
having sys-auth/consolekit installed. |
| 3 |
|
| 4 |
|
| 5 |
Title: Desktop profile switching USE default to elogind |
| 6 |
Author: Andreas Sturmlechner <asturm@g.o> |
| 7 |
Posted: 2020-04-13 |
| 8 |
Revision: 1 |
| 9 |
News-Item-Format: 2.0 |
| 10 |
Display-If-Installed: sys-auth/consolekit |
| 11 |
|
| 12 |
Modern desktop environments make use of PAM session tracking for users, login |
| 13 |
sessions and seats. [1] The most user-visible part of that is device and file |
| 14 |
permissions management and reboot/shutdown handling without superuser rights. |
| 15 |
|
| 16 |
Users with systemd can stop reading here and continue with their daily |
| 17 |
routine. |
| 18 |
|
| 19 |
ConsoleKit2 is unmaintained upstream for almost two years [2]. There are many |
| 20 |
longstanding bugs and papercuts with consumers that aren't being fixed, not |
| 21 |
least because these code paths receive very little testing. |
| 22 |
|
| 23 |
Enter the elogind project [3], which is a standalone logind implementation |
| 24 |
based on systemd code, currently maintained by a fellow Gentoo user. We have |
| 25 |
had sys-auth/elogind available in Gentoo since the beginning of 2017, and |
| 26 |
meanwhile it has gained support [4] in KDE Plasma, Gnome [5], Cinnamon, MATE |
| 27 |
and Xfce, as well as most other former consolekit consumers. |
| 28 |
|
| 29 |
Consequently, the desktop profile is switching away from consolekit to |
| 30 |
elogind. Users of sys-auth/consolekit who selected a different profile should |
| 31 |
consider doing the same. A guide is available [6]. Migration is easy, but if |
| 32 |
run from within a consolekit session that session may become broken. |
| 33 |
|
| 34 |
Rely either on the profile, or set USE="elogind -consolekit" in make.conf |
| 35 |
yourself. Make sure there is no consolekit debris in /etc/portage/package.use: |
| 36 |
|
| 37 |
# grep -R consolekit /etc/portage/package.use |
| 38 |
|
| 39 |
Rebuild all affected consumers and remove sys-auth/consolekit: |
| 40 |
|
| 41 |
# emerge --ask --changed-use --deep @world |
| 42 |
# emerge --depclean consolekit |
| 43 |
|
| 44 |
Optional, but recommended in case of trouble such as missing reboot/shutdown |
| 45 |
capabilities in the DM: |
| 46 |
|
| 47 |
# rc-update add elogind boot |
| 48 |
|
| 49 |
For users of startx instead of one of the supported DMs, do not forget to |
| 50 |
update ~/.xinitrc accordingly (ck-launch-session is gone without replacement). |
| 51 |
|
| 52 |
PS: Subsequently, this will lead to the last-riting of sys-power/pm-utils [7] |
| 53 |
which is dead even longer than the original ConsoleKit(1) project. KDE Plasma |
| 54 |
users sticking with sys-auth/consolekit are then going to lose suspend from |
| 55 |
GUI without superuser rights. |
| 56 |
|
| 57 |
[1] https://wiki.gentoo.org/wiki/ConsoleKit |
| 58 |
[2] https://github.com/ConsoleKit2/ConsoleKit2 |
| 59 |
[3] https://github.com/elogind/elogind/blob/master/README.md |
| 60 |
[4] https://bugs.gentoo.org/show_bug.cgi?id=elogind-support |
| 61 |
[5] https://blogs.gentoo.org/leio/2019/03/26/gnome-3-30/ |
| 62 |
[6] https://wiki.gentoo.org/wiki/Elogind |
| 63 |
[7] https://bugs.gentoo.org/659616 |
Archives