GNOME Bugzilla – Bug 592249
Evolution Mail and Calendar: evolution in Debian test...
Last modified: 2009-10-09 10:57:30 UTC
evolution in Debian testing crashes on startup Terminal output: (evolution:4792): camel-WARNING **: camel_exception_get_id called with NULL parameter. GLib-ERROR **: /tmp/buildd/glib2.0-2.20.4/glib/gmem.c:136: failed to allocate 31942089800 bytes aborting... evolution: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed. Multiple segmentation faults occurred; can't display error dialog ** (bug-buddy:4878): WARNING **: Could not read /proc/4792/exe: Failed to read the symbolic link '/proc/4792/exe': Permission denied ptrace: Operation not permitted. /home/srs/4792: No such file or directory. No stack. /usr/share/bug-buddy/gdb-cmd:3: Error in sourced command file: No registers. Backtrace can be supplied on request! Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0
Created attachment 141106 [details] Backtrace when running gdb Backtrace with gnome-dbg and some other -dbg packages installed.
are you trying to move from evolution 2.22.x to 2.26.x and are you moving summary from i586 arch system to x86_64 arch ? see bug 578535 , bug 559153
I'm moving from Debian Lenny 2.22.x to Squeeze 2.26.x, yes. But the architecture for 2.22.x was x86_64 too! The same computer, and I installed Lenny 64bit, not 32bit.
I've found a solution to the summary conversion problem using sqlite. Remove all *.ev-summary and *.ev-summary-meta files in the .evolution/mail/local folder and subfolders below local. Why is this not done automatically when upgrading?? I will file a bug report to Debian too, but the problem should be solved upstream!
The problems reported have been solved, but I'm leaving it open until a solution has been found for the upgrade path!
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 559153 ***