desktopcouch-service crashed with SIGSEGV in dbus_message_get_reply_serial()

Bug #528477 reported by Nicolas DERIVE
94
This bug affects 20 people
Affects Status Importance Assigned to Milestone
desktopcouch (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: desktopcouch

another crash of desktopcouch-service, closing gwibber, listening music with banshee under latest lucid.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912
CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e
CrashCounter: 1
Date: Fri Feb 26 14:22:29 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: desktopcouch 0.6.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=fr_FR.UTF-8
 LANG=fr_FR.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x2ece5c: mov (%edx,%eax,1),%eax
 PC (0x002ece5c) ok
 source "(%edx,%eax,1)" (0x00000048) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: desktopcouch
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: desktopcouch-service crashed with SIGSEGV in dbus_message_get_reply_serial()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video

Revision history for this message
Nicolas DERIVE (kalon33) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _dbus_marshal_read_basic (str=0x8fbad6c, pos=0, type=117,
 _dbus_header_get_field_basic (header=0x8fbad6c, field=5,
 dbus_message_get_reply_serial (message=0x8fbad68)
 _dbus_connection_queue_received_message_link (
 _dbus_transport_queue_messages (transport=0x8fcaff0)

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in desktopcouch (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Martin Nyholm Jelle (mjelle) wrote :

Launching gwibber did this crash with the same error for me.

Revision history for this message
Franck (alci) wrote :

Occured for me while in evolution...

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.