metacity crashed with SIGSEGV in g_hash_table_lookup()

[Aurel Branzeanu]

Binary package hint: metacity

Crashed together with a Firefox crash

ProblemType: Crash
Architecture: i386
Date: Wed Oct 31 11:04:45 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/metacity
NonfreeKernelModules: fglrx cdrom
Package: metacity 1:2.20.0-0ubuntu3
PackageArchitecture: i386
ProcCmdline: /usr/bin/metacity --replace --sm-client-id default0
ProcCwd: /home/thunder
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: metacity
Stacktrace:
 #0 0xb7bda766 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
 #1 0xbf86b078 in ?? ()
 #2 0xb7965929 in g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
 Backtrace stopped: frame did not save the PC
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? ()
 g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
Title: metacity crashed with SIGSEGV in g_hash_table_lookup()
Uname: Linux thunder-mobile 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev root scanner video

[Apport retracing service (apport)]

StacktraceTop:gdk_xid_equal (a=0x88b194c, b=0xbf86b0a4) at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkxid.c:130
IA__g_hash_table_lookup (hash_table=0x80c6f60, key=0xbf86b0a4) at /build/buildd/glib2.0-2.14.1/glib/ghash.c:252
IA__gdk_xid_table_lookup_for_display (display=0x80d8000, xid=16822923) at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkxid.c:100
IA__gdk_window_lookup_for_display (display=0x80d8000, anid=16822923) at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkwindow-x11.c:1083
gdk_event_translate (display=0x80d8000, event=0x80dd6f0, xevent=0xbf86b208, return_exposes=0) at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkevents-x11.c:912

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.