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 599190 - Drag and drop broken for received MIME parts
Drag and drop broken for received MIME parts
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[attachments] evolution[dnd]
: 600401 602191 602302 602362 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-21 13:30 UTC by Pedro Villavicencio
Modified: 2009-11-19 12:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Pedro Villavicencio 2009-10-21 13:30:06 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/456690

"In previous versions of Evolution (2.26, though possibly 2.24 - I don't have either to test just now) it was possible to drag an attachment from one email message to a new email message being composed.

With the current version, if I drag an attachment from the attachment list of a message viewer or a message composer and drop it on a message composer's attachment list - nothing happens. There is no error message and the file being dragged is not attached to the new email.

This feature is very useful when I'm writing a new email to someone and I need to attach a file another person sent me in an email. With previous versions I could simply locate the correct email and drag the attachment from there. With the current version I have to save the attachment to disk, find it using the "open file dialog" from "Add attachment" on the new email composer, and lastly find the file using the file browser and delete it."
Comment 1 Matthew Barnes 2009-10-22 20:55:44 UTC
Confirming, but it works fine for me if you drop it in the text area above the attachment list.  So there's a work around in the interim.
Comment 2 Oded Arbel 2009-10-22 21:07:57 UTC
I'm sorry, but dragging into the text area does not work for me.
Comment 3 Matthew Barnes 2009-10-22 22:52:26 UTC
Where are you dragging from?  The icon in the attachment list at the top of the source message or the button at the bottom that lets you view the attachment inline?  Dragging from the button does not currently work.  Dragging from the icon at the top does.
Comment 4 Oded Arbel 2009-10-23 11:13:22 UTC
I'm dragging from the icon in the list which doesn't work for me. When I drag anywhere from the list - even onto the desktop or a file browser - the "Saving" progress bar plays but nothing happens other then that.

I wasn't aware that its possible to drag the button.
Comment 5 Akhil Laddha 2009-10-26 05:31:18 UTC
Matt, did you forget to close the bug ?  

It should be fixed as per commit 
http://git.gnome.org/cgit/evolution/commit/?id=17b6527680218efff72000b4250dea862cda0cef
Comment 6 Matthew Barnes 2009-10-26 15:02:53 UTC
I can still reproduce this in 2.28.  2.29 works fine after that commit.

A different typo somewhere, I guess.
Comment 7 Matthew Barnes 2009-11-02 14:59:05 UTC
*** Bug 600401 has been marked as a duplicate of this bug. ***
Comment 8 Matthew Barnes 2009-11-02 14:59:52 UTC
Dragging to Nautilus is also broken.  I suspect the underlying cause is the same.
Comment 9 Matthew Barnes 2009-11-18 13:52:30 UTC
*** Bug 602191 has been marked as a duplicate of this bug. ***
Comment 10 Matthew Barnes 2009-11-18 13:53:03 UTC
*** Bug 602302 has been marked as a duplicate of this bug. ***
Comment 11 Matthew Barnes 2009-11-19 00:11:34 UTC
*** Bug 602362 has been marked as a duplicate of this bug. ***
Comment 12 Matthew Barnes 2009-11-19 00:12:27 UTC
Lots of dupes piling up.  I'm working on it.
Comment 13 Matthew Barnes 2009-11-19 12:00:58 UTC
Fixed for Evolution 2.28.2 in:
http://git.gnome.org/cgit/evolution/commit/?h=gnome-2-28&id=e14ec8882808dd938a1edbfcadd399a4f20e1569

I don't understand why the exact same logic works in 2.29 but not 2.28.  I guess if the problem crops up again in a later release I can always revisit this.