Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 429476 - x11-wm/metacity-2.34.1: Used as gnome3 fallback crashes with "meta_ui_get_default_window_icon: assertion failed: (default_icon)" when starting some apps
Summary: x11-wm/metacity-2.34.1: Used as gnome3 fallback crashes with "meta_ui_get_def...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-02 11:58 UTC by Bernd Feige
Modified: 2012-09-11 18:51 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Feige 2012-08-02 11:58:49 UTC
This is a completely up-to-date ~amd64 system with gnome 3.

When running metacity as fallback, no matter whether the system is gnome-shell capable or not, metacity crashes with the above error as soon as an application without own icons is started - simple apps such as xdvi or xev, glxgears and libreoffice are affected.
I think this is the same bug that can be seen when starting metacity-theme-viewer on any system (gnome-shell or not):

Loaded theme "Atlanta" in 0 seconds
**
metacity:ERROR:ui/preview-widget.c:450:meta_preview_get_icon: assertion failed: (default_icon)
Aborted (core dumped)

This can be reproduced on all of my systems here and isn't fixed by installing metacity-themes or by changing gtk-fallback-icon-theme in /etc/gtk-2.0/gtkrc.
Does someone have an idea?

Reproducible: Always
Comment 1 Pacho Ramos gentoo-dev 2012-09-11 18:33:42 UTC
Please retry with 2.34.8 on a new created user account with a new home
Comment 2 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-09-11 18:51:17 UTC
I believe this problem had been fixed in >=metacity-2.34.2, see upstream commit http://git.gnome.org/browse/metacity/commit/?id=234a5e217438ebfeb17555b5ab1d210e4c9820fe

Please reopen this bug report if you still experience the issue after updating to the newest ~amd64 metacity in portage (currently 2.34.8).