Bug 1295210

Summary:	Evolution with Wayland: dragging mail to another folder does a copy instead of a move
Product:	[Fedora] Fedora	Reporter:	Frank Ansari <mail>
Component:	gtk3	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	23	CC:	ccecchi, kparal, lucilanga, mbarnes, mclasen, mcrha, tpopela
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-19 17:19:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Frank Ansari 2016-01-03 16:22:20 UTC

Description of problem:
In the Evolution mail client when I drag an email to another folder it is not moved there but copied. When I want to copy it I can either move and and delete the original mail from the inbox or I can use the menu. From the menu when I select "move" it works.

Version-Release number of selected component (if applicable):
Evolution 3.18.3

How reproducible:
Take a mail from the inbox and drag it to another folder.

Steps to Reproduce:
1.
2.
3.

Actual results:
Mail is copied.

Expected results:
Mail should be moved.

Additional info:
This works as it should when I choose "GNOME" instead of "GNOME Wayland" at gdm.
So it is a problem which occurs in Evolution only when Wayland is used.
I can reproduce this behavior.

Comment 1 Kamil Páral 2016-01-05 14:41:29 UTC

You might want to check the most frequent wayland issues on fedora wiki, this one is reported here:
https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Drag_and_drop_always_makes_copies

Here's the upstream bug for it:
https://bugzilla.gnome.org/show_bug.cgi?id=755625

Comment 2 Milan Crha 2016-01-19 17:19:36 UTC

Thanks for a bug report and the link to the upstream bug. I'm closing this as such, because there is no need to have two places to deal with one issue.