Bug#726763: Gnome depends on systemd being PID 1

[Andreas Cadhalpun]

Hi,

in the last week there have been three bug reports (#731426, #731602, 
#731686) concerning the same problem as described in this bug: Gnome 
depends on systemd being PID 1 for suspend/hibernate/reboot/poweroff to 
fully work in all menus.
Each of these bug reports was against a different package, so the 
reporters did not find an existing report on the issue.

I think that the gnome package in its current state should at least 
recommend systemd-sysv, since this package (or the boot parameter 
'init=/bin/systemd') "would be found together with this one in all but 
unusual installations" [0].

The problem with this is that systemd-sysv replaces sysvinit, which is 
an essential Debian package, thus systemd-sysv cannot be a dependency, 
at least until the technical committee has decided on the init system 
issue (#727708).

On Fri, Oct 18, 2013 at 10:07:49PM +0200, Michael Biebl wrote:
 > Working suspend/resume requires systemd to be PID 1 [1].
 > Boot with init=/bin/systemd for that.
 >
 > I'll probably add a small notification on first login with instructions
 > how to do that.

It seems that this notification is either not yet added, or normal users 
do not find it, as they are still confused and report bugs about the 
issue. So please add this notification in a prominent place to avoid 
countless duplicates of this bug report.

Best regards,
Andreas


0: 
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps