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 444471 - crash in Tasks: Disable a Account
crash in Tasks: Disable a Account
Status: RESOLVED DUPLICATE of bug 348315
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-05 19:37 UTC by Nuno Dias
Modified: 2007-07-01 00:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Nuno Dias 2007-06-05 19:37:25 UTC
What were you doing when the application crashed?
Disable a Account


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

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks_Cairo-Olive
Icon Theme: Gion

Memory status: size: 131825664 vsize: 131825664 resident: 40001536 share: 20545536 rss: 40001536 rss_rlim: 4294967295
CPU usage: start_time: 1181072045 rtime: 1217 utime: 1086 stime: 131 cutime:3 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208989984 (LWP 2612)]
[New Thread -1303696496 (LWP 2726)]
[New Thread -1238561904 (LWP 2682)]
[New Thread -1272226928 (LWP 2641)]
0x00ce8402 in __kernel_vsyscall ()

Thread 1 (Thread -1208989984 (LWP 2612))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 408
  • #4 <signal handler called>
  • #5 camel_folder_summary_content_info_free
    from /usr/lib/libcamel-provider-1.2.so.10
  • #6 camel_message_info_free
    from /usr/lib/libcamel-provider-1.2.so.10
  • #7 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 camel_message_info_free
    from /usr/lib/libcamel-provider-1.2.so.10
  • #9 camel_folder_summary_clear
    from /usr/lib/libcamel-provider-1.2.so.10
  • #10 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #11 camel_object_unref
    from /usr/lib/libcamel-1.2.so.10
  • #12 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #13 camel_object_unref
    from /usr/lib/libcamel-1.2.so.10
  • #14 store_info_unref
    at mail-component.c line 198
  • #15 mail_component_remove_store
    at mail-component.c line 1301
  • #16 mail_component_remove_store_by_uri
    at mail-component.c line 1328
  • #17 account_able_changed
    at em-account-prefs.c line 310
  • #18 account_able_toggled
    at em-account-prefs.c line 372
  • #19 g_cclosure_marshal_VOID__STRING
    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 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_cell_renderer_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /lib/libgobject-2.0.so.0
  • #31 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #32 ??
    from /lib/libgobject-2.0.so.0
  • #33 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #34 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #35 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #39 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #40 ??
    from /lib/libglib-2.0.so.0
  • #41 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #42 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #43 main
    at main.c line 586
  • #0 __kernel_vsyscall


----------- .xsession-errors (42 sec old) ---------------------
(evolution:2612): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xaae4020'
(evolution:2612): e-data-server-ui-CRITICAL **: e_source_combo_box_set_active_uid: assertion `gtk_tree_row_reference_valid (reference)' failed
(evolution:2612): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xaae4140'
/usr/share/themes/Clearlooks_Cairo-Olive/gtk-2.0/gtkrc:52: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive/gtk-2.0/gtkrc:53: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive/gtk-2.0/gtkrc:54: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
(evolution:2612): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject'
(evolution:2612): camel-CRITICAL **: camel_object_cast: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
/usr/share/themes/Clearlooks_Cairo-Olive/gtk-2.0/gtkrc:52: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive/gtk-2.0/gtkrc:53: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive/gtk-2.0/gtkrc:54: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
--------------------------------------------------
Comment 1 palfrey 2007-06-06 10:26:08 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 and
reopen this bug or report a new one. Thanks in advance!
Comment 2 Karsten Bräckelmann 2007-07-01 00:32:27 UTC
(This *obviously* is a duplicate. Please check for dupes first, before plain closing bug reports.)

Nuno, thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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