[Pkg-systemd-maintainers] Bug#732623: Bug#729576: duplicate of bug #726763

[Andreas Cadhalpun]

Hi,

On 22.12.2013 22:33, Vincent Lefevre wrote:
> On 2013-12-22 21:20:18 +0100, Andreas Cadhalpun wrote:
>> I have lightdm installed parallel to gdm3 and just switched to lightdm.
>
> I had the same problem with both installed.
The problem is probably, that systemd is not PID 1.

>> I cannot reproduce the issue described in bug 732623, i.e. for me
>> all the four menu entries are there, independent of how often I
>> login/logout.
>
> Did you try with twm?
I just tried twm, but twm just hangs and gives many of the following errors:
console-kit-daemon[2535]: (process:2928): GLib-CRITICAL **: 
g_slice_set_config: assertion `sys_page_size == 0' failed

This same message comes (but only 6x) when using gnome-shell, but 
gnome-shell starts.

> Now, without logs from systemd, it's hard to tell the cause of
> the difference.
What logs would you like to see?

>>> If GNOME developers want to require systemd as the init system,
>>> I don't see this as a reason not to add the dependency. Users
>>> are not forced to install GNOME packages. And if they want GNOME,
>>> they would have to accept the consequences about the init system.
>> The problem is the policy [1]:
>> "Essential is defined as the minimal set of functionality that must be
>> available and usable on the system at all times"
>> So removing an essential package is not really allowed by the policy.
>
> There's the same problem with systemd-sysv itself. So, I don't think
> it is against the policy. This point is more for tools handling
> package installation and removal, and also to avoid two essential
> packages conflicting each other.
I think it is not acceptable that the default Debian installer (for a 
desktop system) does not install an essential package, which would be 
the case, if gnome depended on systemd-sysv. Currently I think there is 
no package that depends on systemd-sysv without alternative and 
systemd-sysv is a package that actually does nothing else (as far as I 
can tell), but replace sysvinit with a link to systemd.

Best regards,
Andreas