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.

Comments

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.

/usr/bin/dconf-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

Using AMD RX Vega driver OpenCL on Fedora 29

The Raven Ridge APU is very capable processor to handle OpenCL inside some applications like Blender, Darktable and Gimp. Unfortunately, the current implementation from Mesa, clover, stuck to 1.3, is not supported. AMD released their driver 18.40 with OpenCL2.0+ targeting only Red Hat Enterprise Linux/Cent OS 6.10 and 7.5 in addition of Ubuntu LTS. The good new is the former rpm format can be used on Fedora.

The graphical part of Raven Ridge is Vega 8, basically a cut-down of Vega56 or Vega64 meaning choosing either driver for RX Vega.
The instruction is provided for extracting the rpm files but here is
 some requirements for OpenCL:
kernel-devel (provided by Fedora repository)amdgpu-dkmsdkmslibopencl-amdgpu-proopencl-amdgpu-pro-icd Once done, applications needing OpenCL will automatically detect the driver located on /opt/amdgpu/lib64. Blender will list as unknown AMD GPU and Darktable will enable it.



There is a ROCm version but it currently does not support the graphical side of Rav…

Fedora 29 Design Suite Lab available

Fedora 29 Design Suite is available for downloading with latest stable release  applications including Gimp 2.10.6 among the features.
On the bad news side, Blender 2.79b on Fedora 29 has broken user interface due to compatibility issue related to python 3.7. Workaround will be installing from the flathub directory.

Next release will be interesting considering the structural change for the incoming Fedora 30 with the advent of flatpak packages.

HP Envy x360 Convertible Ryzen 2500u update

Nearly one month later, HP Envy x360 Convertible 15  powered by Ryzen 2500U is running smoother on kernel 4.19.0 with someissues:
The LED for the mute button failed to work suggesting a possible ACPI issue.An unfortunate oversight from HP for not including a led for Num Lock button. The touchscreen function failed due to ACPI bug related to a mis-configuration of tables. Sadly, it affects all HP Envy touchscreen series equipped with AMD processors. Workaround made by an Arch user exists and no upstream Linux maintainers has picked up yet for clean up and improvment. The side effect would be an unfortunate false impression HP touchscreen with AMD processors is horrible.The gyroscope needed to automatically rotate the screen depending of the position is broken possibly due to ACPI bug.
On the positive side, I was impressed by the modular adaptability  of HP Envy x360 upgrade wise thanks to the excellent HP documentation. The board can be replaced with the powerful version of Ryzen 7 APU…