Bug 540514 - Gnome-terminal gets "completely white" after running yast (ncurses) in LiveCD
Summary: Gnome-terminal gets "completely white" after running yast (ncurses) in LiveCD
Status: RESOLVED DUPLICATE of bug 539363
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Milestone 7
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-19 17:52 UTC by Camaleon --
Modified: 2009-09-21 18:57 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
YaST ncurses launched from gnome-terminal (45.90 KB, image/png)
2009-09-19 21:59 UTC, Camaleon --
Details
YaST ncurses launched from xterm (42.16 KB, image/png)
2009-09-19 22:04 UTC, Camaleon --
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Camaleon -- 2009-09-19 17:52:02 UTC
After running "yast" command from gnome-terminal I'm getting the following behaviors:

1. ncurses interface gets "corrupted" (blue background gets white zones which are unreadable).

2. Gnome-terminal (all tabs that were opened when launched "yast" command) gets white background (that is, I cannot read "any" text, all is white, both texts and background).

This is not happening when using "xterm".

Tested with LiveCD, 64 bits (gnome)
Comment 1 Camaleon -- 2009-09-19 21:59:55 UTC
Created attachment 318958 [details]
YaST ncurses launched from gnome-terminal
Comment 2 Camaleon -- 2009-09-19 22:04:33 UTC
Created attachment 318959 [details]
YaST ncurses launched from xterm
Comment 3 Camaleon -- 2009-09-20 18:41:30 UTC
Additional info: this behavior also happens after launching "mc" (Midnight Commander) under Gnome terminal.
Comment 4 Forgotten User h13THG8RK1 2009-09-21 18:57:04 UTC
Many oddnesses on gnome-terminal: bug 539363 (ncurses: bug 539525)

*** This bug has been marked as a duplicate of bug 539363 ***