Can this not be fixed? Must I refer to this bookmark to fix “it” every time? I’m very sympathetic to other languages and keyboard layouts that I don’t understand, but can the Scroll-Lock key be so important to be erased with every update?
I’m very happy with Manjaro helping me make Windows 10/11 a thing of the past… but, Windows doesn’t make me remap my keyboard after an update (… much worse for Windows, but that’s not the issue 
(have to laugh after that).
Please fix.
First of all, I don’t really know what purpose Scroll Lock really serves that you can also not attain by using Pause or piping your output through less or bat.
Scroll Lock has been repurposed in most distribution a long time ago as a modifier key for locking and unlocking the tty, which is far more useful than pausing a scrolling terminal output. And within Plasma, I use it as the compose key, allowing me to form characters not on my keyboard by combining characters, such as an em-dash (Scroll Lock---) or “ø” (Scroll Lock/o
That said, while there are still graphical user interfaces that run on X11, GNOME has already dropped all X11 support, and Plasma is about to do the same as of Plasma 6.8.
Anything under the /usr hierarchy should never be modified by anyone unless they know what they’re doing.
/usr is a static filesystem and should be regarded as immutable. Furthermore, /usr is where (most of) the package updates go, and thus anything you manually change there to already existing files is subject to being overwritten during a system update.
Neither Manjaro specifically nor GNU/Linux in general are alternatives to Microsoft Windows, and were also never intended to be. GNU/Linux is a UNIX-family operating system, and as such, an alternative to the proprietary UNIX platforms.
Forget your Microsoft’isms. Don’t expect GNU/Linux to behave like Windows. Learn why it behaves differently, and embrace it for what it is, not for what it isn’t.
Can what be fixed?
The /usr tree is not expected to change manually and as such the package manager has full control over that tree.
If you make changes to files in the /usr tree - these changes may be overwritten without warning.
Changes you make in your home (~/) will always persist through updates.
Changes you make in your /etc tree will also persist across updates (a new file call <config>.pacnew may be created if the package containing the file is updated).
Never change files in /usr.
Always copy the file to the relevant folder in /etc or ~/ and change the file there.
In case of keymaps - it is possible to create custom keymap - and store it in /usr then point your system to use the custom keymap.
See Linux console/Keyboard configuration - ArchWiki for more info.
If you’re using wayland, then you can create a layout in either /etc/xkb/symbols or ~/.config/xkb/symbols and it won’t be overridden by an update.
There’s also /usr/share/X11/xkb/symbols but you need to create a new layout instead of modifying an existing one. This will also work for X11 as would modifying /usr/share/X11/xkb/symbols/custom
AFAIK you still can’t select them in the GUI though, except for /usr/share/X11/xkb/symbols/custom as that’s what it’s there for.
Having said that, if this 
is what you’re after, there seems to be an option to do it for you.
I don’t know what DE you’re using, but here’s how to activate it in KDE Plasma.
System Settings → Keyboard → Keyboard → Key Bindings (button on top right) → Compatibility Options → Map Scroll Lock to Mod3
Check the box and click apply.
If you use another DE it’ll be in the keyboard settings, probably under Options or some variation.
Or for any DE, you can use localectl to set both layouts and options.
Hi, that solution worked for X11, unfortunately not for Wayland :(. I also would like have this functionality now.
What part are you talking about?
To be clear I’ve never used scroll lock. I’m just going on the link you posted, my own knowledge and the available options.
Whole post.
So you’re saying that scroll lock no longer works at all under any circumstances?
Your first post implied that it just needed reconfiguring after an update.
Also this has never worked on X11, no one wanted to backport it.
Vague terse answers and descriptions of the problem don’t help anyone, least of all you. 