Skip to main content

Easy way to fix non functional ctrl key

Ctrl key buttons refused to work on laptop?
  • Tried pressing Ctrl + Alt + Fn? Mixed result.
  • Reboot hardware? No dice.
  • Pressing Ctrl + Left click on Touchpad? Worked

I am not sure what exactly caused the problem as the issue surprisingly affects more models than expected.


You are using Gnome and installed most likely with Anaconda. nevertheless, here is some thing to review

# This note explains how to remove two key combinations that interfere with the keyboard when used with GNOME
# The problem manifests itself when trying to use the key above the [tab] and to the left of the [1]
# Without following the instructions herein, that [~ `] is unreachable.
# The location of keybindings is buried deep within subdirectories of the editor.


# The explanation follows.
# Start the dconf-editor and follow the schema to /org/gnome/desktop/wm/keybindings/
# In my case I looked for for switch-group
# The value before the change : ['Above_Tab','Above_Tab'] Note that "switch-groups" has two setttings,
# Remove the right most setting ",'Above_Tab'" by deleting from right to left.
# While you are erasing the characters, from right to left, you have a highlight for an error indication
# That highlight will disappear when you erase the comma following the first argument.
# You will note an error indication until you arrive at the first parameter
# Your net result should be ['Above_Tab']

# You have to do the same for the shift-setting

# The backwords setting is next to search for #switch-group-backward
# Remove the ,'Above_Tab'

What you need to review is the control key settings. and restore or enable what was changed.

My fix gives you an idea of what you require to investigate.
The issue about Ctrl key suggests BIOS/firmware related in the laptop as the rest of keyboard works as intended within Gnome Shell session.
I run other operating system like Windows 10 which had the same problem.

Popular posts from this blog

Running Sapphire Radeon RX 560 on Fedora 27 beta (follow up)

Following the previous blog and some investigation, it turned out the kernel package from Mystro256 COPR repository based on agd5f kernel branch (one of AMD developers) resolves the blank screen issue. That could trigger a problem for users having a new AMD graphic hardware so perhaps a warning should be written on the release. Perhaps having one of contributors be part of kernel team bringing these improvement until those patches arrive to the mainline kernel for a better user experience.

Past the issue, the desktop experience with Radeon RX 560 was tremendously improved compared to the retired GTX 460 v2. Gnome on Wayland on Fedora runs smooth showing how far the open source amdgpu driver went through compared to previous years. That was also the opportunity to run a vulkan based smoke test demo on RADV, which is a counterpart of glxgears.

Overall the card is excellent once missing software are installed.

Running Sapphire Pulse Radeon RX 560 4GB on Fedora 27 Beta

I bought a Sapphire PulseRadeon RX 560 4GB to replace the broken Nvidia GTX 460 v2 after a long years of service. It is then my first ever dedicated AMD based video-card for a desktop.

The boot sequence on Fedora 27 hit a problem: a plain blank screen suggesting the card is not yet supported. Looking at Phoronix website revealed one of possible requirement missed: LLVM 5.0 which is currently not available to Fedora repository save a failed built. I filed a bug report to address the issue. Hopefully that will land on time for the official release of Fedora 27.