xpra icon
Bug tracker and wiki

Opened 3 weeks ago

Last modified 11 days ago

#2054 new defect

context menu remains at outdated offset if window remains maximized across reconnection

Reported by: Thomas B. Rücker Owned by: Thomas B. Rücker
Priority: minor Milestone: 2.5
Component: server Version: trunk
Keywords: Cc:

Description (last modified by Antoine Martin)

what operating system is used on both the client and server, including the full version details

  • server: Debian Buster/Testing. Linux 4.18.0-2-amd64
  • client: Debian Buster/Testing. Linux 4.19.0-rc7-amd64
  • both are updated regularly. Xpra server was started on 2018-11-19, version information is for _running_ server.

    changes made to the default configuration, if any. This can be shown with the command: "xpra showconfig"

  • server: none (edited)
  • client: none (edited)

    the desktop environment, window manager used - if applicable

  • client: AwesomeWM, 4.2-5
  • server: started a plain XTerm, ran additional applications from within that

    anything that would make the setup unusual: number of screens, resolution, virtualization software, access via another remote desktop tool (VNC, RDP, ..), etc

  • While not at work, only internal display. 1920x1080
  • While at work:
    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)
    
  • server is a Qemu-KVM virtualized instance, no other Xserver/Desktop? manager is running

    the network setup, bandwidth constraints (ie: LAN or DSL)

  • server: 10 MB/s upstream
  • client: ~50-100MB/s LTEa
  • connection is tunnelled into server network via SSH port forwarding

    the full command lines used both on the server and client

  • server: xpra start --start xterm --bind-tcp [::]:14300
  • client: xpra attach tcp:localhost:14300 --dpi=96 --desktop-scaling=1

    the server log file (or output if no log file is used)

  • attaching log files:
    • /var/run/user/1000/xpra/\:0.log
    • /var/run/user/1000/xpra/Xorg.S1509.log
    • /var/run/user/1000/xpra/run-xpra

    the environment (ie: %PATH% on MS Windows, $PATH and $LD_LIBRARY_PATH on Linux, etc)

  • server: PATH="/home/tbr/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
  • client: PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
  • LD_LIBRARY_PATH is not used by either

    "xpra info" for the session

  • See attached xpra-info.txt

    how the software was installed and what version (in full)

  • Installed from xpra.org stable + beta repositories
  • server:
    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
    
  • client:
    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

  1. during 1-screen configuration the application (so far confirmed using deluge-gtk 1.3.15-2) window is maximized
  2. session is disconnected
  3. 3-screen configuration is established
  4. xpra reconnects with the mouse pointer being inside the area 1920x2160:3840x3240 (i.e. not in the same area as disconnected)
  5. The mouse is used to click anywhere in the maximized application and the application opens a context menu

See attached (very large!) screenshot for example with *exact* coordinates

does this happen with all picture encodings?

yes

does switching off certain features make a difference (ie: sound, opengl, clipboard)

  • opengl is always off
  • tried turning off sound, clipboard, bell, notifications, cursors, modal windows, keyboard synchronization with no difference in result. (did not reconnect session after changes)

    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)

  • client-net-util.txt - despite its claim, there are default gateways for IP and legacy-IP.
  • client-loader.txt
  • server-net-util.txt
  • server-loader.txt

    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

OK

Attachments (8)

:0.log (501.1 KB) - added by Thomas B. Rücker 3 weeks ago.
Xorg.S1509.log (352.2 KB) - added by Thomas B. Rücker 3 weeks ago.
xpra-info.txt (215.4 KB) - added by Thomas B. Rücker 3 weeks ago.
client-net-util.txt (9.6 KB) - added by Thomas B. Rücker 3 weeks ago.
client-loader.txt (1.9 KB) - added by Thomas B. Rücker 3 weeks ago.
server-loader.txt (1.9 KB) - added by Thomas B. Rücker 3 weeks ago.
server-net-util.txt (7.9 KB) - added by Thomas B. Rücker 3 weeks ago.
Screenshot_20181121_102316.jpeg (505.1 KB) - added by Thomas B. Rücker 3 weeks ago.

Download all attachments as: .zip

Change History (10)

Changed 3 weeks ago by Thomas B. Rücker

Attachment: :0.log added

Changed 3 weeks ago by Thomas B. Rücker

Attachment: Xorg.S1509.log added

Changed 3 weeks ago by Thomas B. Rücker

Attachment: xpra-info.txt added

Changed 3 weeks ago by Thomas B. Rücker

Attachment: client-net-util.txt added

Changed 3 weeks ago by Thomas B. Rücker

Attachment: client-loader.txt added

Changed 3 weeks ago by Thomas B. Rücker

Attachment: server-loader.txt added

Changed 3 weeks ago by Thomas B. Rücker

Attachment: server-net-util.txt added

Changed 3 weeks ago by Thomas B. Rücker

comment:1 Changed 11 days ago by Antoine Martin

Owner: changed from Antoine Martin to Thomas B. Rücker

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.

comment:2 Changed 11 days ago by Antoine Martin

Description: modified (diff)

(trimming long description)

Note: See TracTickets for help on using tickets.