X2Go Bug report logs -
#1207
Newer Chrome/Chromium maximized window stuck in front with MATE
Reply or subscribe to this bug.
Toggle useless messages
Report forwarded
to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>
:
Bug#1207
; Package x2gothinclient
.
(Sat, 23 Sep 2017 13:50:01 GMT) (full text, mbox, link).
Acknowledgement sent
to Walid MOGHRABI <w.moghrabi@servicemagic.eu>
:
New Bug report received and forwarded. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>
.
(Sat, 23 Sep 2017 13:50:02 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):
Package: x2gothinclient
Version: 4.1.1.0-0~1634~ubuntu16.04.1
With Chrome/Chromium browser >49, there is a strange behaviour that is easily reproducible on a remote MATE session (this is happening too in nxagent nested session) :
- open a Chrome/Chromium browser and maximize its window
- open another application that is not maximized (let's say VLC), it should open in front of the maximized Chrome/Chromium window
- click on the Chrome/Chromium window, this should bring VLC behind
- try to Alt-Tab or click on the windows button in the windows list panel, this should bring it front but, the button in the panel flashes and the window stay stuck behind until you minimize Chrome/Chromium's window
In the .xsession-error log, it triggers these messages :
Window manager warning: 0x2800001 (doc:howto:) appears to be one of the offending windows with a timestamp of 4064013. Working around...
Window manager warning: last_user_time (4064436) is greater than comparison timestamp (2931912784). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Window manager warning: 0x2800001 (doc:howto:) appears to be one of the offending windows with a timestamp of 4064436. Working around...
Window manager warning: last_user_time (4065636) is greater than comparison timestamp (2931914121). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Window manager warning: 0x2800001 (Eclipse do) appears to be one of the offending windows with a timestamp of 4065636. Working around...
Regards,
Walid Moghrabi
TRAVAUX.COM
BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403
13591 AIX EN PROVENCE CEDEX 3
---
DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you
Send a report that this bug log contains spam.
X2Go Developers <owner@bugs.x2go.org>.
Last modified:
Thu Nov 21 14:42:00 2024;
Machine Name:
ymir.das-netzwerkteam.de
X2Go Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.