Am 2015-07-22 00:33, schrieb Felix Miata:
Thomas Wagner composed on 2015-07-21 15:48 (UTC+0200):
On current Tumbleweed 20150712 I switched with CTRL+ALT+F1 to the first virtual console, logged in as root and started yast. The interface decorations, i.e. the borgedr are all wrong (wrong ASCII sign). When yast is started the second virtual console (CTRL+ALT+F2) the interface of yast is correctly displayed.
I suspect this is the same as a longstanding but sporadic cross-distro problem I see launching mc.
http://fm.no-ip.com/SS/Suse/badtty132y.png Yeah, I see a similar pattern, although with other characters.
If so, a workaround is preceding launch with unicode_start. I think Andrei's thread response alludes to the same thing. Because I never got close to creating any reliable reproduction case, I never filed any suse bug, but here is discussion of problem:
http://lists.opensuse.org/opensuse-factory/2014-01/msg00067.html https://bugzilla.opensuse.org/show_bug.cgi?id=750326 https://bugzilla.opensuse.org/show_bug.cgi?id=859710
Other distros: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1437589 https://bugzilla.redhat.com/show_bug.cgi?id=889710
Thanks for the links. In https://bugzilla.opensuse.org/show_bug.cgi?id=750326 I found that /usr/bin/systemctl restart systemd-vconsole-setup.service did solve the problem for openSUSE 12.3. Running this command prior starting yast does also fix the problem on Tumbleweed. Now I wonder wheter there are any sideeffects of restarting systemd-vconsole-setup. If there are no sideeffects: Can we incorporte systemd-vconsole-setup at startup or at the first time yast starts? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org