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 737431 - Brushes too slow with SilverCrest Graphic Tablet after new Update => Use impossible
Brushes too slow with SilverCrest Graphic Tablet after new Update => Use impo...
Status: RESOLVED DUPLICATE of bug 736220
Product: GIMP
Classification: Other
Component: Tools
2.8.14
Other Windows
: Normal blocker
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2014-09-26 13:12 UTC by pokefreak
Modified: 2014-12-26 13:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description pokefreak 2014-09-26 13:12:45 UTC 
After downloading the new Update,
I tried to work on my newest pictures. 

But every time, I want to draw a line with a brush or anything similar, the cursor slows down, when I use my SilverCrest graphic tablet and fails with darwing down the line I drew on the Tablet.
With the computer mouse, it works like usual, no matter to both if soft drawing is enabled or disabled. 
Before the update, my GT worked as it should and I don't think the bug is there, rather in GIMP somewhere. I hope somebody can fix this so I can go on with my pictures.

Greetings.

P.S.: Is it possible that the fading still doesn't work since V.2.8?
Comment 1 Michael Schumacher 2014-09-26 14:45:29 UTC 
This is the same as bug 736220, I guess.
Comment 2 Marie Nad 2014-10-12 08:19:49 UTC 
Hello, i am the same problème with the same tablet since the update the 2.8.10 to 2.8.14 (sorry for my english, i'am french).
Comment 3 Michael Schumacher 2014-10-12 21:01:31 UTC 
Marie, please have a look at bug 736411 - if the symptoms are the same, we can resolve this one as a duplicate.
Comment 4 Michael Schumacher 2014-12-26 13:44:20 UTC 
Assuming it is a duplicate; let's use bug 736220 for now (which might be duplicated to bug 736411 eventually).

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