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 537384 - crash in Evolution Mail and Calendar: left evo running over we...
crash in Evolution Mail and Calendar: left evo running over we...
Status: RESOLVED DUPLICATE of bug 499975
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 537385 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-06-09 11:27 UTC by Reid Thompson
Modified: 2008-06-16 21:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Reid Thompson 2008-06-09 11:27:26 UTC
What were you doing when the application crashed?
left evo running over weekend


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.22.2 2008-06-02 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-gentoo-r8 #1 SMP PREEMPT Tue May 13 08:35:55 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: marble-look
Icon Theme: gnome

Memory status: size: 198950912 vsize: 198950912 resident: 74469376 share: 24002560 rss: 74469376 rss_rlim: 4294967295
CPU usage: start_time: 1212768167 rtime: 14921 utime: 12214 stime: 2707 cutime:2965 cstime: 734 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/evo/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb68e06c0 (LWP 1661)]
[New Thread 0xb19fdb90 (LWP 8561)]
[New Thread 0xacf4cb90 (LWP 8560)]
[New Thread 0xb250fb90 (LWP 12811)]
[New Thread 0xb3d8db90 (LWP 12809)]
[New Thread 0xb21feb90 (LWP 1789)]
[New Thread 0xb4599b90 (LWP 1750)]
[New Thread 0xb3496b90 (LWP 1732)]
0xb7fe5410 in __kernel_vsyscall ()

Thread 2 (Thread 0xb19fdb90 (LWP 8561))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_82
    from /lib/libpthread.so.0
  • #3 __pthread_mutex_lock
    at pthread_mutex_lock.c line 81
  • #4 <signal handler called>
  • #5 ??
  • #6 camel_message_info_ptr
    at ../../../evolution-data-server/camel/camel-folder-summary.c line 3014
  • #7 message_info_save
    at ../../../evolution-data-server/camel/camel-folder-summary.c line 1955
  • #8 message_info_save
    at ../../../evolution-exchange/camel/camel-exchange-summary.c line 236
  • #9 camel_folder_summary_save
    at ../../../evolution-data-server/camel/camel-folder-summary.c line 723
  • #10 exchange_sync
    at ../../../evolution-exchange/camel/camel-exchange-folder.c line 1186
  • #11 camel_folder_sync
    at ../../../evolution-data-server/camel/camel-folder.c line 279
  • #12 store_sync
    at ../../../evolution-data-server/camel/camel-store.c line 649
  • #13 camel_store_sync
    at ../../../evolution-data-server/camel/camel-store.c line 671
  • #14 sync_store_exec
    at ../../../evolution/mail/mail-ops.c line 1573
  • #15 mail_msg_proxy
    at ../../../evolution/mail/mail-mt.c line 523
  • #16 g_thread_pool_thread_proxy
    at ../../../glib/glib/gthreadpool.c line 265
  • #17 g_thread_create_proxy
    at ../../../glib/glib/gthread.c line 635
  • #18 start_thread
    at pthread_create.c line 296
  • #19 clone
    from /lib/libc.so.6


----------- .xsession-errors (52841 sec old) ---------------------
compiz (animation) - Debug: polygon.c: pset null at line 1443
compiz (animation) - Debug: polygon.c: pset null at line 1443
compiz (animation) - Debug: polygon.c: pset null at line 1443
compiz (animation) - Debug: polygon.c: pset null at line 1443
compiz (animation) - Debug: polygon.c: pset null at line 1443
compiz (animation) - Debug: polygon.c: pset null at line 1443
########### /usr/bin/lsof -F +c0 -s
########### /usr/bin/lsof -F +c0 -s
########### /usr/bin/lsof -F +c0 -s
--------------------------------------------------
Comment 1 Reid Thompson 2008-06-09 11:39:30 UTC
*** Bug 537385 has been marked as a duplicate of this bug. ***
Comment 2 Tobias Mueller 2008-06-16 21:36:20 UTC
Hey Reid,

I'd say, this is bug 499975. Maybe you can find a testcase for that bug?

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