Bug 447790 – crash in Tasks: I was deleting some spam...

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 447790 - crash in Tasks: I was deleting some spam...


Summary:	crash in Tasks: I was deleting some spam...


Status:	RESOLVED DUPLICATE of bug 444924

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-15 06:23 UTC by agvg
Modified:	2007-06-15 17:50 UTC

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

Description agvg 2007-06-15 06:23:08 UTC

Version: 2.10

What were you doing when the application crashed?
I was deleting some spam with the junk button in Evolution


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 142520320 vsize: 142520320 resident: 53878784 share: 36093952 rss: 53878784 rss_rlim: 4294967295
CPU usage: start_time: 1181888215 rtime: 771 utime: 676 stime: 95 cutime:2161 cstime: 220 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208658208 (LWP 4068)]
[New Thread -1326081136 (LWP 4322)]
[New Thread -1368040560 (LWP 4320)]
[New Thread -1273627760 (LWP 4319)]
[New Thread -1259152496 (LWP 4091)]
[New Thread -1248662640 (LWP 4090)]
[New Thread -1235473520 (LWP 4089)]
(no debugging symbols found)
0x00f54402 in __kernel_vsyscall ()

+ Trace 141131

Thread 1 (Thread -1208658208 (LWP 4068))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /lib/libgobject-2.0.so.0
#18 ??
from /lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#20 g_signal_emit
from /lib/libgobject-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#24 ??
from /lib/libglib-2.0.so.0
#25 g_main_loop_run
from /lib/libglib-2.0.so.0
#26 bonobo_main
from /usr/lib/libbonobo-2.so.0
#27 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
report junk?? [SPAM] Beware of fake pills
report junk?? [SPAM] Suite 3 Design download
report junk?? [SPAM] Á¾ÇÕ·Ð¸ÂÃã¼ºñ½º¿ù0.7ÆÛ¼¾Æ®±Ý¸®Àû¿ë´Ü±â½ÅºÒÀÚ°¡´É
report junk?? [SPAM] Avoid enhancement pills
report junk?? [SPAM] Àú¶û ¼ÒÁÖ ÇÑÀÜ ÇÏ½Ç ·¡¿ä?
report junk?? [SPAM] cheap oem soft shipping //orldwide
report junk?? [SPAM] Corel Draw
report junk?? [SPAM] Hi, Pal
--------------------------------------------------

Comment 1 André Klapper 2007-06-15 17:50:31 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 444924 ***