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 476169 - crash in Tasks: I just finished reading ...
crash in Tasks: I just finished reading ...
Status: RESOLVED DUPLICATE of bug 444924
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
aklapper[fc7]
Depends on:
Blocks:
 
 
Reported: 2007-09-12 10:54 UTC by rbstancil
Modified: 2007-09-20 17:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description rbstancil 2007-09-12 10:54:46 UTC
Version: 2.10

What were you doing when the application crashed?
I just finished reading a message, and I closed that message window.


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 144719872 vsize: 144719872 resident: 54374400 share: 36663296 rss: 54374400 rss_rlim: 4294967295
CPU usage: start_time: 1189594026 rtime: 999 utime: 912 stime: 87 cutime:3 cstime: 8 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 -1208219936 (LWP 2048)]
[New Thread -1278813296 (LWP 2141)]
[New Thread -1271039088 (LWP 2099)]
[New Thread -1239569520 (LWP 2095)]
[New Thread -1220809840 (LWP 2094)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208219936 (LWP 2048))

  • #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 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 ??
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib/libbonoboui-2.so.0
  • #25 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #26 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #31 ??
    from /lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #34 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_window_propagate_key_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib/libbonoboui-2.so.0
  • #38 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 ??
    from /lib/libgobject-2.0.so.0
  • #40 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #41 ??
    from /lib/libgobject-2.0.so.0
  • #42 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #43 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #44 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 ??
    from /usr/lib/libgdk-x11-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 (24 sec old) ---------------------
(evolution:2048): e-data-server-DEBUG: Loading categories from "/home/rbstancil/.evolution/categories.xml"
(evolution:2048): e-data-server-DEBUG: Loaded 29 categories
(evolution:2048): 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:2048): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8f96380'
(evolution:2048): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8f964a0'
(evolution:2048): gtkhtml-WARNING **: No such file or directory
(evolution:2048): gtkhtml-WARNING **: No such file or directory
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4a00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
JACK tmpdir identified as [/dev/shm]
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-20 17:17:31 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 444924 ***