xchat crashed with signal 5 in g_type_class_ref()

Bug #195628 reported by André Gondim
10
Affects Status Importance Assigned to Milestone
xchat (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: xchat

just crash

ProblemType: Crash
Architecture: i386
Date: Mon Feb 25 21:08:57 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/xchat
NonfreeKernelModules: ath_hal
Package: xchat 2.8.4-0ubuntu6
PackageArchitecture: i386
ProcCmdline: xchat
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: xchat
StacktraceTop:
 g_type_class_ref () from /usr/lib/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
 g_object_new () from /usr/lib/libgobject-2.0.so.0
 g_file_info_new () from /usr/lib/libgio-2.0.so.0
Title: xchat crashed with signal 5 in g_type_class_ref()
Uname: Linux 2.6.24-8-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video

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

StacktraceTop:IA__g_type_class_ref (type=161636144) at /build/buildd/glib2.0-2.15.5/gobject/gtype.c:2403
IA__g_object_newv (object_type=161636144, n_parameters=0, parameters=0x0)
IA__g_object_new_valist (object_type=161636144, first_property_name=0x0,
IA__g_object_new (object_type=161636144, first_property_name=0x0)
IA__g_file_info_new () at /build/buildd/glib2.0-2.15.5/gio/gfileinfo.c:268

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in xchat:
importance: Undecided → Medium
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Has this happened again lately?

Changed in xchat:
status: New → Incomplete
Revision history for this message
Nick Ellery (nick.ellery) wrote :

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!

Changed in xchat:
status: Incomplete → Invalid
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.