e-addressbook-factory crashed with SIGABRT during new Calendar Event
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution-data-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: evolution-
Adding a new calendar event,
I had selected a non-default Google Calendar, pasted content into the body, manually entered title and location, and was in the process of adjusting the default End Time when this crash occurred. Didn't see any other unusual output.
I included a screenshot that might help show exactly what I was up to, and the fields I was editing.
I immediately flipped to my browser create the appointment, and it showed up in evolution (thats the one you see in the screenshot). I also completed the appointment underway in evolution during the crash, and it completed, so I now see both in evolution and in my browser on google calendar.
These observations suggest perhaps the crash is not directly linked to my actions, or the backend services were able to restart/continue interacting with the backend data Google store.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution-
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Fri Apr 15 09:56:57 2011
ExecutablePath: /usr/lib/
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=en_US:en
LANG=en_US.utf8
Signal: 6
SourcePackage: evolution-
StacktraceTop:
raise (sig=6) at ../nptl/
abort () at abort.c:92
g_assertion_
g_assertion_
?? () from /usr/lib/
Title: e-addressbook-
UpgradeStatus: Upgraded to natty on 2011-04-06 (9 days ago)
UserGroups: adm admin cdrom dialout dip disk fax fuse libvirtd lpadmin mythtv netdev plugdev pulse pulse-access sambashare scanner tape vboxusers vde2-net video
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 #751751, 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.