[Bug 1047427] New: YaST - Remote Administration (VNC) kills Xserver, drops to root console login prompt
http://bugzilla.opensuse.org/show_bug.cgi?id=1047427 Bug ID: 1047427 Summary: YaST - Remote Administration (VNC) kills Xserver, drops to root console login prompt Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: bryan.gartner@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 731337 --> http://bugzilla.opensuse.org/attachment.cgi?id=731337&action=edit y2logs Steps taken - Bare metal install on laptop using openSUSE-Leap-42.3-NET-x86_64-Build0300-Media.iso (default install, KDE) - after install completed, used (CLI over ssh access) yast Network Services Remote Administration (VNC) Allow Remote Administration Without Session Management - get classic display manager must be restarted, but the Xserver has already crashed and system is sitting at a root console prompt (no GUI). YaST session is also hung (stuck at 66%, Restarting the Service). NIC is also down at this point. - if last step is run from within window manager, but as a normal user, the DM seems to restart, but network is still dropped. Could this be from not using/properly configuring wireless password into KDE wallet system? Also very similar to bug 1043917 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047427
http://bugzilla.opensuse.org/show_bug.cgi?id=1047427#c11
Fabian Vogt
Ok. So the culprit appears to be sddm. Reassigning.
I'm not sure how the VNC setup without session management is supposed to work and what sddm needs to support. Currently sddm maps SIGHUP to quit(), so it just quits on rcxdm reload. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047427
http://bugzilla.opensuse.org/show_bug.cgi?id=1047427#c12
Michal Srb
(In reply to Stefan Dirsch from comment #10)
Ok. So the culprit appears to be sddm. Reassigning.
I'm not sure how the VNC setup without session management is supposed to work and what sddm needs to support.
Currently sddm maps SIGHUP to quit(), so it just quits on rcxdm reload.
Both VNC with and without session management requires that the display manager communicates with XDMCP. So when you enable either of those modes in YaST, it will change the DISPLAYMANAGER_REMOTE_ACCESS to "yes" in /etc/sysconfig/displaymanager, then it will call the "/usr/lib/X11/display-manager reload" to reload the configuration, which sends SIGHUP to the display manager. By the way, sddm doesn't (yet) support XDMCP, so even if SIGHUP wouldn't kill it and it would reload the configuration, it would not be useful for VNC. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047427
http://bugzilla.opensuse.org/show_bug.cgi?id=1047427#c13
--- Comment #13 from Fabian Vogt
(In reply to Fabian Vogt from comment #11)
(In reply to Stefan Dirsch from comment #10)
Ok. So the culprit appears to be sddm. Reassigning.
I'm not sure how the VNC setup without session management is supposed to work and what sddm needs to support.
Currently sddm maps SIGHUP to quit(), so it just quits on rcxdm reload.
Both VNC with and without session management requires that the display manager communicates with XDMCP. So when you enable either of those modes in YaST, it will change the DISPLAYMANAGER_REMOTE_ACCESS to "yes" in /etc/sysconfig/displaymanager, then it will call the "/usr/lib/X11/display-manager reload" to reload the configuration, which sends SIGHUP to the display manager.
By the way, sddm doesn't (yet) support XDMCP, so even if SIGHUP wouldn't kill it and it would reload the configuration, it would not be useful for VNC.
I see, so RESOLVED WONTFIX? Should I remove the SIGHUP handling in sddm to avoid killing the session needlessly? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047427
http://bugzilla.opensuse.org/show_bug.cgi?id=1047427#c14
--- Comment #14 from Stefan Dirsch
I see, so RESOLVED WONTFIX? Should I remove the SIGHUP handling in sddm to avoid killing the session needlessly?
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? 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 ... -- You are receiving this mail because: You are on the CC list for the bug.
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.
participants (1)
-
bugzilla_noreply＠novell.com