Console displays colors incorrectly

Bug #118906 reported by Scott Severance
16
Affects Status Importance Assigned to Milestone
console-tools (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

For command line work, I use differently colored prompts to help distinguish between machines. When I first installed Ubuntu, Dapper was the current version, and the colors worked equally well in gnome-terminal as on the console. When I upgraded to Edgy, my prompts broke. I've now done a clean install of Feisty and experienced the same thing.

My laptop's prompt color is yellow/brown (actually, color codes 1;33m and 33m, respectively). They show up as a dark gray that is very difficult to read against a black background. Furthermore, the console fails to distinguish between bold and regular text, making my two colors identical.

When I boot without the "splash" option, I get a different console font--beginning with Feisty. In this situation, my yellow/brown color scheme displays as brown/brown (due to the lack of distinction between normal and bold colors). But, that's better than dark gray. Still, I have to boot without usplash to get the benefit of readable text. (There must be some bug somewhere that prevents the console from being set up properly when usplash runs.)

This bug occurs on my HP Compaq nx9010 laptop. My Edgy desktop behaves perfectly.

NOTE: This bug was, at one time, erroneously marked as a duplicate of bug 60915. However, it's a distinct issue. Usplash affects how the colors are displayed, but the colors are incorrect regardless of usplash--usplash simply makes the situation worse.

description: updated
Revision history for this message
Colin Watson (cjwatson) wrote :

Does running 'sudo setupcon' from the console fix this problem? See bug 91422.

Changed in usplash:
assignee: nobody → kamion
status: Unconfirmed → Needs Info
Revision history for this message
Scott Severance (scott.severance) wrote :

It adjusts the font (I actually prefer the bolder standard font), but does nothing for the color situation.

Revision history for this message
Colin Watson (cjwatson) wrote :

OK. I don't know offhand how that stuff works and will need to investigate.

Changed in usplash:
status: Needs Info → Confirmed
Revision history for this message
Scott Severance (scott.severance) wrote :

I'm not sure that this is really a duplicate of bug 60915. Maybe it is, but my color issue occurs with or without usplash. In other words, booting without usplash results in better colors, but they still aren't correct as there's no difference between bold and regular colors.

On every other console I've used--as well as terminal programs--bold colors display as lighter colors. For example, bold brown is actually yellow.

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Scott Severance : You are right, your bug report speaks about two different issues. I suggest to let this bug as a duplicate and to create another bug which does not speak about the usplash part but only the console bad colors part. It will be better this way. Thanks for your contribution to ubuntu so far.

Revision history for this message
Scott Severance (scott.severance) wrote :

Saïvann,

I'm not sure that I'm understanding you correctly. Which part are you suggesting that I file separately? The problem is that the colors display incorrectly. usplash affects how they're displayed, but either way, they're wrong.

It seems to me that if I filed a separate bug, it would look pretty much like this one. So I think it would be best for this bug to be unmarked as a duplicate. I'd do it myself, but I can't find a way.

Am I missing something?

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Scott Severance : No problem here, you can go for it. It is true that the title of your bug is explicit and the description too. However, to avoid confusion, if you don't post another clean new bug that speaks only about the color problems (and not about usplash), at least I suggest that you remove any reference to usplash in your description. Also, the package name should be changed to the good one (not usplash) I will ask people from the bug squad if they know which package that bug should have.

To set this bug as being not a duplicate, you just have to click on "Mark as a duplicate" and remove 60915. Thanks for your work on this!

description: updated
Revision history for this message
Scott Severance (scott.severance) wrote :

In e-mail, Saïvann Carignan suggested--but wasn't positive--that this is a console-tools bug. I'm changing the package accordingly.

Revision history for this message
Ilja Sidoroff (ilja-sidoroff) wrote :

I can confirm this issue. I first noticed this when trying to play nethack and some of the colours were incorrect (Yellow was brown, white was light gray etc, perhaps a bit different situation that what was described above). I am using current hardy beta (as of today), amd64 and nvidia.

Revision history for this message
Ilja Sidoroff (ilja-sidoroff) wrote :

And to add to my previous post: (nvidia proprietary driver). I had the same problem with gutsy. I suspected that usplash might had something to do with the issue, but the colour were the same, whether usplash was enabled or not.

Revision history for this message
Ilja Sidoroff (ilja-sidoroff) wrote :

Ok, after a bit of digging (should have done this in the first place), I have Finnish keyboard and I noticed that some special characters (eurosymbol, äöå) don't work as well. I was able to fix that and colours by doing:

sudo dpkg-reconfigure console-setup

https://bugs.launchpad.net/ubuntu/+source/console-tools/+bug/83487 has some more information on topic, this but might be a duplicate of that.

Revision history for this message
Matthew Caron (matt-mattcaron) wrote :

I can confirm this on Hardy, and it is fixed with

sudo dpkg-reconfigure console-setup

as described above.

Changed in console-tools:
importance: Undecided → Low
Revision history for this message
Colin Watson (cjwatson) wrote :

Anything that's fixed by 'sudo dpkg-reconfigure console-setup' or 'sudo setupcon' is bug 130444, not this bug.

Changed in console-tools:
assignee: kamion → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.