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 490869 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 426496
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-27 18:35 UTC by Jesse
Modified: 2007-12-19 03:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Jesse 2007-10-27 18:35:33 UTC
Version: 2.10

What were you doing when the application crashed?



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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 275087360 vsize: 275087360 resident: 122281984 share: 38862848 rss: 122281984 rss_rlim: 4294967295
CPU usage: start_time: 1193508563 rtime: 5360 utime: 4482 stime: 878 cutime:0 cstime: 2 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 -1208518944 (LWP 18326)]
[New Thread -1453347952 (LWP 19272)]
[New Thread -1432368240 (LWP 19266)]
[New Thread -1296041072 (LWP 19253)]
[New Thread -1358955632 (LWP 19195)]
[New Thread -1252476016 (LWP 19082)]
[New Thread -1356858480 (LWP 18991)]
[New Thread -1210618992 (LWP 18450)]
[New Thread -1241986160 (LWP 18415)]
[New Thread -1221108848 (LWP 18414)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208518944 (LWP 18326))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
  • #6 html_object_get_left_margin
    from /usr/lib/libgtkhtml-3.14.so.19
  • #7 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #8 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #9 html_object_calc_size
    from /usr/lib/libgtkhtml-3.14.so.19
  • #10 html_engine_calc_size
    from /usr/lib/libgtkhtml-3.14.so.19
  • #11 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #12 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #17 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #18 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(evolution:18326): libecal-WARNING **: e-cal.c:317: Unexpected response
(evolution:18326): libecal-WARNING **: e-cal.c:317: Unexpected response
(evolution:18326): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ItipView'
** (evolution:18326): CRITICAL **: itip_view_add_lower_info_item_printf: assertion `ITIP_IS_VIEW (view)' failed
(evolution:18326): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ItipView'
** (evolution:18326): CRITICAL **: itip_view_remove_lower_info_item: assertion `ITIP_IS_VIEW (view)' failed
(evolution:18326): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ItipView'
** (evolution:18326): CRITICAL **: itip_view_add_lower_info_item_printf: assertion `ITIP_IS_VIEW (view)' failed
--------------------------------------------------
Comment 1 André Klapper 2007-12-19 03:24:19 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 426496 ***