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 610208 - Overrides gnome theme's text foreground color
Overrides gnome theme's text foreground color
Status: RESOLVED FIXED
Product: meld
Classification: Other
Component: general
1.3.x
Other Linux
: Normal minor
: ---
Assigned To: Stephen Kennedy
Stephen Kennedy
Depends on:
Blocks:
 
 
Reported: 2010-02-16 23:56 UTC by lucasrangit
Modified: 2012-12-07 02:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description lucasrangit 2010-02-16 23:56:37 UTC
I'm using Meld 1.3.0 on Ubuntu 9.10 using Gnome 2.28.1 and a theme with a white text foreground and a black text background. Meld shows text on a black background but with a black foreground rendering the text unreadable. I believe Meld is overriding the text foreground color specified by the Gnome GTK theme.
Comment 1 tombart 2011-01-29 11:34:49 UTC
Same for Meld 1.3.2 on Ubuntu 10.10 and KDE 4.5.1. I have black background and font is light gray but on highlighted red or light blue is the same font invisible.
Comment 2 Pete Beardmore 2011-05-03 18:56:27 UTC
since i started using a dark theme meld is pretty useless to me too :(
Comment 3 David Biesack 2011-11-09 14:59:34 UTC
I have the same problem with my dark theme.

https://bbs.archlinux.org/viewtopic.php?id=98296 shows tips to hack preferences.py to change this, but that is only a hack. It would be
best if meld honored my theme fg/bg and used other color variations for
dark themes.
Comment 4 Kai Willadsen 2012-09-04 21:12:23 UTC
I've just pushed a branch to git that makes all of our colours go through gtkrc. Meld won't work out-of-the-box with dark themes, but it should be possible to tweak whatever you need to to make it work.

If you run across problems getting this to work, please comment.
Comment 5 Kai Willadsen 2012-12-07 02:08:20 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.