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 483977 - crash in Tasks: I was in Evolution Prefe...
crash in Tasks: I was in Evolution Prefe...
Status: RESOLVED DUPLICATE of bug 480210
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-06 01:47 UTC by rohare2
Modified: 2007-10-06 19:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description rohare2 2007-10-06 01:47:07 UTC
Version: 2.10

What were you doing when the application crashed?
I was in Evolution Preferences making changes to an email account.


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.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 582565888 vsize: 582565888 resident: 60162048 share: 40005632 rss: 60162048 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191635072 rtime: 287 utime: 259 stime: 28 cutime:0 cstime: 1 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 46912496373904 (LWP 10642)]
[New Thread 1115965776 (LWP 10664)]
[New Thread 1094719824 (LWP 10660)]
(no debugging symbols found)
0x00000038cc80d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496373904 (LWP 10642))

  • #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_free1
    from /lib64/libglib-2.0.so.0
  • #7 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #8 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #9 ??
    from /lib64/libglib-2.0.so.0
  • #10 g_node_traverse
    from /lib64/libglib-2.0.so.0
  • #11 gtk_tree_store_remove
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 em_folder_tree_model_remove_folders
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #13 em_folder_tree_model_remove_folders
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #14 em_folder_tree_model_remove_folders
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #15 em_folder_tree_model_remove_store
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #16 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #17 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #18 ??
    from /lib64/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #22 e_config_commit
    from /usr/lib64/evolution/2.10/libeutil.so.0
  • #23 ??
    from /usr/lib64/evolution/2.10/libeutil.so.0
  • #24 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #25 ??
    from /lib64/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /lib64/libgobject-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_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #34 ??
    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/libgtk-x11-2.0.so.0
  • #38 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #39 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #40 ??
    from /lib64/libgobject-2.0.so.0
  • #41 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #42 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #43 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #44 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #45 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #46 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #47 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #48 ??
    from /lib64/libglib-2.0.so.0
  • #49 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #50 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #51 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
(evolution:10642): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:10642): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:10642): 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:10642): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8ca7c0'
(evolution:10642): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8cafc0'
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 Susana 2007-10-06 19:42:05 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 480210 ***