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 720259 - Paint along selection/path not working on the official build
Paint along selection/path not working on the official build
Status: RESOLVED DUPLICATE of bug 719593
Product: GIMP
Classification: Other
Component: General
2.8.10
Other Mac OS
: Normal normal
: 2.8
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-12-11 15:23 UTC by jodycollinge
Modified: 2013-12-12 08:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jodycollinge 2013-12-11 15:23:58 UTC
I have had several problems with 2.8.10 for Mac
--Paint along selection not working
--Brush outline not showing
--Other minor issues

These seem to be resolved when I use the native Mac build for 2.8.10
http://gimp.lisanet.de/Website/Download.html
Comment 1 Róman Joost 2013-12-12 02:27:43 UTC
Dear Jody,

may I ask why you are reporting problems, when they seem to be resolved by the native Mac build?

Thanks.
Comment 2 Jehan 2013-12-12 06:54:39 UTC
Indeed. This said, the brush outline is a known bug and fixed, but I don't recall a "paint along selection" bug and can't find it in our git log. And the lisanet.de build is a third party build. Apparently the user here says that our official build would have the bug, but not the lisanet.de one.
I asked by email (dev ml in Cc) this third-party's maintainer if she has any patch about such a bug, or if it is a known one otherwise fixed another way.
Comment 3 su-v 2013-12-12 08:50:36 UTC
See bug #719744.
Comment 4 Jehan 2013-12-12 08:59:59 UTC
Indeed, it seems the same bug. I missed it. :-)
And this was actually fixed with the same fix as the "no brush outline" bug, which is why I was not finding it on a git log.

Moreover it was also reported by you, Jody. So indeed I wonder why you reported this one again. Anyway, that's ok. Mistakes happen. Next time, just try to avoid reporting several times the same bugs. Thanks anyway. :-)
Closed as a duplicate.

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