Bug 58955 - After the current display manager .service file is removed, the DM cannot be changed.
Summary: After the current display manager .service file is removed, the DM cannot be ...
Status: RESOLVED NOTOURBUG
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-02 19:25 UTC by Kwpolska
Modified: 2013-01-14 22:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Kwpolska 2013-01-02 19:25:58 UTC
If the .service file for the current display manager is removed, the DM cannot be changed cleanly.

[root@kwpolska-lin system]# systemctl enable lxdm.service
Failed to issue method call: File exists
[root@kwpolska-lin system]# systemctl disable kdm.service
Failed to issue method call: No such file or directory

The only fix is to manually remove /etc/systemd/system/display-manager.service and link it to the new DM, or temporarily rename a DM .service file to the one that got removed.

(I found out about the bug after getting rid of Plymouth, using kdm-plymouth.service instead of kdm.service.  Plymouth sucks under Arch Linux.)
Comment 1 Lennart Poettering 2013-01-14 22:35:53 UTC
You can use "systemctl enable --force".

That said, your packaging scripts are broken. The old display manager should have removed the symlink on removal. This is usually done from the package removal scripts of your display manager rpm. Please report this to your distribution, to the package of your old DM.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.