Bug#729576: Bug#726763: gnome should depend on systemd-shim | systemd-sysv

Andreas Cadhalpun andreas.cadhalpun at googlemail.com
Sat Jan 4 16:02:23 UTC 2014


Control: reassign 726763 gnome-settings-daemon 3.8.5-2
Control: severity 726763 important

Hi,

I tested systemd-shim and, using it, suspend etc. from GNOME menus work 
agin with sysvinit/upstart.

So to resolve this bug, GNOME should depend on:
systemd-shim | systemd-sysv

This ordering ensures that installing GNOME does not switch the init 
system, but since it works with systemd as PID 1, the dependency can 
also be satisfied by systemd-sysv.

The best place to add this new dependency seems the 
gnome-settings-daemon, since it directly depends on systemd, which is 
not enough to provide the necessary working dbus interfaces.
Since gdm3 depends on gnome-settings-daemon, this will solve the issue 
in gdm3 menus as well.

I think that according to policy [1] systemd-shim should be Priority: 
optional and not extra, because gnome-settings-daemon is optional and 
packages must not depend on packages with lower priority.

Furthermore I changed the severity to important as I think this bug has 
a 'major effect on the usability' [2].

Best regards,
Andreas

1: http://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities
2: http://www.debian.org/Bugs/Developer.html



More information about the pkg-gnome-maintainers mailing list