Bug 954118

Summary: mc and yast unusable in runlevel 3
Product: [openSUSE] openSUSE Tumbleweed Reporter: Cristian ANITA <cristian_anita>
Component: BasesystemAssignee: systemd maintainers <systemd-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: ancor, chcao, cristian_anita, fvogt
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Cristian ANITA 2015-11-07 23:06:43 UTC 
Text and menus are unreadable in mc and yast in runlevel 3.

Similar to Bug 750326: https://bugzilla.novell.com/show_bug.cgi?id=750326 Bug 556555 https://bugzilla.novell.com/show_bug.cgi?id=556555#c7 has attachment https://bugzilla.novell.com/attachment.cgi?id=328219 that is similar to what happens.

System: openSUSE Tumbleweed KDE 20151030 x86_64 kernel 4.2.4-1-default, systemd-224-1.1

Steps to reproduce:
- boot in runlevel 3 (or CTRL+Alt+F1 in KDE)
- login (regular user or root)
- run mc or yast2
Expected result: text and menus are readable
Actual result: garbled unreadable text/menus (similar to https://bugzilla.novell.com/attachment.cgi?id=328219)
Reproducible: always
Note: launching mc or yast2 from konsole in KDE is OK
Workaround: (current session only): before mc or yast run unicode_start or /usr/lib/systemd/systemd-vconsole-setup
Comment 1 Cristian ANITA 2015-11-09 09:58:23 UTC 
It seems this bug is systemd, not yast2, related but I do not see systemd in the Component list. This is why I choosed Basesystem. Also I do not know who it should be assigned to (systemd maintainer).
Comment 2 Fabian Vogt 2015-11-09 10:08:26 UTC 
Can you confirm that this is a duplicate of bug 927250?
To test, you should be able to fix it using the workaround in bug 927250, comment 24.
Comment 3 Cristian ANITA 2015-11-09 10:23:28 UTC 
I'm at work right now and I do not have Tumbleweed here. I will test tonight.
Comment 4 Ancor Gonzalez Sosa 2015-11-09 12:34:23 UTC 
Looks like everybody agrees this is not a yast2 specific issue. But a systemd problem related to ncurses. Thus, reassigning to systemd maintainers.
Comment 5 Cristian ANITA 2015-11-09 16:57:24 UTC 
- the issue described in bug Bug 927250 is the same.
- tested the workaround in Bug 927250, comment 24 and it works.
- marking as duplicate of Bug 927250

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