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 517053 - crash in Tasks: Opening an attached JPEG
crash in Tasks: Opening an attached JPEG
Status: RESOLVED DUPLICATE of bug 340165
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-02-17 18:58 UTC by bgo
Modified: 2008-02-18 09:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bgo 2008-02-17 18:58:15 UTC 
Version: 2.10

What were you doing when the application crashed?
Opening an attached 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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 130416640 vsize: 130416640 resident: 49913856 share: 32948224 rss: 49913856 rss_rlim: 4294967295
CPU usage: start_time: 1203274529 rtime: 1684 utime: 1497 stime: 187 cutime:71 cstime: 29 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 -1208780048 (LWP 8115)]
[New Thread -1284142192 (LWP 8171)]
[New Thread -1236730992 (LWP 8134)]
[New Thread -1225831536 (LWP 8120)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 189503

Thread 1 (Thread -1208780048 (LWP 8115))

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


----------- .xsession-errors (26 sec old) ---------------------
  Resource id:  0x3e01d49
(evolution:8115): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject'
(evolution:8115): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
(evolution:8115): camel-CRITICAL **: camel_object_ref: assertion `CAMEL_IS_OBJECT(o)' failed
(evolution:8115): camel-WARNING **: Trying to check junk data is OBJECT 'medium'
(evolution:8115): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
(evolution:8115): camel-CRITICAL **: camel_medium_get_content_object: assertion `CAMEL_IS_MEDIUM (medium)' failed
(evolution:8115): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-18 09:36:33 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 340165 ***