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 567754 - crash in Evolution Mail and Calendar: Evolution was sitting id...
crash in Evolution Mail and Calendar: Evolution was sitting id...
Status: RESOLVED DUPLICATE of bug 555276
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-01-14 15:31 UTC by bkahn
Modified: 2009-01-15 13:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description bkahn 2009-01-14 15:31:24 UTC
What were you doing when the application crashed?
Evolution was sitting idle, checking mail.


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.2 2008-11-25 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.9-159.fc10.i686 #1 SMP Tue Dec 16 15:12:04 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: Tango

Memory status: size: 246132736 vsize: 246132736 resident: 85151744 share: 22429696 rss: 85151744 rss_rlim: 18446744073709551615
CPU usage: start_time: 1231939137 rtime: 11090 utime: 10016 stime: 1074 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb7fef980 (LWP 3599)]
[New Thread 0xb68e6b90 (LWP 18873)]
[New Thread 0xb72e7b90 (LWP 3637)]
0x00110416 in __kernel_vsyscall ()

Thread 2 (Thread 0xb68e6b90 (LWP 18873))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S line 136
  • #2 _L_lock_89
    from /lib/libpthread.so.0
  • #3 __pthread_mutex_lock
    at pthread_mutex_lock.c line 86
  • #4 segv_redirect
    at main.c line 423
  • #5 <signal handler called>
  • #6 vee_get_message
    at camel-vee-folder.c line 636
  • #7 camel_folder_get_message
    at camel-folder.c line 1123
  • #8 get_message_exec
    at mail-ops.c line 1824
  • #9 mail_msg_proxy
    at mail-mt.c line 520
  • #10 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #11 g_thread_create_proxy
    at gthread.c line 635
  • #12 start_thread
    at pthread_create.c line 297
  • #13 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130


----------- .xsession-errors (18 sec old) ---------------------
Window manager warning: Attempt to perform window operation 26 on window none when operation 26 on none already in effect
Window manager warning: Attempt to perform window operation 26 on window none when operation 26 on none already in effect
Window manager warning: Attempt to perform window operation 26 on window none when operation 26 on none already in effect
Window manager warning: Attempt to perform window operation 26 on window none when operation 26 on none already in effect
Window manager warning: Attempt to perform window operation 26 on window none when operation 26 on none already in effect
Window manager warning: Attempt to perform window operation 26 on window none when operation 26 on none already in effect
(evolution:3599): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed
(evolution:3599): camel-CRITICAL **: camel_object_ref: assertion `CAMEL_IS_OBJECT(o)' failed
(evolution:3599): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed
(evolution:3599): camel-CRITICAL **: camel_object_ref: assertion `CAMEL_IS_OBJECT(o)' failed
Window manager warning: Attempt to perform window operation 26 on window none when operation 26 on none already in effect
--------------------------------------------------
Comment 1 Akhil Laddha 2009-01-15 06:14:52 UTC
so many signal_handler calls .... one call is dupe of bug 567654 
Comment 2 palfrey 2009-01-15 13:02:39 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 555276 ***