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 520556 - crash in exchange_get_folder_info at camel-exchange-store.c:756
crash in exchange_get_folder_info at camel-exchange-store.c:756
Status: RESOLVED DUPLICATE of bug 528022
Product: evolution
Classification: Applications
Component: general
2.12.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 521609 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-03-05 17:49 UTC by hans.bausewein
Modified: 2009-08-25 04:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description hans.bausewein 2008-03-05 17:49:43 UTC 
What were you doing when the application crashed?
nothing, as always.

I was probably not even using my pc.

Hope this helped. At least some more stack trace.


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Grand-Canyon
Icon Theme: Smokey-Red

Memory status: size: 154263552 vsize: 154263552 resident: 60121088 share: 16953344 rss: 60121088 rss_rlim: 4294967295
CPU usage: start_time: 1204736745 rtime: 250 utime: 234 stime: 16 cutime:0 cstime: 0 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 0xb687f6d0 (LWP 4445)]
[New Thread 0xb1f44b90 (LWP 4655)]
[New Thread 0xb27cbb90 (LWP 4644)]
[New Thread 0xb2fccb90 (LWP 4643)]
[New Thread 0xb3813b90 (LWP 4495)]
[New Thread 0xb4014b90 (LWP 4494)]
[New Thread 0xb4815b90 (LWP 4493)]
[New Thread 0xb512eb90 (LWP 4490)]
[New Thread 0xb592fb90 (LWP 4488)]
[New Thread 0xb6130b90 (LWP 4484)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 191401

Thread 4 (Thread 0xb2fccb90 (LWP 4643))

  • #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 422
  • #5 <signal handler called>
  • #6 exchange_get_folder_info
    at camel-exchange-store.c line 756
  • #7 camel_store_get_folder_info
    at camel-store.c line 790
  • #8 get_folderinfo_get
    at mail-ops.c line 1071
  • #9 mail_msg_received
    at mail-mt.c line 582
  • #10 thread_dispatch
    at e-msgport.c line 1005
  • #11 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #12 clone
    from /lib/i686/cmov/libc.so.6 


----------- .xsession-errors (335 sec old) ---------------------
(evolution:4445): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (512)
(evolution:4445): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (512)
(evolution:4445): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (512)
(evolution:4445): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (512)
(evolution:4445): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (512)
(evolution:4445): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (512)
(evolution:4445): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (512)
(evolution:4445): camel-exchange-provider-CRITICAL **: camel-stub.c:472: Uncaught case (512)
--------------------------------------------------
Comment 1 Tobias Mueller 2008-03-06 16:19:24 UTC 
Hi,

thanks for that stacktrace :) It looks unique according to s-d-f.
Comment 2 Milan Crha 2008-09-18 15:23:56 UTC 
*** Bug 521609 has been marked as a duplicate of this bug. ***
Comment 3 Akhil Laddha 2009-08-25 04:08:24 UTC 

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