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 783943 - GIMP 2.9.5 MyPaint-Brushes weird effect
GIMP 2.9.5 MyPaint-Brushes weird effect
Status: RESOLVED DUPLICATE of bug 785087
Product: GIMP
Classification: Other
Component: Tools
git master
Other All
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2017-06-19 02:50 UTC by SenlinOS
Modified: 2018-01-03 08:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description SenlinOS 2017-06-19 02:50:48 UTC 
GIMP 2.9.5 PPA (Just updated)

Such as: MyPaint Brushes deevad-v6
spray2: A spacing stroke appeared in the splash effect.
watercolor expressive: Using this brush will cause GIMP to Feign death.
Some MyPaint Brushes: There will be a big of spacing or no flow.   

Because it's in GIMP, so I think it should be sent here？
Comment 1 SenlinOS 2017-06-20 16:05:11 UTC 
Since the libmypaint adds new features, the previous brush needs to be readjusted.
Libmypaint-Git has replied. (Continue to wait and see)
Comment 2 SenlinOS 2017-06-25 12:43:44 UTC 
PPA updated, gimp-edge : otto06217
GIMP 2.9.5, The MyPaint-brushes has returned to normal.

Close post.
Comment 3 Michael Schumacher 2017-06-25 13:30:22 UTC 
We prefer to know what change precisely fixed something. Do you know what did this?
Comment 4 SenlinOS 2017-06-25 14:18:37 UTC 
(In reply to Michael Schumacher from comment #3)
> We prefer to know what change precisely fixed something. Do you know what
> did this?

Libmypaint-Git updated to 2.0
Didn't the GIMP-Team change the libmypaint-API?

If the GIMP team hasn't changed the code yet, 
The author of PPA will know the exact reason.

Of course I don't know the exact change!
I'm just looking at the effect of painting.
Comment 5 Michael Schumacher 2018-01-03 08:21:16 UTC 

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