Bug 510375 – crash in Tasks: tentando acessar a conta...

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 510375 - crash in Tasks: tentando acessar a conta...


Summary:	crash in Tasks: tentando acessar a conta...


Status:	RESOLVED DUPLICATE of bug 447591

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:	2008-01-18 11:55 UTC by leliosr
Modified:	2008-01-18 23:06 UTC

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

Description leliosr 2008-01-18 11:55:34 UTC

What were you doing when the application crashed?
tentando acessar a conta de email


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 748896256 vsize: 748896256 resident: 40222720 share: 21852160 rss: 40222720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200656742 rtime: 297 utime: 277 stime: 20 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496356960 (LWP 17695)]
[New Thread 1157658960 (LWP 17824)]
[New Thread 1084229968 (LWP 17801)]
[New Thread 1168148816 (LWP 17736)]
(no debugging symbols found)
0x00000036d140d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 185811

Thread 1 (Thread 46912496356960 (LWP 17695))

#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
from /lib64/libglib-2.0.so.0
#8 gtk_widget_remove_mnemonic_label
from /usr/lib64/libgtk-x11-2.0.so.0
#9 gtk_label_set_mnemonic_widget
from /usr/lib64/libgtk-x11-2.0.so.0
#10 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#11 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#12 ??
from /lib64/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit
from /lib64/libgobject-2.0.so.0
#15 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#16 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#17 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#19 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#20 ??
from /lib64/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#22 g_signal_emit
from /lib64/libgobject-2.0.so.0
#23 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#24 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#25 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#26 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#27 ??
from /lib64/libgobject-2.0.so.0
#28 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#29 g_signal_emit
from /lib64/libgobject-2.0.so.0
#30 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#31 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#32 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#33 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#34 ??
from /lib64/libgobject-2.0.so.0
#35 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#36 g_signal_emit
from /lib64/libgobject-2.0.so.0
#37 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#38 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#39 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#40 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#41 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#42 ??
from /lib64/libgobject-2.0.so.0
#43 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#44 g_signal_emit
from /lib64/libgobject-2.0.so.0
#45 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#46 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#47 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#48 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#49 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#50 ??
from /lib64/libgobject-2.0.so.0
#51 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#52 g_signal_emit
from /lib64/libgobject-2.0.so.0
#53 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#54 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#55 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#56 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#57 ??
from /lib64/libgobject-2.0.so.0
#58 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#59 g_signal_emit
from /lib64/libgobject-2.0.so.0
#60 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#61 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#62 ??
from /usr/lib64/libedataserverui-1.2.so.8
#63 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#64 ??
from /lib64/libglib-2.0.so.0
#65 g_main_loop_run
from /lib64/libglib-2.0.so.0
#66 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#67 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (104 sec old) ---------------------
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:17695): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------

Comment 1 Bruno Boaventura 2008-01-18 23:06:59 UTC

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 447591 ***