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 512579 - crash in Evolution Mail and Calendar: Closing evolution
crash in Evolution Mail and Calendar: Closing evolution
Status: RESOLVED DUPLICATE of bug 434802
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-28 15:22 UTC by Wouter Bolsterlee (uws)
Modified: 2008-02-21 17:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Wouter Bolsterlee (uws) 2008-01-28 15:22:05 UTC 
Version: 2.22.x

What were you doing when the application crashed?
Closing evolution



Distribution: Debian lenny/sid
Gnome Release: 2.21.5 2008-01-17 (JHBuild)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-uws-elin #1 SMP PREEMPT Wed Dec 12 23:41:45 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 111382528 vsize: 111382528 resident: 35037184 share: 20180992 rss: 35037184 rss_rlim: 4294967295
CPU usage: start_time: 1201531774 rtime: 1425 utime: 1264 stime: 161 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome-2-22/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb68b7900 (LWP 16036)]
[New Thread 0xb0f36b90 (LWP 31853)]
[New Thread 0xaf736b90 (LWP 30879)]
[New Thread 0xb2b7db90 (LWP 16149)]
0xb72b8321 in waitpid () from /lib/libpthread.so.0

+ Trace 187069

Thread 2 (Thread 0xb0f36b90 (LWP 31853))

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_lock_95
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 folder_changed
    at camel-vee-folder.c line 1469
  • #6 camel_object_trigger_event
    at camel-object.c line 1494
  • #7 folder_changed_change
    at camel-vee-folder.c line 1426
  • #8 session_thread_proxy
    at camel-session.c line 532
  • #9 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #10 g_thread_create_proxy
    at gthread.c line 635
  • #11 start_thread
    from /lib/libpthread.so.0
  • #12 clone
    from /lib/libc.so.6 


----------- .xsession-errors (271 sec old) ---------------------
(nautilus:11869): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(nautilus:11869): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(evolution:16036): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(evolution:16036): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(evolution:16036): calendar-gui-CRITICAL **: e_week_view_event_item_draw: assertion `wveitem->event_num < week_view->events->len' failed
(gnome-terminal:14546): Vte-WARNING **: Geen afhandelaar voor controlecombinatie `device-control-string' gedefinieerd.
calendar-gui-Message: Check if default client matches (1128034192.20069.1@elin 1131666005.12344.2@elin)
sys:1: GtkWarning: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
sys:1: GtkWarning: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
--------------------------------------------------
Comment 1 Milan Crha 2008-02-21 17:49:04 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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