• Support

  • Super key doesn't open Budgie Menu after update

check your keyboard layout
Settings > Region & Language > Input Sources
click eye icon of the selected language to see the keyboard layout and test the Super key then set the value

if it is Left Super key then
gsettings set org.gnome.mutter overlay-key 'Super_L'
if it is Right Super key then
gsettings set org.gnome.mutter overlay-key 'Super_R'

    AlienTux

    Hmm, I got this as well today.....

    I'm using multiple "Input sources" (English (US) and Swedish), and I'm switching between them with the super+space, and that works.
    But to only press the super key (to open the menu) does work for English US, but not for Swedish.

    This worked for both layouts before.

        viyoriya Thank you very much. This seems to have worked perfectly 🙂 I must say tho that when I opened the eye icon and checked the keyboard layout I did press the Super L key, but it didn't get highlighted... The menu did start opening tho.

        henkesteen I use Dvorak and it was working before as well. I did find a hotfix of Budgie Desktop, installed it, but that didn't work. Tried @viyoriya solution and that worked. I also added a standard US keyboard and then removed it.

            Ok... So an interesting development... I have 2 keyboard layouts (Dvorak alt intl and Dvorak intl with dead keys). If I switch layout to my "secondary" layout then the Super_L key stops opening the menu. If I change keyboard layout back to the "primary" keyboard layout then the Super_L key works properly.

            I tried setting either layout as primary and it works with either. Is this a Budgie Desktop problem? Or perhaps a Gnome problem?

              AlienTux

              Exactly the same issue here, my primary (first one in the list) works, the secondary does not.
              And as @AlienTux says, if I switch the order, the primary one always work.

                Having the same issue. Primary, first in the list, layout works, secondary doesn't work.

                So we should probably open a ticket? I guess this would be in the Budgie Git?

                JoshStrobl But it's kinda weird because that bug report is from 2007 and my issue just came up recently. Maybe they're unrelated?