metacity crashed with SIGSEGV in _XkeyTable()

[Wade Menard]

Binary package hint: metacity

was switching workspaces with keyboard

ProblemType: Crash
Architecture: i386
Date: Sat Feb 16 01:26:18 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/metacity
NonfreeKernelModules: vmnet vmblock vmmon rt61 nvidia
Package: metacity 1:2.21.13-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/bin/metacity --sm-client-id=default0
ProcCwd: /home/wade
ProcEnviron:
 PATH=/home/wade/bin:/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
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 _XkeyTable () from /usr/lib/libX11.so.6
Title: metacity crashed with SIGSEGV in _XkeyTable()
Uname: Linux tinkerbell 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video
SegvAnalysis:
 Segfault happened at: 0x805e2be <g_io_channel_unref@plt+42778>: mov (%edi),%esi
 PC (0x0805e2be) ok
 source "(%edi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA

[Apport retracing service (apport)]

StacktraceTop:meta_display_get_tab_next (display=0x80fd3a8, type=META_TAB_LIST_NORMAL, screen=0x8101758,
do_choose_window (display=0x80fd3a8, screen=0x8101758, event_window=<value optimized out>,
meta_display_process_key_event (display=0x80fd3a8, window=0x0, event=0xbf89f5a8)
event_callback (event=0xbf89f5a8, data=0x80fd3a8) at core/display.c:1770
filter_func (xevent=0xbf89f5a8, event=0x813b818, data=0x8102c78) at ui/ui.c:83

[Pedro Villavicencio (pedro)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=518608

[Thomas Thurman (marnanel)]

Is this repeatable?

The line in question appears to be

   tmp = workspace->mru_list;

and with that call stack, "workspace" is the current workspace. I can't see why it would be pointing outside the current segment, though I'd like to know. If you can repeat this, we can capture logs and see.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

I am closing this bug since no further information has been provided.