also apparent in Cinnamon DE install same .iso

Thanks for the report.
Can you say what display manager(s) we are talking about? One imagines LXDM for the LXDE-only install; but for Cinnamon?

And whether despite the displayed error, it continues OK - you can log in?

CC: (none) => lewyssmith

Cinnamon uses lightDM.

yes, login is ok and desktop is fine.

it is just *untidy*

Thanks.
More questions! Should have asked them before.
Do you know:
- whether it applies just to single-desktop installs? (I have never seen this with my multi-desktop M8-to-Cauldron system.
- whether you see it with Gnome GDM or Plasma SDDM? PAD reporters should have noted it.

just finished a 4n1 install - Xcfe, Cinn, Mate & LXDE

issue noted there.

I have yet to try a Gnome or Plasma install.

Wise desktops choice!
Thanks for extra info, so it looks generic. Why only you complaining?
What about those people testing the single-desktop Live ISOs?

CC'ing Jani who might have an idea.

CC: (none) => jani.valimaa

(In reply to Lewis Smith from comment #6)
> Wise desktops choice!

:)

> What about those people testing the single-desktop Live ISOs?
> 

no Lives yet, just the CIs

also affects Live Plasma

So it looks to be a unversal problem, not related to one display manager.
No choice but to launch this globally.

CC: lewyssmith => (none)
Assignee: bugsquad => pkg-bugs
Summary: "cannot open include file qwerty-layout.uni syntax error, unexpected ERROR" => Before display manager login screen: "cannot open include file qwerty-layout.uni syntax error, unexpected ERROR"

Hi,

I have the same error (but with "azerty-layaout.uni") and I found that the error message comes very early in the boot process so I suspect this is a problem in initramfs images or with systemd.

Best regards,

Nico.

CC: (none) => nicolas.salguero

s/azerty-layaout.uni/azerty-layout.uni

(In reply to Nicolas Salguero from comment #10)
> Hi,
> 
> I have the same error (but with "azerty-layaout.uni") and I found that the
> error message comes very early in the boot process so I suspect this is a
> problem in initramfs images or with systemd.
> 
> Best regards,
> 
> Nico.

I Agree. It's is shown very early. I saw it in every installation. Mageia 9 alpha or upgrade from Mageia 8. VM or not. No impact after login.

here it is "de-latin1.uni.map"

Ulrich

CC: (none) => bequimao.de

Should be fixed by dracut-057-3.mga9. You will need to rebuild your initrd after installing the update (as root, run 'dracut -f').

Source RPM: (none) => dracut-057-2
CC: (none) => mageia

Hi, I've been struggling with boot failures for about 40 hours already; my immediate and hopefully last issue is failing on qwerty-layout.uni...  the system eventually drops to a dracut prompt which I'm not familiar with.  dracut has very limited capabilities, so no idea what to do with it.

System will not finish booting, except into SystemRescue or single user text mode (via SystemRescue)...  I'm available to do what it takes to help resolve this issue.
Thanks,  Pierre

CC: (none) => pfortin

(In reply to Pierre Fortin from comment #14)
> Hi, I've been struggling with boot failures for about 40 hours already; my
> immediate and hopefully last issue is failing on qwerty-layout.uni...

This is not a fatal error. It only causes loadkeys to fail, and only affects keyboard entry in the dracut shell. You will need to fix your system, apply the update, and regenerate your initrd to eliminate the error, but it is not the cause of your boot failure.

Did you try the suggestions I posted on the discuss ML? Please answer there, not in this bug report.

(In reply to Martin Whitaker from comment #13)
> Should be fixed by dracut-057-3.mga9. You will need to rebuild your initrd
> after installing the update (as root, run 'dracut -f').

I can confirm dracut-057-3.mga9 solved that issue.

Thanks for confirming Nicolas. Closing as fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED