Windows that are resized when not visible have black regions.

[timthelion]

Using a tiling window manager, if I have two windows side by side and then full screen one, then the other will be resized to full screen size when it is not visible. If I then switch to that window, I will see a black region in the window which covers the newly added space. If I then resize the window again while it is visible, the bug goes away.

Here is a screenshot:

You can see that the bottom half of the window is black.

This is on:

$ xpra --version
xpra v0.17.5

[Antoine Martin]

converting to attachment

[Antoine Martin]

Please provide:

• which window manager can be used to reproduce (exact version, distro, etc)
• which applications are affected? (all?)
• "2 windows side by side", what windows are those? Does it matter?
• please attach the "-d geometry" debug output (both client and server)
• can you reproduce with a supported version? (0.17 was EOL last year)

[timthelion]

1) stumpwm on debian jessie: ​https://packages.debian.org/jessie/stumpwm
version 2:0.9.8-7
2) All applications are effected.
3) Doesn't matter. To reproduce press ctrl-t s ctrl-t q with two xpra windows open. The one that isn't focused will be cut when you use ctrl-t space several times to switch to it.
4) I'll get back to you on this in a moment.
5) Is there something wrong with the debian packaging process? Sid still has 0.17 ​https://packages.debian.org/sid/xpra

[Antoine Martin]

Do you have those log samples?
I'll try to carve out time to test this during the 2.1 release cycle - doesn't look too hard.
As for sid shipping a broken version, this is a recurring theme which we have documented: wiki/Packaging/DistributionPackages.

[timthelion]

xpra server log with -d geometry

[timthelion]

Sorry for not getting back to you sooner. I got sidetracked by my inability to tell xpra where to store the log file. Despite setting the --log-file flag, it seems to always store it in ~/.xpra/Xorg.:100.log . Thus my email question about why the if statement was written that way.

But that doesn't give me a client log file and this mess isn't really readable for you: (So I'm going to have to launch xpra normally and not in a container.)

Starting xpra client...
['run', '--rm', '--cidfile', '/tmp/subuser-!service-subuser-xterm-xpra-client', '-e', 'XPRA_SOCKET_HOSTNAME=server', '-e', 'TMPDIR=/home/timothy/tmp', '-e', 'HOME=/home/timothy', '--workdir=/home/timothy', '--net=none', '-e', 'DISPLAY=unix:0.0', '--volume=/tmp/.X11-unix:/tmp/.X11-unix:rw', '--volume=/home/timothy/.subuser/volumes/x11/17337/!service-subuser-xterm-xpra-client/.Xauthority:/subuser/.Xauthority:ro', '-e', 'XAUTHORITY=/subuser/.Xauthority', '--volume=/home/timothy/.subuser/volumes/xpra/xterm/xpra-home/tmp:/home/timothy/tmp:rw', '--volume=/home/timothy/.subuser/volumes/xpra/xterm/xpra-home/.xpra/xpra-serverdf8a9e65759fe10ef0121a796fc75ef76b4948bce28275cf592a-100:/home/timothy/.xpra/server-100:rw', '-e', 'USER=timothy', '--user=1000', '--hostname', 'b2d663d2e9da187f6b43', '--entrypoint', '/usr/bin/xpra', 'sha256:97998b3ac53afe43c63c24c3739f3f7d982eb8c32c26ae138029f6b4fc4a21f3', 'attach', '--no-tray', '--compress=0', '--encoding=rgb', '--border', 'red', '-d', 'geometry', '--no-daemon', '--no-notifications', '--mmap', '--opengl=no', '--no-system-tray', '--cursors', '--clipboard']
2017-03-20 14:06:38,857 Error: no encryption libraries could be loaded
2017-03-20 14:06:38,857  pycrypto is not available: No module named Crypto
2017-03-20 14:06:38,857  python-cryptography is not available: No module named cryptography
2017-03-20 14:06:38,858 Xpra gtk2 client version 0.17.5-r13454
2017-03-20 14:06:38,858  running on Linux debian stretch/sid
2017-03-20 14:06:38,858 Warning: failed to import opencv:
2017-03-20 14:06:38,858  No module named cv2
2017-03-20 14:06:38,859  webcam forwarding is disabled
Warning: failed to import GStreamer:
GStreamer 1.0: Namespace Gst not available
GStreamer 0.10: No module named pygst
2017-03-20 14:06:39,009 Error: failed to query sound subsystem:
2017-03-20 14:06:39,009  query did not return any data
2017-03-20 14:06:39,519 Error setting up dbus signals:
2017-03-20 14:06:39,519  org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
2017-03-20 14:06:39,613  detected keyboard: rules=evdev, model=pc105, layout=cz
2017-03-20 14:06:39,614  desktop size is 1920x1080 with 1 screen:
2017-03-20 14:06:39,614   unix:0.0 (506x285 mm - DPI: 96x96)
2017-03-20 14:06:39,615     eDP1 (276x156 mm - DPI: 176x175)
2017-03-20 14:06:39,873 enabled fast mmap transfers using 256MB shared memory area
2017-03-20 14:06:39,874 Xpra X11 server version 0.17.5-r13454
2017-03-20 14:06:39,874  running on Linux debian stretch/sid
2017-03-20 14:06:39,875 enabled remote logging
2017-03-20 14:06:39,876 Attached to :100 (press Control-C to detach)

2017-03-20 14:06:39,881 process_new_common: wid=1, OR=False, geometry([0, 0, 484, 316])=(0, 0, 484, 316, 484, 316)
2017-03-20 14:06:39,883 setup_window() position=(0, 0), set_initial_position=False, OR=False, decorated=True
2017-03-20 14:06:39,915 ['configure-window', 1, 1, 33, 1918, 1044, {'encoding.transparency': False, 'encodings.rgb_formats': ['RGB', 'RGBX']}, 0, {}, False, 1, (622, 512), []]
2017-03-20 14:06:39,920 map-window for wid=1 with client props={'workspace': 65535}, state={'frame': (0, 1, 0, 2)}
2017-03-20 14:06:39,922 ['configure-window', 1, 1, 33, 1918, 1044, {'screen': 0, 'workspace': 1}, 0, {}, False, 1, (622, 512), []]
2017-03-20 14:06:49,156 ['configure-window', 1, 1, 37, 1918, 511, {}, 0, {}, False, 1, (622, 513), []]
2017-03-20 14:06:49,159 ['configure-window', 1, 1, 37, 1918, 511, {}, 0, {'frame': (0, 5, 0, 6)}, True, 1, (622, 513), []]
2017-03-20 14:06:53,919 ['configure-window', 1, 1, 33, 1918, 1044, {}, 0, {'iconified': True, 'frame': (0, 1, 0, 2)}, True, 1, (622, 513), []]
2017-03-20 14:06:54,740 map-window for wid=1 with client props={'workspace': 1}, state={'frame': (0, 1, 0, 2)}
2017-03-20 14:06:54,743 map-window for wid=1 with client props={'workspace': 1}, state={'iconified': False, 'frame': (0, 1, 0, 2)}
2017-03-20 14:06:54,746 ['configure-window', 1, 1, 33, 1918, 1044, {}, 0, {}, False, 1, (622, 513), []]

got signal SIGTERM, exiting
2017-03-20 14:06:58,025 Error: printing disabled:
2017-03-20 14:06:58,025  No module named cups

[Antoine Martin]

Despite setting the --log-file flag, it seems to always store it in ~/.xpra/Xorg.:100.log

The "log-file" argument is for xpra's log file, "Xorg.:100.log" is Xorg's log file, not xpra's.
You can modify where that goes by editing the xvfb command line.
I had to edit comment:4 because the indentation was really messed up, never seen that before!

There's a client log file for what seems to be the same bug here: ticket:1469#comment:2.

[timthelion]

Aha, I think that this is clearly a dup of #1469.

[Antoine Martin]

Please see ticket:1469#comment:10.

[Antoine Martin]

Probably caused by buggy Intel drivers, see ticket:1469#comment:14.

[migration script]

this ticket has been moved to: ​https://github.com/Xpra-org/xpra/issues/1468