xchat-gnome crashed with SIGSEGV

Bug #122872 reported by Anmar Oueja
2
Affects Status Importance Assigned to Milestone
XChat-GNOME
Fix Released
Critical
xchat-gnome (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: xchat-gnome

simply tried to launch it from the applications tool bar.

Here is what I get when I try launching it from the terminal:

(xchat-gnome:22316): libglade-CRITICAL **: glade_xml_get_widget: assertion `self != NULL' failed

(xchat-gnome:22316): libglade-CRITICAL **: glade_xml_get_widget: assertion `self != NULL' failed

(xchat-gnome:22316): libglade-CRITICAL **: glade_xml_get_widget: assertion `self != NULL' failed

(xchat-gnome:22316): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed

(xchat-gnome:22316): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Jun 28 10:56:55 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/xchat-gnome
NonfreeKernelModules: nvidia
Package: xchat-gnome 1:0.17-0ubuntu1
PackageArchitecture: i386
ProcCmdline: xchat-gnome
ProcCwd: /home/anmar
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: xchat-gnome
Stacktrace:
 #0 0x080752b3 in ?? ()
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 21909):
 #0 0x080752b3 in ?? ()
 #1 0x00000000 in ?? ()
Title: xchat-gnome crashed with SIGSEGV
Uname: Linux gutsy 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Anmar Oueja (anmar) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_cclosure_marshal_VOID__VOID (closure=0x8142eb8, return_value=0x0, n_param_values=1, param_values=0xbffb742c, invocation_hint=0xbffb730c,
IA__g_closure_invoke (closure=0x8142eb8, return_value=0x0, n_param_values=1, param_values=0xbffb742c, invocation_hint=0xbffb730c)
signal_emit_unlocked_R (node=0x80cb030, detail=0, instance=0x811f8e0, emission_return=0x0, instance_and_params=0xbffb742c)
IA__g_signal_emit_valist (instance=0x811f8e0, signal_id=111, detail=0, var_args=0x0) at /build/buildd/glib2.0-2.13.5/gobject/gsignal.c:2199
IA__g_signal_emit_by_name (instance=0x811f8e0, detailed_signal=0xb7d5e135 "changed") at /build/buildd/glib2.0-2.13.5/gobject/gsignal.c:2267

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Laurent Bigonville (bigon) wrote :

Did you try to lanch x-g for the first time?

Changed in xchat-gnome:
status: New → Incomplete
assignee: nobody → bigon
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. The crash stacktrace matches http://bugzilla.gnome.org/show_bug.cgi?id=425836 which has already been fixed upstream

Changed in xchat-gnome:
assignee: bigon → desktop-bugs
importance: Undecided → Medium
status: Incomplete → Fix Committed
Changed in xchat-gnome:
status: Unknown → Fix Released
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, according to upstream this bug was already fixed in xchat-gnome 0.18 which is already available in gutsy, if after try it and see that is not fixed for you, please re-open the bug. Thanks in advance.

Changed in xchat-gnome:
status: Fix Committed → Fix Released
Changed in xchat-gnome:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.