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 514316 - crash in Tasks: Editing an account.
crash in Tasks: Editing an account.
Status: RESOLVED DUPLICATE of bug 349913
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-02-04 15:21 UTC by GSicherman
Modified: 2008-02-05 08:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description GSicherman 2008-02-04 15:21:15 UTC
Version: 2.10

What were you doing when the application crashed?
Editing an 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.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 124620800 vsize: 124620800 resident: 47742976 share: 35799040 rss: 47742976 rss_rlim: 4294967295
CPU usage: start_time: 1202138318 rtime: 343 utime: 317 stime: 26 cutime:0 cstime: 0 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 -1208359200 (LWP 26752)]
[New Thread -1245959280 (LWP 26769)]
[New Thread -1210459248 (LWP 26764)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208359200 (LWP 26752))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 strchr
    from /lib/libc.so.6
  • #6 camel_url_new_with_base
    from /usr/lib/libcamel-1.2.so.10
  • #7 camel_url_new
    from /usr/lib/libcamel-1.2.so.10
  • #8 exchange_config_listener_authenticate
    from /usr/lib/evolution/2.10/plugins/liborg-gnome-exchange-operations.so
  • #9 exchange_operations_get_exchange_account
    from /usr/lib/evolution/2.10/plugins/liborg-gnome-exchange-operations.so
  • #10 org_gnome_exchange_auth_section
    from /usr/lib/evolution/2.10/plugins/liborg-gnome-exchange-operations.so
  • #11 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #12 e_plugin_invoke
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #13 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #14 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #15 e_config_create_widget
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #16 e_config_create_window
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #17 em_account_editor_new
    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 (7 sec old) ---------------------
(evolution:26752): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__gsicherman@https:__nj-owa1.vonage.net_'
(evolution:26752): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__gsicherman@https:__nj-owa1.vonage.net_' in group 'Passwords-Exchange'
(evolution:26752): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__gsicherman@https:__nj-owa1.vonage.net_'
(evolution:26752): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__gsicherman@https:__nj-owa1.vonage.net_' in group 'Passwords-Exchange'
(evolution:26752): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__VONAGE%5cGSICHERMAN;auth_Basic@nj-owa1.vonage.net_'
** (evolution:26752): WARNING **: Unexpected kerberos error -1765328164
** (evolution:26752): WARNING **: Unexpected kerberos error -1765328164
(evolution:26752): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__GSICHERMAN;auth_Basic@nj-owa1.vonage.net_' in group 'Passwords-Exchange'
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-05 08:08:39 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 349913 ***