Bug 487688 – crash in Tasks: Clilcking on a jpeg 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 487688 - crash in Tasks: Clilcking on a jpeg atta...


Summary:	crash in Tasks: Clilcking on a jpeg atta...


Status:	RESOLVED DUPLICATE of bug 467763

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-17 22:29 UTC by jarvi
Modified:	2007-11-29 06:33 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description jarvi 2007-10-17 22:29:52 UTC

What were you doing when the application crashed?
Clilcking on a jpeg attachment


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 09:29:36 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 60802000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 1018077184 vsize: 1018077184 resident: 212336640 share: 22425600 rss: 212336640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192564761 rtime: 7940 utime: 7056 stime: 884 cutime:1 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

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

(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 46912496508512 (LWP 10947)]
[New Thread 1105209680 (LWP 714)]
[New Thread 1136679248 (LWP 16141)]
[New Thread 1074006352 (LWP 10971)]
[New Thread 1094719824 (LWP 10954)]
(no debugging symbols found)
0x0000003f1fa0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 170971

Thread 1 (Thread 46912496508512 (LWP 10947))

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

Comment 1 Akhil Laddha 2007-11-29 06:33:31 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 467763 ***