Bug 394057 - ghost clicking when using selection tools
Summary: ghost clicking when using selection tools
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: 4.0.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-05-09 19:28 UTC by arielle
Modified: 2018-11-12 16:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
video demonstrating ghost clicking while using rectangle select tool (432.75 KB, video/x-flv)
2018-05-09 19:28 UTC, arielle
Details
krita_log (465.20 KB, application/octet-stream)
2018-05-12 03:29 UTC, arielle
Details

Note You need to log in before you can comment on or make changes to this bug.
Description arielle 2018-05-09 19:28:00 UTC
Created attachment 112538 [details]
video demonstrating ghost clicking while using rectangle select tool

This happens when I use the rectangle select or sometimes the rectangle draw tool.
I use a Huion graphics tablet as my monitor, and I've confirmed that that my keyboard or mouse are not causing an interference. (nothing causing the clicks from other devices)

I'll be drawing a rectangle and Krita thinks I've lifted my stylus prematurely. The undo history also indicates that Krita thinks I clicked several times in the spot where the ghost click happened as well.

I've attached a video to demonstrate. I did not lift my stylus at all during the video.
Comment 1 Halla Rempt 2018-05-10 11:26:22 UTC
* To be clear, this happens when using the stylus? 

* Could you also make a tablet log? I suspect that we're getting spurious pen proximity events, though. See https://docs.krita.org/KritaFAQ#What_if_your_tablet_is_not_recognized_by_Krita.3F for instructions on making a tablet log.

* It could also be related using libinput, like in https://bugs.kde.org/show_bug.cgi?id=394061
Comment 2 arielle 2018-05-12 03:29:41 UTC
Created attachment 112591 [details]
krita_log

Yes, this only happens with stylus. I've tested with the mouse and there's
no problem.

I haven't been experiencing anything like the bug linked in the previous
email; the brush works just fine.

I managed to create a log of the event. The file is attached.

On Thu, May 10, 2018 at 4:26 AM, Boudewijn Rempt <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=394057
>
> Boudewijn Rempt <boud@valdyas.org> changed:
>
>            What    |Removed                     |Added
> ------------------------------------------------------------
> ----------------
>                  CC|                            |boud@valdyas.org
>              Status|UNCONFIRMED                 |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
>
> --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> ---
> * To be clear, this happens when using the stylus?
>
> * Could you also make a tablet log? I suspect that we're getting spurious
> pen
> proximity events, though. See
> https://docs.krita.org/KritaFAQ#What_if_your_tablet_
> is_not_recognized_by_Krita.3F
> for instructions on making a tablet log.
>
> * It could also be related using libinput, like in
> https://bugs.kde.org/show_bug.cgi?id=394061
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Halla Rempt 2018-05-12 08:02:27 UTC
Thanks for the log.
Comment 4 Halla Rempt 2018-10-09 13:42:19 UTC
I'm sorry, but that doesn't really show anything clear :-( I'm not sure what might be going on here.
Comment 5 mvowada 2018-10-10 22:12:55 UTC
Hi Arielle,
are you still able to reproduce it with the latest Krita (https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/)? Thanks
Comment 6 Andrew Crouthamel 2018-10-27 04:10:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2018-11-12 16:04:40 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!