Ctrl + click to select multiple elements not working on Manjaro/Linux

Fabiano

I think this is a problem related to my new Linux distribution I've just moved to, since it's pretty difficult to work with, but I'm not seeing anybody complaining about it.
I'm running Manjaro with GNOME.

Problem

I'm trying to CTRL + LEFT CLICK on single elements to make multiple selections and instead of adding to selection, it just selects the last element, as if I wasn't pressing CTRL at all. Same issue with SHIFT.
Please notice that anything else involving CTRL works just fine, so I can save though CTRL + S, store a selection, write a capital letter...
Obviously both CTRL and SHIFT work correctly in any other context outside of Spine.

Editor information

My Spine is up to date, version 4.2.18, and I don't know if it can be related, but I'm getting a weird error message about the hotkeys-1.txt file, which is included in the log:

Spine Launcher 4.2.18
Esoteric Software LLC (C) 2013-2024 | http://esotericsoftware.com
Linux amd64 6.9.12-3-MANJARO
AMD, AMD Radeon Graphics (radeonsi, raphael_mendocino, LLVM 18.1.8, DRM 3.57, 6.9.12-3-MANJARO), 4.6 (Compatibility Profile) Mesa 24.1.6-arch1.1
Starting: Spine 4.2.36 Professional
Spine 4.2.36 Professional
Licensed to: <removed>
WARNING: Some hotkeys were not recognized: /home/fabiano/.spine/settings/hotkeys-1.txt
Azione non valida: --- General ---
Started.
OpenAL 1.1, Default audio device
WARNING: Some hotkeys were not recognized: /home/fabiano/.spine/settings/hotkeys-1.txt
Azione non valida: --- General ---

I'm pretty sure it didn't give me the error after a fresh install, so it must have happened after I set my usual custom hotkeys. Anyway, I'm also attaching my hotkeys-1.txt so you can check that there's nothing wrong with it.

hotkeys-1.txt

8kB

Anyway, the CTRL problem occurs also with an unmodified version of the hotkeys-1.txt, tested though deleting my custom version and having Spine recreate it.

Spinebot

It seems like the issue you're experiencing with CTRL + LEFT CLICK and SHIFT not working for multiple selections in Spine on Manjaro/Linux could be related to how the operating system or desktop environment (GNOME) is handling modifier keys. Here are a few steps you can try to troubleshoot and potentially resolve the issue:

Check for Stuck Modifier Keys: Sometimes, modifier keys can get "stuck" in the system's state. Try pressing and releasing CTRL, SHIFT, and ALT keys on both sides of your keyboard to ensure they are not stuck.
Check for Conflicting Software: Ensure that no other software is interfering with the hotkeys. This includes global hotkey managers, clipboard managers, or any software that might be capturing keyboard input.
Review and Reset Hotkeys: Since you mentioned an error with the hotkeys-1.txt file, it might be worth resetting your hotkeys to default and then reapplying your custom hotkeys. You can do this by deleting the hotkeys-1.txt file and restarting Spine. This will generate a new default hotkeys file.
Check Spine Log for Errors: Review the spine.log file for any additional errors or warnings that might provide more insight into the issue. The log file is located at ~/.spine/spine.log.
Test with a Different Desktop Environment: If possible, try running Spine under a different desktop environment (e.g., KDE, XFCE) to see if the issue persists. This can help determine if the problem is specific to GNOME.
Update System and Drivers: Ensure that your system and graphics drivers are up to date. Sometimes, issues with input handling can be resolved with updates.

If none of these steps resolve the issue, it might be a deeper compatibility problem with Manjaro/GNOME and Spine. In that case, you might consider reaching out to the Manjaro or GNOME communities for further assistance.

Fabiano

So I put Manjaro GNOME in a VM, problem didn’t occur there, so I began rebooting and starting Spine after every step of change from the fresh install.
The problem turned out to be a setting in Layout Switcher called “Wayland session”. If that’s activated, the problem in Spine occurs after a reboot, so that needs to be kept turned off.

What that settings does is partially explained when it’s toggled, since it asks for a password, which is launching the program /usr/bin/sed and changing the setting WaylandEnable=false in /etc/gdm/custom.conf. Maybe it does more than that.