no repaint of unity at end of fullscreen chromium

Bug #1244529 reported by Tor Sjowall on 2013-10-25
This bug affects 6 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)

Bug Description

I use the full screen mode of the Chromium browser and toggle between maximized and full screen with F11.

When leaving full screen mode the unity areas of the screen does not repaint properly until after a delay of up to tens of seconds.

I've only seen this behavior with Chromium, not with Firefox or Google Chrome or other programs in full screen mode.

This behavior is new with Ubuntu release 13.10.

To reproduce:
- start Chromium Browser
- maximize Chromium window (Alt+' ' X)
- enter full screen mode (F11)
- leave full screen mode (F11)
At this point there is garbage above and to the left of the Chromium window.
See the attached screendump.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: chromium-browser 29.0.1547.65-0ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
Date: Fri Oct 25 07:42:36 2013
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
InstallationDate: Installed on 2012-05-04 (538 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
 PATH=(custom, no user)
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to saucy on 2013-10-18 (6 days ago)
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

Tor Sjowall (u-cor-u) wrote :
Chad Miller (cmiller) wrote :

Suppose you start xeyes and chromium, side by side, and then click in chromium, and try to trigger the bug.

After chromium shrinks, can you see xeyes responding to you before the "unity" areas are?

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Tor Sjowall (u-cor-u) wrote :

With xeyes and chromium both running I get the same unpainted unity areas after shrinking chromium. But the moment I move the cursor the unity areas are repainted. This happens even if xeyes is hidden behind chromium. It seems that xeyes triggers a repaint.

Also, if I click where I know the icons are at the top right of the screen, the entire unity areas repaint.

Also, if I leave everything alone for a few 10's of seconds, the unity areas repaint.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed
Sergio (sergiorussia) wrote :

actually its not chromium-only problem, leaving evince full screen mode also reproduces the bug

affects: chromium-browser → evince
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evince (Ubuntu):
status: New → Confirmed
Sergio (sergiorussia) on 2013-10-27
affects: evince → evince (Ubuntu)
Christopher Townsend (townsend) wrote :

Hi Tor, et. al.,

Thanks for reporting this bug and providing additional info. This is a duplicate of bug #1240595. I will be talking to the developer who committed the offending code this week and will work on getting a proper fix.


no longer affects: evince (Ubuntu)
no longer affects: chromium-browser (Ubuntu)
Maciej Jurga (vortex-rikkers) wrote :

I have same problem using normal Chrome, also same thing happens after full screen in SMPlayer

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers