Bug 441717 – crash in Evolution: downloading jpeg file

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 441717 - crash in Evolution: downloading jpeg file


Summary:	crash in Evolution: downloading jpeg file


Status:	RESOLVED DUPLICATE of bug 441634

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-05-28 01:46 UTC by mstasiko
Modified:	2007-05-28 12:55 UTC

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

Description mstasiko 2007-05-28 01:46:37 UTC

What were you doing when the application crashed?
downloading jpeg file


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 565981184 vsize: 565981184 resident: 51236864 share: 23064576 rss: 74301440 rss_rlim: 1793720320
CPU usage: start_time: 1180315337 rtime: 1159 utime: 1078 stime: 81 cutime:182 cstime: 21 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47318889536720 (LWP 14005)]
[New Thread 1132755264 (LWP 14127)]
[New Thread 1124362560 (LWP 14032)]
[New Thread 1115969856 (LWP 14017)]
[New Thread 1115703616 (LWP 14016)]
[New Thread 1107310912 (LWP 14015)]
[New Thread 1098918208 (LWP 14014)]
[New Thread 1090525504 (LWP 14012)]
[New Thread 1082132800 (LWP 14009)]
(no debugging symbols found)
0x00002b0947248c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 136373

Thread 1 (Thread 47318889536720 (LWP 14005))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_hash_table_lookup
from /opt/gnome/lib64/libglib-2.0.so.0
#4 em_format_set_inline
from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
#5 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#6 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#8 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#9 gtk_button_set_alignment
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#10 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#11 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#13 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#14 gtk_button_released
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#15 gtk_marshal_BOOLEAN__VOID
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#16 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#17 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#19 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#20 gtk_widget_get_default_style
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#21 gtk_propagate_event
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#22 gtk_main_do_event
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#23 gdk_add_client_message_filter
from /opt/gnome/lib64/libgdk-x11-2.0.so.0
#24 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#25 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#26 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#27 bonobo_main
from /opt/gnome/lib64/libbonobo-2.so.0
#28 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Pedro Villavicencio 2007-05-28 12:55:49 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 441634 ***