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 229176 - crash when changing folders (spontaneous)
crash when changing folders (spontaneous)
Status: RESOLVED DUPLICATE of bug 215344
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-08-20 17:40 UTC by aaron
Modified: 2002-08-20 17:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description aaron 2002-08-20 17:40:11 UTC
Package: Evolution
Priority: Normal
Version: 1.1.0.99
Synopsis: crash when changing folders (spontaneous)
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Crashed switching folders.



Debugging Information:

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

[New Thread 1024 (LWP 10344)]
[New Thread 2049 (LWP 10405)]
[New Thread 1026 (LWP 10406)]
[New Thread 2051 (LWP 10407)]
[New Thread 3076 (LWP 10411)]
[New Thread 5125 (LWP 10482)]
[New Thread 8198 (LWP 10514)]
0x40fe1369 in __wait4 () at __wait4:-1
	in __wait4

Thread 7 (Thread 8198 (LWP 10514))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 969
  • #2 pthread_cond_wait
    at restart.h line 34
  • #3 e_msgport_wait
    at e-msgport.c line 198
  • #4 mail_call_main
    at mail-mt.c line 774
  • #5 get_filter_driver
    at mail-session.c line 925
  • #6 camel_session_get_filter_driver
    at camel-session.c line 740
  • #7 folder_changed
    at camel-folder.c line 1600
  • #8 camel_object_trigger_event
    at camel-object.c line 854
  • #9 camel_imap_folder_changed
    at camel-imap-folder.c line 2350
  • #10 camel_imap_folder_selected
    at camel-imap-folder.c line 379
  • #11 imap_refresh_info
    at camel-imap-folder.c line 486
  • #12 disco_refresh_info
    at camel-disco-folder.c line 98
  • #13 camel_folder_refresh_info
    at camel-folder.c line 305
  • #14 refresh_folder_refresh
    at mail-ops.c line 1564
  • #15 mail_msg_received
    at mail-mt.c line 503
  • #16 thread_received_msg
    at e-msgport.c line 518
  • #17 thread_dispatch
    at e-msgport.c line 599
  • #18 pthread_start_thread
    at manager.c line 284

Thread 6 (Thread 5125 (LWP 10482))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 969
  • #2 pthread_cond_wait
    at restart.h line 34
  • #3 e_msgport_wait
    at e-msgport.c line 198
  • #4 thread_dispatch
    at e-msgport.c line 566
  • #5 pthread_start_thread
    at manager.c line 284

Thread 5 (Thread 3076 (LWP 10411))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 969
  • #2 pthread_cond_wait
    at restart.h line 34
  • #3 e_msgport_wait
    at e-msgport.c line 198
  • #4 thread_dispatch
    at e-msgport.c line 566
  • #5 pthread_start_thread
    at manager.c line 284

Thread 4 (Thread 2051 (LWP 10407))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 969
  • #2 pthread_cond_wait
    at restart.h line 34
  • #3 e_msgport_wait
    at e-msgport.c line 198
  • #4 thread_dispatch
    at e-msgport.c line 566
  • #5 pthread_start_thread
    at manager.c line 284

Thread 3 (Thread 1026 (LWP 10406))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 969
  • #2 pthread_cond_wait
    at restart.h line 34
  • #3 e_mutex_lock
    at e-msgport.c line 767
  • #4 imap_sync_online
    at camel-imap-folder.c line 730


Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Gerardo Marin 2002-08-20 17:47:42 UTC

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