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 569333 - crash in Evolution Mail and Calendar: Evolution was starting, ...
crash in Evolution Mail and Calendar: Evolution was starting, ...
Status: RESOLVED DUPLICATE of bug 556555
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-01-27 13:51 UTC by cpebenito
Modified: 2009-01-27 16:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description cpebenito 2009-01-27 13:51:25 UTC
What were you doing when the application crashed?
Evolution was starting, and the exchange folders were being loaded.


Distribution: Gentoo Base System release 1.12.12
Gnome Release: 2.24.3 2009-01-14 (Gentoo)
BugBuddy Version: 2.24.1

System: Linux 2.6.25-gentoo-r4 #5 SMP PREEMPT Mon Dec 8 09:48:42 EST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 519155712 vsize: 519155712 resident: 31191040 share: 21299200 rss: 31191040 rss_rlim: 18446744073709551615
CPU usage: start_time: 1233064168 rtime: 62 utime: 51 stime: 11 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f4921ff1820 (LWP 1830)]
[New Thread 0x442ab950 (LWP 1901)]
[New Thread 0x40f9c950 (LWP 1877)]
[New Thread 0x432a9950 (LWP 1875)]
[New Thread 0x422a7950 (LWP 1874)]
[New Thread 0x42aa8950 (LWP 1872)]
0x00007f4916f47e9f in waitpid () from /lib/libpthread.so.0
Current language:  auto; currently asm

Thread 3 (Thread 0x40f9c950 (LWP 1877))

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_lock_51
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 camel_folder_summary_load_from_db
    from /usr/lib/libcamel-provider-1.2.so.14
  • #5 camel_exchange_summary_new
    from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #6 camel_exchange_folder_construct
    from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #7 exchange_get_folder
    from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #8 camel_store_get_folder
    from /usr/lib/libcamel-provider-1.2.so.14
  • #9 mail_tool_uri_to_folder
    from /usr/lib64/evolution/2.24/components/libevolution-mail.so
  • #10 get_folder_exec
    from /usr/lib64/evolution/2.24/components/libevolution-mail.so
  • #11 mail_msg_proxy
    from /usr/lib64/evolution/2.24/components/libevolution-mail.so
  • #12 g_thread_pool_thread_proxy
    from /usr/lib/libglib-2.0.so.0
  • #13 g_thread_create_proxy
    from /usr/lib/libglib-2.0.so.0
  • #14 start_thread
    from /lib/libpthread.so.0
  • #15 clone
    from /lib/libc.so.6
  • #16 ??


----------- .xsession-errors (76 sec old) ---------------------
--------------------------------------------------
Comment 1 André Klapper 2009-01-27 16:01:49 UTC
Are you sure that evolution-exchange was built against the correct version of evolution-data-server?
This looks a lot like a duplicate of bug 569333 to me.
Comment 2 André Klapper 2009-01-27 16:02:19 UTC
Whoops.
Are you sure that evolution-exchange was built against the correct version of evolution-data-server?
This looks a lot like a duplicate of bug 556555 to me.
Comment 3 cpebenito 2009-01-27 16:18:42 UTC
Evolution-exchange was built against evolution-data-server 2.24.2, so I rebuilt it and it works again.  Sorry for the noise.
Comment 4 André Klapper 2009-01-27 16:37:24 UTC
OK :-)

*** This bug has been marked as a duplicate of 556555 ***