xchat-gnome crashed with SIGSEGV in g_cclosure_marshal_VOID()

[Rick Spencer]

Binary package hint: xchat-gnome

This occurs when I select an message from the messaging menu *sometimes*. Perhaps a bug in the plugin?

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: xchat-gnome 1:0.26.1-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
CrashCounter: 1
Date: Fri Apr 16 15:19:35 2010
Disassembly: => 0x2: Cannot access memory at address 0x2
ExecutablePath: /usr/bin/xchat-gnome
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: xchat-gnome
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x2: Cannot access memory at address 0x2
 PC (0x00000002) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: xchat-gnome
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID(unsigned int0_t) ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: xchat-gnome crashed with SIGSEGV in g_cclosure_marshal_VOID()
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

[Rick Spencer (rick-rickspencer3)]

Ken , assigning to you as I suspect the xchat plugin for messaging menu is implicated here. Please reassign, unassign, etc... as appropriate.

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0

[Ken VanDine (ken-vandine)]

Fixed in 0.3.3, packaging branch is at lp:~ubuntu-desktop/xchat-indicator/ubuntu

[Launchpad Janitor (janitor)]

This bug was fixed in the package xchat-indicator - 0.3.3-0ubuntu1

---------------
xchat-indicator (0.3.3-0ubuntu1) lucid; urgency=low

  * New upstream release
    - Fixed crasher, ensure indicator is in the hash table before trying
      to remove it (LP: #565061)
 -- Ken VanDine <email address hidden> Fri, 23 Apr 2010 16:40:39 -0400