Changes between Initial Version and Version 1 of Ticket #2434
- Timestamp:
- 10/01/19 06:03:33 (19 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2434
-
Property
Status
changed from
new
toclosed
-
Property
Resolution
changed from
to
duplicate
-
Property
Status
changed from
-
Ticket #2434 – Description
initial v1 1 1 I am running 64-bit xpra 3.0, newly installed from xpra PPA, on ubuntu 18.04 on both server and client. 2 2 3 The client has a dual-screen setup, with a laptop screen 1440x900 and an external display of 1280x1024 (both of those are well over a decade old! That's why I connect them to a server with speedier hardware!). This is an extended desktop setup. I am running gnome desktop, but not wayland or gnome3 bu rin a "fallback" desktop environment with metacity Window manager3 The client has a dual-screen setup, with a laptop screen 1440x900 and an external display of 1280x1024 (both of those are well over a decade old! That's why I connect them to a server with speedier hardware!). This is an extended desktop setup. I am running gnome desktop, but not wayland or gnome3 but in a "fallback" desktop environment with metacity Window manager 4 4 5 5 I put my browser windows on the external display. When I maximize them (e.g. by hitting the maximization the maximization button on the window, or by using keyboard shortcut), the window fills the external display (1280x1024), as expected. … … 12 12 13 13 P.S. I got these errors on the client side several times, don't know whether they are related to the bug: 14 {{{ 14 15 2019-10-01 00:15:13,208 Error handling unmap event 15 16 Traceback (most recent call last): … … 27 28 gtk.Window.do_unmap_event(self, event) 28 29 GLib.GError: g-invoke-error-quark: Class GtkWindow doesn't implement unmap_event (1) 30 }}}