Bug 494294

Summary:	strange mouse (click -> double click) behavior after resuming
Product:	[Plasma] kwin	Reporter:	Thomas Eschenbacher <Thomas.Eschenbacher>
Component:	input	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	duha.bugs
Priority:	NOR
Version First Reported In:	6.1.5
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Thomas Eschenbacher 2024-10-08 14:19:41 UTC

SUMMARY


STEPS TO REPRODUCE
1.  start a plasma session and open a "konsole" window
2.  suspend
3.  resume
4. click on a tab or try to use the mouse within a konsole window

OBSERVED RESULT

The konsole window shows weird behaviour, when doing a single mouse click, the reaction is like normally done for double clicks. This has nothing to do with the mouse, other windows (e.g. Firefox) behave normally. 

EXPECTED RESULT

Mouse events should be handles as before.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux 2.15
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION

I have configured the desktop to use single clicks instead of double clicks for starting programs.

The behavior is specific to all instances of the program which have been been there before suspending, when I start a new instance in parallel it behaves normally - that means: I can have two instances (an old/resumed one and a freshly started one) side by side on the same screen and one is behaving wrong, the other one works fine. I have not found a workaround, closing the window and starting a new instance seems to be the only way out.

Sometimes kdevelop shows the same strange behaviour. Only restarting helps.

Comment 1 Thomas Eschenbacher 2024-10-18 12:30:59 UTC

update:
This also happens when switching to a text console and then switching back into X11.
In the meanwhile I also switched the X11 input driver from evdev to libevent - no change :-(

Comment 2 Thomas Eschenbacher 2024-10-22 18:19:23 UTC

I tried "qterminal" instead of "konsole" and it shows the same misbehaviour after suspend/resume, so I guess it has nothing to do with the application itself but with the framework.

Comment 3 Thomas Eschenbacher 2024-11-21 09:06:50 UTC

problem is gone, no idea why, probably one of the latest Gentoo updates