Bug 457692 – crash in Evolution: Evolution - opening a sc...

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 457692 - crash in Evolution: Evolution - opening a sc...


Summary:	crash in Evolution: Evolution - opening a sc...


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-07-17 16:28 UTC by elo
Modified:	2007-07-29 14:40 UTC

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

Description elo 2007-07-17 16:28:35 UTC

What were you doing when the application crashed?
Evolution - opening a scanned baby LPEG picture attached


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

Memory status: size: 578031616 vsize: 578031616 resident: 51630080 share: 21585920 rss: 73216000 rss_rlim: 1791457280
CPU usage: start_time: 1184689613 rtime: 425 utime: 379 stime: 46 cutime:24 cstime: 9 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 47489312042160 (LWP 3869)]
[New Thread 1107577152 (LWP 3908)]
[New Thread 1107310912 (LWP 3907)]
[New Thread 1098918208 (LWP 3905)]
[New Thread 1090525504 (LWP 3899)]
[New Thread 1082132800 (LWP 3878)]
0x00002b30f51d9c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 148619

Thread 1 (Thread 47489312042160 (LWP 3869))

#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 André Klapper 2007-07-29 14:40:57 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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