Bug 1056698 - YaST2 sw_single text interface is broken in terminal emulator
Summary: YaST2 sw_single text interface is broken in terminal emulator
Status: RESOLVED DUPLICATE of bug 1054448
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-31 18:31 UTC by Tristan Miller
Modified: 2017-09-01 08:59 UTC (History)
1 user (show)

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


Attachments
Screenshot showing yast2 sw_single run in konsole (37.62 KB, image/png)
2017-08-31 18:31 UTC, Tristan Miller
Details
Screenshot of htop showing similar display corruption (109.17 KB, image/png)
2017-08-31 19:30 UTC, Tristan Miller
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Miller 2017-08-31 18:31:44 UTC
Created attachment 739063 [details]
Screenshot showing yast2 sw_single run in konsole

Following a recent update to openSUSE Tumbleweed, YaST2 sw_single no longer runs correctly in an xterm.  The interface is completely garbled an unusable (see screenshot).  This happens when running every X11 terminal emulator I've tried (gnome-terminal, konsole, xterm).  However, the interface still looks good when run from a text console.

This issue will be a particular problem for those hit by Bug 1054150, which makes it impossible to start the GUI version of sw_single.
Comment 1 Tristan Miller 2017-08-31 19:30:01 UTC
Created attachment 739067 [details]
Screenshot of htop showing similar display corruption

htop has a similar problem (see attached screenshot).  Perhaps the problem is in ncurses?
Comment 2 Forgotten User FKVxtKwswt 2017-09-01 01:08:00 UTC
This problem happens on my system too.
I switched many mono fonts, but didn't help.
CTRL + L works only for htop.
Comment 3 Tristan Miller 2017-09-01 08:59:14 UTC
Seems to be the same problem described in Bug 1054448.

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