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 570913 - crash in Evolution Mail and Calendar: Pressing the "Today" but...
crash in Evolution Mail and Calendar: Pressing the "Today" but...
Status: RESOLVED DUPLICATE of bug 451144
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: 2009-02-08 01:08 UTC by ben
Modified: 2009-02-08 13:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description ben 2009-02-08 01:08:20 UTC 
What were you doing when the application crashed?
Pressing the "Today" button on the calendars view.  I had just linked my Google Calendar.


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 119939072 vsize: 119939072 resident: 51740672 share: 22732800 rss: 51740672 rss_rlim: 4294967295
CPU usage: start_time: 1234051259 rtime: 3490 utime: 3180 stime: 310 cutime:2 cstime: 4 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 0xb65e96d0 (LWP 6751)]
[New Thread 0xb42b2b90 (LWP 7886)]
[New Thread 0xb28e0b90 (LWP 7883)]
[New Thread 0xb5ba3b90 (LWP 6991)]
(no debugging symbols found)
0xb7f53424 in __kernel_vsyscall ()

+ Trace 212334

Thread 1 (Thread 0xb65e96d0 (LWP 6751))

  • #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 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 <signal handler called>
  • #15 g_object_ref
    from /usr/lib/libgobject-2.0.so.0
  • #16 e_cal_model_copy_component_data
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #17 calendar_control_sensitize_calendar_commands
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #18 ??
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #19 ??
  • #20 ??
  • #21 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (7 sec old) ---------------------
(evolution:6751): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:6751): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:6751): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:6751): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:6751): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:6751): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:6751): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:6751): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
--------------------------------------------------
Comment 1 Akhil Laddha 2009-02-08 13:42:29 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 451144 ***