Bug#767388: gdm3: (with default=kdm) gdm.service gives failed status

[Michael Biebl]

Control: tags -1 moreinfo
Am 30.10.2014 um 20:24 schrieb r.ductor:
> Package: gdm3
> Version: 3.14.0-1
> Severity: minor
> 
> Dear Maintainer,
> 
> I have kdm as default display manager.
> Systemd starts gdm.service,
> which contains an ExecStartPre assertion default=gdm
> that fails giving a failure log and a failure status.
> 
> I do not know if this is a bug or a feature,
> nor if I should report this to kdm,
> but in my mind having a programmatic failure in a normal situation
> should not be normal...
> 
> Thanks for your time
> ric
> 
> # cat /etc/X11/default-display-manager
> /usr/bin/kdm
> 
> # systemctl status gdm.service
> ● gdm.service - GNOME Display Manager                             
>    Loaded: loaded (/lib/systemd/system/gdm.service; static)       
>    Active: failed (Result: start-limit) since Thu 2014-10-30 09:19:36 CET; 10h ago
>   Process: 1145 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm3" ] (code=exited, status=1/FAILURE)                                  
>                                                                   
> Oct 30 09:19:35 IPhT-IA-004976 systemd[1]: Failed to start GNOME Display Manager.
> Oct 30 09:19:35 IPhT-IA-004976 systemd[1]: Unit gdm.service entered failed state.
> Oct 30 09:19:36 IPhT-IA-004976 systemd[1]: gdm.service start request repeated too quickly, refusing to start.
> Oct 30 09:19:36 IPhT-IA-004976 systemd[1]: Failed to start GNOME Display Manager.
> Oct 30 09:19:36 IPhT-IA-004976 systemd[1]: Unit gdm.service entered failed state.
>                                                                   

This is actually an issue due to kdm not shipping a native .service file
yet and not setting up the /etc/systemd/systemd/display-manager.service
symlink

We added a workaround to systemd by masking the non-default display
manager. So a gdm.service start should actually not be attempted.
What's the output of
ls -la /run/systemd/generator.early/display-manager.service ?

You should have a journal entry like this:
Jun 08 14:27:27 pluto systemd-default-display-manager-generator[13256]:
/lib/systemd/system/kdm.service is not a systemd unit, we disable the
systemd enabled display manager


Is that actually still an issue?
> Oct 30 09:19:36
Is your clock off or is that from an earlier systemd version?
Which systemd version do you have installed?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20150608/70ea2e17/attachment.sig>