17

I just updated from Ubuntu 16.04 Unity to Ubuntu 18.04 with GNOME. The update went well except for one thing: some times IntelliJ Ultimate keyboard shortcuts simply stop working. They work for some time and then they stop. I have only 2 GNOME extensions enabled: Ubuntu Dock and User Themes.

What can be the cause? How can I troubleshoot this?

If I restart IntelliJ they start working again, but eventually stop working.

All the keyboard shortcuts are affected:

  • Ctrl+Shift+A (to open settings in IntelliJ)
  • Shift+Alt+Left/Right to move back and forward in the code.
  • All shortcut keys.
  • Arrow keys don't even work to move up and down in the code.
8
  • 1
    Too broad. Which exact shortcuts are broken? – N0rbert Aug 20 '18 at 10:04
  • 1
    All... Ctrl + Shift + A (to open settings in IntelliJ), Shift + Alt + Left/Right to move back and forward in the code. All shortcut keys. Arrows in the code don't even work like up or down. – ddreian Aug 20 '18 at 11:25
  • I hava the some problem with eclipse, look like the combination Shift+Ctrl+XXX not working, may be caused of IME? – Yu Jiaao Oct 12 '18 at 1:03
  • 1
    On "Settings> Devices> Keyboard" all my custom shortcuts that use xdotool like xdotool key XF86AudioNext stop working because also on terminal won't work. I wonder if this is related to some other shortcuts on "Sound and Media" stop working also. Maybe one of this bugs?. Worth taking a look to dconf dump /org/gnome/desktop/wm/keybindings/ | grep -v disabled. – Pablo Bianchi Jun 5 '19 at 23:01
  • Upgrading always can have some glitches. You may want to reinstall fresh. – vanadium Jul 15 '19 at 12:31
1

I don't really have great insights into this problem, but rather than leaving it without any answers, I'll share what I have. I think the comments on the question are great. Given that the problem happens after some time elapses running IntelliJ, I would suspect that some other application starts running and grabs those shortcut keys. It might even be some sort of plug-in in IntelliJ.

You might investigate any recently started processes when you first notice the problem start happening, via

ps e -o pid,start_time,command --sort start_time

If it is a transient process, that could be harder.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.