The installation script broke my layouts

[carbon-starlight]

At first I ran the install script. I was able to add new layouts, but they didn't work—typing on them just defaulted back to QWERTY (or JCUKEN if I choose the Cyrillic layout). I ran the second script and now all my Colemaks are, I believe, -DHs; phonetic Russian doesn't work (defaults to Colemak) and it looks like on some layouts keys are displaced? (I use ANSI keyboard) and CapsLock doesn't work nor for BS, nor for Extend. It looks like elements of previous layouts are left for some reason when I switch.

I believe I had a similar problem when I experimented with xkb on a VM months ago—it was caused by, I believe, a displaced semicolon or wrong layout name in evdev.xml.

Fedora 40, GNOME Wayland

I wanted to try logging in with Xorg, but it is not displayed in the logging screen anymore for some reason (only GNOME and GNOME Classic are left for some reason).

I'm adding my xkb file after modifications were made by the script so you could troubleshoot it in a VM:

xkb.zip

Layouts I tried:

[carbon-starlight]

Update: I replaced xkb folder with a backup the script created, rebooted because old layout names didn't go away and now I no longer can boot up the system: It's just a black screen with an underscore at upper left corner after selecting any option with GRUB.

[carbon-starlight]

I replaced the file again with one from my another operating system installation via tty. See no further issues.

[DreymaR]

Oh dear. Yes, messing around too much with XKB can be surprisingly dangerous it turns out. Glad you solved your issue.

As for the original issue, I'm not sure I get it completely. But you should study how the BigBag implements its components as various xkb settings. Sometimes you can have conflicts with other settings management. And sometimes you'll need a script to set and unset your whole setup, as it's not done solely by the layout component but also by model and options.

[carbon-starlight]

I was trying to replicate this issue in a virtual machine—unsuccessful yet (no bugs happen except that the Extend layer doesn't work), but I found out I still have journalctl logs I saved this day. Maybe you'll find the reason this glitch happened there.

This journal is covering multiple days: the incident happened 12th, the last recorded day.

journal_full.log

[carbon-starlight]

After attempts to create a version of the scripts that would work on my Fedora computer, I'm continuing my investigation. I ran the installation script one more time. Extend doesn't work (CL is BS instead), Rulemak ("Russian (Colemak, phonetic E-Slavic)") acts as QWERTY but with CL>BS, but computer boots. Here are some logs I'm seeing.

I'm investigating the issue. The probable reason is the fact that new files from xkb folder got conflicts with old files (as I observed, the installation script does not delete existing files that are not present in xkb-data_xmod). Can you please send the entire xkb folder as it is on your computer? I'll try to paste it fully replacing my original one and see if it works.