** Changed in: metacity (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/467972
Title:
metacity assert failure:
** Changed in: metacity
Status: Unknown = Fix Released
** Changed in: metacity
Importance: Unknown = Medium
--
metacity assert failure:
metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed:
(window-frame != NULL)
https://bugs.launchpad.net/bugs/467972
You
This metacity crasher has been fixed upstream by Gnome. I nominate it
for release in the karmic updates channel.
--
metacity assert failure:
metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed:
(window-frame != NULL)
https://bugs.launchpad.net/bugs/467972
You received this
Since chromium-browser and metacity are packaged in Ubuntu, can we see
an updated metacity package that has this (very simple) patch applied?
--
metacity assert failure:
metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed:
(window-frame != NULL)
** Changed in: metacity (Ubuntu)
Importance: Undecided = Medium
** Changed in: metacity (Ubuntu)
Status: Confirmed = Triaged
** Changed in: metacity (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
metacity assert failure:
** Bug watch added: GNOME Bug Tracker #598231
https://bugzilla.gnome.org/show_bug.cgi?id=598231
** Also affects: metacity via
https://bugzilla.gnome.org/show_bug.cgi?id=598231
Importance: Unknown
Status: Unknown
--
metacity assert failure:
I attached a patch to fix this in metacity at
https://bugzilla.gnome.org/show_bug.cgi?id=601907 .
** Bug watch added: GNOME Bug Tracker #601907
https://bugzilla.gnome.org/show_bug.cgi?id=601907
--
metacity assert failure:
metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion
(I think that one can also work around this by changing the Visual
alert setting in Sound Preferences - Sounds to something other than
Flash window.)
--
metacity assert failure:
metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed:
(window-frame != NULL)
The same for me! I'm using chromium, not chrome, but the problem is very
similar, I can see that assert message in .xsession-errors too. It
happens almost every day once or more. I'm using Ubuntu 9.10 on 32 bit.
I think bug 434389 is quite similar to this one, though.
metacity:
Installed:
Maybe the problem, that Chromium (and also Chrome) does not have window
border/decoration (by window manager) by default? :)
** Changed in: metacity (Ubuntu)
Status: New = Confirmed
--
metacity assert failure:
metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed:
http://code.google.com/p/chromium/issues/detail?id=27654
chrome:3337): Gdk-WARNING **: XID collision, trouble ahead
However I don't know it's chromium or metacity bug then, metacity
shouldn't crash by a client though, at least imho.
** Bug watch added: code.google.com/p/chromium/issues #27654
Exactly the same for me. Seems to be related to Google Chrome entering
somethin in forms (it happens only when I'm editing my blog posts).
--
metacity assert failure:
metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed:
(window-frame != NULL)
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34839192/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/34839193/Disassembly.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/34839194/ProcMaps.txt
** Attachment
13 matches
Mail list logo
