Keyboard shortcuts not operational on 18.04

[Dustin Krysak]

After installing 18.04, I noticed that certain keyboard shortcuts no longer function.

It appears to be related to the shortcuts that gnome-settings-daemon control as my shortcuts that are provided by my desktop (Budgie) still function.

Some examples are:

* Media keys for volume up/down/mute
* ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same behaviour.

I double checked, and it looks like the needed daemon is still running,

```
dustin 3337 0.0 0.2 500736 22216 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard
dustin 3338 0.0 0.3 943372 25732 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-media-keys
dustin 3343 0.0 0.0 274908 5844 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-mouse
dustin 3345 0.0 0.3 519896 25144 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-power
dustin 3348 0.0 0.1 346004 10212 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications
dustin 3351 0.0 0.0 374684 7952 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-smartcard
dustin 3355 0.0 0.1 329584 8064 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sound
dustin 3361 0.0 0.1 449708 9856 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sharing
dustin 3367 0.0 0.0 272416 4772 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
dustin 3375 0.0 0.0 420028 5804 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-rfkill
dustin 3383 0.0 0.2 507120 23244 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-wacom
dustin 3385 0.0 0.3 498040 25040 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-xsettings
dustin 3387 0.0 0.0 274900 5936 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
dustin 3392 0.0 0.2 496016 22044 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-clipboard
dustin 3395 0.0 0.3 810156 25976 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-color
dustin 3396 0.0 0.2 471656 21080 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-datetime
dustin 3400 0.0 0.0 361196 7116 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping
dustin 3433 0.0 0.1 505404 12576 ? Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-printer
dustin 9776 0.0 0.0 18188 1032 pts/1 S+ 21:19 0:00 grep --color=auto gnome-settings-daemon
```

Reboot does not seem to help. However, occasionally the shortcuts do seem to work - but only very occasionally.

Any other info needed?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Tue Mar 27 21:12:18 2018
InstallationDate: Installed on 2018-03-05 (22 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for your bug report, does it work under an Ubuntu session?

[Jean-Francois Bourdeau (jfbourdeau)]

I also experience the same thing from time to time... Sames key stop functioning on my Logitech K800 keyboard but it is " intermittent"... IF the problems comes back, I will let you know and troubleshoot " Report any info you want

[Dustin Krysak (bashfulrobot)]

Another test I just completed. In a situation where my shortcuts were working… I put caffeine on to prevent sleep or hibernation… and my shortcuts are still working. Granted I was not doing a lot on the machine over this time… Used it for a bit and then went to bed. But 8 hrs later. still good. I’m going to work shortly and I might try to leave my laptop running for my commute and then use the machine through the day with caffeine on. See how it goes.

@seb128
What do you mean an "Ubuntu" session... under a gnome desktop session? This was installed via the Ubuntu Budgie ISO. I have no alternate session on this machine.

[Dustin Krysak (bashfulrobot)]

15 hrs later - keyboard still functioning as expected with caffeine on. Probably going to stop soon and see if I can get it to break.

[Dustin Krysak (bashfulrobot)]

Additional Info:

I just found out another detail quite by accident.

My system is set up to use the “fn” key to make the F buttons behave as an f button (F1-12). Meaning by default a press will trigger the volume up/down, etc.

So when the audio keys conk out… my other f key functions (brightness, etc) still work. BUT, if I hold “alt”, and press my audio keys - they work!

Now knowing this pattern, - I went through my F keys… and tested what worked (brightness, audio, mute, search)

    F1 (mute) - “F1” works with the “fn” key, and the mute only works when also pressing “alt”
    F2 (vol down) - “F2” works with the “fn” key, and the vol down only works when also pressing “alt”
    F3 (vol up) - “F3” works with the “fn” key, and the vol up only works when also pressing “alt”
    F4 (disable mic) - Works as expected.
    F5 (bright down) - Works as expected.
    F6 (bright up) - Works as expected.
    F7 (projector) - Untested.
    F8 (airplane mode) - Works as expected.
    F9 (tools) - Does not work in any capacity
    F10 (Search) - “F10” works with the “fn” key, and the search only works when also pressing “alt”
    F11 (launchA) - Works as expected.
    F12 (open file browser) - Works as expected.

Also filed an upstream bug. https://bugzilla.gnome.org/show_bug.cgi?id=794385

[Dustin Krysak (bashfulrobot)]

I had forgotten to update my comment (wrote on 2018-03-28: ) - About a day later the behaviour returned and the caffeine test was not effective.

[WinEunuchs2Unix (ricklee518)]

Like #3 I also have the Logitech K800 wireless keyboard.

- Ctrl+Alt+T doesn't open terminal must use Dash and select gnome-terminal
- Alt+PrintScreen doesn't open screen-shot must use Dash and select Screenshot
- Media keys don't work

Resorting to laptop's keyboard (Alienware 17 R3) Ctrl+Alt+T doesn't work either.

Ubuntu 16.04 upgraded to Ubuntu 18.04 (luckily in test environment). Answered Y to half a dozen prompts to convert login.d, sane, network and others to new configuration format. Only declined not to update /etc/default/grub to new configuration format.

Signed in with Unity under Xorg.

[WinEunuchs2Unix (ricklee518)]

Reply to #8, problem seems to have gone away on it's own today. Had tried multiple DE's that didn't work and went into Unity. A message that "Updates are available" appeared. Clicking on it installed nothing but probably ran `sudo apt update`, `sudo apt upgrade` in the background. Rebooted into 16.04. Later rebooted into 18.04 test environment and `Ctrl`+`Alt`+`T` and media keys are working.

[Juhyung Park (arter97)]

I'm also experiencing the exact same issues.

[Juhyung Park (arter97)]

I've been able to get a workaround for this issue.

I was using compiz(Unity) on my Ubuntu 18.04.
While GNOME seems to be fine, it looks like compiz is causing a race-condition with another process.

A workaround is to delay compiz launch for a few seconds.

Open up /usr/lib/systemd/user/unity7.service and add
ExecStartPre=/bin/sleep 2
before
ExecStart=/usr/bin/compiz

If this doesn't work, try increasing 2 to 3 or maybe 5.

This is a very dirty workaround and I'd like to see some real solutions,
but since compiz and Unity's development is pretty much banned,

I'm not sure if it'll ever get a fix.

[Dustin Krysak (bashfulrobot)]

For myself, it is happening much less frequently. I have only had it once since the final release. I'm curious if there is pattern here with upgrades vs fresh install. (I was a fresh install).

[Dustin Krysak (bashfulrobot)]

I just had it come back. Just cannot nail it down (pattern).

[Dustin Krysak (bashfulrobot)]

@arter97 - in my scenario, I have never had Compiz running (Does not come on Ubuntu Budgie)

[hossam ragheb (thundermind)]

I have the same keyboard shortcut problem ctrl-alt-t doesn't work. It starts once i login with Unity, and after switching between GNOME and Unity couple of times and restart, it starts to work again.

[Nhat Nguyen (nmnguyen)]

I have the same problem as well: After fresh install ubuntu 18.04 on the x360 spectre 13 inch 2017 version, the shortcut Ctrl+Alt+T to open the terminal doesn't work.

[Nhat Nguyen (nmnguyen)]

Just want to mention that the hotkey doesn't work on Wayland as well as Xorg. The DE is GNOME.

[Delacroix (tdelacro)]

Problem solved itself after logging out (from Unity), logging back into Ubuntu, logging back out and back into Unity. Since then the shortcuts work perfectly.

[Dustin Krysak (bashfulrobot)]

Have confirmed this to be an issue on other distros besides Ubuntu budgie. Usually restarting the window manager solves it. Wondering if it is something to do with gnome 3.28.

We never had this issue in 17. 10. Which was running on a previous version. The lastest change to the UB stack was the version bump to gnome 3.28

[Antonio Arauzo-Azofra (arauzo)]

On a fresh install with just the updates of today 2018-06-06, I have problems with Ctrl-Alt-Fn to switch terminals. It fails being logged in (at virtual console from Ctrl-Alt-F7) and from the login screen (Ctrl-Alt-F1). I thought console terminals had been disabled but ended up reading this bug.

From console terminals (F2 to F6) Ctrl-Alt-Fn keys always work.

However, they always fail when Ctrl-Alt-F7 are pressed being in console terminals (from 2 to 5), Ctrl-Alt are kept pressed while releasing F7 and pressing Fn (2 to 5) to go back to console terminals. The same with Ctrl-Alt-F1 for the login screen.

I have a usb corded Benq Spanish keyboard.

[Louis (louisgag)]

I have a fresh Ubuntu 18.04 install and experience the same problems: some keyboard shortcut do not work all of a sudden (they worked before, on the same installation)

Examples: super-L to lock screen, alt-printScreen, ...

[Mike Edwards (m1nermike)]

I have a fresh install of 18.04 on an LG Gram. The [control] [alt] T keys do not open the terminal. Within the terminal, the control keys don't work either. This is frustrating.

[Dustin Krysak (bashfulrobot)]

I have seen some people who have made these types of comments with desktops
other than Budgie, Can you confirm which one you are on?
On Wed, Jun 27, 2018 at 2:31 PM Mike Edwards <email address hidden>
wrote:

> I have a fresh install of 18.04 on an LG Gram. The [control] [alt] T
> keys do not open the terminal. Within the terminal, the control keys
> don't work either. This is frustrating.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1759462
>
> Title:
> Keyboard shortcuts not operational on 18.04
>
> Status in gnome-settings-daemon package in Ubuntu:
> Incomplete
>
> Bug description:
> After installing 18.04, I noticed that certain keyboard shortcuts no
> longer function.
>
> It appears to be related to the shortcuts that gnome-settings-daemon
> control as my shortcuts that are provided by my desktop (Budgie) still
> function.
>
> Some examples are:
>
> * Media keys for volume up/down/mute
> * ctrl-alt-t for the terminal. I tried changing the shortcut to test.
> Same behaviour.
>
> I double checked, and it looks like the needed daemon is still
> running,
>
> ```
> dustin 3337 0.0 0.2 500736 22216 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-keyboard
> dustin 3338 0.0 0.3 943372 25732 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-media-keys
> dustin 3343 0.0 0.0 274908 5844 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-mouse
> dustin 3345 0.0 0.3 519896 25144 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-power
> dustin 3348 0.0 0.1 346004 10212 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-print-notifications
> dustin 3351 0.0 0.0 374684 7952 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-smartcard
> dustin 3355 0.0 0.1 329584 8064 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-sound
> dustin 3361 0.0 0.1 449708 9856 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-sharing
> dustin 3367 0.0 0.0 272416 4772 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
> dustin 3375 0.0 0.0 420028 5804 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-rfkill
> dustin 3383 0.0 0.2 507120 23244 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-wacom
> dustin 3385 0.0 0.3 498040 25040 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-xsettings
> dustin 3387 0.0 0.0 274900 5936 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-a11y-settings
> dustin 3392 0.0 0.2 496016 22044 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-clipboard
> dustin 3395 0.0 0.3 810156 25976 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-color
> dustin 3396 0.0 0.2 471656 21080 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-datetime
> dustin 3400 0.0 0.0 361196 7116 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-housekeeping
> dustin 3433 0.0 0.1 5054...

[Mike Edwards (m1nermike)]

Thanks for the question. My desktop is just Ubuntu. I'm not familiar with Budgie.

I've found, though, that Ctrl Alt T works WHEN I use the right [CtRL] key, but not the left one. The left key does not register on the Keyboard Tester website, although it gives a key code of 37 when queried. The right key on the keyboard tester website controls both right and left [Ctrl] keys. This may just be a key mapping issue, rather than a Ubuntu issue. I can work with using the right control key in the interim. Of course, as a new Ubuntu user, I'm always glad to hear advice.

[Dustin Krysak (bashfulrobot)]

One thing I’ve noticed is that on budgie, when you restart the window
manager, keyboard shortcuts begin working again. I’m curious if that would
work for you…
On Wed, Jun 27, 2018 at 5:50 PM Mike Edwards <email address hidden>
wrote:

> Thanks for the question. My desktop is just Ubuntu. I'm not familiar
> with Budgie.
>
> I've found, though, that Ctrl Alt T works WHEN I use the right [CtRL]
> key, but not the left one. The left key does not register on the
> Keyboard Tester website, although it gives a key code of 37 when
> queried. The right key on the keyboard tester website controls both
> right and left [Ctrl] keys. This may just be a key mapping issue,
> rather than a Ubuntu issue. I can work with using the right control key
> in the interim. Of course, as a new Ubuntu user, I'm always glad to hear
> advice.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1759462
>
> Title:
> Keyboard shortcuts not operational on 18.04
>
> Status in gnome-settings-daemon package in Ubuntu:
> Incomplete
>
> Bug description:
> After installing 18.04, I noticed that certain keyboard shortcuts no
> longer function.
>
> It appears to be related to the shortcuts that gnome-settings-daemon
> control as my shortcuts that are provided by my desktop (Budgie) still
> function.
>
> Some examples are:
>
> * Media keys for volume up/down/mute
> * ctrl-alt-t for the terminal. I tried changing the shortcut to test.
> Same behaviour.
>
> I double checked, and it looks like the needed daemon is still
> running,
>
> ```
> dustin 3337 0.0 0.2 500736 22216 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-keyboard
> dustin 3338 0.0 0.3 943372 25732 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-media-keys
> dustin 3343 0.0 0.0 274908 5844 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-mouse
> dustin 3345 0.0 0.3 519896 25144 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-power
> dustin 3348 0.0 0.1 346004 10212 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-print-notifications
> dustin 3351 0.0 0.0 374684 7952 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-smartcard
> dustin 3355 0.0 0.1 329584 8064 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-sound
> dustin 3361 0.0 0.1 449708 9856 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-sharing
> dustin 3367 0.0 0.0 272416 4772 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
> dustin 3375 0.0 0.0 420028 5804 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-rfkill
> dustin 3383 0.0 0.2 507120 23244 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-wacom
> dustin 3385 0.0 0.3 498040 25040 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-xsettings
> dustin 3387 0.0 0.0 274900 5936 ? Sl 21:03 0:00
> /usr/lib/gnome-settings-daemon/gsd-a11y-settings
> dustin 3392 0.0 0.2 496016 22044 ? Sl 21:...

[fossfreedom (fossfreedom)]

Mike - just wondering if this is an ibus issue - UB has had various people confirm that the following seems to fix/help - https://discourse.ubuntubudgie.org/t/volume-up-down-calculator-ctr-altl-t-windows-key-a-and-more-not-working-anymore/140/75

gnome settings -> region&language and there, click on “manage installed languages” then changed “keyboard input method system” to none instead of ibus. Logout and login.

[fossfreedom (fossfreedom)]

seb - various comments here indicate that this affect ubuntu session - so it seems generic ... or at least to GNOME based desktops like Ubuntu and Ubuntu Budgie. Changing from incomplete to confirmed.

[Mike Edwards (m1nermike)]

Changing the keyboard input method system to none fixed my problem. The left control key is working great. [ctrl] [alt] T brings up the terminal window from the left side as well as the right. Now I just need to learn some terminal commands! Thanks very much for the assist.

[Zakhar (alainb06)]

Fresh install of 18.04.1 + Unity

I had the bug, but I can confirm than workaround at post #11 (2 seconds delay before starting compiz) has fixed it.

Thanks Park Ju Hyung!

[chrismart (chrismart)]

I just install 18.04.1.
With Gnome 3, no problem of keyboard shortcuts.
With Unity, some shortcuts don't work (Ctrl+Alt+T, Print screen , Media keys).

I try 2 solutions :

1. Post #11 (with delay 5sec) => in some sessions, they don't work, forced to restart.
2. Keyboard input method system to none => don't work for me.

Annoying :(

[nishant poddar (poddardelhi)]

I am having the same issue

[Gabor Csejtey (csgz2)]

I had the same problem with sound and brightness hot keys after upgrading to Ubuntu 18.04 on a Lenovo P50 using Unity.

Park Ju Hyung (arter97) solution #11 worked for me but with a slight modification:

ExecStartPre=/bin/sleep 1

Otherwise the hotkeys worked but the fonts began to fade making the text unreadable in all applications.

[Andre (a-blankers)]

Upgraded from Ubuntu 16.04 to 18.04 and media keys, Ctrl-`, Ctrl-Alt-T, and many more are not working.
Now I can't assign Ctrl-` any more, very annoying, now I use shift-` but this is a bad fix (it blocks ~).

[Andre (a-blankers)]

Fix from #11 works for me:

A workaround is to delay compiz launch for a few seconds.

Open up /usr/lib/systemd/user/unity7.service and add
ExecStartPre=/bin/sleep 2
before
ExecStart=/usr/bin/compiz

[István Mátis (1mi)]

Fix from #11 worked only until I locked the screen. After unlock my custom keyboard shortcuts did not work again.

[Khurshid Alam (khurshid-alam)]

For unity, see my comment here: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1188569/comments/15

[e-fernbach (e-fernbach)]

have the problem mentioned above, some shortcuts work some don't in particular ctrl-alt-t for opening a terminal, ctrl-alt-c in libreoffice.
What I observe is: ctrl-alt switches input source (I have two keyboards layouts defined en and de) although in the shortcut settings in settings the shortcut for switching between input sources is defined differently.
If I try to change the shortcut to open a terminal from ctrl-alt-t in the settings menu to again ctrl-alt-t, the shortcut ctrl-t is shown in the menue although I pressed ctrl-alt-t. If I accept the selection, the new shortcut ctrl-t works.
When in libreoffice ctrl-alt switches input source and ctrl-alt-c does not work to add comments.
Thus it looks like the problem might be with the alt key. Just guessing

Here is my system: Ubuntu 18.04.1 LTS with Gnome desktop 3.28.2, no compiz.
I remember that right after installing the shortcuts worked well.

[Sey Mza (smza)]

I have the same problem. I have installed Ubuntu 18.04 with Unity using the mini ISO. So I don't have GNOME installed with Unity. Keyboard shortcuts (e.g., launching Terminal or switching between keyboard layouts) don't work. Adding sleep 5 before launching compiz in /usr/lib/systemd/user/unity7.service works but only if I don't lock the screen. After unlocking the screen, shortcuts don't work again. The other solution that I've tried is to toggle "Commands" in "CompizConfig Settings Manager." This works but only if I don't log out. So I have to redo it every time I log out and log in. Is there any permanent solution to this? This is really irritating.

[Sey Mza (smza)]

I don't believe it's important, but like a few others in this thread, I have a Logitech Combo keyboard (MK550).

[Lennart Rolland (lennartrolland)]

This affects me.

My hw:

 + Lenovo P70
 + Cooler Master - Quickfire XTi

Description of problem:

After fresh boot I can use media keys on lenovo built in keybaord as well as the Fn + pgup/pgdn keys on the external USB keybaord to adjust audio volume.

But after hibernation or other power interruption this stops working. Only workaround is reboot.

It has been like this since I installed 18.04 fresh when it was new.

[Mike Kelly (kel008)]

This (keyboard shortcuts not working) happened to me, specifically CTRL+ALT+T not giving me the terminal. I experimented and found that the ALT key was at fault - it wasn't registering. I then found a reference on line (sorry don't have the URL) to this being a keyboard Language issue. I then tried: Settings, Language and Region, then set Language to English (United States) - I had it on English (Australia). My ALT key is now working.

[Vijit (vijit-7)]

The same problem with Yakuake:

Shift + Ins works, it makes "paste"
Ctrl + Ins doesn't work. Appeares "5~".

Taking in account, that Yakuake just a wrapper for Konsole, I checked combinations there and they works, as expected.

Before update from KUbuntu 16.04.4 to 18.04 all works fine.

[Vijit (vijit-7)]

What did you do with the keyboard?!

I found a lot of other problems, because triple combinations keys doesn't work at all. From the other side, we've got "on-screen keyboard" which is useless on DESKTOP Linux.

How to return the normal keyboard behavior from KUbunutu 16.04?

[Vincenzo Di Somma (vds)]

"Alt-F2 restart" temporarily fixes the problem, yes it's ugly, but at least, it's fast.

[Vincenzo Di Somma (vds)]

I can consistently replicate the issue when resuming from suspend. After resuming the shortcuts don't work anymore, running Alt-F2 restart solves the problem.

[Juhyung Park (arter97)]

For folks using Unity, I think I got a solution that doesn't require #11 's awful sleep hack.

Using 19.04's development version of unity-settings-daemon seems to fix everything.
I've rebooted 10 times straight in a row and all of them got shortcuts working.

First, upgrade colord(unity-settings-daemon depends on newer version of these):
colord_1.4.3-4_amd64.deb
colord-data_1.4.3-4_all.deb
libcolord2_1.4.3-4_amd64.deb

Then, upgrade unity-settings-daemon:
unity-settings-daemon_15.04.1+19.04.20181122-0ubuntu1_amd64.deb
libunity-settings-daemon1_15.04.1+19.04.20181122-0ubuntu1_amd64.deb

You can Google these and easily get the .deb files from official Ubuntu APT repository.

Install these debs and you won't require that awful sleep hack.

If anyone's still using Unity with that hack, please let me know how it goes!

[Juhyung Park (arter97)]

Nvm, ignore my previous comment.

Correct solution is posted here:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1188569

https://code.launchpad.net/~unity7maintainers/+archive/ubuntu/unity7-desktop

[Christian Lehmann (christian-lehmann)]

Kubuntu 18.04, KDE Plasma Version 5.12.7, Qt Version 5.9.5, Microsoft Natural keyboard:
Same thing: Although configured in Global Shortcuts, Ctrl-Alt-t does not trigger Konsole

[Artemis (alexander-plaza-net)]

I am currently using Ubuntu Budgie and I can confirm this issue still occurs with the latest 18.04.2 version. Fresh install and I can only get shortcuts to work using the Alt button. I am using an X240 Lenovo Thinkpad Laptop. If anyone has any possible fixes let us know.

[Aslan (human45762132508)]

I have the same issue. It has started recently after several months of usage. Super+D works. Most other shortcuts including Ctrl+Alt+T for opening terminal do not work. The physical volume buttons have stopped working too. Tried assigning custom shortcuts but that did not work too. Restarting does not solve the issue. Version: Ubuntu 18.04.2 LTS (Budgie) with all updates installed.

[Aslan (human45762132508)]

It saddens me to see the importance marked as low since this disrupts my workflow.

[Rudolph P (roprop)]

Just switched to budgie (from lubuntu) and encountered this issue, specifically while trying to fix the launcher shortcut for 'launch terminal'. After trying a number of the suggested workarounds, including the language/region ones, I dug into gnome settings and found that:

gsettings set org.gnome.desktop.default-applications.terminal exec x-terminal-emulator

worked for me.

[Rudolph P (roprop)]

Forgot to add: this is on disco with budgie* 10.5-0ubuntu1.1 and gsd 3.32.1-0ubuntu1

[manof (manof)]

Great, #11 - this worked for me, having exactly the same problems.
Dell 17 G7 7790

[Jenna Nelson (jem)]

#26 worked for me, although possibly in an unexpected way.

gnome settings -> region&language and there, click on “manage installed languages” then changed “keyboard input method system” to none instead of ibus. Logout and login.

...When I clicked on “manage installed languages” it said this wasn't fully installed. I completed the install, then I used alt-F2 and 'r' <enter> to restart the window manager. And woo! It worked (And critically no logout-login or restart required.)

[Jānis Kangarooo (kangarooo)]

 Kubuntu 18.04.04 doesnt have Dolphin shortcut Ctrl+E
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1866763
 Kubuntu 18.04.04 terminal doenst have shortcut ctrl+t
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1866764

[Nimrod Ben-Nes (yonatan)]

Had issues with keyboard shortcuts for changing language, up/down volume, open terminal and so on...

First I tried comment #55 and logged out and back in, it didn't help.

I went to try comment #11 (sleep solution) but then I remembered that few days ago I installed Skype and it was auto starting when I logged in and maybe cause of that the "timing went off", so instead of setting the sleep I just removed Skype from the auto start and restarted... and it worked!

[Nimrod Ben-Nes (yonatan)]

Just to be clear about the comment I wrote above, the solution is not really related to Skype, its probably just the fact that something new is loading up on log in and removing it will (hopefully) solve the issue.

[Gregory Kramida (algomorph)]

My particular problem stemmed from reconfiguring python3 to point to python3.7 instead of python3.6 via update-alternatives. Logging into terminal-only mode (Ctrl + F3), setting update-alternatives to use the system version of python3.6 again, and rebooting solved the issue.