https://bugs.kde.org/show_bug.cgi?id=527255
Bug ID: 527255
Summary: krdp exclusive mode does not return control to main
monitor after client disconnects
Classification: Plasma
Product: KRdp
Version First 6.8.0
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
DESCRIPTION
I followed the addition of the exclusive mode with interest, as this made
connecting to a host with a client whose resolution was different a lot more
useful. https://invent.kde.org/plasma/krdp/-/merge_requests/230
However, there may be some growing pains. After a client has connected to the
host and subsequently disconnected, the host seems to stay in "virtual display"
mode. I would expect it to return to the physical display.
The first problem this causes is just an inconvenience - upon physically
returning to my desktop (the host I was connecting to), the screen is black and
does not wake up. I found a workaround, by switching to another VT (for example
with Ctrl-Alt-F2) and then switching back with Ctrl-Alt-F1, the screen comes
back. But I should not need to do this.
The second problem it causes is more serious. I connect to this machine through
RDP for regular system maintenance tasks, but for gaming I connect to it with
Moonlight (with Sunshine running on the host). But Sunshine will not connect
properly if the physical display on the host is not "alive".
I have found that in this state, running commands I would use to wake up the
screen or query outputs through ssh, which used to succeed, now fail. For
example:
QT_QPA_PLATFORM=wayland kscreen-doctor -o
or
QT_QPA_PLATFORM=wayland kscreen-doctor --dpms on
(the latter I used to use to wake the display remotely)
These used to work (connected to the host PC through ssh), but now after
connecting and disconnecting through krdp, both fail with the following output:
Failed to create wl_display (No such file or directory)
Could not load the Qt platform plugin "wayland" in "" even though it was found.
could not connect to display
>From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform
plugin.
Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be
initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen,
vkkhrdisplay, vnc, wayland-brcm, wayland-egl, wayland, xcb.
The lines about xcb are not significant, they are only there because the
wayland platform plugin couldn't be loaded and it tried to fall back to that.
Normally QT_QPA_PLATFORM=wayland makes the wayland plugin get loaded.
STEPS TO REPRODUCE
1. Enable Exclusive mode in the Remote Desktop System Settings panel
2. Connect to the host from another PC (I tried both krdc and Remmina) and
disconnect.
3. Physically go back to the host PC, or try to connect to it using Moonlight
on the client and Sunshine on the host, or try to run kscreen-doctor commands
(even specifying the wayland platform plugin).
OBSERVED RESULT
The screen on the host PC is black and will not wake up even if you press the
keyboard or move the mouse, unless you go to another VT and back.
Connecting with Moonlight will fail with an error "is the screen on?".
Connecting with ssh to the host and using the kscreen-doctor commands above
will fail.
EXPECTED RESULT
The physical screen should show an image after disconnection from krdp. (i.e.
the virtual monitor that krdp created should be disabled and control should go
back to the physical one(s) ).
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window): CachyOS Linux
KDE Plasma Version: 6.8.0
KDE Frameworks Version: 6.31.0
Qt Version: 6.12.0
ADDITIONAL INFORMATION
krdp version: 6.8.0-1.1
freerdp version: 2:3.32.2-1.1
--
You are receiving this mail because:
You are watching all bug changes.
