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 583031 - Freeze on exit
Freeze on exit
Status: RESOLVED DUPLICATE of bug 579360
Product: evolution
Classification: Applications
Component: general
2.26.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-05-18 09:28 UTC by Reinout van Schouwen
Modified: 2009-05-19 04:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Reinout van Schouwen 2009-05-18 09:28:36 UTC 
Evolution freezes when I press the Close button on the window and doesn't complete exiting, and it keeps accessing the harddisk. The stacktrace is similar to some crasher bugs but this is not a crash, just a freeze. I've attached gdb on the process and got the stacktrace below. The problem occurs very often.

+ Trace 215553

Thread 3 (Thread 0x7fb98796b950 (LWP 24739))

  • #0 __lll_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_lock_100
    from /lib64/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #3 camel_db_begin_transaction
    at camel-db.c line 514
  • #4 camel_db_delete_uid
    at camel-db.c line 1481
  • #5 camel_folder_summary_remove
    at camel-folder-summary.c line 2227
  • #6 camel_folder_summary_remove_uid
    at camel-folder-summary.c line 2254
  • #7 folder_changed_remove_uid
    at camel-vee-folder.c line 1394
  • #8 folder_changed_change
    at camel-vee-folder.c line 1544
  • #9 session_thread_proxy
    at camel-session.c line 597
  • #10 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #11 g_thread_create_proxy
    at gthread.c line 635
  • #12 start_thread
    from /lib64/libpthread.so.0
  • #13 clone
    from /lib64/libc.so.6 






Comment 1


Akhil Laddha





          2009-05-19 04:17:42 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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