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 586313 - crash in Evolution Mail and Calendar: Problem with calendar
crash in Evolution Mail and Calendar: Problem with calendar
Status: RESOLVED DUPLICATE of bug 573263
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.26.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-06-18 21:00 UTC by Luca Foppiano
Modified: 2009-06-18 21:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Luca Foppiano 2009-06-18 21:00:36 UTC
What were you doing when the application crashed?
Problem with calendar


Distribution: Fedora release 11 (Leonidas)
Gnome Release: 2.26.2 2009-06-01 (Red Hat, Inc)
BugBuddy Version: 2.26.0

System: Linux 2.6.29.4-167.fc11.x86_64 #1 SMP Wed May 27 17:27:08 EDT 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10601901
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora
GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad

Memory status: size: 1850613760 vsize: 1850613760 resident: 134987776 share: 26902528 rss: 134987776 rss_rlim: 18446744073709551615
CPU usage: start_time: 1245353203 rtime: 12734 utime: 11412 stime: 1322 cutime:43 cstime: 100 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f5bf17fb910 (LWP 6017)]
[New Thread 0x7f5bf0dfa910 (LWP 5497)]
[New Thread 0x7f5bf3fff910 (LWP 5494)]
[New Thread 0x7f5bf2bfd910 (LWP 5493)]
[New Thread 0x7f5bf35fe910 (LWP 5182)]
[New Thread 0x7f5c3df9b910 (LWP 5179)]
[New Thread 0x7f5bfa1fc910 (LWP 5178)]
[New Thread 0x7f5c3ef78910 (LWP 4998)]
[New Thread 0x7f5bf8dfa910 (LWP 4996)]
[New Thread 0x7f5bfbfff910 (LWP 3206)]
[New Thread 0x7f5c0cdfa910 (LWP 3205)]
[New Thread 0x7f5c0ebfd910 (LWP 3202)]
[New Thread 0x7f5c0f5fe910 (LWP 3201)]
[New Thread 0x7f5c0ffff910 (LWP 3200)]
[New Thread 0x7f5c2d13e910 (LWP 3199)]
[New Thread 0x7f5c2db3f910 (LWP 3198)]
[New Thread 0x7f5c2e540910 (LWP 3197)]
[New Thread 0x7f5c2f5fe910 (LWP 3196)]
[New Thread 0x7f5c2ffff910 (LWP 3194)]
[New Thread 0x7f5c3fe1f910 (LWP 3189)]
[New Thread 0x7f5c40820910 (LWP 3188)]
0x0000003bbdc0e9dd in __libc_waitpid (pid=6086, 
    stat_loc=<value optimized out>, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
Current language:  auto; currently minimal

Thread 1 (Thread 0x7f5c4c4dd7f0 (LWP 3183))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 g_spawn_sync
    from /lib64/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /lib64/libglib-2.0.so.0
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
    from /usr/lib64/libpango-1.0.so.0
  • #6 pango_layout_context_changed
    from /usr/lib64/libpango-1.0.so.0
  • #7 reset_layout
    at e-text.c line 426
  • #8 e_text_draw
    at e-text.c line 1525
  • #9 gnome_canvas_group_draw
    at gnome-canvas.c line 1676
  • #10 gnome_canvas_paint_rect
    at gnome-canvas.c line 2996
  • #11 gnome_canvas_expose
    at gnome-canvas.c line 3051
  • #12 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #14 ??
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #18 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #20 gdk_window_process_all_updates
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #21 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #22 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #23 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #24 ??
    from /lib64/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #26 bonobo_main
    at bonobo-main.c line 311
  • #27 main
    at main.c line 704


---- Critical and fatal warnings logged during execution ----

** calendar-gui **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed 
** calendar-gui **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed 
** calendar-gui **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed 
** calendar-gui **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed 


----------- .xsession-errors (7 sec old) ---------------------
warning: the debug information found in "/usr/lib/debug/usr/lib64/libgconf-2.so.4.1.5.debug" does not match "/usr/lib64/libgconf-2.so.4" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib64/libgailutil.so.18.0.1.debug" does not match "/usr/lib64/libgailutil.so.18" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib64/libgailutil.so.18.0.1.debug" does not match "/usr/lib64/libgailutil.so.18" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib64/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so.debug" does not match "/usr/lib64/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so" (CRC m
warning: the debug information found in "/usr/lib/debug/usr/lib64/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so.debug" does not match "/usr/lib64/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so" (CRC mi
--------------------------------------------------
Comment 1 André Klapper 2009-06-18 21:43:02 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 573263 ***