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 442090 - crash in Tasks: switching folders on an ...
crash in Tasks: switching folders on an ...
Status: RESOLVED DUPLICATE of bug 442082
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-05-29 15:22 UTC by cam
Modified: 2007-05-29 20:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description cam 2007-05-29 15:22:47 UTC
What were you doing when the application crashed?
switching folders on an exchange account (again)


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

System: Linux 2.6.21-1.3189.fc7 #1 SMP Tue May 22 17:14:22 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: 146817024 vsize: 146817024 resident: 38789120 share: 22765568 rss: 38789120 rss_rlim: 4294967295
CPU usage: start_time: 1180451626 rtime: 1886 utime: 1687 stime: 199 cutime:0 cstime: 0 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 -1209141536 (LWP 4612)]
[New Thread -1367802992 (LWP 5035)]
[New Thread -1283490928 (LWP 4865)]
[New Thread -1251673200 (LWP 4625)]
[New Thread -1253049456 (LWP 4623)]
[New Thread -1240777840 (LWP 4622)]
(no debugging symbols found)
0x005f0402 in __kernel_vsyscall ()

Thread 1 (Thread -1209141536 (LWP 4612))

  • #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 (19 sec old) ---------------------
(evolution:4612): e-data-server-DEBUG: Loading categories from "/home/cpietrafeso/.evolution/categories.xml"
(evolution:4612): e-data-server-DEBUG: Loaded 29 categories
(evolution:4612): e-data-server-ui-WARNING **: ENameSelectorDialog failed to open book!
(evolution:4612): 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:4612): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9f60128'
(evolution:4612): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9f60248'
(evolution:4612): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(evolution:4612): libebook-CRITICAL **: file e-book.c: line 3807: assertion `source && E_IS_SOURCE (source)' failed
--------------------------------------------------
Comment 1 Pascal Terjan 2007-05-29 20:56:20 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Pascal Terjan 2007-05-29 20:58:17 UTC

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