Bug 487236 – crash in Tasks: open picture in email

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 487236 - crash in Tasks: open picture in email


Summary:	crash in Tasks: open picture in email


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-16 18:02 UTC by rettinger
Modified:	2007-10-22 07:58 UTC

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

Description rettinger 2007-10-16 18:02:23 UTC

Version: 2.10

What were you doing when the application crashed?
open picture in email


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 169746432 vsize: 169746432 resident: 79728640 share: 43020288 rss: 79728640 rss_rlim: 4294967295
CPU usage: start_time: 1192563517 rtime: 6139 utime: 5868 stime: 271 cutime:3 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208412448 (LWP 7146)]
[New Thread -1360028784 (LWP 18601)]
[New Thread -1237005424 (LWP 7264)]
[New Thread -1226007664 (LWP 7183)]
(no debugging symbols found)
0x0023a402 in __kernel_vsyscall ()

+ Trace 170625

Thread 1 (Thread -1208412448 (LWP 7146))

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



----------- .xsession-errors (38 sec old) ---------------------
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
QF
--------------------------------------------------

Comment 1 Akhil Laddha 2007-10-22 07:58:24 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 ***