Remapping Super L Key to launch Qubes Launcher

Hi there.

I’m trying to remap the “Super L” key (the Windows key) to trigger the Qubes Launcher command when pressing. (Kinda similar to how it would work in Windows.)

I went to Keyboard → Application Shortcuts → Add → Input Details → Save

Details:
Shortcut: Super L
Command: gdbus call --session --dest org.qubesos.appmenu --object-path "/org/qubesos/appmenu" --method org.freedesktop.Application.Activate "{}"

The problem is it works, but the Qubes Launcher opens up whenever my mouse is hovering, instead of remaining in the (left) corner of the screen where it rests naturally.

So how do I remap this key without this issue?

Maybe you can create a script that will get current mouse pointer position using xdotool, set mouse pointer to top left position where your menu is normally, open the menu using gdbus, restore current mouse pointer position.

2 Likes

I think there is a good snippet here:

3 Likes

I found the same thing, was surprised but decided I preferred it that way (to either my system moving the mouse pointer or having to move it myself to the top left for no real reason).

But: bash -c 'xdotool mousemove 0 0 && gdbus call --session --dest org.qubesos.appmenu --object-path "/org/qubesos/appmenu" --method org.freedesktop.Application.Activate "{}"' works for me.

3 Likes

On Qubes 4.3.0RC4 neither the “default” combination of “Meta key+F1” or trying to make a command works for me. Thoughts?

To be clear on my objective, I am trying to preferably have a right or center button click on mouse or trackpad open a launcher or menu at the mouse pointer if on the desktop with a menu ala XCFE, NeXT-like. PErfer not needing a key at all.

Until Wayland happens (and there is probably already an equivalent program), you can try using sxhkd. It’s a program you install in dom0 that maps keys to programs. May be a cleaner solution if you like mapping a lot of hotkeys.

WARNING (Don't install programs in dom0)

If you install this, it needs to be in the GUIVM, which is currently dom0 (and these wanrings should probably propagate to GUIVM when it comes out). Don’t install things in dom0 without consulting your threat model and understanding how it would affect your system. Installing malware in dom0 would be FATAL.

Thank you for your reply. Seen a few comments about a possible Wayland conflict, seems keymapping for such a basic function wouldn’t be such a conflict (not commenting on dev work). Was expecting odd behavior like poor menu display or missing items. But I get zero action. Well aware off the security concern. not a big keymapper. Reason I like the menu is it saves a lot of pointer movement from having to go to upper left corner. Seemed this Topic was new enough it was a expected to work item.

Funny how it handles assigning actions too open individual qubevm windows to virtual desktops well which seems wold be much more difficult.

The display manager is a lot bigger than most people think, it’s basically all the underlying stuff that turns it from a TTY (console) to a Desktop Experience™, which includes handling keypresses. Why? Well, for example, it has to direct keypresses to the correct window. This is a display manager problem because it’s a difference between a console and desktop. Therefore, it handles all* keypresses. (There are exceptions, but not relevant to this.) It seems complicated, and it makes a lot more sense when you understand where it comes from.

Switch to KDE, and you get straightforward shortcut creation, a fully
customisable menu, and features that work better with Qubes.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

I am glad you chimed in, I was pretty sure you know the most about KDE on Qubes but didn’t want to bother you with it. I was not clear, I am running KDE and like you say it gives a extensive ability too customize. KDE is much better than XCFE if the HW can run it. This is the only key binding I have found not working. I have tried both right clicking on the quick-launch widget and setting the keyboard as well as in the full keyboard settings in system settings. Neither triggers any sort of action. I also tried applying the command above in the keyboard shortcuts. Same issue. I know the key works, so like Win+Tab cycles through applcation windows. Just wanting to see others experience before trying to search logs and/or any suggestion where too look to troubleshoot.

I also tried adding an Application Launcher and the Win key works fine. It doesn’t have same sorting but can be configured to be close too the Qubes Quick Launch tool. I dregged it from the Widgets selection window to the desktop. Now if I could get it too "float with the pointer it would be close. As it is now it is fixed on the desktop.

Finally after several days of searches, conflicting info (never breads trust), I came across a forum describing and answering my biggest need almost perfectly. Bring back the magic: cascading menu quick-access ANCESTOR - #4 by anon97535808 - Brainstorm - KDE Discuss
" → right-click on the desktop → Configure Desktop and WallpaperMouse Actions → select Application Launcher from the drop-down menu for a mouse button of your choice"
This opens a system setting for KDE I couldnt find. It allows the function I am looking for now I need to do a bit of menu editing to get it perfect but at least it floats saving full screen movements. Weird thing is I now cant find that system setting.
Same settings panel nowhere to be found. specfically the Mouse Action settings in KDE.
Finally found this:

2. **Edit Configuration File** : If mouse actions were misconfigured, manually edit `~/.config/plasma-org.kde.plasma.desktop-appletsrc` . Ensure the `[ActionPlugins]` section includes:

RightButton;NoModifier=org.kde.contextmenu

Then restart Plasma with:

kquitapp6 plasmashell && plasmashell

Best part is finding the Mouse Actions panel to configure other button settings.