e-addressbook-factory crashed with SIGSEGV in dbus_message_get_reply_serial()

Bug #725700 reported by Curtis Hovey
74
This bug affects 11 people
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution-data-server

I tried to view Contacts > CouchDB > Ubuntu One hoping to see that my u1 contacts had synced. I got an error. Contacts has never synced with this computer.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution-data-server 2.32.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
NonfreeKernelModules: nvidia wl
Architecture: i386
CrashCounter: 1
Date: Sat Feb 26 13:44:33 2011
ExecutablePath: /usr/lib/evolution/e-addressbook-factory
ProcCmdline: /usr/lib/evolution/e-addressbook-factory
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xbc49ef: mov (%edx,%eax,1),%edx
 PC (0x00bc49ef) ok
 source "(%edx,%eax,1)" (0x00000060) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution-data-server
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: e-addressbook-factory crashed with SIGSEGV in dbus_message_get_reply_serial()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Curtis Hovey (sinzui) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _dbus_marshal_read_basic (str=0x98fab6c, pos=28, type=117, value=0xb6f50cfc, byte_order=0, new_pos=0x0) at dbus-marshal-basic.c:549
 _dbus_header_get_field_basic (header=0x98fab6c, field=5, type=117, value=0xb6f50cfc) at dbus-marshal-header.c:1342
 dbus_message_get_reply_serial (message=0x98fab68) at dbus-message.c:1030
 _dbus_connection_queue_received_message_link (connection=0x99224c8, link=0x9912620) at dbus-connection.c:478
 _dbus_transport_queue_messages (transport=0x98fac20) at dbus-transport.c:1148

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 evolution-data-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Curtis Hovey (sinzui)
visibility: private → public
Revision history for this message
Curtis Hovey (sinzui) wrote :

After a recent fix to counchdb, I can now see the contact db in my browser. All the data is there and it is syncing. This looks like e-addressbook-factory does not want to talk to couchdb or it is very confused by the db's content.

I suspect the later, case. I have used evolution as my addressbook for 10 years. There could be some oddness left over from older version. My contacts first got to Ubuntu One from another computer running a clean version of evolution with an import of my address book.

Revision history for this message
Chad A Davis (chadadavis) wrote :

My environment was not inherited from a previous version of Ubuntu. I am on Natty, development branch (up to date as of 2011-03-12). I am logged in to U1 but have no contacts in U1 nor in Evolution (apart from my self-contact, which was automatically added to the local address book). I started evolution for the first time, setup a Gmail account, testing sending and receiving, which worked. Then I switch to "Contacts" from within Evolution when I see:

Unable to open address book

This address book cannot be opened. This either means that an incorrect URI was entered, or the server is unreachable.

Detailed error message: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

The error is repeatable and happens each time I select the U1 CouchDB contacts.

Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in evolution-data-server (Ubuntu):
status: New → Invalid
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.