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 490144 - crash in Tasks: Browsing emails in evolu...
crash in Tasks: Browsing emails in evolu...
Status: RESOLVED DUPLICATE of bug 440388
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-25 13:53 UTC by it
Modified: 2007-12-06 02:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description it 2007-10-25 13:53:23 UTC
Version: 2.10

What were you doing when the application crashed?
Browsing emails in evolution


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.18-8.1.14.el5xen #1 SMP Thu Sep 27 19:44:27 EDT 2007 x86_64
X Vendor: The XFree86 Project, Inc
X Vendor Release: 40300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 760291328 vsize: 760291328 resident: 71888896 share: 50028544 rss: 71888896 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193318098 rtime: 296 utime: 240 stime: 56 cutime:911 cstime: 126 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496390288 (LWP 16952)]
[New Thread 1084229968 (LWP 17206)]
[New Thread 1115699536 (LWP 17205)]
[New Thread 1136945488 (LWP 17114)]
[New Thread 1094719824 (LWP 16985)]
[New Thread 1126455632 (LWP 16975)]
[New Thread 1126189392 (LWP 16974)]
(no debugging symbols found)
0x0000003e39a0d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496390288 (LWP 16952))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 g_slice_free_chain_with_offset
    from /lib64/libglib-2.0.so.0
  • #7 pango_attr_list_unref
    from /usr/lib64/libpango-1.0.so.0
  • #8 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #9 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #10 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #11 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #12 html_engine_parse
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #13 gtk_html_begin_full
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #14 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #16 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #17 ??
    from /lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #19 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #20 main
  • #0 waitpid
    from /lib64/libpthread.so.0

Comment 1 Tobias Mueller 2007-12-06 02:06:13 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 440388 ***