Hello,

has this image been exported with GIMP? Or is it a screenshot?
And could you upload the XCF file of this test (or another showing similar issue).

Created attachment 254899 [details]
XCF file showing same issue

First image was exported with GIMP.

Well I see the green outlines at startup (because the preview is kind of embedded, it does not re-render it if I don't touch it, so I see what you saw last) but as soon as I touch the text (add a space, or whatever), the green disappears.

Didn't you do anything particular? Some filter or whatnot?

Can you reproduce it every time? In particular does the following simple procedure reproduce the bug for you every time:
1/ create a new file with black background;
2/ select the text tool and set it to white color;
3/ write some text. => the text has green outlines.

Thanks.

Hi,

I can reproduce it everytime with above staps.
I reproduced it with all the following fonts I tried: Ubuntu, Sans, Droid Sans.
I reproduced with 72px/in and 300px/in image. 
I doubt that I have any filter enabled because I reproduced this behavior it with completely new Image, also I checked that:
1) mode for text layer is normal and 
2) Repeat-last is disabled(grayed out) in filter menu.

btw, I am on Ubuntu 13.04 and I have a 1366x768 screen if that matter.

Thanks.

Well I am kind of stuck because I definitely can't reproduce, which also means I cannot try and trace the issue. And since I have no single idea what could be the problem, hard-guessing and pointing a piece of code is also hard.

I would like to propose you 2 additional tests:

1/ Try with a fresh configuration. For this, move the folder $HOME/.gimp-2.8/ (for instance to $HOME/.gimp-2.8.save, so that you can move it back later if ever you have any configuration you don't want to lose. You can also just delete the folder if you don't care about losing any customization you may have made).
Then check if this happens again directly after the first run.

2/ Could you try with the latest version of GIMP, 2.8.6. I see that Ubuntu only packaged 2.8.4. But if you have any previous experience of compiling software, it should not be hard to compile GIMP 2.8.6 from source (typical configure, make, make install).
You can get the source there: http://www.gimp.org/downloads/

After installing 2.8.6, get a fresh config directory again (same as above), and check if you have the problem.
Thanks!

Hi,
For the first part I reproduced it with fresh configuration. I also checked it in a guest account(ubuntu create a new home directory for guest session).

For testing 2.8.6, is there is any official PPA for that so I can just add PPA and update using apt-get. It will also help getting future updates.
If PPA is not available then can you tell me how much time it will take to compile GIMP from source because I don't have very powerful machine(i3 2.1GHz with 3GB RAM). Also when I install from source I just want to install in home directory(all binary in $HOME without polluting /usr/local or anything), so I can delete it afterword without leaving traces. Can you provide instruction for same?

Hi guys!
I think I pinned down this issue. I also installed infinality patches. I find this thread with exect same issue http://www.infinality.net/forum/viewtopic.php?f=2&t=229 . Can we do something about it?

Thanks.

Hi,

well we use indeed pango/freetype for font rendering. If this guy makes patches on freetype (to render "nicer" fonts, if I understood the description), and as a consequence broke freetype, there is not much we can do about it on GIMP. The problem is with these patches and we have no reach there.

I would suggest to either uninstall this infinality-patched freetype, make a bug report to this person, or to use the workaround that someone proposed in the last message on the forum thread you linked (but yeah if the patch makes these green stripes, it kind of failed its advertised purpose of "provid[ing] the nicest font rendering of any operating system.", so the best would be for the maintainer to fix it).

I don't get it though, if really this person thinks he improved font rendering, why doesn't he propose his patches upstream? That would make it easier to review and fix and would profit anyone. :-)

Anyway I think we got the source of the issue, so I am closing as RESOLVED > NOTGNOME and I suggest you revive the linked thread or any bug report to infinality for it to be fixed there.

P.S.: to answer comment 7, even though probably not needed anymore:

- there is no official PPA from the GIMP team, as far as I know, but I can see some (and one in particular) which seems to be set to always propose the last version of GIMP. I won't name it though (but it is easy to find with "ubuntu ppa gimp" on any web search engine, and you can add a "site:launchpad.net" or similar search tag) because as it is not official, I cannot personally vouch for it because I don't actually know if it is safe (and there has been known harmful fake GIMP builds, at least on Windows). Up to you to get a feeling there.

- as a general GNU rule, for any package created by the autotools, you can use the --prefix configure option to set a custom prefix. For instance, this is a common path I use to install software on my home (and this way, not even needing to be root to `make install`):
$ ./configure --prefix=/home/jehan/.local

Of course, you will want to update your PATH and LD_LIBRARY_PATH (in .bashrc or equivalent for other shells):
$ export PATH=/home/jehan/.local/bin:$PATH
$ export LD_LIBRARY_PATH=/home/jehan/.local/lib::$LD_LIBRARY_PATH

Enjoy!

Is this the known "system sub-pixel smoothing affects text in other application" problem?

No idea. I don't know this other problem. :-)

See bug #657047

Well, I can see some similarities in the symptoms, but that still feels a little different (they are all about glitches in text rendering, but screenshot are not exactly the same). Moreover the bug in the other ticket speaks about cairo and fontconfig, here this is freetype (though obviously there is a strong link).

On the other hand, if you look the screenshot in this ticket, and the one in the forum thread that A. K. Sharma linked, this is not just "similarities", that's really identical symptoms. And the maintainer of this third-party patch could reproduce the problem easily (cf. the forum thread).

I'd say these are different issues. But I may be wrong. I did not investigate deeper than this because I think I already spent too much time on this. :p

Hi,

So here is final thing I did. This bug was caused by a package "fontconfig-infinality". Possible solution are:
1) remove above package, that is what I did.
2) uncheck 'antialiasing' checkbox in GIMP, but text may look ugly.

There is other solution suggested in thread linked in comment 8 but I haven't tried it.

Thanks.

*** Bug 792669 has been marked as a duplicate of this bug. ***