Issue metadata
Sign in to add a comment
|
BlockUntilWindowMapped() block forever on inactive workspace on xfwm4 and gets killed
Reported by
radomir....@gmail.com,
Mar 27 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/57.0.2987.98 Chrome/57.0.2987.98 Safari/537.36 Steps to reproduce the problem: 1. Start Chromium on workspace 0 under xfm4 2. Switch to workspace 1 and open a terminal 3. Type "xfg-open http://example.com" and press enter 4. Wait for 30 seconds 5. Observe Chromium getting killed and a new window getting opened on the current workspace What is the expected behavior? Chromium should open and load the url in a new tab and raise the window, so that the window manager can either switch to that workspace, or bring the browser window to the current workspace (depending on the settings). What went wrong? It seems that Chromium is waiting for a window to get mapped, but that never happens, because it's on an inactive workspace. Eventually it times out and gets killed. Switching to the browser's workspace within those 30s makes it work. Did this work before? Yes Chrome version: 57.0.2987.98 Channel: beta OS Version: Ubuntu 16.04 (64-bit) Flash Version: Shockwave Flash 25.0 r0
,
Mar 27 2017
This should also be fixed with https://codereview.chromium.org/2630773002 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ellyjo...@chromium.org
, Mar 27 2017Status: Assigned (was: Unconfirmed)