Bug 1895636 - Can't drag and drop attachments to evolution mail composer
Summary: Can't drag and drop attachments to evolution mail composer
Keywords:
Status: CLOSED DUPLICATE of bug 1888623
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milan Crha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-07 22:47 UTC by pkoz
Modified: 2020-11-09 08:26 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-09 08:26:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description pkoz 2020-11-07 22:47:21 UTC
Description of problem:
Can't drag and drop file attachments to evolution mail composer when composer is started from the main mail reader by New. Instead attaching the file, its file:// link is inserted in the mail text regardless where it is dropped: mail text field or attachment bar.

When attempting to "attach" a second file, evolution crashes while the second attachment yet hovers above the composer window but before it is actually dropped: dumps core on FC32 and severely hangs on FC33, blocking the whole desktop so that I had to switch to a terminal, log in and kill -9 both evolution and file browser (caja).

Drag and drop mostly works in a standalone composer: dragging file to attachmnet bar produces an attachment, and dragging it to text field produces the file:// link, no crashes.  Mostly means that some files are not accepted by the composer but I was not able to make out any particular pattern.
 


Version-Release number of selected component (if applicable):
Name        : evolution
Version     : 3.38.1
Release     : 1.fc33
Architecture: x86_64

How reproducible:
Always

Steps to Reproduce:
See desription.

Actual results:
Evolution crashes

Expected results:
File is attached to the mail.

Additional info:

Comment 1 Milan Crha 2020-11-09 08:26:42 UTC
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

*** This bug has been marked as a duplicate of bug 1888623 ***


Note You need to log in before you can comment on or make changes to this bug.