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 454939 - crash in Tasks: reading email -- nothing...
crash in Tasks: reading email -- nothing...
Status: RESOLVED DUPLICATE of bug 455077
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-08 19:57 UTC by bug_buddy
Modified: 2007-07-29 19:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description bug_buddy 2007-07-08 19:57:59 UTC
Version: 2.10

What were you doing when the application crashed?
reading email -- nothing special. 


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:18:59 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 591802368 vsize: 591802368 resident: 60329984 share: 34193408 rss: 60329984 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183923489 rtime: 355 utime: 333 stime: 22 cutime:2 cstime: 14 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 46912496422496 (LWP 6998)]
[New Thread 1094719824 (LWP 10797)]
[New Thread 1126189392 (LWP 10796)]
[New Thread 1105209680 (LWP 10777)]
[New Thread 1115699536 (LWP 10721)]
[New Thread 1147435344 (LWP 7069)]
[New Thread 1136679248 (LWP 7040)]
(no debugging symbols found)
0x00000035df00d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496422496 (LWP 6998))

  • #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_item_free
    from /usr/lib64/libpango-1.0.so.0
  • #8 html_text_pango_info_destroy
    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 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #13 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #14 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #15 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #16 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #17 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #18 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #19 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #20 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #21 ??
    from /lib64/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #24 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #25 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #26 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #28 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #29 ??
    from /lib64/libgobject-2.0.so.0
  • #30 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #31 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #32 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #33 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #34 g_value_unset
    from /lib64/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #36 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #37 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #38 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #39 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #40 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #41 html_engine_parse
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #42 gtk_html_begin_full
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #43 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #44 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #45 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #46 ??
    from /lib64/libglib-2.0.so.0
  • #47 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #48 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #49 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (54 sec old) ---------------------
(evolution:6537): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8b51b0'
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:6998): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:6998): DEBUG: mailto URL program: evolution
(evolution:6998): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:6998): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8b45b0'
(evolution:6998): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8b49b0'
(evolution:6998): e-data-server-DEBUG: Loading categories from "/home/titus/.evolution/categories.xml"
(evolution:6998): e-data-server-DEBUG: Loaded 29 categories
--------------------------------------------------
Comment 1 Rob Bradford 2007-07-29 19:07:04 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 455077 ***