filezilla crashed with SIGSEGV in dbus_connection_dispatch()

Bug #421208 reported by kamrog
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
FileZilla
Fix Committed
Undecided
Tim Kosse
filezilla (Ubuntu)
Fix Released
Medium
Adrien Cunin

Bug Description

Binary package hint: filezilla

I was trying to launch an application.

ProblemType: Crash
Architecture: amd64
Date: Sat Aug 29 20:39:00 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/filezilla
Package: filezilla 3.2.7.1-1
ProcCmdline: filezilla
ProcEnviron:
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
SegvAnalysis:
 Segfault happened at: 0x32420b0: jo 0x3242052
 PC (0x032420b0) in non-executable VMA region: 0x02831000-0x03605000 rw-p [heap]
 source "0x3242052" (0x03242052) ok
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: filezilla
StacktraceTop:
 ?? ()
 dbus_connection_dispatch () from /lib/libdbus-1.so.3
 ?? ()
 wxThreadInternal::PthreadStart(wxThread*) ()
 start_thread () from /lib/libpthread.so.0
Title: filezilla crashed with SIGSEGV in dbus_connection_dispatch()
Uname: Linux 2.6.31-7-generic x86_64
UserGroups: adm admin audio cdrom dialout fax fuse lpadmin netdev plugdev root sambashare tape video

Related branches

Revision history for this message
kamrog (kamilrogalinski) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
dbus_connection_dispatch (connection=0x296bd10)
?? ()
wxThreadInternal::PthreadStart ()
start_thread () from /lib/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in filezilla (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Adrien Cunin (adri2000)
visibility: private → public
Revision history for this message
Adrien Cunin (adri2000) wrote :

Thanks for reporting this bug. When exactly did this crash happen? If you can reproduce it, please tell us step by step how to do. This will make it easier for us to track down the problem and eventually fix it.

Changed in filezilla (Ubuntu):
status: New → Incomplete
Revision history for this message
Tim Kosse (tim-kosse) wrote :

Fix in revision 3345.

Changed in filezilla:
assignee: nobody → Tim Kosse (tim-kosse)
status: New → Fix Committed
Revision history for this message
Tim Kosse (tim-kosse) wrote :

This problem has been fixed upstream, see http://filezilla.svn.sourceforge.net/viewvc/filezilla?view=rev&revision=3445

The root cause was that threading wasn't initialized in libdbus, leading to plenty of race condition causing the observed crash.

Two possible workarounds for this issue until the FileZilla package in Ubuntu gets updated:
a) Disable the "Prevent system from entering idle sleep during transfers and other operations" option in the settings dialog of FileZIlla
b) alternatively install the ibus-gtk package, if it gets loaded during startup of FileZilla it initializes threading in libdbus before FileZilla calls any function from libdbus.

Tim Kosse (tim-kosse)
Changed in filezilla (Ubuntu):
status: Incomplete → Confirmed
Adrien Cunin (adri2000)
Changed in filezilla (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Adrien Cunin (adri2000)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package filezilla - 3.2.7.2-0ubuntu3

---------------
filezilla (3.2.7.2-0ubuntu3) karmic; urgency=low

  * Another fix from upstream svn:
     - src/dbus/wxdbusconnection.cpp: added dbus threading initialization
       (rev. 3445), should fix dbus related crashes, that is at least
       LP: #421208 and its duplicates

 -- Adrien Cunin <email address hidden> Wed, 14 Oct 2009 00:29:46 +0200

Changed in filezilla (Ubuntu):
status: In Progress → 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.