[apport] xchat crashed with SIGSEGV in IA__g_datalist_id_set_data_full()

Bug #88551 reported by canofspam3
6
Affects Status Importance Assigned to Milestone
xchat (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: xchat

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Feb 27 17:37:01 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/xchat
Package: xchat 2.8.0-0ubuntu4
ProcCmdline: xchat
ProcCwd: /home/agrajag
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US
 SHELL=/bin/bash
Signal: 11
SourcePackage: xchat
StacktraceTop:
 IA__g_datalist_id_set_data_full (datalist=0x81b00a8,
 IA__g_object_thaw_notify (object=0x81b00a0)
 IA__gtk_tree_view_column_cell_set_cell_data (
 gtk_tree_view_expose (widget=0x81ad1e0, event=0xbff646f4)
 _gtk_marshal_BOOLEAN__BOXED (closure=0x814bfb8,
Uname: Linux morpheus 2.6.20-9-lowlatency #2 SMP PREEMPT Mon Feb 26 03:04:39 UTC 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
canofspam3 (canofspam3) wrote :
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Thank you for the bug report. Also, please answer these questions:

* Is this crash reproducible?
* If so, which are the steps that lead to it?

This will greatly aid us in tracking down your problem.

Changed in xchat:
assignee: nobody → caravena
status: Unconfirmed → Needs Info
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_datalist_id_set_data_full (datalist=0xb7662be0, key_id=53, data=0x0, destroy_func=0) at gdataset.c:358
IA__g_object_thaw_notify (object=0x81b00a0) at gobjectnotifyqueue.c:120
_gtk_tree_view_column_cell_render (tree_column=0x0, window=0x8198f00, background_area=0xbff640a0, cell_area=0x0, expose_area=0x81b00a0, flags=3085818638)
gtk_tree_view_expose (widget=0x81ad1e0, event=0xbff646f4) at gtktreeview.c:4845
_gtk_marshal_BOOLEAN__BOXED_BOXED (closure=0x814bfb8, return_value=0xbff64320, n_param_values=2, param_values=0x81ad1e0, invocation_hint=0xbff6430c,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Thanks for your report

Changed in xchat:
assignee: caravena → nobody
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Áron Sisak (asisak) wrote :

Thanks for all the work you did to triage this bug. We are closing this bug report as it does not contain the steps to reproduce, what we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

The xchat source in Gutsy (2.8.4 ATM) has been transformed a lot and these crash reports seem to be from Feisty.

Changed in xchat:
status: Confirmed → Invalid
Revision history for this message
o_portista17 (o-portista17-) wrote :

I have the same bug, and it only happens when i try to connect to a network, with the plugin "blowfish".
What could be the problem?

The only work around that i have is, to start the xchat, don't let him connect to any network, and don't let him read the fish.so (unload the plugin), if i do that, i have no problem, and when i start the server that i use, and then read the fish.so, it's all fine.

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.