Bug 490011 – crash in Tasks: syncing gmail imap folde...

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 490011 - crash in Tasks: syncing gmail imap folde...


Summary:	crash in Tasks: syncing gmail imap folde...


Status:	RESOLVED DUPLICATE of bug 438139

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-10-25 02:50 UTC by zebthepilot
Modified:	2007-10-25 06:25 UTC

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

Description zebthepilot 2007-10-25 02:50:51 UTC

Version: 2.10

What were you doing when the application crashed?
syncing gmail imap folders after applying filters


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 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: 728576000 vsize: 728576000 resident: 110854144 share: 32980992 rss: 110854144 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193274024 rtime: 7319 utime: 6034 stime: 1285 cutime:60274 cstime: 5796 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 46912496394384 (LWP 10938)]
[New Thread 1094719824 (LWP 12526)]
[New Thread 1126189392 (LWP 12511)]
[New Thread 1084229968 (LWP 11638)]
[New Thread 1147435344 (LWP 10955)]
[New Thread 1105209680 (LWP 10946)]
(no debugging symbols found)
0x0000003f9ea0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 172678

Thread 1 (Thread 46912496394384 (LWP 10938))

#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 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#9 gtk_window_remove_mnemonic
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 ??
from /usr/lib64/libgtk-x11-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 ??
from /usr/lib64/libgtk-x11-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 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#25 gtk_widget_unparent
from /usr/lib64/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#27 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#28 ??
from /lib64/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#30 g_signal_emit
from /lib64/libgobject-2.0.so.0
#31 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#32 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#33 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#34 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#35 ??
from /lib64/libgobject-2.0.so.0
#36 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#37 g_signal_emit
from /lib64/libgobject-2.0.so.0
#38 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#39 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#40 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#41 ??
from /lib64/libgobject-2.0.so.0
#42 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#43 g_signal_emit
from /lib64/libgobject-2.0.so.0
#44 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#45 ??
from /lib64/libgobject-2.0.so.0
#46 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#47 g_signal_emit
from /lib64/libgobject-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 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#55 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#56 ??
from /lib64/libgobject-2.0.so.0
#57 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#58 g_signal_emit
from /lib64/libgobject-2.0.so.0
#59 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#60 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#61 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#62 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#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 (11 sec old) ---------------------
report junk?? Repl1ca r0lex w4tches! SAVE Big!
report junk?? Women will never complain.
report junk?? gmail.com gifts!
report junk?? Small penis will never be your problem any more
report junk?? 7 Steps to Get a Career in the Federal Government
report junk?? RE:
report junk?? ?o?????????????????q
report junk?? Your Amb1en 0rder #2212219
--------------------------------------------------

Comment 1 Akhil Laddha 2007-10-25 06:25:28 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 438139 ***