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 463943 - 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-08-06 09:48 UTC by sameerisgrover
Modified: 2007-08-11 00:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sameerisgrover 2007-08-06 09:48:48 UTC
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 160116736 vsize: 160116736 resident: 33026048 share: 19701760 rss: 33026048 rss_rlim: 4294967295
CPU usage: start_time: 1186391619 rtime: 1221 utime: 1066 stime: 155 cutime:0 cstime: 1 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 -1209162016 (LWP 4669)]
[New Thread -1246835824 (LWP 5215)]
[New Thread -1340212336 (LWP 5131)]
[New Thread -1314854000 (LWP 4695)]
[New Thread -1235948656 (LWP 4688)]
(no debugging symbols found)
0x005b2402 in __kernel_vsyscall ()

Thread 1 (Thread -1209162016 (LWP 4669))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 html_object_get_left_margin
    from /usr/lib/libgtkhtml-3.14.so.19
  • #6 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #7 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #8 html_object_calc_size
    from /usr/lib/libgtkhtml-3.14.so.19
  • #9 html_engine_calc_size
    from /usr/lib/libgtkhtml-3.14.so.19
  • #10 ??
    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 gtk_html_stream_close
    from /usr/lib/libgtkhtml-3.14.so.19
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #21 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (11 sec old) ---------------------
(evolution:4669): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
(evolution:4669): camel-CRITICAL **: camel_stream_write: assertion `CAMEL_IS_STREAM (stream)' failed
(evolution:4669): camel-WARNING **: Trying to check junk data is OBJECT 'CamelStream'
(evolution:4669): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
(evolution:4669): camel-CRITICAL **: camel_stream_printf: assertion `CAMEL_IS_STREAM (stream)' failed
(evolution:4669): camel-WARNING **: Trying to check junk data is OBJECT 'CamelStream'
(evolution:4669): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
(evolution:4669): camel-CRITICAL **: camel_stream_write: assertion `CAMEL_IS_STREAM (stream)' failed
--------------------------------------------------
Comment 1 Tobias Mueller 2007-08-11 00:07:22 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 ***