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 543302 - crash in Evolution Mail and Calendar: evo running in backgroud
crash in Evolution Mail and Calendar: evo running in backgroud
Status: RESOLVED DUPLICATE of bug 499975
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-07-16 16:08 UTC by Reid Thompson
Modified: 2008-07-20 21:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Reid Thompson 2008-07-16 16:08:05 UTC
What were you doing when the application crashed?
evo running in backgroud


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.22.3 2008-07-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: 245731328 vsize: 245731328 resident: 104865792 share: 20746240 rss: 104865792 rss_rlim: 4294967295
CPU usage: start_time: 1216134539 rtime: 39672 utime: 32127 stime: 7545 cutime:6867 cstime: 4676 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 0xb67f86c0 (LWP 14572)]
[New Thread 0xb10ffb90 (LWP 18633)]
[New Thread 0xab5fcb90 (LWP 18629)]
[New Thread 0xb1682b90 (LWP 19625)]
[New Thread 0xb532ab90 (LWP 19623)]
[New Thread 0xb290eb90 (LWP 14657)]
[New Thread 0xb39f3b90 (LWP 14589)]
[New Thread 0xb49f5b90 (LWP 14587)]
0xb7f7f410 in __kernel_vsyscall ()

Thread 2 (Thread 0xb10ffb90 (LWP 18633))

  • #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 camel_message_info_ptr
    at ../../../evolution-data-server/camel/camel-folder-summary.c line 3018
  • #6 message_info_save
    at ../../../evolution-data-server/camel/camel-folder-summary.c line 1959
  • #7 message_info_save
    at ../../../evolution-exchange/camel/camel-exchange-summary.c line 236
  • #8 camel_folder_summary_save
    at ../../../evolution-data-server/camel/camel-folder-summary.c line 723
  • #9 exchange_sync
    at ../../../evolution-exchange/camel/camel-exchange-folder.c line 1186
  • #10 camel_folder_sync
    at ../../../evolution-data-server/camel/camel-folder.c line 282
  • #11 store_sync
    at ../../../evolution-data-server/camel/camel-store.c line 649
  • #12 camel_store_sync
    at ../../../evolution-data-server/camel/camel-store.c line 671
  • #13 sync_store_exec
    at ../../../evolution/mail/mail-ops.c line 1573
  • #14 mail_msg_proxy
    at ../../../evolution/mail/mail-mt.c line 523
  • #15 g_thread_pool_thread_proxy
    at ../../../glib/glib/gthreadpool.c line 265
  • #16 g_thread_create_proxy
    at ../../../glib/glib/gthread.c line 635
  • #17 start_thread
    at pthread_create.c line 296
  • #18 clone
    from /lib/libc.so.6


----------- .xsession-errors (2796 sec old) ---------------------
Got keycode 96
Got modmask 0
Keymap changed! Regrabbing keys...Removing grab for 'F12'
Got accel 65481, 0, 0
Got keycode 96
Got modmask 0
JNI: disconnectNX: sending SIGINT to netExtender (PID = 16415)
Disconnecting NetExtender...
SSL-VPN logging out...
SSL-VPN connection is terminated.
Exiting NetExtender client
JNI: LaunchNX: Exiting LaunchNX, returning (1)
Loading saved profiles...
Loaded profile: hatch.ateb.com
Done.
--------------------------------------------------
Comment 1 Tobias Mueller 2008-07-20 21:54:20 UTC
Hey :)

This is acutally a dup, thus marking it as such.

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