|
Bugzilla – Full Text Bug Listing |
| Summary: | on installation (init 3) unicode_start is missing | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Forgotten User QtBI7gWTIh <forgotten_QtBI7gWTIh> |
| Component: | Basesystem | Assignee: | Gabriele Mohr <gs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_QtBI7gWTIh, gs, jeroen.forums.opensuse.org, mrmazda |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | The Yast Logs from init 3 installation | ||
|
Description
Forgotten User QtBI7gWTIh
2014-01-21 16:00:11 UTC
From bug description it sounds like duplicate of bnc #750326 which is solved for 13.1. To see what's different here, please attach the YaST log files (http://en.opensuse.org/openSUSE:Bugreport_YaST). Hello Gabriele, I found your your comment any time ago and it is working in a full installation (KDE) when I switch to console. But on my Test Server installing most minimal with KVM on the server and clients it is not working. Created attachment 578018 [details]
The Yast Logs from init 3 installation
unicode_start fails to run on several Factory systems here, others not. Most of my installations were originally minimal X, not minimal server. I've yet to check if the claimed fix for 13.1 has appeared on systems suffering the problem here. Mailing list thread: http://lists.opensuse.org/opensuse-factory/2014-01/msg00067.html I cannot reproduce the bug with 13.1. GM installation in VirtualBox. I have selected 'Minimal Server (Text mode)' like settings found in attached y2log. On my installation I didn't have problem with broken frames (tried without reboot on tty1 as well as on other ttys). Comment #4 was about 'unicode_start' failing on some systems. But your initial description says that after 'unicode_start' frames are OK, so seems not to apply to your installation. On my systems I can only say yast2 and mc have broken frames, after start "unicode_start" manually the frames are OK in init 3. Maybe these help to understand why this problem? http://lists.freedesktop.org/archives/systemd-devel/2014-April/018583.html http://cgit.freedesktop.org/systemd/systemd/commit/?id=1640944a847249d3f5f0fb0d5a5f820a82efaed0 https://bugzilla.redhat.com/show_bug.cgi?id=663900 I have tested 13.2 Beta1 'Minimal Server (Text mode)' installation. Text mode YaST works like expected, frames are shown correctly. Could you please also retest on your machines? In the moment it is not possible, I have to much work a new Project and SLES. but I have planed to install 13.2 in the next week. I'm not sure I have any systems doing this any longer. I've not seen it in openSUSE in several weeks or more that I can remember. It will be a while before I could check them all. Setting status to resolved, please reopen if the problem reoccurs on your system. I don't think it is fixed, as I think I can reproduce this in Tumbleweed. See https://forums.opensuse.org/showthread.php/507434-local-console-yast-linedrawing-characters-garbage-after-first-reboot |