http://bugzilla.opensuse.org/show_bug.cgi?id=1047427
http://bugzilla.opensuse.org/show_bug.cgi?id=1047427#c15
--- Comment #15 from Michal Srb
(In reply to Fabian Vogt from comment #13)
I see, so RESOLVED WONTFIX? Should I remove the SIGHUP handling in sddm to avoid killing the session needlessly?
It would be nice if sddm reloaded its configuration on SIGHUP anyway. I am guessing that YaST will send it SIGHUP even on other configuration changes - for example when enabling/disabling passwordless login. However, that sounds rather like a feature request...
I would say so, yes. What concerns me is, that I believe we had a DM (KDM, mainly or even exclusively used for KDE), that still supported XDMCP. Or am I wrong here?
The default DM for KDE used to be KDM and it supported XDMCP. It is still possible to use it today, but it's not the default.
It's not really obvious for the user, that remote access via VNC cannot work when not using gdm/xdm. In many/most cases the user even doesn't know, what a DM is ...
Ideally YaST should warn the user. Most users will try to enable VNC using YaST and YaST knowns which DM is currently in use. -- You are receiving this mail because: You are on the CC list for the bug.