Gaim always crashes on exit

Bug #58135 reported by LGB [Gábor Lénárt]
6
Affects Status Importance Assigned to Milestone
gaim (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Gaim always crashes on exit on AMD64, just click on gaim icon in systray, select exit.

Revision history for this message
LGB [Gábor Lénárt] (lgb) wrote :
Revision history for this message
Matti Lindell (mlind) wrote :

DistroRelease: Ubuntu 6.10
Package: gaim 1:2.0.0+beta3.1-1ubuntu2

Could you install gaim-dbg package and attach a backtrace as described on
https://wiki.ubuntu.com/Backtrace

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

Can you get a backtrace with evolution-data-server-dbg and gaim-dbg installed?

Changed in gaim:
importance: Untriaged → Medium
status: Unconfirmed → Needs Info
Revision history for this message
LGB [Gábor Lénárt] (lgb) wrote :

I can't if I try, "sorry gdb is crashed" right now after start (which is not the case when I start without gnu debugger, the crash come at exit) and file is created under /var/crash with "gdb" in it . Also this apport thing is totally crazy it renders my desktop unusable for some minutes (I think it is because of its negative nice level or such).

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

the file created to /var/crash has the backtrace

Revision history for this message
LGB [Gábor Lénárt] (lgb) wrote :

Hope it's OK and helps.

Revision history for this message
Ruben Vermeersch (ruben) wrote :
Revision history for this message
Emilio Pavia (emilio-pavia-deactivatedaccount) wrote :

I have the same problem.

Revision history for this message
LGB [Gábor Lénárt] (lgb) wrote :

Both of i386 and x86 architectures are affected, it seems.

Revision history for this message
Mark Doliner (thekingant) wrote :

That backtrace is pretty cryptic. It's hard to tell what's going on. For one thing it looks like there are 3 threads running. I can't imagine why that would be happening in Gaim 2.0.0 beta 3.1, unless the Ubuntu build of that version of Gaim has the changes we had made to try to work around the dbus/gnome-vfs crash?

A backtrace from someone else experiencing this crash might be useful. It also might be wise to start Gaim from a terminal with "gaim -d" and look for error messages that may be printed shortly before it crashes.

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

Mark, thank you for the useful comment and sorry for the extra work. The gaim package had a patch initializing locks to workaround the issue with dbus 0.6, I've just uploaded a new revision of the package without it since the new dbus fixes the issue:

 gaim (1:2.0.0+beta3.1-1ubuntu5) edgy; urgency=low
 .
   * debian/patches/01_gnomevfs_dbus_thread_init_fix_crasher.patch:
     - dropped, that issue is fixed by the new dbus version

Marking the bug has fixed, feel free to reopen if that's not the case and you still get the issue with that version

Changed in gaim:
assignee: nobody → desktop-bugs
status: Needs Info → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

("initializing threads" rather)

Revision history for this message
Mark Doliner (thekingant) wrote :

Neato. Thanks Sebastien!

Revision history for this message
a.sappia (a-sappia) wrote :

Note that there are at least some duplicate bugs
72762 Gaim Crash after Exit
73541 Gaim crash at exit

Revision history for this message
a.sappia (a-sappia) wrote :
Revision history for this message
a.sappia (a-sappia) wrote :
Revision history for this message
LGB [Gábor Lénárt] (lgb) wrote :

Btw, gaim still crashes (not always though) on exit both on AMD64 running feisty, and x86 running edgy. I usually use 'killall gaim' from a terminal to be able to 'exit' from gaim to avoid crash dialog and such.

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

a.sappia, thank you for your bug interest, commenting on some random closed bug which doesn't match your problem is confusing and make the work harder for the bugsquad team and the package maintainer, could you open a new bug?

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.