public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Sturmlechner <asturm@gentoo.org>
To: pr <pr@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] News Item v2: Desktop profile switching USE default to elogind
Date: Tue, 29 Oct 2019 16:01:49 +0100	[thread overview]
Message-ID: <2184987.AYBGTMIK51@tux200s> (raw)
In-Reply-To: <w6gwocp3zua.fsf@kph.uni-mainz.de>

Title: Desktop profile switching USE default to elogind
Author: Andreas Sturmlechner <asturm@gentoo.org>
Posted: 2019-10-31
Revision: 1
News-Item-Format: 2.0
Display-If-Installed: sys-auth/consolekit
Display-If-Profile: default/linux/alpha/17.0/desktop
Display-If-Profile: default/linux/amd64/17.0/desktop
Display-If-Profile: default/linux/amd64/17.0/desktop/plasma
Display-If-Profile: default/linux/amd64/17.1/desktop
Display-If-Profile: default/linux/amd64/17.1/desktop/plasma
Display-If-Profile: default/linux/arm/17.0/armv4/desktop
Display-If-Profile: default/linux/arm/17.0/armv4/desktop/plasma
Display-If-Profile: default/linux/arm/17.0/armv4t/desktop
Display-If-Profile: default/linux/arm/17.0/armv4t/desktop/plasma
Display-If-Profile: default/linux/arm/17.0/armv5te/desktop
Display-If-Profile: default/linux/arm/17.0/armv5te/desktop/plasma
Display-If-Profile: default/linux/arm/17.0/armv6j/desktop
Display-If-Profile: default/linux/arm/17.0/armv6j/desktop/plasma
Display-If-Profile: default/linux/arm/17.0/armv7a/desktop
Display-If-Profile: default/linux/arm/17.0/armv7a/desktop/plasma
Display-If-Profile: default/linux/arm/17.0/desktop
Display-If-Profile: default/linux/arm/17.0/desktop/plasma
Display-If-Profile: default/linux/arm64/17.0/desktop
Display-If-Profile: default/linux/arm64/17.0/desktop/plasma
Display-If-Profile: default/linux/hppa/17.0/desktop
Display-If-Profile: default/linux/ia64/17.0/desktop
Display-If-Profile: default/linux/m68k/17.0/desktop
Display-If-Profile: default/linux/powerpc/ppc32/17.0/desktop
Display-If-Profile: default/linux/powerpc/ppc64/17.0/32bit-userland/desktop
Display-If-Profile: default/linux/powerpc/ppc64/17.0/64bit-userland/desktop
Display-If-Profile: default/linux/sh/17.0/desktop
Display-If-Profile: default/linux/sparc/17.0/64ul/desktop
Display-If-Profile: default/linux/sparc/17.0/desktop
Display-If-Profile: default/linux/x86/17.0/desktop
Display-If-Profile: default/linux/x86/17.0/desktop/plasma

Modern desktop environments make use of PAM session tracking for users, login 
sessions and seats. [1] The most user-visible part of that is device and file 
permissions management and reboot/shutdown handling without superuser rights.

Users with systemd can stop reading here and continue with their daily routine.

ConsoleKit2 is unmaintained upstream for almost two years [2]. There are many 
longstanding bugs and papercuts with consumers that aren't being fixed, not 
least because these code paths receive very little testing.

Enter the elogind project [3], which is a standalone logind implementation 
based on systemd code, currently maintained by a fellow Gentoo user. We have 
had sys-auth/elogind available in Gentoo since the beginning of 2017, and 
meanwhile it has gained support [4] in KDE Plasma, Gnome [5], Cinnamon, MATE 
and Xfce, as well as most other former consolekit consumers.

Consequently, the desktop profile is switching away from consolekit to elogind. 
Users of sys-auth/consolekit who selected a different profile should consider 
doing the same. A guide is available [6]. Migration is easy, but if run from 
within a consolekit session that session may become broken.

Rely either on the profile, or set USE="elogind -consolekit" in make.conf 
yourself. Make sure there is no consolekit debris in /etc/portage/package.use:

# grep -R consolekit /etc/portage/package.use

Rebuild all affected consumers and remove sys-auth/consolekit:

# emerge --ask --changed-use --deep @world
# emerge --depclean consolekit

Optional, but recommended in case of trouble such as missing reboot/shutdown 
capabilities in the DM:

# rc-update add elogind boot

For users of startx instead of one of the supported DMs, do not forget to 
update ~/.xinitrc accordingly (ck-launch-session is gone without replacement).

PS: Subsequently, this will lead to the last-riting of sys-power/pm-utils [7]
which is dead even longer than the original ConsoleKit(1) project. KDE Plasma 
users sticking with sys-auth/consolekit are then going to lose suspend from 
GUI without superuser rights.

[1] https://wiki.gentoo.org/wiki/ConsoleKit
[2] https://github.com/ConsoleKit2/ConsoleKit2
[3] https://github.com/elogind/elogind/blob/master/README.md
[4] https://bugs.gentoo.org/show_bug.cgi?id=elogind-support
[5] https://blogs.gentoo.org/leio/2019/03/26/gnome-3-30/
[6] https://wiki.gentoo.org/wiki/Elogind
[7] https://bugs.gentoo.org/659616





      parent reply	other threads:[~2019-10-29 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26 18:39 [gentoo-dev] [RFC] News Item: sys-fs/cryfs-0.10.2 update Andreas Sturmlechner
2019-10-26 20:57 ` [gentoo-dev] Re: [RFC] News Item v2: " Andreas Sturmlechner
2019-10-28  0:38   ` [gentoo-dev] Re: [RFC] News Item v3: " Andreas Sturmlechner
2019-10-28 10:54     ` Ulrich Mueller
2019-10-29  9:58       ` Andreas Sturmlechner
2019-10-29 15:01       ` Andreas Sturmlechner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2184987.AYBGTMIK51@tux200s \
    --to=asturm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=pr@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox