Bug 14984

Summary:	drakdm has no immediate effect (you must reboot)
Product:	Mageia	Reporter:	David Walser <luigiwalser>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	doktor5000, mageia, ottoleipala1
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	drakxtools-16.49-1.mga5.src.rpm	CVE:
Status comment:

Description David Walser 2015-01-08 02:32:55 CET

When you use drakdm to change the DM (for instance, KDM to SDDM, or vice versa), it says it will immediately restart the prefdm service, which will log you out.  In Mageia 4, it does.  In current Cauldron, it has no immediate effect, and even if you log out, the DM has not changed.  Once you reboot, the change does take effect (I guess if you restart the prefdm service manually it would too).

Reproducible: 

Steps to Reproduce:

David Walser 2015-01-08 02:33:07 CET

CC: (none) => doktor5000

Comment 1 Otto Leipälä 2015-02-25 13:13:55 CET

Try this it's from neoclust wiki how to enable sddm.

systemctl disable prefdm.service && systemctl enable sddm.service
 
http://mageia.nicolaslecureuil.fr/

CC: (none) => ozkyster

Comment 2 Florian Hubold 2015-02-25 22:10:04 CET

That will not help in restarting the currently running DM. drakdm would need to be amended for the required logic to select between prefdm or and specific other dm, and restart them.

Apart from that, it would be
systemctl restart prefdm
although that's not a graceful logout, but a hard restart.

Comment 3 Otto Leipälä 2015-02-26 10:43:42 CET

Yes you are right i tested it too and it will not logout and change to sddm from kdm but restart it does it.

Comment 4 Thierry Vignaud 2015-02-26 11:28:06 CET

Colin, can you adapt perl-install/standalone/drakedm to the death of the dm service?

CC: (none) => mageia

Comment 5 Colin Guthrie 2015-02-26 13:19:06 CET

(In reply to Thierry Vignaud from comment #4)
> Colin, can you adapt perl-install/standalone/drakedm to the death of the dm
> service?


I thought I had in 8598eb09637c23d2f21d4807d30c691b5cb17dbd (note that display-manager.service is just an alias for prefdm.service so either should be fine to use in a restart or status command).


Personally, on my machine, I've gone off the beaten track and started using per-dm service files (gdm.service ssdm.service etc.) rather than the combined prefdm magic thing that reads sysconfig file and uses lookupdm stuff, but for normal installs, this should still work.

No idea why it wouldn't work.

Can one run "systemctl restart display-manager.service" in a shell and report what happens? If that does not work, does "systemctl restart prefdm.service" do the necessary?

Is /etc/sysconfig/desktop update correctly?

No idea why it wouldn't work unless you have a stray symlink to display-manager.service somewhere in /etc/ overriding the one shipped currently with rpm.

Comment 6 David Walser 2015-02-27 23:01:31 CET

Actually this is working now, it was fixed some time since I reported it.  Now, when it asks you if you really want to restart dm, you're immediately kicked out of X (it doesn't even gracefully log out, which would be preferable if possible) and it starts the selected DM.

Status: NEW => RESOLVED
Resolution: (none) => FIXED