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 540302 - crash in Evolution Mail and Calendar: Fetching email, running ...
crash in Evolution Mail and Calendar: Fetching email, running ...
Status: RESOLVED DUPLICATE of bug 444939
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-06-26 11:46 UTC by gdunse
Modified: 2008-09-23 16:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description gdunse 2008-06-26 11:46:22 UTC 
What were you doing when the application crashed?
Fetching email, running updates, listening to music


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-rc8-686 #1 SMP Fri Jan 25 16:21:17 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 96411648 vsize: 96411648 resident: 30646272 share: 17948672 rss: 30646272 rss_rlim: 4294967295
CPU usage: start_time: 1214480432 rtime: 2325 utime: 516 stime: 1809 cutime:4 cstime: 37 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb67b9740 (LWP 4942)]
[New Thread 0xb3884b90 (LWP 5028)]
[New Thread 0xb4a9bb90 (LWP 5004)]
[New Thread 0xb52a5b90 (LWP 4991)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 201435

Thread 3 (Thread 0xb4a9bb90 (LWP 5004))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_lock_95
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #4 segv_redirect
    at main.c line 528
  • #5 <signal handler called>
  • #6 camel_local_summary_check
    at camel-local-summary.c line 268
  • #7 local_refresh_info
    at camel-local-folder.c line 474
  • #8 camel_folder_refresh_info
    at camel-folder.c line 301
  • #9 refresh_folder_exec
    at mail-ops.c line 1554
  • #10 mail_msg_proxy
    at mail-mt.c line 523
  • #11 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.16.3/glib/gthreadpool.c line 265
  • #12 g_thread_create_proxy
    at /build/buildd/glib2.0-2.16.3/glib/gthread.c line 635
  • #13 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #14 clone
    from /lib/i686/cmov/libc.so.6 


----------- .xsession-errors (45 sec old) ---------------------
(evolution:4942): camel-local-provider-WARNING **: Expected a From line here, didn't get it. SO recovering....
(evolution:4942): camel-local-provider-WARNING **: Expected a From line here, didn't get it. SO recovering....
(evolution:4942): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject'
(evolution:4942): camel-CRITICAL **: camel_object_cast: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
--------------------------------------------------
Comment 1 Tobias Mueller 2008-06-26 15:42:47 UTC 
Hm. I don't know whether thread 2 or thread 3 crashes.

If it's thread 2, it would be a dup of bug 535708.
I didn't find any reasonable dup for thread 3, which is camel_local_summary_check.

Can you trigger this issue somehow?
Comment 2 gdunse 2008-07-11 12:50:07 UTC 
Ok I remember to try again..... so at the time

I can not repeat.
Started Evolution again and continued downloading emails.
All was fine.

Just noticed Debian package update just became available.

Cant access bugzilla link so replying to the email.
Comment 3 Milan Crha 2008-09-23 16:25:23 UTC 
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 444939 ***