After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 553862 - crash in Evolution Mail and Calendar: Attempting to launch evo...
crash in Evolution Mail and Calendar: Attempting to launch evo...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
evolution[disk-summary]
: 553863 (view as bug list)
Depends on:
Blocks: 543389
 
 
Reported: 2008-09-25 23:24 UTC by robertbogdon
Modified: 2009-01-29 05:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description robertbogdon 2008-09-25 23:24:38 UTC 
What were you doing when the application crashed?
Attempting to launch evolution.


Distribution: Ubuntu 8.10 (intrepid)
Gnome Release: 2.24.0 2008-09-22 (Ubuntu)
BugBuddy Version: 2.24.0

System: Linux 2.6.27-4-generic #1 SMP Wed Sep 24 01:29:06 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10501000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human

Memory status: size: 548229120 vsize: 548229120 resident: 35508224 share: 20455424 rss: 35508224 rss_rlim: 18446744073709551615
CPU usage: start_time: 1222385011 rtime: 49 utime: 38 stime: 11 cutime:1 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0x7fd2a2c34790 (LWP 14781)]
[New Thread 0x43320950 (LWP 14811)]
[New Thread 0x409ba950 (LWP 14809)]
0x00007fd29c933c2f in waitpid () from /lib/libpthread.so.0

+ Trace 207359

Thread 2 (Thread 0x43320950 (LWP 14811))

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_lock_102
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 camel_folder_summary_check_uid
    at camel-folder-summary.c line 454
  • #6 camel_imap_message_cache_new
    at camel-imap-message-cache.c line 181
  • #7 camel_imap_folder_new
    at camel-imap-folder.c line 264
  • #8 get_folder
    at camel-imap-store.c line 2038
  • #9 camel_store_get_folder
    at camel-store.c line 319
  • #10 mail_tool_uri_to_folder
    at mail-tools.c line 331
  • #11 get_folder_exec
    at mail-ops.c line 1213
  • #12 mail_msg_proxy
    at mail-mt.c line 520
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6
  • #17 ?? 


----------- .xsession-errors (65 sec old) ---------------------
7f8d6f67a000-7f8d6f682000 rw-p 7f8d6f67a000 00:00 0 
7f8d6f682000-7f8d6f683000 r--p 0001e000 08:02 323268                     /lib/ld-2.8.90.so
7f8d6f683000-7f8d6f684000 rw-p 0001f000 08:02 323268                     /lib/ld-2.8.90.so
7fff77669000-7fff77684000 rw-p 7ffffffe4000 00:00 0                      [stack]
7fff77774000-7fff77775000 r-xp 7fff77774000 00:00 0                      [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
store_db_path /home/robert/.evolution/mail/local/folders.db
folders table successfully created 
store_db_path /home/robert/.evolution/mail/imap/robertbogdon@gmail.com@imap.gmail.com/folders.db
folders table successfully created 
store_db_path /home/robert/.evolution/mail/imap/spam@blah.net@imap.gmail.com/folders.db
folders table successfully created 
store_db_path /home/robert/.evolution/mail/vfolder/folders.db
folders table successfully created 
Multiple segmentation faults occurred; can't display error dialog
--------------------------------------------------
Comment 1 robertbogdon 2008-09-25 23:34:57 UTC 
*** Bug 553863 has been marked as a duplicate of this bug. ***
Comment 2 Milan Crha 2008-12-08 14:45:11 UTC 
Thanks for the bug report. Do you still see the issue with latest 2.24.2, please?
There has been done so many fixes meanwhile, thus I would like to know whether it's till reproducible for you. Thanks in advance.
Comment 3 Srinivasa Ragavan 2009-01-29 05:52:24 UTC 
Please reopen the bug, if you see it again. Thanks.