GNOME Bugzilla – Bug 328682
Critical warning crash on launch
Last modified: 2013-09-13 00:51:15 UTC
After launch I saw the little "this is an unstable version of Evolution just for testing purposes; we suggest Evolution-2.4.2.1 for non-testers" warning or whatever it said exactly, clicked on the "don't tell me again" button, then clicked okay, and about a second later before any other window came up I got this crash. (This is cut & pasted from a "message denied" email received due to I'm guessing a bad sendmail setup but in any event generated it was originally created by bug-buddy; should hopefully still be intact...). Debugging Information: Backtrace was generated from '/opt/gnome2/bin/evolution-2.6' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -166537536 (LWP 24910)] 0x007927a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 65628
Thread 1 (Thread -166537536 (LWP 24910))
unique stack trace
Stack trace shows that the issue in loading up the Calendar & Memos component. Re-assigning to appropriate component
*** Bug 329377 has been marked as a duplicate of this bug. ***
I suspect this is the same issue, isn't it? Backtrace was generated from '/opt/gnome2/bin/evolution-2.6' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1232804160 (LWP 22488)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 65974
Thread 1 (Thread -1232804160 (LWP 22488))
luca: yes, it's the same issue. quoting vincent from bug 331614: "It seems it only happens if there's no evolution configuration." targetting to 2.5.
*** Bug 331614 has been marked as a duplicate of this bug. ***
(In reply to comment #5) > quoting vincent from bug 331614: "It seems it only happens if there's no > evolution configuration." > It could be true. I experienced the crash using a newly created account for testing.
*** Bug 332505 has been marked as a duplicate of this bug. ***
after reading the stacktrace i am pretty sure that this is a duplicate of bug 333234 which has been already fixed. see attached patch at bug 333234. *** This bug has been marked as a duplicate of 333234 ***