Bug#729576: duplicate of bug #726763

[Vincent Lefevre]

Hi,

On 2013-12-22 21:20:18 +0100, Andreas Cadhalpun wrote:
> On 22.12.2013 20:41, Vincent Lefevre wrote:
> >Sorry, I mixed up two bugs related to systemd and with similar bug
> >number (the other one is 732623, where the installation of systemd
> >breaks some lightdm features).
> I have lightdm installed parallel to gdm3 and just switched to lightdm.

I had the same problem with both installed.

> 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?

Now, without logs from systemd, it's hard to tell the cause of
the difference.

> >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.

> >>Have you tried using systemd as PID 1?
> >
> >No, I don't want to do such kind of risky test. Since I was not
> >using the GNOME desktop environment, but just gdm3 and some GNOME
> >apps, I decided to drop those that depend on systemd. For me,
> >this meant:
> >   * gdm3 -> lightdm (but systemd must *not* be installed due to
> >     bug 732623),
> Since this problem does not occur for me and I am using systemd as it was
> meant to be used, i.e. as PID 1, perhaps you may want to reconsider trying
> systemd as PID 1?
> By the way, that is not 'risky' in any way: You can just edit the boot entry
> in grub (or whatever boot loader you use) by appending 'init=\bin\systemd'
> (with the package systemd installed). With this, you can try booting with
> systemd just for one session, without changing any configuration on your
> hard disk.

I'll have to think to try that on my desktop machine (which is much
faster to do various tests than my old laptop).

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)