New issue
Advanced search Search tips
Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 370022
Owner: ----
Closed: May 2014
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment
link

Issue 375037: Chrome failing to repaint correctly when used with non-compositing window managers under Ubuntu 14.04

Reported by mdempsky@chromium.org, May 20 2014 Project Member

Issue description

Several Googlers have reported that since upgrading to Goobuntu 14.04, if they use Chrome with a non-compositing window manager (e.g., XMonad, Awesome) that Chrome won't always repaint properly when switching between windows.  (See b/12995284.)

Current workaround is to run a standalone compositing manager like xcompmgr.

Suspicions are this is related to the new Aura UI stuff, but no concrete evidence for that currently.
 

Comment 1 by e...@chromium.org, May 21 2014

Cc: piman@chromium.org sadrul@chromium.org

Comment 2 by piman@chromium.org, May 21 2014

That bug report mentions chrome 33? Is it still relevant? 33 was certainly not Aura.

Comment 3 by mdempsky@chromium.org, May 21 2014

I know I was able to reproduce the bug just last week when I installed Goobuntu 14.04, using the stock version of Chrome that was installed.  (I.e., the google-chrome-stable package, which I believe was 35 at the time.)

But yeah, the fact that people were seeing similar effects before 35 seems to make Aura a less likely suspect.

Comment 4 by marga@google.com, May 27 2014

This has now also been reported as https://code.google.com/p/chromium/issues/detail?id=370022

The problem pre-dates Aura, and affects any non-compositing window environment.

Comment 5 by mdempsky@chromium.org, May 27 2014

Mergedinto: 370022
Status: Duplicate

Sign in to add a comment