Ctrl + click for multiple selection doesn't work in Spine

[Fabiano]

Hi glorious FOSS people,

Spine is a 2D Animation software for games and I use it for work. https://en.esotericsoftware.com/

I’ve just recently switched to Manjaro GNOME and I’m trying to do multiple selections in Spine through CTRL + LEFT CLICK or SHIFT + LEFT CLICK, but I can’t make it work.

Please notice that anything else involving CTRL inside Spine works just fine, so I can save though CTRL + S, store a selection, write a capital letter…
Obviously both CTRL and SHIFT always work correctly in any other context outside of Spine.

It used to work perfectly in KDE Neon, so I’m willing to test it in Manjaro KDE as well, even though I had to switch to GNOME for other reasons.

In the meantime, does anybody have any clue about this behaviour?
Any effective way to debug it?
I’ve tried to disable the Clipboard Indicator extension, as long as deactivating ALL extensions directly and tried a reboot with them deactivated; I’ve also deactivated all GNOME hotkeys involving CTRL I could find… no luck.

I’ve also asked on their forum, for future reference: Ctrl + click to select multiple elements not working on Manjaro/Linux - Spine Forum

Cheers

---

EDIT: I tested it in Manjaro KDE in a virtual machine and the problem doesn’t occur.

[BG405]

@Fabiano

I tested it in Manjaro KDE in a virtual machine and the problem doesn’t occur.

If you haven’t already, it’s worth trying that with Manjaro GNOME in a VM as well, just to see if it is something in your current configurations. Or a fresh user profile in your installed system.

[Fabiano]

Right, that’s what I’ve been spending these last 3 hours doing (I’m a beginner at VMs).

Put Manjaro GNOME in a VM, problem didn’t occur there either, 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.

At this point I’d have a huge list of questions to understand how exactly this problem is happening (deactivating this means the elements controlled by Layout Switcher are not running under Wayland? Isn’t that a setting picked at login screen? How can it influence the CTRL and SHIFT key so weirdly?)
but I guess the scope of this discussion is over.
Thanks a lot for the idea.