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 462457 - crash in Tasks: Completely on a differen...
crash in Tasks: Completely on a differen...
Status: RESOLVED DUPLICATE of bug 371913
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-01 13:26 UTC by agupta
Modified: 2007-08-01 16:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description agupta 2007-08-01 13:26:33 UTC
Version: 2.10

What were you doing when the application crashed?
Completely on a different screen....


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 203456512 vsize: 203456512 resident: 99844096 share: 51605504 rss: 99844096 rss_rlim: 4294967295
CPU usage: start_time: 1185887357 rtime: 14323 utime: 11170 stime: 3153 cutime:2 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209116960 (LWP 11007)]
[New Thread -1309619312 (LWP 11198)]
[New Thread -1211217008 (LWP 11100)]
[New Thread -1250223216 (LWP 11043)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209116960 (LWP 11007))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 e_table_model_row_count
    from /usr/lib/evolution/2.10/libetable.so.0
  • #6 ??
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #7 e_util_marshal_VOID__INT_INT
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #8 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #9 ??
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #12 e_table_model_rows_deleted
    from /usr/lib/evolution/2.10/libetable.so.0
  • #13 e_table_model_row_deleted
    from /usr/lib/evolution/2.10/libetable.so.0
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #15 ??
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #16 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 ??
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/libecal-1.2.so.7
  • #22 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #23 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #24 ??
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #27 ??
    from /usr/lib/libedataserver-1.2.so.9
  • #28 ??
    from /usr/lib/libORBit-2.so.0
  • #29 ??
    from /usr/lib/libORBit-2.so.0
  • #30 ??
    from /lib/libglib-2.0.so.0
  • #31 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #32 ??
    from /lib/libglib-2.0.so.0
  • #33 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #34 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #35 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (152057 sec old) ---------------------
(evolution:12846): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:12846): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:12846): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:12846): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:12846): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:12846): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:12846): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-08-01 16:45:58 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 371913 ***