Bug 370455

Summary: Brush cursor changes to arrow on certain linear areas on the canvas
Product: [Applications] krita Reporter: Raghavendra kamath <raghu>
Component: GeneralAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: halla
Priority: NOR    
Version: git master (please specify the git hash!)   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: demo showing the bug

Description Raghavendra kamath 2016-10-11 12:15:02 UTC 
In some areas along the canvas , along a line , the brush cursor changes to arrow and when users goes to paint by clicking on that particular spot the cursor changes to grab handle and moves the entire krita window, as if it is moved by holding the alt key in linux.

I tested if this is the same bug as https://bugs.kde.org/show_bug.cgi?id=363283 but this also happens in  import/export refactoring branch which has the fix for the above mentioned bug.

So I assume this is a different bug.

the cursor changes to arrow along a particular line in different places in canvas as if it was an edge of a tile. this changes hinders the painting process as it accidentally moves krita window

Reproducible: Always
Comment 1 Raghavendra kamath 2016-10-11 12:20:10 UTC 
Created attachment 101526 [details]
demo showing the bug
Comment 2 Raghavendra kamath 2016-10-11 14:27:03 UTC 
update : This happens with all the tools not just brush
Comment 3 Raghavendra kamath 2016-10-12 09:55:14 UTC 
This also happens when opengl is off and also in the latest appimage (krita-3.0.1.1-x86_64)

My graphic driver (nvidia) got updated on 09-09-2016 however this issue started recently in this week.

I'll try to test more to see if something on my computer is causing this
Comment 4 Halla Rempt 2016-10-13 09:36:26 UTC 
Did changing window manager make a difference?
Comment 5 Raghavendra kamath 2016-10-13 14:07:56 UTC 
yes changing the wm to openbox helped.
Thus confirming that it is a kwin issue

I wonder how i should describe this while reporting to kwin bugs

marking it resolved invalid now :)

thank you