Ubuntu
chromium-browser package

Desktop notifications from Chromium can not be closed

Bug #710127 reported by Christian Stefanescu on 2011-01-30

22

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	Chromium Browser	Unknown	Unknown	chromium #61300
	chromium-browser (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: chromium-browser

Desktop notifications from Chromium can only be closed in the first few seconds after appearing. After this time they remain open, hovering the 'x' for closing doesn't work and the only workaround is to disable and re-enable compositing (in my case: metacity compositing).

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: chromium-browser 8.0.552.237~r70801-0ubuntu0.10.10.1
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic i686
NonfreeKernelModules: wl
Architecture: i386
CheckboxSubmission: 60acb532cba35348c06d5739fe7dc5e8
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Sun Jan 30 13:06:17 2011
Desktop-Session:
DESKTOP_SESSION = gnome
GNOME_DESKTOP_SESSION_ID = this-is-deprecated
XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg
XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcEnviron:

SourcePackage: chromium-browser
chromium-default: CHROMIUM_FLAGS=""

Tags:

Revision history for this message

Christian Stefanescu (st-chris) wrote on 2011-01-30:

#1

ChromiumPrefs.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.3 KiB, text/plain; charset="utf-8")
DetectedPlugins.txt Edit (1.7 KiB, text/plain; charset="utf-8")
InstalledPlugins.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (38.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (803 bytes, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (623 bytes, text/plain; charset="utf-8")
RelatedPackagesPolicy.txt Edit (6.1 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (3.3 KiB, text/plain; charset="utf-8")
gconf-keys.txt Edit (524 bytes, text/plain; charset="utf-8")

tags:

added: compositing metacity
removed: ubuntu-une

Revision history for this message

Rob Clark (rob-ti) wrote on 2011-03-05:

#2

fwiw, it appears as if the popup cannot get mouse focus, so clicks to close the popup go straight thru to whatever is behind the popup. I've seen some similar issue with popup menus and metacity compositing that could be related to the same root cause.

Revision history for this message

Rob Clark (rob-ti) wrote on 2011-03-09:

#3

also, I notice a bunch of warnings from metacity which could be related..

Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4c1fcaf (<snip>); these messages lack timestamps and therefore suck.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4c00091 (<snip>); these messages lack timestamps and therefore suck.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4c00091 (<snip>); these messages lack timestamps and therefore suck.

these seem to be related to the popup notifications that get "stuck"

Revision history for this message

Olivier Tilloy (osomon) wrote on 2017-04-26:

#4

Closing due to the last update to this bug being 6 years old. Please file a new bug if this still applies to recent releases of chromium-browser.

Changed in chromium-browser (Ubuntu):
status:	New → Won't Fix

Revision history for this message

Olivier Tilloy (osomon) wrote on 2017-04-26:

#5

And according to the upstream bug report, this was a metacity bug.

Changed in chromium-browser (Ubuntu):
status:	Won't Fix → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

chromium #61300 Edit

Bug watches keep track of this bug in other bug trackers.