e-addressbook-factory crashed with SIGABRT in g_object_unref()

Bug #759796 reported by Alex
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: evolution-data-server

Appeared after closing Evolution straight after opening it accidentally.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution-data-server 2.32.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Apr 13 14:24:02 2011
ExecutablePath: /usr/lib/evolution/e-addressbook-factory
ProcCmdline: /usr/lib/evolution/e-addressbook-factory
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
Signal: 6
SourcePackage: evolution-data-server
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0
 ?? () from /usr/lib/libedata-book-1.2.so.8
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/libedata-book-1.2.so.8
 _e_gdbus_gdbus_cclosure_marshaller_BOOLEAN__OBJECT () from /usr/lib/libedata-book-1.2.so.8
Title: e-addressbook-factory crashed with SIGABRT in g_object_unref()
UpgradeStatus: Upgraded to natty on 2011-04-06 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Alex (alex.b)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #744464, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
Revision history for this message
Alex (alex.b) wrote :

Right.

That bug appears to be private, I can't access it and so I can't "look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report". Which isn't good.

Any tips on how I access the bug you want me to access?

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

you should have access to the other bug now

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.