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 470566 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 440422
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-27 01:36 UTC by mr.jackieho
Modified: 2007-09-21 18:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mr.jackieho 2007-08-27 01:36:21 UTC
Version: 2.10

What were you doing when the application crashed?



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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 156667904 vsize: 156667904 resident: 53956608 share: 38707200 rss: 53956608 rss_rlim: 4294967295
CPU usage: start_time: 1188177766 rtime: 630 utime: 588 stime: 42 cutime:2 cstime: 5 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 -1208793376 (LWP 3042)]
[New Thread -1312654448 (LWP 3663)]
[New Thread -1302164592 (LWP 3660)]
[New Thread -1261945968 (LWP 3659)]
[New Thread -1219667056 (LWP 3656)]
[New Thread -1291674736 (LWP 3655)]
[New Thread -1251456112 (LWP 3653)]
[New Thread -1282651248 (LWP 3110)]
[New Thread -1230156912 (LWP 3082)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208793376 (LWP 3042))

  • #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_item_free
    from /usr/lib/libpango-1.0.so.0
  • #11 html_text_pango_info_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #12 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #13 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #14 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #15 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #16 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #17 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #18 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #19 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #20 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #21 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #22 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #23 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #24 html_engine_parse
    from /usr/lib/libgtkhtml-3.14.so.19
  • #25 gtk_html_begin_full
    from /usr/lib/libgtkhtml-3.14.so.19
  • #26 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #27 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #28 ??
    from /lib/libglib-2.0.so.0
  • #29 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #30 ??
    from /lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #32 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #33 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (113 sec old) ---------------------
(evolution:3042): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x89f5010'
(evolution:3042): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x89f5130'
(evolution:3042): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:3042): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution:3042): 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?)
(evolution:3042): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x89f5250'
(evolution:3042): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x89f5370'
(evolution:3042): camel-WARNING **: camel_exception_get_id called with NULL parameter.
--------------------------------------------------
Comment 1 Suman Manjunath 2007-08-27 04:03:08 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If
you have time and can still reproduce the bug, please read
http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to
this bug.

Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here.  Thanks!

[1] debugging packages for evolution, evolution-data-server and gtkhtml,
   plus debugging packages for some basic GNOME libs. More details can
   be found here:
   http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Comment 2 Suman Manjunath 2007-09-04 15:22:38 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 440422 ***