Le Sun, 4 May 2014 18:32:14 +0200, Kurt Roeckx <k...@roeckx.be> a écrit :
> On Sun, May 04, 2014 at 04:07:47PM +0200, Laurent Bigonville wrote: > > Package: argyll > > Version: 1.5.1-5+b1 > > Severity: normal > > > > Hi, > > > > Now that systemd has been selected as the default init system, all > > session tracking is done via logind and consolekit is not needed > > anymore. > > So what about other init systems? Isn't it useful to have it on > them? With other init, logind will also still be used, but to make it work (with systemd >> 204) you need to have systemd-shim installed. systemd-shim is pulled by libpam-systemd (systemd-sysv | systemd-shim) since a week. GDM, KDM and lightdm (and tty sessions via libpam-systemd) are already creating a logind session when it's running. If a software really requires consolekit it should explicitly depend on it. > > argyll is installed (via a chain of recommends) by > > task-gnome-desktop and I guess we don't want to have consolekit > > installed on these systems after they fully have migrated to logind. > > Is there a reason you don't want it? Will it break things? > Doesn't that mean you need to do something so that it can be > installed at the same time so things don't break? We could maybe replace it by: Recommends: libpam-systemd [linux-any] consolekit will not break anything, but I'm however not sure we want to have it installed by default when installing GNOME as it's (or it will be) completely useless. In this case it's only needed to have the permissions properly set for the devices and as long has you have a session (logind or consolekit) registered it should be OK. But like said the tag in the udev rule file should be adjusted too. Cheers, Laurent Bigonville -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140504192030.09bd7...@fornost.bigon.be
