Bug 516298 – crash in Tasks: click on search's clean ...

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 516298 - crash in Tasks: click on search's clean ...


Summary:	crash in Tasks: click on search's clean ...


Status:	RESOLVED DUPLICATE of bug 349913

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-02-13 20:29 UTC by fabriciopf
Modified:	2008-02-20 05:37 UTC

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

Description fabriciopf 2008-02-13 20:29:26 UTC

What were you doing when the application crashed?
click on search's clean icon


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

Memory status: size: 121106432 vsize: 121106432 resident: 29093888 share: 20049920 rss: 29093888 rss_rlim: 4294967295
CPU usage: start_time: 1202934125 rtime: 588 utime: 545 stime: 43 cutime:1 cstime: 4 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 -1208998176 (LWP 3226)]
[New Thread -1253053552 (LWP 3433)]
[New Thread -1283490928 (LWP 3297)]
[New Thread -1304667248 (LWP 3287)]
[New Thread -1230361712 (LWP 3263)]
(no debugging symbols found)
0x00717402 in __kernel_vsyscall ()

+ Trace 189104

Thread 1 (Thread -1208998176 (LWP 3226))

#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 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#9 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 ??
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 g_signal_emit
from /lib/libgobject-2.0.so.0
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#15 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#21 ??
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_closure_invoke
from /lib/libgobject-2.0.so.0
#24 ??
from /lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#26 g_signal_emit
from /lib/libgobject-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgdk-x11-2.0.so.0
#31 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#32 ??
from /lib/libglib-2.0.so.0
#33 g_main_loop_run
from /lib/libglib-2.0.so.0
#34 bonobo_main
from /usr/lib/libbonobo-2.so.0
#35 main
#0 __kernel_vsyscall



----------- .xsession-errors (2480 sec old) ---------------------
gw connection dispose 
gw connection finalize
gw connection dispose 
gw connection finalize
gw connection dispose 
gw connection finalize
gw connection dispose 
gw connection finalize
gw connection dispose 
gw connection finalize
gw connection dispose 
gw connection finalize
gw connection dispose 
gw connection
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-20 05:37: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 ***