xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Changes between Initial Version and Version 1 of Ticket #2434


Ignore:
Timestamp:
10/01/19 06:03:33 (2 years ago)
Author:
Antoine Martin
Comment:

The Error handling unmap event should be fixed in r24051. Do you mind telling me how to trigger it? It was reported before but I just could not find a way to trigger it, which is why I left the warning.

But as soon as my cursor move to the laptop window, the maximization state is lost...

This is an exact duplicate of #2423.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2434

    • Property Status changed from new to closed
    • Property Resolution changed from to duplicate

  • Ticket #2434 – Description

    initial v1  
    11I am running 64-bit xpra 3.0, newly installed from xpra PPA, on ubuntu 18.04 on both server and client.
    22
    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 bur in a "fallback" desktop environment with metacity Window manager
     3The 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
    44
    55I 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.
    … …  
    1212
    1313P.S. I got these errors on the client side several times, don't know whether they are related to the bug:
     14{{{
    14152019-10-01 00:15:13,208 Error handling unmap event
    1516Traceback (most recent call last):
    … …  
    2728    gtk.Window.do_unmap_event(self, event)
    2829GLib.GError: g-invoke-error-quark: Class GtkWindow doesn't implement unmap_event (1)
     30}}}