Bug 388444 – crash in Evolution: Just saved an email atta...

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 388444 - crash in Evolution: Just saved an email atta...


Summary:	crash in Evolution: Just saved an email atta...


Status:	RESOLVED DUPLICATE of bug 363472

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:	2006-12-21 23:13 UTC by alexmcconnell
Modified:	2006-12-21 23:38 UTC

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

Description alexmcconnell 2006-12-21 23:13:17 UTC

What were you doing when the application crashed?
Just saved an email attachment to disk.


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

Memory status: size: 250499072 vsize: 0 resident: 250499072 share: 0 rss: 56725504 rss_rlim: 0
CPU usage: start_time: 1166735788 rtime: 0 utime: 8532 stime: 0 cutime:8182 cstime: 0 timeout: 350 it_real_value: 0 frequency: 5365

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 -1232738640 (LWP 5839)]
[New Thread -1374741600 (LWP 6158)]
[New Thread -1290814560 (LWP 5904)]
[New Thread -1257243744 (LWP 5899)]
[New Thread -1399919712 (LWP 5898)]
[New Thread -1255916640 (LWP 5874)]
[New Thread -1366348896 (LWP 5860)]
[New Thread -1357956192 (LWP 5859)]
[New Thread -1349563488 (LWP 5858)]
[New Thread -1315992672 (LWP 5854)]
[New Thread -1307599968 (LWP 5853)]
[New Thread -1299207264 (LWP 5852)]
[New Thread -1282421856 (LWP 5850)]
[New Thread -1274029152 (LWP 5849)]
[New Thread -1265636448 (LWP 5848)]
[New Thread -1247421536 (LWP 5846)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 96097

Thread 1 (Thread -1232738640 (LWP 5839))

#0 __kernel_vsyscall
#1 waitpid
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 gtk_file_info_get_is_folder
from /usr/lib/libgtk-x11-2.0.so.0
#6 _gtk_file_chooser_default_new
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_tree_model_filter_convert_child_iter_to_iter
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_tree_model_sort_convert_iter_to_child_iter
from /usr/lib/libgtk-x11-2.0.so.0
#9 _gtk_marshal_VOID__BOXED_BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 gtk_tree_model_row_inserted
from /usr/lib/libgtk-x11-2.0.so.0
#15 _gtk_file_system_model_get_info
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_cclosure_marshal_VOID__POINTER
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#21 fs_module_create
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#22 gnome_vfs_monitor_callback
from /usr/lib/libgnomevfs-2.so.0
#23 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#27 bonobo_main
from /usr/lib/libbonobo-2.so.0
#28 main
at main.c line 615
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-12-21 23:38:01 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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