Bug 371725

Summary: Cursor Changes to Arrow on Text Editors
Product: [Plasma] kwin Reporter: Tsu Jan <tsujan2000>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 5.8.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Arrow Cursor Inside Kate

Description Tsu Jan 2016-10-26 21:36:38 UTC
Created attachment 101812 [details]
Arrow Cursor Inside Kate

With compositing enabled, when a text editor is tiled by dragging to a screen edge, the cursor changes from `Qt::IBeamCursor` to `Qt::ArrowCursor` when it's near the center horizontally (and maybe in other places too). That not only makes it impossible to select/edit the text but also moves the window if the left mouse button is pressed.

The text editor isn't important in this (the attached screenshot is about Kate). I can reproduce this issue both in KDE Plasma and in LXQt+kwin; so I think the problem is in kwin.

The problem only occurs when the window is tiled, as far as I've seen.
Comment 1 Tsu Jan 2016-10-26 22:35:21 UTC
More info:

As soon as I resize a left/right tiled window (of a text editor) just a little, the problem disappears, even after I re-tile it. But when I close, open and tile it again, the problem appears exactly on the same horizontal line near the center.
Comment 2 Tsu Jan 2016-10-26 23:11:55 UTC
Still more info:

There is definitely a `QEvent::Leave` in QPlainTextEdit when the cursor reaches the horizontal middle line -- I tested with a text editor of mine.
Comment 3 Martin Flöser 2016-10-27 05:34:30 UTC
That might be a problem I investigated this week: https://phabricator.kde.org/D3151

If you have a chance to test the patch and verify that it fixes the problem, that would be appreciated.
Comment 4 Tsu Jan 2016-10-27 13:14:56 UTC
I confirm that the issue is fixed by https://phabricator.kde.org/D3151. Thank you very much!
Comment 5 Martin Flöser 2016-10-28 09:51:32 UTC
Thanks for testing! I mark as duplicate to the original bug reported about the issue. Now I need to make sure that we get that into 5.8.3!

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