Installed now using boot-nonfree.iso 64 bit When done, i realised i had AZERTY keyboard, and i could not remember i got asked about locale, language or rights agreement as is usual in beginning of installation. Probably that is why installer terminal (Ctrl-Alt-F2) use AZERTY keyboard layout, bug 12082 Reproducible: Steps to Reproduce:
*** Bug 12082 has been marked as a duplicate of this bug. ***
Didn't you make an upgrade ? Please provide the file /root/drakx/report.bug.xz as an attachment
Keywords: (none) => NEEDINFO
This latest is a fresh install in a virtualbox vm using fresh virtual disk KDE lang became british en; kbd azerty
Created attachment 4660 [details] /root/drakx/report.bug.xz
I think i got it! I thought this was a new feature: In stage it directly tries to get stage 2 from 192.168.0.10 /mageia/unstable (which of course fail, and i can then define my local proxy) Looking here: https://wiki.mageia.org/en/Stage_One_install#Custom_automatic_stage1 I see it seem automatic installation is enabled in this version! So you probably just need to rebuild with that option off.
BTW, this reveals a small bug: stage 2 do NOT use azerty as i think is intended, as both terminal (Ctrl-Alt-F2) and the resulting system use AZERTY.
Keywords: NEEDINFO => (none)Priority: Normal => release_blockerAssignee: bugsquad => thierry.vignaud
* running: mutter * lang:en_US charset:C font:DejaVu Sans 12 consolefont:lat0-16 (mutter:383): mutter-WARNING **: Could not load library [/usr/lib64/mutter/plugins/default.so (/usr/lib64/mutter/plugins/default.so: cannot open shared object file: No such file or directory)] Unable to load plugin module [/usr/lib64/mutter/plugins/default.so]: /usr/lib64/mutter/pluugins/default.so: cannot open shared object file: No such file or directory* starting step `selectLanguage' (I confirm btw)
sorry. fixed
Status: NEW => RESOLVEDResolution: (none) => FIXED
*** Bug 12090 has been marked as a duplicate of this bug. ***
CC: (none) => paiiou
Yeah, it is easy to forget, having your head manu places :) Thanks Thierry, I confirm it is fixed. However... another problem with it appeared: bug 12118 ;)
The same problem is reappeared with the last one boot.iso
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
last ? what for md5 ?
(In reply to Manuel Hiebel from comment #13) > last ? February 16th what for md5 ? md5 is correct. It is exactly the former problem which returns
last one is from today (there was a rebuild ~1hour before your comment) and if I ask for md5 it's to compare them ;)
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
And there was no need to reopen both bugs as they are the same and dully tagged as such (duplicate)
(In reply to Thierry Vignaud from comment #16) > And there was no need to reopen both bugs as they are the same and dully > tagged as such (duplicate) Still it was necessary to know that 12090 will be corrected.