gaim crashes after closing conversation window

Bug #69491 reported by Hennadiy Brych
32
Affects Status Importance Assigned to Milestone
Gaim
Invalid
Undecided
Unassigned
gaim (Ubuntu)
Fix Released
Medium
Rolf Leggewie

Bug Description

Binary package hint: gaim

distribution: ubuntu edgy (development branch)
package: gaim-1:2.0.0+beta3.1-1ubuntu9
steps to reproduce:
1. run gaim
2. wait for conversation window appear (when someone send you a message)
3. try to close this conversation window
4. wait approximately 10 sec.

===============gdb-gaim.txt================
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/gaim
[Thread debugging using libthread_db enabled]
[New Thread -1221237072 (LWP 9535)]
[New Thread -1251234912 (LWP 9542)]
[New Thread -1259627616 (LWP 9545)]
[New Thread -1259893856 (LWP 9548)]
[Thread -1259893856 (LWP 9548) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1221237072 (LWP 9535)]
gtkconv_set_unseen (gtkconv=0x0, state=GAIM_UNSEEN_NONE) at ../../src/gtkconv.c:6797
6797 ../../src/gtkconv.c: No such file or directory.
        in ../../src/gtkconv.c
(gdb) backtrace
#0 gtkconv_set_unseen (gtkconv=0x0, state=GAIM_UNSEEN_NONE) at ../../src/gtkconv.c:6797
#1 0x080e8588 in focus_win_cb (w=0x81d78a8, e=0x866a8f8, d=0x832d910) at ../../src/gtkconv.c:6823
#2 0xb7b8cb00 in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0
#3 0xb78c679b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#4 0xb78d6b93 in g_signal_chain_from_overridden () from /usr/lib/libgobject-2.0.so.0
#5 0xb78d7e7f in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#6 0xb78d8279 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#7 0xb7ca05f8 in gtk_widget_get_default_style () from /usr/lib/libgtk-x11-2.0.so.0
#8 0xb7b871e9 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
#9 0xb7a107ea in _gdk_events_init () from /usr/lib/libgdk-x11-2.0.so.0
#10 0xb7852802 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#11 0xb78557df in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#12 0xb7855b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#13 0xb7b87574 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#14 0x0810fd0c in main (argc=Cannot access memory at address 0x0
) at ../../src/gtkmain.c:764
(gdb) info registers
eax 0x0 0
ecx 0xe0105 917765
edx 0x0 0
ebx 0xb7d9cb90 -1210463344
esp 0xbfd565a0 0xbfd565a0
ebp 0xbfd565a8 0xbfd565a8
esi 0x80e8570 135169392
edi 0x81d78a8 136149160
eip 0x80e851a 0x80e851a <gtkconv_set_unseen+10>
eflags 0x210246 [ PF ZF IF RF ID ]
cs 0x73 115
ss 0x7b 123
ds 0x7b 123
es 0x7b 123
fs 0x0 0
gs 0x33 51
(gdb) thread apply all backtrace

Thread 3 (Thread -1259627616 (LWP 9545)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb75c3803 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7855813 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#3 0xb7855b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#4 0xb6f3c7e0 in link_set_io_thread () from /usr/lib/libORBit-2.so.0
#5 0xb787038f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0
#6 0xb77ef504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0xb75cd51e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread -1251234912 (LWP 9542)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb75c3803 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7855813 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#3 0xb7855b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#4 0xb71aee62 in e_book_get_type () from /usr/lib/libebook-1.2.so.9
#5 0xb787038f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0
#6 0xb77ef504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0xb75cd51e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1221237072 (LWP 9535)):
#0 gtkconv_set_unseen (gtkconv=0x0, state=GAIM_UNSEEN_NONE) at ../../src/gtkconv.c:6797
#1 0x080e8588 in focus_win_cb (w=0x81d78a8, e=0x866a8f8, d=0x832d910) at ../../src/gtkconv.c:6823
#2 0xb7b8cb00 in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0
#3 0xb78c679b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#4 0xb78d6b93 in g_signal_chain_from_overridden () from /usr/lib/libgobject-2.0.so.0
#5 0xb78d7e7f in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#6 0xb78d8279 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#7 0xb7ca05f8 in gtk_widget_get_default_style () from /usr/lib/libgtk-x11-2.0.so.0
#8 0xb7b871e9 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
#9 0xb7a107ea in _gdk_events_init () from /usr/lib/libgdk-x11-2.0.so.0
#10 0xb7852802 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#11 0xb78557df in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#12 0xb7855b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#13 0xb7b87574 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#14 0x0810fd0c in main (argc=Cannot access memory at address 0x0
) at ../../src/gtkmain.c:764
======================================

Hennadiy Brych (superg)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gaim:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Alan (stalefries) wrote :

I've experienced this several times. Every time, I have 2 duplicate conversation windows opened upon receiving messages from the same contact. Attempting to close one crashes Gaim. I've attached the auto-generated crash report.

Revision history for this message
mark (ubuntu-marki) wrote :

same here -- crash report attached.

Revision history for this message
Ian (typppo) wrote :

This happens to me as well, but only when I do not have my status marked as "available." So it's triggered by any away message/invisibility.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

I also experience gaim crashing on closure. I am installing gaim-dbg now to get a backtrace.

When looking for other reports on this I found bug 69491, bug 69385, bug 72762 and bug 73487 as possible dupes.

Revision history for this message
Thorbjørn Møller Pedersen (thorbjorn-pedersen) wrote :

same here -- another crash report attached

Revision history for this message
Thorbjørn Møller Pedersen (thorbjorn-pedersen) wrote :

Same here. Attached crash report.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thorbjørn thank you for your bug interest, could you try not commenting on random bugs though? Your crash is a different one than the bug you comment on, it creates confusion and extra work for people working on it. If you are not sure of what you are doing you can open a new bug, the bugsquad will mark it duplicate if required

Revision history for this message
Rolf Leggewie (r0lf) wrote :

no more crashes in gutsy pidgin (and I don't remember seeing them for a while even while I was still on edgy until last week). Can this one be closed? I intend to do so unless someone speaks up and lets us know that these crashes are still an issue for them.

Changed in gaim:
status: Confirmed → Incomplete
status: New → Invalid
Rolf Leggewie (r0lf)
Changed in gaim:
assignee: nobody → r0lf
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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