evolution assert failure: *** glibc detected *** evolution: double free or corruption (!prev): 0x00007f1d1c034b70 ***

Bug #632257 reported by Daniel Holm
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: evolution

Tried to check my calendar and it died.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.3-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
AssertionMessage: *** glibc detected *** evolution: double free or corruption (!prev): 0x00007f1d1c034b70 ***
CheckboxSubmission: 815e8f34b552bb24015c69e3d0ec0d35
CheckboxSystem: 4359ae94444d1d712e0f7d48453d9e6b
Date: Tue Sep 7 10:48:54 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcCmdline: evolution
ProcEnviron:
 LANG=sv_SE.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: evolution
StacktraceTop:
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 free () from /lib/libc.so.6
Title: evolution assert failure: *** glibc detected *** evolution: double free or corruption (!prev): 0x00007f1d1c034b70 ***
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in evolution (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in evolution (Ubuntu):
status: Incomplete → 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.