Bug 446891

Summary:	Wayland: drag-source application cannot terminate correctly after dragging something from them
Product:	[Plasma] kwin	Reporter:	Alexey Ilyin <alexey-ilyin>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	almazgaliev99, andrea.ippo, auxsvr, mauromol, nate
Priority:	NOR	Keywords:	wayland-only
Version First Reported In:	5.23.4	Flags:	alexey-ilyin: Wayland+
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=438004
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Alexey Ilyin 2021-12-12 18:51:05 UTC

It looks like a drag-and-drop operation from any KDE app does not complete correctly, which leads to the cursor then behaving strangely (see https://bugs.kde.org/show_bug.cgi?id=438004), and the drag-source application after that cannot terminate its work and remains stuck after closing. Running the drag-source app from the terminal gives no hints of errors.

I'm not sure which category I should place this bug in, so please don't judge strictly =)
I would be happy to help with reproducing this.

STEPS TO REPRODUCE
1. Start Wayland session
2. Run Konsole and Kate, for example
3. Drag some text from Konsole to Kate
4. Close Konsole
5. Open the System Monitor and make sure Konsole hasn't exited

Instead of Konsole and Kate, there can be any two KDE applications.


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20211210
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.6-1-default (64-bit)
Graphics Platform: Wayland

Comment 1 Nate Graham 2021-12-14 21:41:56 UTC

Can reproduce dragging something from Spectacle, too. The app stops responding to keyboard input.

Comment 2 Andrea Ippolito 2022-01-22 14:57:13 UTC

Can reproduce while dragging from Dolphin some big files into a Firefox tab open on myediafire account to initiate an upload.

Comment 3 Nate Graham 2022-02-03 16:38:32 UTC

This has been fixed by the fix for Bug 449362; marking it as a duplicate!

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