Bug 477958 – crash in Evolution: while trying to close window

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 477958 - crash in Evolution: while trying to close window


Summary:	crash in Evolution: while trying to close window


Status:	RESOLVED DUPLICATE of bug 387143

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-09-18 06:47 UTC by lesley.walker
Modified:	2007-09-25 01:40 UTC

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

Description lesley.walker 2007-09-18 06:47:56 UTC

What were you doing when the application crashed?
I had opened an email for reading (likely HTML format wtih graphics) and the window wasn't responding. I clicked on the corner "x" box to close the window, and then it crashed.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 169889792 vsize: 0 resident: 169889792 share: 0 rss: 33497088 rss_rlim: 0
CPU usage: start_time: 1188194949 rtime: 0 utime: 40635 stime: 0 cutime:39592 cstime: 0 timeout: 1043 it_real_value: 0 frequency: 1

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233451344 (LWP 22726)]
[New Thread -1350763616 (LWP 11461)]
[New Thread -1359156320 (LWP 7329)]
[New Thread -1322660960 (LWP 7322)]
[New Thread -1324352608 (LWP 7318)]
[New Thread -1297020000 (LWP 22742)]
[New Thread -1274025056 (LWP 22737)]
[New Thread -1265632352 (LWP 22735)]
[New Thread -1255552096 (LWP 22734)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 163690

Thread 1 (Thread -1233451344 (LWP 22726))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 segv_redirect
at main.c line 426
#4 <signal handler called>
#5 resort_node
at e-tree-table-adapter.c line 158
#6 etta_sort_info_changed
at e-tree-table-adapter.c line 824
#7 resort_model
at e-tree-table-adapter.c line 751
#8 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#11 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#12 bonobo_main
from /usr/lib/libbonobo-2.so.0
#13 main
at main.c line 615
#0 __kernel_vsyscall

Comment 1 lesley.walker 2007-09-18 06:52:25 UTC

See also bug number 468347 which resulted from a previous crash. After that crash, I applied all the Evolution updates that were available.

Comment 2 lesley.walker 2007-09-25 01:33:44 UTC

This is most likely yet another duplicate of 364700. I'll mark it as such, and live with it at least until a newer version comes through the distribution channel.

*** This bug has been marked as a duplicate of 364700 ***

Comment 3 Tobias Mueller 2007-09-25 01:40:30 UTC

well. I don't know why you think so, but I'd say this is a dup of bug 387143 since the stacktrace matches pretty well.
See, here we have the functions
  resort_node, etta_sort_info_changed, resort_model, g_source_is_destroyed 
called (in reversed order, though). So do we in bug 387143.

Cheers :)

*** This bug has been marked as a duplicate of 387143 ***