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 444831 - crash in Tasks: Switching mail folder
crash in Tasks: Switching mail folder
Status: RESOLVED DUPLICATE of bug 433922
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-06 18:19 UTC by derek
Modified: 2007-06-11 04:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description derek 2007-06-06 18:19:44 UTC
What were you doing when the application crashed?
Switching 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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 173793280 vsize: 173793280 resident: 68976640 share: 22339584 rss: 68976640 rss_rlim: 4294967295
CPU usage: start_time: 1181153717 rtime: 911 utime: 825 stime: 86 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 -1208858912 (LWP 28050)]
[New Thread -1360012400 (LWP 28280)]
[New Thread -1254495344 (LWP 28116)]
[New Thread -1231692912 (LWP 28114)]
[New Thread -1243612272 (LWP 28087)]
(no debugging symbols found)
0x00fb6402 in __kernel_vsyscall ()

Thread 1 (Thread -1208858912 (LWP 28050))

  • #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 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #19 html_object_destroy
    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 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #23 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #24 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #25 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #26 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #27 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #28 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #29 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #30 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #31 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #32 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #33 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #34 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #35 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #36 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #37 html_engine_parse
    from /usr/lib/libgtkhtml-3.14.so.19
  • #38 gtk_html_begin_full
    from /usr/lib/libgtkhtml-3.14.so.19
  • #39 gtk_html_begin
    from /usr/lib/libgtkhtml-3.14.so.19
  • #40 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #41 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #42 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #43 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #44 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #45 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #46 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #47 ??
    from /lib/libglib-2.0.so.0
  • #48 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #49 ??
    from /lib/libglib-2.0.so.0
  • #50 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #51 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #52 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (16 sec old) ---------------------
(evolution:28050): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:28050): e-data-server-DEBUG: Loading categories from "/home/derek/.evolution/categories.xml"
(evolution:28050): e-data-server-DEBUG: Loaded 29 categories
(evolution:28050): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
(evolution:28050): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
(evolution:28050): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:28050): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9ac0250'
(evolution:28050): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9ac0370'
--------------------------------------------------
Comment 1 Akhil Laddha 2007-06-11 04:12:19 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 433922 ***