Bug 441633 – crash in Evolution: I was trying to open a j...

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 441633 - crash in Evolution: I was trying to open a j...


Summary:	crash in Evolution: I was trying to open a j...


Status:	RESOLVED DUPLICATE of bug 273386

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-27 18:03 UTC by mstasiko
Modified:	2007-05-28 12:54 UTC

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

Description mstasiko 2007-05-27 18:03:34 UTC

What were you doing when the application crashed?
I was trying to open a jpeg image


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

Memory status: size: 507555840 vsize: 507555840 resident: 42373120 share: 20074496 rss: 62447616 rss_rlim: 1793720320
CPU usage: start_time: 1180289045 rtime: 699 utime: 671 stime: 28 cutime:0 cstime: 0 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 47379246779600 (LWP 12875)]
[New Thread 1115969856 (LWP 12887)]
[New Thread 1115703616 (LWP 12886)]
[New Thread 1107310912 (LWP 12885)]
[New Thread 1090525504 (LWP 12884)]
[New Thread 1098918208 (LWP 12882)]
[New Thread 1082132800 (LWP 12879)]
(no debugging symbols found)
0x00002b1754b6fc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 136308

Thread 1 (Thread 47379246779600 (LWP 12875))

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

Comment 1 Pedro Villavicencio 2007-05-28 12:54:38 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 273386 ***