I just installed eix-0.27.5, and it's completely unreadable on a shell with a black background. Really. Previous version was a bit flashy, but at least it was convenient to read its output. Now, it's impossible to see anything : dark grey on black, that's not a good idea.
It may be good to, maybe, create color profiles or something like that…
Steps to Reproduce:
1. install eix-0.27.5
2. run eix, like eix -I eix
3. cry when you have a black shell
unreadable output, colors aren't visible
should be readable on a black shell
One more information:
seems something may be broken in the shell detection or something like that - creating a ~/.eixrc having DARK="true" seems to work nicely now.
I'm using rxvt-unicode, recognized as "rxvt" according to `echo $TERM`.
This is needed on some old systems for screen - they do not know about rxvt-unicode nore screen.rxvt.
Hope this info may help others.
Please search for existing bugs first
*** This bug has been marked as a duplicate of bug 438076 ***
I searched for bugs matching my version, as I didn't have problem before :(. Sorry.
I guess it is not a duplicate.
1. Everything worked fine upto app-portage/eix-0.27.4 inclusive
2. For me happens under konsole. I have none of the rxvt versions installed.
3. It behaves differently under different accounts (root is affected, regular user is NOT). I have no individual eix configs, /etc/eixrc is world readable.
Please follow along bug 438076 and try its upcoming solution before reporting any new similar bugs or deeming bugs are not a duplicate of it; notice how that bug is not yet marked resolved which means that it is still in progress, and that the solution to that bug could therefore be a potential fix to related color bugs.
1. Forced black backgrounds were noticed in my app-portage/eix-0.27.4.
2. I also have color problems on app-portage/eix-0.27.5 under Guake.
3. Accounts should not matter, if they do you can strace to see which config files it is accessing and correct it manually; if it does act UID dependent then that should be reported on the other bug, because that would point out a more severe bug in the color code (which should just access ~/... or /etc/...).
The upstream bug is noticed of at least two duplicates, they are aware latter versions still have color bugs; I'll update its title.
Please continue to read from bug 438076 comment 24