Found a minor bug while working on the automated tests. My server and client are both Fedora 28 machines running trunk r20495.
In order to run into this issue, you have to start a server and use xrandr as a start option to resize the display as so:
xpra start-desktop --bind-tcp=0.0.0.0:2200 --start="xrandr -s 1920x1080" --start=xterm
Upon initial connection with
xpra attach ssh:user@host, the xterm will appear above the top of the session window. If you disconnect and reconnect, the Xterm appears at the top of the window as it should. I'll attach screenshots to demonstrate what I'm seeing. Alternatively, you can add
--start=i3 to the start command, and the bottom bar appears above where it should be on the first connection; it makes it more obvious what's going on.
Unfortunately, I have no idea what
-d logs I should be getting.
Screenshot of the initial connection
After disconnecting and re-attaching
third screenshot with i3 running to show the offset more clearly (replacing with a more reasonable file size)
Since we're capturing the whole screen as one buffer in desktop mode, if this is a bug in xpra then it is likely to be client side.
To answer your questions up front:
If I start and attach with OpenGL disabled, it works fine on the initial connection. If I start and attach with OpenGL enabled, that's where I see the offset. I'll retry this with
-d opengl,paint logs running; the initial connection and the second connection where it shows up properly.
For good measure, I'll also attach
-d paint when attaching without OpenGL for a comparison to a working case.
Shouldn't take me more than a few minutes.
-d opengl,paint logs of the initial connection.
-d opengl,paint logs of the second connection (same session)
-d paint logs of a different session, with a working initial connection
I retested this with a local setup - Fedora 28 workstation running trunk r20535.
I started a session with
xpra start-desktop :13 --start="xrandr -s 1920x1080" --start=xterm and attached with
xpra attach :13 (and also with
--opengl=no). Even connecting locally, I still see the offset.
It's pretty straightforward to trigger for me, but I should mention an important caveat:
My workstation has an Nvidia GTX 745, so I think that may be a contributing factor. In my experience, a lot of OpenGL weirdness usually stems from the Nvidia driver - my laptop has an Intel Iris Pro + Nvidia GTX 850 and the Primus bridge means the GPU is disabled 99% of the time, and I never seem to run into nearly as many OpenGL oddities as I do with my other machines that only use the Nvidia card. Of course, all of the mentioned machines run Fedora.
In the meantime, I'll play around with it a little bit and try a few more xrandr resolutions.
I still cannot reproduce.
To answer your questions:
xrandr --listmonitorsand this is the output:
[max@vorfuehreffekt ~] $ xrandr --listmonitors xrandr: Failed to get size of gamma for output default Monitors: 1 0: +default 1920/508x1024/271+0+0 default
As you can see, it lowered the virtual display's resolution from 1920x1080 -> 1920x1024, which about matches with the ~60 or so pixels missing from the bottom.
I'll retry and get the
xpra info and
-d metadata momentarily.
In the meantime, both my client and server have been updated to r20536.
after clicking re-initialize from the systray
Xpra info before connection
Xpra info after first connection
Xpra info after second connection disconnects
-d metadata of initial client connection (with offset)
-d metadata of second client connection (without offset)
Posted requested info, and I also ran an upgrade real quick and rebooted all my machines, and I still see the same issues. But, I'm still seeing the same driver version, which is the latest that is available, and has been for some time.
Well, I managed to reproduce a problem, just not the same symptom. And that's only using the laptop's 1080p screen. I will have to play with client resolutions to try to reproduce this more reliably, including your particular version of this bug.
Back from vacation!
I've upped my server and client to r20635 and I'm still seeing the exact same issue - I also don't see any solid black prints when starting with i3, just the offset bottom bar as shown in the i3 screenshot I already posted.
However I do get a DPI warning saying that it's set to 96x96 and it wanted 108x107, is that related?
@maxmylyn: do you use a wacky window manager by any chance?
Is this bug really caused by the first vs second connection, or just by the resizing that happens when you connect? Does it trigger again if you run this before re-connecting:
DISPLAY=:13 xrandr -s 1920x1080
@antoine: It's KDE, so maybe?
It triggers again if I run that in between connections.
Just to be clear:
Initial connection with
xrandr -s 1920x1080 set as a start command -> offset
Disconnect and reconnect -> Offset goes away
DISPLAY=:13 xrandr -s 1920x1080, then reconnect -> offset
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1967