Description of problem: See screenshots. This bug could be related to or triggered changes introduced by bug 4724, since at least the rescue didn't have this problem before it.
Created attachment 1728 [details] faulty rescue
Created attachment 1729 [details] text installer
CC: (none) => thierry.vignaud
CC: (none) => pterjan
CC: (none) => jquelin
Confirming this bug is present on the Beta 2 pre-release i586 dvd iso.
CC: (none) => davidwhodgins
What's strange is that it now affects stage1 which uses its own copy of slang and only link with external libz.a libldetect.a libkmod.a libpci.a & liblzma.a, so nothing that should affect its output... I wonder what happens ?????
As noted previously, looks like a charset problem â (U+2500) is C4 in PC437/PC850 but does not exist in ISO-8859-1 or ISO-8859-15 where C4 is à It's reproducible with drakboot with TERM=linux when locale is not UTF-8, but not with TERM=screen: TERM | UTF-8 | no-UTF-8 ---------+-------------- linux[1] | OK | BUG screen | OK | OK [1] like in the installer As already stated, since it also affects stage1 (which cames with its own slang+newt), it may some change in the build environment.
how easy is it to set the locales to UTF-8?
Priority: Normal => LowSeverity: normal => minor
CC: (none) => mageia
Source RPM: (none) => drakx-installer-binaries
Created attachment 1804 [details] set TERM to "screen" instead of "linux" I won't try to debug ncurses further and I think I'll just go with that patch. "screen" works better than "linux-vt" that I tested too The only remaining issue is that on exiting rescue-gui, the terminal is set to TERM=linux, I'ven't tried the tree/etc/rc.sysinit modification yet
Keywords: (none) => PATCH
using the old boot.iso didn't work? do i need to use a new iso for this patch to work?
You need to: 1) rebuild drakx-installer-binaries with that patch (actually part of it: anything touching mdkstage1) 2) install it 3) rebuild drakx-installer-images with part of the patch (the images/ bits) 4) rebuild drakx-installer-stage2 with the perl-install/ part 5) rebuild drakx-installer-rescue with the rescue/ part 6) extract boot.iso from d-i-images, mdkinst.sqfs from d-i-stage2, and rescue.sqfd from d-i-rescue, and overwite install/{images,stage2} on your local mirror in order to test
I've commited the patch & uploaded a fixed installer. lines are now ok (but vertical ones with languages with accents). I suspect we got regressions in ncurses between 5.8 & 5.9
Source RPM: drakx-installer-binaries => ncurses
i can confirm it with the new boot.iso, most of it works nicely though
user and password dialog has issues now when typing stuff, definately with backspace
Created attachment 1939 [details] text installer special chars display in custom partitioner in custom partitioner, there is this when making a new partition (chosen language dutch) you see that the likely reason for this is the ë character.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Hi, i have a situatuion here... https://forums.mageia.org/en/viewtopic.php?f=8&t=2621 Do i fill a new bug? or its the same?
CC: (none) => controle.um
yep seems the same
Keywords: NEEDINFO => (none)
assuming i understand the issue, it seems these problems only appear if you're not using utf-8... perhaps we can just make everything utf-8 and not have any problem anymore?
(In reply to comment #17) > assuming i understand the issue, it seems these problems only appear if you're > not using utf-8... perhaps we can just make everything utf-8 and not have any > problem anymore? I can't make everything utf-8.
hmm is there any reason this isn't assigned to tv?
check yourselft the maintainer of the ncurses package
i mean, tv did the last action on this bug. and he said there would be regressions... i assume he means to fix it as a lower priority? or did i read/assume this wrong?
Is this still valid? I think not?
it's been a while, but i haven't tested text installation recently...
Indeed it's fixed
Status: NEW => RESOLVEDResolution: (none) => FIXED