what operating system is used on both the client and server, including the full version details
changes made to the default configuration, if any. This can be shown with the command: "xpra showconfig"
the desktop environment, window manager used - if applicable
anything that would make the setup unusual: number of screens, resolution, virtualization software, access via another remote desktop tool (VNC, RDP, ..), etc
Screen 0: minimum 320 x 200, current 7680 x 3240, maximum 8192 x 8192 eDP-1 connected primary 1920x1080+1920+2160 (normal left inverted right x axis y axis) 309mm x 174mm 1920x1080 60.02*+ 60.01 59.97 59.96 59.93 […] DP-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 3840x2160 29.98*+ […] HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-2-1 disconnected (normal left inverted right x axis y axis) DP-2-2 connected 3840x2160+3840+0 (normal left inverted right x axis y axis) 597mm x 336mm 3840x2160 60.00*+ 29.98 […] DP-2-3 disconnected (normal left inverted right x axis y axis)
the network setup, bandwidth constraints (ie: LAN or DSL)
the full command lines used both on the server and client
xpra start --start xterm --bind-tcp [::]:14300
xpra attach tcp:localhost:14300 --dpi=96 --desktop-scaling=1
the server log file (or output if no log file is used)
the environment (ie: %PATH% on MS Windows, $PATH and $LD_LIBRARY_PATH on Linux, etc)
"xpra info" for the session
how the software was installed and what version (in full)
xpra-html5:amd64 2.5-20181119r21028-1 xpra:amd64 2.5-20181119r21028-1 python2-xpra:amd64 2.5-20181119r21028-1 xserver-xorg-video-dummy:amd64 1:0.3.8-5
python2-xpra 2.5-20181120r21055-1 amd64 xpra 2.5-20181120r21055-1 amd64 xpra-html5 2.5-20181120r21055-1 amd64 xserver-xorg-video-dummy 1:0.3.8-5 amd64
is this a new problem or a regression? (if a regression, when did it start?)
It's a problem
are there other bugs that are similar?
Yes #2036, which still seems to occur, but collecting data before I reopen it.
are there other unusual issues / behaviour apart from this particular bug?
Yes #2036 points in a similar, albeit not quite same direction
is it reproducible reliably? and if so, how?
To my current understanding it occurs if
See attached (very large!) screenshot for example with *exact* coordinates
does this happen with all picture encodings?
does switching off certain features make a difference (ie: sound, opengl, clipboard)
include relevant parts of the log files - including enough context to investigate (not just the last line showing the error message, but not necessarily the whole log file either)
all files provided are in full, not edited and not truncated
does re-connecting help?
reconnecting (under identical circumstances) does not change behaviour
does it happen with other type of clients (different OS, etc)
not tested, not available
try to include the output of some of the diagnosis tools we bundle (ie: Network_Info.exe and Encoding_Info.exe on MS Windows, net_util.py and loader.py everywhere else)
if possible, follow the debugging instructions
Please request _specific_ debug information if you *really* need them. Compiling the information contained in this ticket took me over an hour already.
please don't use pastebins
This works absolutely fine here with gnome-shell, which re-opens the window on the first monitor.
Please try with a different window manager (something less exotic), and if the problem does come from awesome, please include the client's
-d workspace,events,geometry,metadata log output of the re-connection with awesome.
(trimming long description)
Not heard back.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2054