|
Bugzilla – Full Text Bug Listing |
| Summary: | ncuses: Fails with 256 color terminal | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Bernhard Walle <bwalle> |
| Component: | YaST2 | Assignee: | Katarina Machalkova <kmachalkova> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | dickey, kde-maintainers, marko.schugardt, mrueckert |
| Version: | Beta 2 plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
The reason for failure is not given. Normally ncurses will work - but without configuring for extended colors, can show only 16 colors and 256 pairs. Given that, applications that do not attempt to use the extra colors in xterm-256color work fine. Just to clarify, the bug is not present in general in ncurses applications, so mutt and mc work fine, only yast is affected. Wow, I can reproduce with KDE Konsole and xterm (no wonder - the support for 256 colors is afaics not compiled into SUSE xterm). YaST is running, there's even no error message in the log, but the display is just black. Bernhard, I just wonder what you need 256color support for ;-) For safety sake, adding kde-maintainers to Cc: Well, I simply want nice vim themes. :) OK, apparently we have some problems with xterm and linux ncurses color themes. If I use monochromatic theme in 256color xterm instead, YaST displays menus and dialogs correctly. Since trying to adjust current themes might break the display somewhere else (on different type of terminal), it will be probably best if I create new theme specific for 256color enabled terminals. But not for 10.2, I'm afraid ;-) *** Bug 223896 has been marked as a duplicate of this bug. *** Fixed in yast2-ncurses 2.15.0 Yast2-ncurses-2.15.0 never reached openSUSE 10.2!?! Could it be that TERM=rxvt-unicode in generell is a problem for Ncurses? I mean, also in the textmode. Against comment #2 I watched a strange behavior in Vim and Mcedit too. Reopened. I set TERM back to TERM=xterm and the problem is gone. Maybe the problem is also allocated in /etc/DIR_COLORS? I set a "TERM rxvt-unicode" there. > Yast2-ncurses-2.15.0 never reached openSUSE 10.2!?! Right. Yast packages with 2.15.x version are part of openSUSE 10.3. I'm afraid there is nothing I can do for openSUSE 10.2 but request releasing online update. But i) as this issue affects only very few users ii) there is an easy workaround mentioned in comment #10, I doubt it'll be really worth online update. Neverethless, I can try. > Could it be that > TERM=rxvt-unicode in generell is a problem for Ncurses? I mean, also in the > textmode. Against comment #2 I watched a strange behavior in Vim and Mcedit > too. Hm ... no clue (as only yast2-ncurses is mine). Adding darix (mrueckert) to Cc: in generall TERM=rxvt-unicode is not a problem for ncurses (as long the terminfo file exists) i use it regularly and have no problems with vim. mc sometimes chokes on the F1-F12 keys. but i havent investigated further. (In reply to comment #11 from Katarina Machalkova) > Right. Yast packages with 2.15.x version are part of openSUSE 10.3. I'm afraid > there is nothing I can do for openSUSE 10.2 but request releasing online > update. But i) as this issue affects only very few users ii) there is an easy > workaround mentioned in comment #10, I doubt it'll be really worth online > update. Neverethless, I can try. > I accept the workaround as solution. I was a bit afraid at the beginning. (comment #8) (In reply to comment #12 from Marcus Rueckert) > in generall TERM=rxvt-unicode is not a problem for ncurses (as long the > terminfo file exists) i use it regularly and have no problems with vim. mc > sometimes chokes on the F1-F12 keys. but i havent investigated further. > Thanks for the info. |
Both Konsole and gnome-terminal (or Terminal from Xfce, both use the VTE widget) have support for 256 colors. TERM=xterm-256color yast fails. I think an easy fix would be if [ "$TERM" = "xterm-256color" ] ; then TERM="xterm" fi in the yast2 start script.