Red Hat Bugzilla – Bug 434659
On black background, an inverse-video at sign doesn't show
Last modified: 2008-04-08 23:53:08 EDT
Description of problem: I'm addicted to crawl http://sourceforge.net/projects/crawl-ref, a roguelike game. As currently Gnome is broken beyond usage, I'm using XFCE. And in Terminal the at sign representing the character doesn't show. In an xterm or gnome-terminal it works fine. crawl uses a black background, and uses curses. Version-Release number of selected component (if applicable): Terminal-0.2.8-3.fc9.i386 ncurses-libs-5.6-15.20080112.fc9.i386 (crawl uses ncursesw) How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Should I attach the executable, or the source tarball, for the game?
Interesting, as both Terminal and gnome-terminal use the 'vte' package for their backends. You have a black background, what is your cusor color set to? Text color? If you change the preferences->advanced-> $TERM from 'xterm' to 'vt100' does it work?
Setting it to vt100 and resetting the Terminal gives an at-sign. Cursor and text are black, background white. I just tried side by side with gnome-terminal, there it works
Sorry, no. I did X in the game (shows an overview of the dungeon level), there the at sign shows, going back to the "normal" view and the at is gone again. Shows just as a black space (on black).
I'm really not sure how to track this down further... Would you be willing to file an upstream bug? Or if you prefer I can file one for you?
Sorry, I was away (from this bug). Where should I file?
http://bugzilla.xfce.org/ Or if you don't want to deal with another account there I can file it... Just let me know if you would like me to do so.
Reported as http://bugzilla.xfce.org/show_bug.cgi?id=3925. Strangely, today (no changes in Terminal, ncurses-libs!) the game shows as black characters (only, no colors for potions or others!) on white. I hacked together one of the ncurses examples to compile, that one I attached upstream.
Shall we keep this open as a reminder in case upstream has a patch we need to apply? Or go ahead and close it now? I added myself to CC on the upstream bug. If there is anything further I can do, please let me know.
I'm just the bug reporter here, whoever is the owner of the package should make that call. Thanks!
Well, since I am CC'ed on the upstream bug I should be able to see when/if there is activity on it, so I will go ahead and close this UPSTREAM. Feel free to reopen or file a new bug if you spot anything further.