Touchscreen issues
Hi!
Your script has worked for me perfectly in the past; on KDE, if I remember right.
I installed your script earlier today on GNOME and after a reboot noticed my touchscreen did not work other than gestures. Using your install script's -r fixed the issues after a reboot. GNOME also kept enabling some sort of autocomplete feature for text at random, and I'm not even sure how you enable/disable it on normal terms - couldn't find anything in accessibility settings or anyone talking about it.
I'm on a Thinkpad T14 Gen 1 AMD, running GNOME 46.5 on Fedora 40.
Please let me know if you need any other details or need me to re-attempt! I imagine this is hard to debug (especially without a touchscreen device), but thought I would share these issues nonetheless just in case.
Thank you for all your work on this in the first place :)
Hiya!
I'm on a ThinkPad too, but I haven't used the XKB files for a while, and I haven't used later iterations of GNOME nor Wayland.
Therefore, I'm not entirely sure what's going on here but it does look like similar problems in the past. The issue would be that some fancy shortcuts are triggered. But what? I know we've had some issues with three-finger gestures in the past.
Just to be clear: Do you actually have a touchscreen, or did you mean the Thinkpad's touchpad?
Try enabling the BigBag without Extend as a first debugging step? That is, unset the options then add back only what you need there without the "misc:extend,lv5:caps_switch_lock" part. On second thought, leave out the "compose:menu" part too.
If that is the issue, you could try commenting out the fkey include in the symbols/extend file to see if that helps.
Hi! Yes, I'm talking about the touchscreen, not the touchpad. I'll try your suggestion out a little later!
I ran the install script with no arguments then setxkbmap -v 9 -option "" .. Nothing was broken before a reboot, except that my keyboard stopped working for a very scary 30 seconds or so, however strangely I can still enable Extend through GNOME Tweaks! Which seems to work almost perfectly, ignoring the other issues. After a reboot, it is the same issue.
Somewhat unrelated, but before I did this I tried to play a game and noticed that, even on a qwerty layout enabled with bigbag supposedly reverted, the game (well, games - Satisfactory and King of the Hat) seemed to think I was on colemak in terms of controls. Is this intended/expected?
As before, touchscreen works again after reverting and rebooting!
Hi! I ran it again for a few days, this time without keyboard issues for days until I ran setxkbmap -v 9 -option "". I had extend working, but didn't make any modifications to my keyboard other than that.
Touchscreen gestures stopped working as they should on gnome, but the feeling I got was that gnome was reverting to some kind of Xorg setup, rather than interacting with gestures themselves.
Commenting in case it helps anyone, although I know this is an incredibly niche subject - again, thank you for all you do!
When you run that command, X11 removes all previously set xkb options. What effect that has, depends on what options were set beforehand. Looks like you removed some options you needed? Which ones?
When I ran it this time I did not use setxkbmap at all before that time. I still had extend working without it. The only thing I did when I had it working (with minor touchscreen issues) was run the install script once without any arguments.
Options can be set in various ways. So in your case, you should check your settings before running a setxkbmap -option "" command to see what you've got active.
Extend requires some options to be set, which tells us you had something active. The install script can call the setkb script, so maybe that's what. Or your GUI set those options, maybe.
Before scratching options, look at the output of a simple setxkbmap -v 9 listing. Which options were active then?
Remind me: Why did you want to remove all options with the -option "" switch?
I ran setxkbmap -v 9 before running the install script, after running it, after setting the layout through GNOME settings, and after enabling extend through GUI options, and all gave the following:
Setting verbose level to 9
WARNING: Running setxkbmap against an Xwayland server
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: pc105
layout: us
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+inet(evdev)
geometry: pc(pc105)
I ran it with no options as your first reply said I should delete part of the options, and I didn't need anything other than what you listed I should remove:
That is, unset the options then add back only what you need there without the "misc:extend,lv5:caps_switch_lock" part. On second thought, leave out the "compose:menu" part too.
If it helps, the part of the GUI that I use to enable extend has a bunch of options such as setting the meta key to be something else, solaris compatibility, putting the euro key on something, etc. The extend option is under the "options for compatibility", and is titled "Enable level5 Extend mappings (home positions arrows etc)". Specifically, I use GNOME Tweaks, not GNOME settings, for this.
Thank you again, and sorry for how long I took to respond!