evolution crashes with GLib Memoery Error

Bug #251921 reported by Zack Powers
4
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Summary:
Evolution Crashes on launch after updating to Intrepid Ibex Alpha 3.

Console Output:
zpowers@zircon:~$ evolution
CalDAV Eplugin starting up ...

** (evolution:14288): WARNING **: LDAP authentication failed (0xffffffff)

** (evolution:14288): DEBUG: mailto URL command: evolution %s
** (evolution:14288): DEBUG: mailto URL program: evolution

(evolution:14288): camel-WARNING **: Cannot load summary file: '/home/zpowers/.evolution/mail/local/Inbox.ev-summary': No such file or directory

(evolution:14288): camel-WARNING **: Cannot load summary file: '/home/zpowers/.evolution/mail/local/Outbox.ev-summary': No such file or directory

(evolution:14288): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder: Permission denied

GLib-ERROR **: /build/buildd/glib2.0-2.17.4/glib/gmem.c:136: failed to allocate 31232569456 bytes
aborting...
Trace/breakpoint trap

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:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Zack Powers (zpowers) wrote :

Here is a Valgrind log as requested by Sebastian Bacher.

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

did you get the bug while getting the valgrind log? it doesn't seem to list an error

Revision history for this message
Zack Powers (zpowers) wrote :

Yes, I would do another run however I can not reproduce the results as I resolved the issue after executing "rm -r ~/.evolution".

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

the log has no error, closing the bug since you workaround it and can't sent extra details now, feel free to reopen if you get it again though

Changed in evolution:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.