Summary: | ncurses on new/clean ppc install has blacked out borders | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jason Beaudoin <JasonBeaudoin> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | trivial | CC: | dickey, josejx, ppc |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic-p-2753674.html#2753674 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jason Beaudoin
2005-09-25 21:10:10 UTC
It looks like extended ASCII characters with use="unicode" break on PPC. Building ncurses with -unicode seems to fix the problem with ncurses-5.4-r6. ncurses-5.4-r5 doesn't seem to exhibit this behaviour. Reproduced here on my PegII with a RadeonFB. did you emerge dialog with USE=unicode ? Dialog's unicode flag was set the same as ncurses. Compiling dialog without the unicode flag, but ncurses with, results in no change. I don't see the $TERM value. Since Linux console doesn't use vt100-compatible line-drawing in UTF-8 mode, ncurses looks at $TERM and the locale settings to decide if it has to work around this. Also (see man ncurses), $NCURSES_NO_UTF8_ACS can be set to do the same thing. TERM is set to linux Hi there, I ran into the same problem on a x86 host. I recompiled all stuff and ncurses apps where still acting weird. I had to set the UNICODE="no" in rc.conf to fix it. HTH, Michael Happens here too on x86 with unicode. After unmasking and merging ncurses-5.5-r2 it seems ok. Another way to fix this is to make a '/etc/env.d/02locale' file as described at http://www.gentoo.org/doc/en/utf-8.xml. This will make ncurses use the plus, dash, and pipe characters to draw window borders, but it's better than the screen being totally corrupt. Trying to use alsamixer without the border characters working is almost impossible. (In reply to comment #8) I have 02locale set to utf8 locales. 5.4-r6 is broken anyways. 5.5-r2 uses the plus, dash, and pipe characters as you say (in framebuffer console). Both versions use single pixel borders in X console (Konsole). ok ... solution: use 5.5-r2 i'll see about getting it stabilized |