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 510213 - crash in Tasks: deleting an email accoun...
crash in Tasks: deleting an email accoun...
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-17 16:21 UTC by hhayford
Modified: 2008-02-05 08:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description hhayford 2008-01-17 16:21:30 UTC
Version: 2.10

What were you doing when the application crashed?
deleting an email account



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 145707008 vsize: 145707008 resident: 62316544 share: 37691392 rss: 62316544 rss_rlim: 4294967295
CPU usage: start_time: 1200579740 rtime: 11692 utime: 11154 stime: 538 cutime:5 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 -1208838432 (LWP 16469)]
[New Thread -1272464496 (LWP 17150)]
[New Thread -1271010416 (LWP 16599)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208838432 (LWP 16469))

  • #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_free1
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free_1
    from /lib/libglib-2.0.so.0
  • #10 g_slist_remove
    from /lib/libglib-2.0.so.0
  • #11 gtk_tree_row_reference_free
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 em_folder_tree_model_remove_folders
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #13 em_folder_tree_model_remove_folders
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #14 em_folder_tree_model_remove_folders
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 em_folder_tree_model_remove_store
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #16 mail_component_remove_store
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #17 mail_component_remove_store_by_uri
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #18 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #19 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #24 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #27 ??
    from /lib/libgobject-2.0.so.0
  • #28 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #29 ??
    from /lib/libgobject-2.0.so.0
  • #30 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #31 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #32 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
    from /lib/libgobject-2.0.so.0
  • #36 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #37 ??
    from /lib/libgobject-2.0.so.0
  • #38 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #39 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #40 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #44 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #45 ??
    from /lib/libglib-2.0.so.0
  • #46 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #47 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #48 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (11 sec old) ---------------------
(evolution:16469): Bonobo-WARNING **: FIXME: verb 'Helpevolution0' not found, emit exception
(evolution:16469): 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:16469): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8767eb8'
(evolution:16469): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9027008'
(evolution:16469): 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:16469): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9027128'
(evolution:16469): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9027248'
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x420ebb4 specified for 0x420f956 (Delete acc).
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-05 08:46:08 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in the next software version. You may want to check for a software
upgrade.

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