Bug 446423 – crash in Tasks:

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 446423 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 431585

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-11 16:14 UTC by james-elmborg
Modified:	2007-06-12 15:58 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description james-elmborg 2007-06-11 16:14:32 UTC

What were you doing when the application crashed?



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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 132157440 vsize: 132157440 resident: 34942976 share: 21360640 rss: 34942976 rss_rlim: 4294967295
CPU usage: start_time: 1181578377 rtime: 452 utime: 417 stime: 35 cutime:0 cstime: 2 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 -1208428832 (LWP 3472)]
[New Thread -1276478576 (LWP 3500)]
[New Thread -1265988720 (LWP 3499)]
[New Thread -1234109552 (LWP 3496)]
(no debugging symbols found)
0x00a42402 in __kernel_vsyscall ()

+ Trace 140106

Thread 1 (Thread -1208428832 (LWP 3472))

#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 (20 sec old) ---------------------
(evolution:3472): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__iowa%5cjelmborg;auth_Basic@emailalt.iowa.uiowa.edu_'
(evolution:3472): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3472): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3472): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__iowa\jelmborg@https:__emailalt.iowa.uiowa.edu_exchange_'
(evolution:3472): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3472): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3472): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3472): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3472): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3472): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__iowa%5cjelmborg;auth_Basic@emailalt.iowa.uiowa.edu_' in group 'Passwords-Exchange'
(evolution:3472): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3472): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__jelmborg;auth_Basic@emailalt.iowa.uiowa.edu_' in group 'Passwords-Exchange'
--------------------------------------------------

Comment 1 palfrey 2007-06-12 15:58:14 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 431585 ***