After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 758500 - Surface Pro 3 Pen eraser only works once
Surface Pro 3 Pen eraser only works once
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: General
2.8.16
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2015-11-22 17:43 UTC by Florian
Modified: 2018-05-24 15:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
crash switching between stylus and eraser (8.01 KB, text/plain)
2018-05-13 18:42 UTC, Joshua
Details

Description Florian 2015-11-22 17:43:13 UTC
I have some problem with the Surface Pro 3 pen input.

The eraser only works the first time used.

How to reproduce:
- Enable eraser and stylus in input devices
- draw something with the stylus
- use the eraser(works)
- draw something with stylus
- use the eraser again (not working any more)

gimp --version --verbose output:
GNU Image Manipulation Program Version 2.8.16
git-describe: GIMP_2_8_14-268-g3152b6e

verwendet GEGL Version 0.2.0 (gebaut gegen Version 0.2.0)
verwendet GLib Version 2.46.1 (gebaut gegen Version 2.46.1)
verwendet GdkPixbuf Version 2.30.8 (gebaut gegen Version 2.30.8)
verwendet GTK+ Version 2.24.28 (gebaut gegen Version 2.24.28)
verwendet Pango Version 1.38.1 (gebaut gegen Version 1.38.1)
verwendet Fontconfig Version 2.11.94 (gebaut gegen Version 2.11.94)
verwendet Cairo Version 1.14.2 (gebaut gegen Version 1.14.2)
Comment 1 Michael Schumacher 2015-11-23 11:17:01 UTC
But you get switched back to the eraser, right? Do any of its tool options change?
Comment 2 Florian 2015-11-23 11:32:57 UTC
Gimp switches back to the eraser, but it is not following the pen.
The tool options don't change.
Comment 3 Florian 2015-11-23 12:16:19 UTC
here is a small video with the problem
https://www.youtube.com/watch?v=s7Xl5UmEI-w

I just noticed, that the first time after using the eraser, the Stylus is not drawing. (at 0:08 in the video)
Comment 4 Andrew Chadwick 2016-06-16 12:45:53 UTC
Possibly related MyPaint bug (under GTK3): https://github.com/mypaint/mypaint/issues/484

We have a bounty out on that one, and may be directing folks towards current GDK if the problem lies there.
Comment 5 Pete 2016-07-06 01:24:16 UTC
I have the same problem with Surface Book and more specifically, it seems to be related to the eraser stylus's "mouse Up" command not being received or interpreted.  using the eraser the first time after gimp startup (and only the eraser) when I press and release, it draws lines in between what should be separate strokes, as if it were staying pressed down the whole time.

Also no pressure data seems to be making it through (which is not a problem, per-se, and might be a limitation of Microsoft's "nTrig" technology)

I also made a video to demonstrate:
https://www.youtube.com/watch?v=jyVAlmBQUqY
Comment 6 davidgslade 2017-10-14 04:57:36 UTC
I'm having the same issue on my Surface Pro 4.  Exactly as described, at start up it functions perfectly but afterwords it switches to eraser when I engage eraser part of my surface pen but the cursor remains frozen, even though the program appears to be clocking the changes in location of the stylus (x y coordinate data changes while cursor is frozen).  Problem persists in 2.9.6 as well.
Comment 7 Ben 2018-02-12 18:26:02 UTC
I am also having this issue on my surface pro 2, Which uses wacom tech not nTrig. I get the exact same effect in GIMP and Krita, so I don't think the issue is specifically gimp. running ubuntu 17.10 gnome gdm wayland
Comment 8 Joshua 2018-05-13 18:42:15 UTC
Created attachment 371977 [details]
crash switching between stylus and eraser

I've been having the problem that along with it only work once it also crashes sometimes when you try to switch between the stylus and eraser.
Comment 9 GNOME Infrastructure Team 2018-05-24 15:56:40 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/808.