Bug 404873 – crash in Evolution: Did a delete from sent i...

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 404873 - crash in Evolution: Did a delete from sent i...


Summary:	crash in Evolution: Did a delete from sent i...


Status:	RESOLVED DUPLICATE of bug 404871

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-06 07:18 UTC by V Sridhar
Modified:	2007-02-06 17:45 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description V Sridhar 2007-02-06 07:18:06 UTC

What were you doing when the application crashed?
Did a delete from sent items - then scrolled down. Application crashed.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-02-05 (GARNOME)
BugBuddy Version: 2.16.1

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 18:32:37 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 191049728 vsize: 0 resident: 191049728 share: 0 rss: 52178944 rss_rlim: 0
CPU usage: start_time: 1170745449 rtime: 0 utime: 2120 stime: 0 cutime:1980 cstime: 0 timeout: 140 it_real_value: 0 frequency: 0

Backtrace was generated from '/home/vsridhars/apps/garnome/bin/evolution-2.8'

(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 -1209116256 (LWP 6561)]
[New Thread -1329595504 (LWP 6597)]
[New Thread -1318061168 (LWP 6579)]
[New Thread -1299588208 (LWP 6578)]
[New Thread -1289098352 (LWP 6577)]
[New Thread -1278215280 (LWP 6576)]
[New Thread -1267725424 (LWP 6575)]
[New Thread -1257235568 (LWP 6572)]
[New Thread -1245713520 (LWP 6570)]
[New Thread -1235223664 (LWP 6569)]
[New Thread -1222759536 (LWP 6568)]
[New Thread -1212253296 (LWP 6566)]
0x00a8c402 in __kernel_vsyscall ()

+ Trace 108376

Thread 1 (Thread -1209116256 (LWP 6561))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
from /home/vsridhars/apps/garnome/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 resort_node
from /home/vsridhars/apps/garnome/lib/evolution/2.8/libetable.so.0
#5 etta_sort_info_changed
from /home/vsridhars/apps/garnome/lib/evolution/2.8/libetable.so.0
#6 resort_model
from /home/vsridhars/apps/garnome/lib/evolution/2.8/libetable.so.0
#7 g_idle_dispatch
from /home/vsridhars/apps/garnome/lib/libglib-2.0.so.0
#8 g_main_context_dispatch
from /home/vsridhars/apps/garnome/lib/libglib-2.0.so.0
#9 g_main_context_iterate
from /home/vsridhars/apps/garnome/lib/libglib-2.0.so.0
#10 g_main_loop_run
from /home/vsridhars/apps/garnome/lib/libglib-2.0.so.0
#11 bonobo_main
from /home/vsridhars/apps/garnome/lib/libbonobo-2.so.0
#12 main
#0 __kernel_vsyscall



----------- .xsession-errors (16360 sec old) ---------------------
** (ssindex:3580): WARNING **: Unable to load key '/apps/gnumeric/core/sort/default/retain-formats'
** (ssindex:3580): WARNING **: Using default value 'true'
** (ssindex:3580): WARNING **: Unable to load key '/apps/gnumeric/core/sort/default/ascending'
** (ssindex:3580): WARNING **: Using default value 'true'
** (ssindex:3580): WARNING **: Unable to load key '/apps/gnumeric/core/sort/dialog/max-initial-clauses'
** (ssindex:3580): WARNING **: Using default value '10'
** (ssindex:3580): WARNING **: Unable to load key '/apps/gnumeric/dialogs/rs/unfocused'
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-02-06 17:45:21 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 404871 ***