Bug 521622 – crash in Tasks: viewing "inline" attachm...

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 521622 - crash in Tasks: viewing "inline" attachm...


Summary:	crash in Tasks: viewing "inline" attachm...


Status:	RESOLVED DUPLICATE of bug 467763

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-03-10 17:25 UTC by johenkel
Modified:	2008-03-11 15:17 UTC

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

Description johenkel 2008-03-10 17:25:47 UTC

Version: 2.10

What were you doing when the application crashed?
viewing "inline" attachments (jpeg)


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

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 187092992 vsize: 187092992 resident: 54870016 share: 45244416 rss: 54870016 rss_rlim: 4294967295
CPU usage: start_time: 1205169729 rtime: 1717 utime: 1499 stime: 218 cutime:0 cstime: 0 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 -1208710416 (LWP 31733)]
[New Thread -1263191152 (LWP 31804)]
[New Thread -1284564080 (LWP 31781)]
[New Thread -1210811504 (LWP 31755)]
[New Thread -1252693104 (LWP 31753)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 191991

Thread 1 (Thread -1208710416 (LWP 31733))

#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/libeutil.so.0
#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_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /lib/libgobject-2.0.so.0
#20 ??
from /lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#22 g_signal_emit
from /lib/libgobject-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib/libgdk-x11-2.0.so.0
#27 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#28 ??
from /lib/libglib-2.0.so.0
#29 g_main_loop_run
from /lib/libglib-2.0.so.0
#30 bonobo_main
from /usr/lib/libbonobo-2.so.0
#31 main
#0 __kernel_vsyscall



----------- .xsession-errors (32 sec old) ---------------------
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x15118f8
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x15118f8
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x15118f8
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x15118f8
--------------------------------------------------

Comment 1 Tobias Mueller 2008-03-11 15:17:00 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 467763 ***