Closed CorbinWunderlich closed 1 week ago
Sorry, I didn't realize that I wasn't using start-desktop.
In seamless mode, there can only be one display manager: xpra
or i3
.
If i3
claims the _NEW_WM_CM_S0
selection, then xpra should have printed the message:
https://github.com/Xpra-org/xpra/blob/0dfe55ed50404565e53d4fab4a47ea4d5295c4ec/xpra/x11/gtk/wm_check.py#L111-L115
Did it?
xpra --use-display [display]
This is not a valid command.
Xpra Server Version 6.1.3
This is out of date.
In seamless mode, there can only be one display manager:
xpra
ori3
.If
i3
claims the_NEW_WM_CM_S0
selection, then xpra should have printed the message:Did it?
xpra --use-display [display]
This is not a valid command.
Xpra Server Version 6.1.3
This is out of date.
Hm. It's working great for me now. Using start-desktop instead of start allows me to use my own wm.
Using start-desktop ...
Yes, that's desktop mode. xpra start
is seamless mode.
The more modern syntax is :xpra desktop
or xpra seamless
instead of xpra start-whatever
Using start-desktop ...
Yes, that's desktop mode.
xpra start
is seamless mode.The more modern syntax is :
xpra desktop
orxpra seamless
instead ofxpra start-whatever
Alright. No complains, so far the best remote desktop solution I've tried. html5 client has some audio latency but it seems to be a known issue and it isn't a necessity. Thanks for creating this great software!
Describe the bug When trying to use the --use-display flag with xpra to take over a gpu-accelerated display, if that is running i3, the display will crash back to the display manager, and if I wrap i3 in say, xfce, it just becomes a seamless session with all the windows on that display. I tried this with plasma, and it worked flawlessly. I am using the html5 client.
To Reproduce Steps to reproduce the behavior:
System Information (please complete the following information):
Additional context Add any other context about the problem here. Please see "reporting bugs" in the wiki section.