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 466116 - crash in Tasks: Clicked the sent mail fo...
crash in Tasks: Clicked the sent mail fo...
Status: RESOLVED DUPLICATE of bug 461900
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-13 02:34 UTC by jimsmith
Modified: 2007-08-13 14:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jimsmith 2007-08-13 02:34:10 UTC
What were you doing when the application crashed?
Clicked the sent mail folder


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 125419520 vsize: 125419520 resident: 35393536 share: 21737472 rss: 35393536 rss_rlim: 4294967295
CPU usage: start_time: 1186957601 rtime: 1203 utime: 1133 stime: 70 cutime:91 cstime: 20 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 -1208768800 (LWP 4693)]
[New Thread -1240413296 (LWP 4849)]
[New Thread -1305039984 (LWP 4762)]
[New Thread -1229923440 (LWP 4702)]
[New Thread -1251300464 (LWP 4701)]
(no debugging symbols found)
0x00cd1402 in __kernel_vsyscall ()

Thread 1 (Thread -1208768800 (LWP 4693))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free_chain_with_offset
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free
    from /lib/libglib-2.0.so.0
  • #10 pango_attr_list_unref
    from /usr/lib/libpango-1.0.so.0
  • #11 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #12 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #13 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #14 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #15 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #16 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #17 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #18 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #19 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #20 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #21 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #22 html_engine_parse
    from /usr/lib/libgtkhtml-3.14.so.19
  • #23 gtk_html_begin_full
    from /usr/lib/libgtkhtml-3.14.so.19
  • #24 gtk_html_begin
    from /usr/lib/libgtkhtml-3.14.so.19
  • #25 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #26 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #27 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #28 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #29 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #30 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #31 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #32 ??
    from /lib/libglib-2.0.so.0
  • #33 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #34 ??
    from /lib/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #36 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #37 main
  • #0 __kernel_vsyscall

Comment 1 palfrey 2007-08-13 14:12:07 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 461900 ***