Reopening this again as the proposed solution by Harald is not even a workaround but probably considered by the majority of people as a mere hack as ANY display manager upstart script is executed in the first place only to see if /etc/x11/default-display-manager contains a DM of choice or not. With many DM conf files cluttering up /etc/init this adds additional overhead during system start which can be avoided.
A way more elegant solution would be for a corresponding DEB-package to check if the conf file for the respective display manager is already present in /etc/init (if disabled enabling it again) - if not, copy it from the DEB package and disabling any other DM conf files present in /etc/init. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1004932 Title: kdm.conf file not removed after dpkg-reconfigure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1004932/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
