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 413754 - Crash while attaching images.
Crash while attaching images.
Status: RESOLVED DUPLICATE of bug 342242
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-03-02 06:19 UTC by liquidsunshine
Modified: 2007-03-02 13:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description liquidsunshine 2007-03-02 06:17:13 UTC 
From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: Crash while attaching images.

Distribution: Ubuntu 6.06 (dapper)
Package: Evolution
Severity: critical
Version: GNOME2.14.3 2.6.x
Gnome-Distributor: Ubuntu
Synopsis: Crash while attaching images.
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Evolution crashes while attaching an image to an email dragged from
FireFox.

Steps to reproduce the crash:
1. Drag an image from firefox into an email being composed.  
2. Specifically, the image at
http://www.judithbarathart.com/input/image/Flower%20Photography/Flower%
20Photography_M/Blue%20Carnation.jpg
was used
3. Evolution crashes.

Expected Results:
It should attach normally (and does with some images) but in this
instance it crashes.

How often does this happen?
Consistently.

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231124256 (LWP 27348)]
[New Thread -1331807312 (LWP 27379)]
[New Thread -1323127888 (LWP 27378)]
[New Thread -1298138192 (LWP 27363)]
[New Thread -1297871952 (LWP 27356)]
[New Thread -1257108560 (LWP 27355)]
[New Thread -1267729488 (LWP 27354)]
[New Thread -1276122192 (LWP 27352)]
[New Thread -1248678992 (LWP 27349)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 115120

Thread 1 (Thread -1231124256 (LWP 27348))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 820
  • #3 es_menu_hook_get_type
  • #4 <signal handler called>
  • #5 camel_mime_part_get_content_type
    from /usr/lib/libcamel-1.2.so.0
  • #6 e_attachment_new
    from /usr/lib/evolution/2.6/libemiscwidgets.so.0
  • #7 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 e_attachment_build_remote_file
    from /usr/lib/evolution/2.6/libemiscwidgets.so.0
  • #13 gnome_vfs_async_get_job_limit
    from /usr/lib/libgnomevfs-2.so.0
  • #14 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 main
  • #0 __kernel_vsyscall 







------- Bug created by bug-buddy at 2007-03-02 06:19 -------


Bugreport had an attachment. This cannot be imported to Bugzilla.
Contact bugmaster@gnome.org if you are willing to write a patch for this.
Comment 1 Susana 2007-03-02 13:23:02 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 342242 ***