Bug 464515 – crash in Tasks: trying to add a new emai...

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 464515 - crash in Tasks: trying to add a new emai...


Summary:	crash in Tasks: trying to add a new emai...


Status:	RESOLVED DUPLICATE of bug 434653

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-08-07 23:03 UTC by eric
Modified:	2007-09-21 13:10 UTC

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

Description eric 2007-08-07 23:03:21 UTC

What were you doing when the application crashed?
trying to add a new email account, but the username/password was incorrect. Could not cancel login


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.20-2925.9.fc7xen #1 SMP Tue May 22 09:29:36 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 627503104 vsize: 627503104 resident: 58454016 share: 39198720 rss: 58454016 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186526931 rtime: 286 utime: 262 stime: 24 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496410160 (LWP 4902)]
[New Thread 1157925200 (LWP 5041)]
[New Thread 1115699536 (LWP 5038)]
[New Thread 1126455632 (LWP 4927)]
[New Thread 1084229968 (LWP 4921)]
(no debugging symbols found)
0x0000003bacc0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 153583

Thread 1 (Thread 46912496410160 (LWP 4902))

#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 g_slist_remove_all
from /lib64/libglib-2.0.so.0
#8 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#9 g_object_unref
from /lib64/libgobject-2.0.so.0
#10 g_datalist_clear
from /lib64/libglib-2.0.so.0
#11 g_object_unref
from /lib64/libgobject-2.0.so.0
#12 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#14 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#15 ??
from /lib64/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit
from /lib64/libgobject-2.0.so.0
#18 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#19 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#20 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#22 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#23 ??
from /lib64/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#25 g_signal_emit
from /lib64/libgobject-2.0.so.0
#26 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#27 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#28 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#30 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#31 ??
from /lib64/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#33 g_signal_emit
from /lib64/libgobject-2.0.so.0
#34 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#35 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#36 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#37 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#38 ??
from /lib64/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#40 g_signal_emit
from /lib64/libgobject-2.0.so.0
#41 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#42 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#43 ??
from /usr/lib64/libedataserverui-1.2.so.8
#44 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#45 ??
from /lib64/libglib-2.0.so.0
#46 g_main_loop_run
from /lib64/libglib-2.0.so.0
#47 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#48 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (25 sec old) ---------------------
BBDB spinning up...
(evolution:4902): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x846b20'
(evolution:4902): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x846920'
(evolution:4902): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4902): e-data-server-ui-WARNING **: Key file does not have key 'pop:__eseneres@pop.att.yahoo.com_'
(evolution:4902): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4902): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4902): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4902): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4902): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4902): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4902): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------

Comment 1 palfrey 2007-09-21 13:10:15 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 434653 ***