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 719593 - On clang, brush outline is not displayed
On clang, brush outline is not displayed
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: General
2.8.10
Other All
: Normal normal
: 2.8
Assigned To: GIMP Bugs
GIMP Bugs
: 719744 720254 720255 720259 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-11-30 11:05 UTC by Maurizio Loreti
Modified: 2013-12-19 23:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Maurizio Loreti 2013-11-30 11:05:31 UTC
Hello, list - I have a severe problem that shows itself under OS X (10.9 "Mavericks") both with GIMP 2.8.8 and with 2.8.10; 2.8.6 behaves correctly.  The problem happens both on my iMac and on my MacBook Pro.

I have installed on my computers the distribution "GIMP on OS X" by Simone Karin Lehmann; I have alerted about my problem the maintainer of the distribution, because it is probably due to a wrong interaction of GIMP with OS X graphics.


Here is what happens: using the pencil tool (or the brush tool), with 2.8.6 I was used to see the outline of the brush shown on the GIMP canvas; that was extremely useful since I was able to check the current size of the brush on my screen, also while increasing/decreasing that size.  Now, I cannot see the brush outline anymore.  And this happens with the clone/healing tools too; I cannot see where the clone source will be set (with cmd-click), nor where exactly the cloned zone will land on my image (with left-click).

Maybe I am not so clear (english is my third language only); but I have done two screen recordings, in the .mov format, the first one with 2.8.6 and the second one with 2.8.10; they are available for download on Google Drive, and the link is:

https://drive.google.com/folderview?id=0B1oP_87P_BIOLW13X1hOeTV5Znc&usp=sharing

In the first video you may see the brush outline (while I am using the pencil tool and clone tool); in the second one, they are not visible.

Please, help; I know that I could downgrade to 2.8.6, but I would like to see a current GIMP correctly working on my computer.
Comment 1 Michael Natterer 2013-11-30 19:28:18 UTC
When I look at the changes between 2.8.6 and 2.8.10 I see nothing that would
even remotely look like it could break brush outline drawing.

Can you try copying libcairo from the 2.8.6 app to 2.8.10 and check if
that fixes the problem? Keep the overwritten file around please :)

(this is just a wild guess)
Comment 2 su-v 2013-11-30 21:35:12 UTC
Reproduced with local builds on OS X 10.7.5, with various versions of GIMP: 2.8.0 (X11), 2.8.4 (Quartz), 2.8.10 and git master (X11, Quartz). The dependencies are installed via MacPorts.

The missing brush outlines seem to depend on which compiler was used to build GIMP: the brush outlines are rendered as expected after a complete rebuild with llvm-gcc-4.2 instead of clang (tested and confirmed with current git master on OS X 10.7.5).
Comment 3 Téo Mazars 2013-11-30 21:38:32 UTC
Confirming on Linux + GIMP master + clang 3.3. Setting OS to All
Comment 4 Mike Henning (drawoc) 2013-11-30 21:39:27 UTC
Fixed in master and 2.8

commit 95becc7615c7e9cf2f6135c8d5b0fe1cca86648f
Author: Michael Henning <drawoc@darkrefraction.com>
Date:   Sat Nov 30 16:31:57 2013 -0500

    Bug 719593 - On clang, brush outline is not displayed
    
    Don't access path_data->len after path_data has been freed.
Comment 5 Maurizio Loreti 2013-12-01 05:40:07 UTC
(In reply to comment #4)
> Fixed in master and 2.8
> 
> commit 95becc7615c7e9cf2f6135c8d5b0fe1cca86648f
> Author: Michael Henning <drawoc@darkrefraction.com>
> Date:   Sat Nov 30 16:31:57 2013 -0500
> 
>     Bug 719593 - On clang, brush outline is not displayed
> 
>     Don't access path_data->len after path_data has been freed.

Well, a common programming error...  So, I'll wait for a new release that fixes my problem.  Thank you for the quick diagnosis and fix,   M.
Comment 6 Michael Natterer 2013-12-03 22:01:24 UTC
*** Bug 719744 has been marked as a duplicate of this bug. ***
Comment 7 Jehan 2013-12-12 02:55:30 UTC
*** Bug 720255 has been marked as a duplicate of this bug. ***
Comment 8 Jehan 2013-12-12 09:00:00 UTC
*** Bug 720259 has been marked as a duplicate of this bug. ***
Comment 9 Michael Schumacher 2013-12-19 23:06:44 UTC
*** Bug 720254 has been marked as a duplicate of this bug. ***