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 553026 - crash in Evolution Mail and Calendar: i was updating a ( alrea...
crash in Evolution Mail and Calendar: i was updating a ( alrea...
Status: RESOLVED DUPLICATE of bug 544187
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-09-20 16:34 UTC by james
Modified: 2008-09-21 22:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description james 2008-09-20 16:34:00 UTC 
What were you doing when the application crashed?
i was updating a ( already created ) task.  I went to save ( using ctrl+s ) and the bug reporting tool came up.  and now here we are.


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-486 #1 Thu Aug 28 11:14:57 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 76021760 vsize: 76021760 resident: 30412800 share: 18567168 rss: 30412800 rss_rlim: 4294967295
CPU usage: start_time: 1221870535 rtime: 5736 utime: 5551 stime: 185 cutime:4 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb66a9b80 (LWP 4038)]
[New Thread 0xb5309b90 (LWP 5130)]
[New Thread 0xb534ab90 (LWP 4089)]
[New Thread 0xb5b52b90 (LWP 4086)]
(no debugging symbols found)
0xb7f9a430 in __kernel_vsyscall ()

+ Trace 207016

Thread 1 (Thread 0xb66a9b80 (LWP 4038))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
  • #6 ??
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #11 ??
  • #12 ??
  • #13 <signal handler called>
  • #14 e_cal_menu_target_new_select
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #15 tasks_control_sensitize_commands
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #16 ??
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib/libgobject-2.0.so.0
  • #24 ??
  • #25 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (6 sec old) ---------------------
(firefox-bin:3278): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
(firefox-bin:3278): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
(firefox-bin:3278): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
(firefox-bin:3278): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
(firefox-bin:3278): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
(firefox-bin:3278): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
(evolution:4038): calendar-gui-CRITICAL **: e_cal_model_get_component_at: assertion `row >= 0 && row < priv->objects->len' failed
(evolution:4038): calendar-gui-CRITICAL **: e_cal_model_copy_component_data: assertion `comp_data != NULL' failed
--------------------------------------------------
Comment 1 André Klapper 2008-09-21 22:15:42 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.


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