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 552962 - crash in Evolution Mail and Calendar: I had just finished upda...
crash in Evolution Mail and Calendar: I had just finished upda...
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 00:21 UTC by james
Modified: 2008-09-20 11:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description james 2008-09-20 00:21:34 UTC 
What were you doing when the application crashed?
I had just finished updating a task.  I clicked on the 'Save' button, 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: 85864448 vsize: 85864448 resident: 32047104 share: 18747392 rss: 32047104 rss_rlim: 4294967295
CPU usage: start_time: 1221954707 rtime: 2656 utime: 2546 stime: 110 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 0xb66a6b80 (LWP 3189)]
[New Thread 0xb5306b90 (LWP 3264)]
[New Thread 0xb5347b90 (LWP 3246)]
[New Thread 0xb5b4fb90 (LWP 3244)]
(no debugging symbols found)
0xb7f97430 in __kernel_vsyscall ()

+ Trace 207002

Thread 1 (Thread 0xb66a6b80 (LWP 3189))

  • #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 (11 sec old) ---------------------
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x12088f7 (Zip 100); these messages lack timestamps and therefore suck.
closing
gnome-mount 0.7
(nautilus:3113): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character reference '3' does not encode a permitted character
closing
gnome-mount 0.7
(nautilus:3113): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character reference '3' does not encode a permitted character
closing
gnome-mount 0.7
(evolution:3189): calendar-gui-CRITICAL **: e_cal_model_get_component_at: assertion `row >= 0 && row < priv->objects->len' failed
(evolution:3189): calendar-gui-CRITICAL **: e_cal_model_copy_component_data: assertion `comp_data != NULL' failed
--------------------------------------------------
Comment 1 Susana 2008-09-20 11:22:27 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 544187 ***