filezilla crashed with SIGSEGV in dbus_message_get_reply_serial()

Bug #448973 reported by Maltalossewen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
filezilla (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: filezilla

FileZilla crashed when trying to open the Site Manager via the menu

ProblemType: Crash
Architecture: i386
Date: Sun Oct 11 21:25:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/filezilla
NonfreeKernelModules: nvidia
Package: filezilla 3.2.7.2-0ubuntu1
ProcCmdline: filezilla
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
SegvAnalysis:
 Segfault happened at: 0x2a5e7c: mov (%edx,%eax,1),%eax
 PC (0x002a5e7c) ok
 source "(%edx,%eax,1)" (0x000000dc) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: filezilla
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 dbus_message_get_reply_serial () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
Title: filezilla crashed with SIGSEGV in dbus_message_get_reply_serial()
Uname: Linux 2.6.31-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

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

StacktraceTop:_dbus_marshal_read_basic (str=0x99f8184, pos=0, type=117,
_dbus_header_get_field_basic (header=0x99f8184, field=5,
dbus_message_get_reply_serial (message=0x99f8180)
_dbus_connection_queue_received_message_link (
_dbus_transport_queue_messages (transport=0x9ae1990)

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