[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#727708: init system coupling etc.

On 02/14/2014 01:52 PM, Steve Langasek wrote:
On Fri, Feb 14, 2014 at 07:49:32PM +0100, Andres Freund wrote:

I am not so sure it's there. The current version runs without systemd
but doesn't support everything
Based on what?  There is only one new interface in logind between v204 and
v208, an 'org.freedesktop.login1.Manager.GetUserByPID' method.  Are you
telling me that this is a critical feature for desktops, that they won't run
correctly without?
Nono, that's not what I meant, sorry for being imprecise. Logind calls
out to systemd for shutting down. -shim now supports some of that, but
the last time I tried logind without systemd but just -shim didn't work
fully yet?
systemd-shim+logind is working fine in Ubuntu - and shutdown is pretty basic
functionality, that's expected to work.  I have recently seen some reports
(via IRC) that logind-based logout is not working from GNOME in unstable,
even when running systemd as PID1.  So there may be some bugs here, but I
have yet to receive any bug reports on the systemd-shim package pointing to
a problem with systemd-shim vs. systemd compatibility.

has any one reported this bug on systemd 205 and up also systemd 207 was a bug's fix release and systemd 204 is really dated i use systemd 204 in Debian testing but the ABI's have change with cgroup's for a newer systemd then 204.

but on the other hand Wayland support in Mutter relies on logind to handle VT switching this is a nice little rabbit hole that needs looked into Wayland-Mutter requires logind from a PID 1 systemd "critical feature" and Mir will too as well as they share some code no? down the road also systemd 208 has a major addition to logind for Wayland

Reply to: