thoughtsetr.blogg.se - Problems with xquartz window size

#Problems with xquartz window size update
#Problems with xquartz window size Patch
#Problems with xquartz window size windows

+ #update the max packet size (may have gone up): + nd("desktop_size", root_w, root_h, self.get_screen_sizes()) + log.debug("sending updated screen size to server: %sx%s", root_w, root_h) #update the max packet size (may have gone up): nd("desktop_size", root_w, root_h, self.get_screen_sizes()) log.debug("sending updated screen size to server: %sx%s", root_w, root_h)

src/xpra/client/gtk2/client.py (revision 3560) If, for whatever reason, the root window size is not updated by the time we get our size changed event, this would help: Unless the log is not from the test case described in the ticket? I would expect to see "sending updated screen size to server: WxH", twice: one for each resolution change.

#Problems with xquartz window size update

There may be more than one screen, and we want to send the full display size, not just the screen that has changed.Īlso, from the logs, I see that we correctly set the screen size to 1650x1050 on connection (circa 21:25:16,***) and then we are notified that the screen resolution has changed (at around 21:25:28,***) and we correctly update the vfb size to 640x480.īut I see no trace in this log sample of the change back to 1650x1050, having the /trimmed/ client debug log would help. Tue, 09:45:40 GMT - Antoine Martin: owner, status, description changedĬhanged from Antoine Martin to Antoine Martin #update the max packet size (may have gone up): nd("desktop_size", root_w, root_h, self.get_screen_sizes()) Log.debug("sending updated screen size to server: %sx%s", root_w, root_h)

+ def _screen_size_changed(self, screen):

#Problems with xquartz window size Patch

It seems that when I change the resolution from R1 to R2 xpra sets the screen size to R1 and not R2! Here is a patch that fixes the problem for me:.

21:25:16,642 keyboard mapping already configured (skipped) 21:25:16,639 setting key repeat rate from client: 500ms delay / 33ms interval 21:25:16,621 mmap is enabled using 128MB area in /tmp/ 21:25:16,621 Python/Gtk2 Linux client version 0.9.4 connected from 'sauna' 21:25:16,619 Handshake complete enabling connection 21:25:16,371 New connection received: SocketConnection(/home/lindi/.xpra/sauna-7) The xpra server log shows how xpra continues to think that the resolution is 640x480 even after it has been set back to normal: The only workaround I have found so far is to disconnect and reattach xpra. Only a 640x480 pixel area in the upper left corner of each window is accessible.

#Problems with xquartz window size windows

in gnome System->Preferences->Monitors)Īll parts of xpra windows can be accessed with mouse

change resolution of the client machine to 640x480 temporarily.

Which version of GTK you are using - Happens both on versions in //master and is another bug from Timo (with patch) reported as is from.

The size of the css shadow should have no affect on the default size of the window. That the window default size correctly calculates the shadow area, and behaves on X11 like it does on Wayland. Subclasses of GtkWindow like AdwWindow are also affected.Īs you can see, when the shadows are big, there is a large difference between X11 and Wayland.Īlso for context, how much shadows can change the size of the window compared to small shadows. Which make this issue much more noticable and makes libadwaita apps quite broken on X11 (as default window sizes will be designed for how it behaves on Wayland, leaving X11 users with a pretty broken experience with oversized windows). The most visible example of this is the new Libadwaita shadows, which are significantly bigger than before, It should be 600x300, but apparently with legacy shadows on X11 it is 652x352. 600 300 Hello, World! Hello, World! True