GNOME Bugzilla – Bug 476279
Corrupt icon cache results in hang with no input possible
Last modified: 2008-03-05 22:45:55 UTC
[ Forwarded from http://bugs.debian.org/427406 ] metacity-dialog hangs, and no keyboard or mouse input is possible if metacity is started with a corrupt icon cache. Steps to reproduce: * Drop the corrupt icon file (attached) in /usr/share/icons/hicolor * Generate the icon cache using GTK+ 2.10 * Restart metacity and invoke metacity-dialog. This only happens with GTK+ 2.10, in 2.11 it refuses to create the cache, complaining about a bad image index. The corrupt icon came from an old version of autopackage, they have since replaced it, http://trac.autopackage.org/ticket/31 I attached the the process after the hang, and got a limited backtrace:
+ Trace 162407
Thread 1 (Thread -1219770704 (LWP 5879))
Created attachment 95467 [details] corrupt icon file
Seems unlikely to be metacity-specific, though metacity-dialog using gtk_dialog_run may trigger it while other apps don't. Reassigning to gtk since no code I know of in metacity should care about the icon cache directly.
The stack trace is corrupt, there's not a lot we can do. Sven: can you still reproduce? If so, please send in a new stack trace after you installed the dbg/dbgsym packages for glib/gtk.
Thanks for reminding me. No, I can not reproduce it with GTK+ 2.12.8 (still using 2.10 to generate the icon cache) and Metacity 2.23. I guess the bug can be closed.