Bug 366241 - Brush Settings' Test Area locks up if you press weird combinations of buttons. Only restarting Kitra fixes it.
Summary: Brush Settings' Test Area locks up if you press weird combinations of buttons...
Status: RESOLVED DUPLICATE of bug 363080
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.0.1 Alpha
Platform: unspecified All
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-29 12:38 UTC by Scott Mansell
Modified: 2016-08-08 17:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Mansell 2016-07-29 12:38:46 UTC
Sometimes the Test area gets confused when you press multiple mouse (or tablet) buttons at once and stops drawing anything until your restart kitra.




Reproducible: Always

Steps to Reproduce:
Reproduction with a mouse:

1. Create new document, Open Brush settings.
2. Start Drawing into the test area with left click
3. While still holding left click, press the right mouse button.

Actual Results:  
Notice that you can't draw in the test area any more. Nothing short of restarting Krita will fix it.

Expected Results:  
Not having to restart Krita every time I hit the wrong button on my stylus. 

I've managed to reproduce this on both Windows 10 and Linux on both Krita 3.0 and 3.0.1 alpha with some mixed results, like either middle clicking and right clicking while holding left mouse will lock it on Linux. But on windows only right click triggers it when using the mouse and only middle click triggers it when using a drawing tablet (I have a Wacom PTZ-630)

I'm pretty sure that the same bug (or a closely related one) exists in the main canvas too, but I haven't managed to reliably reproduce it: only sporadically on windows and only with a tablet (and it fixes itself when you switch brushes).
Comment 1 wolthera 2016-08-08 17:53:52 UTC

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