Bug 452413 – crash in Tasks: deleting mail in inbox f...

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 452413 - crash in Tasks: deleting mail in inbox f...


Summary:	crash in Tasks: deleting mail in inbox f...


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-29 23:30 UTC by peterdali
Modified:	2007-06-30 15:23 UTC

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

Description peterdali 2007-06-29 23:30:41 UTC

Version: 2.10

What were you doing when the application crashed?
deleting mail in inbox folder


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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 128045056 vsize: 128045056 resident: 56762368 share: 39239680 rss: 56762368 rss_rlim: 4294967295
CPU usage: start_time: 1183147546 rtime: 3160 utime: 2859 stime: 301 cutime:91 cstime: 44 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 -1208338720 (LWP 3131)]
[New Thread -1343562864 (LWP 7053)]
[New Thread -1283425392 (LWP 7052)]
[New Thread -1227601008 (LWP 3232)]
[New Thread -1241465968 (LWP 3225)]
(no debugging symbols found)
0x00da0402 in __kernel_vsyscall ()

+ Trace 144741

Thread 1 (Thread -1208338720 (LWP 3131))

#0 __kernel_vsyscall
#1 waitpid
from /lib/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 (6 sec old) ---------------------
warning: .dynamic section for "/usr/lib/librsvg-2.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgsf-1.so.114" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libbz2.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 palfrey 2007-06-30 15:23:06 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 ***