Recently completed a routine upgrade from Leap 42.1 to 42.2:
– I changed no settings, yet in any administrative or settings utilities my letter “d” does not type at all.
– Checked SETTINGS > WORKSPACE > SHORTCUTS > GLOBAL (and the others), but no “d” key is listed throughout.
– No application is using ‘d’ as a global shortcut.
– It works most everywhere else, in the browser, text editors, for example.
– Everything in /etc/X11/xorg.conf.d is fine, and the correct keyboard is selected under Input Devices.
– Konsole doesn’t let me input any password at all, not even passwd.
If you switch to VT1 with CTRL + Alt + F1, and log in does the key then work as expected? That would help rule out any DE specific bindings. You can switch back to the graphical session again with CTRL + Alt + F7.
I would also put in a live cd/usb if you have one just to make sure that it’s not a hardware issue. It’s always best to check the obvious possibilities first.
Thanks, though this did not work. I could type my login ID, but not the password. However, there’s no “d” in my login ID. I get the same result whenever I use Konsole or Bash.
Please tell us which physical Keyboard Layout is present on your system.
If your physical Keyboard Layout is not something like a QWERTY keyboard then, in the 2nd from bottom row of keys the 3 leftmost keys are not “A”, “S”, “D”.
It may be that during the upgrade the system keyboard has been changed to “en-US” (QWERTY).
It’s a QWERTY (Microsoft Natural) keyboard, labeled as such in the Keyboard Hardware and Layout dialog, where the Switching Policy on the Layouts tab is set to Global. Also, the hardware info from YaST reads it as an AT Translated Set 2 keyboard (/dev/input/event0).
@zaine_ridling:
What happens if you boot either the Leap 42.2 DVD ISO image or the Leap 42.2 NET ISO image (fits on a CD-ROM)?
The 1st screen allows the system language and keyboard layout to be chosen – with a keyboard test field.
It works just fine there, actually. You can see why this is a great mystery to me. I changed three keyboards today just to confirm it’s not an hardware issue.
Can you please give us an idea of how your partitions are laid out?
Renaming mount points is not normally needed – a “normal” user never ever needs to know where directories are mounted. Why do you feel that the default system mount points need to be renamed?
Which Fluendo codecs did you install? The audio ones which are supplied with openSUSE or, the video codecs which have to be bought from the Fluendo folks?
(a) BTRFS
(b) Mainly the basic partitions: /sda (BTRFS) /sda1 (Grub) /sda2 (swap) /sda3 (native) /sda4 (XFS for this one)
(c) Not the default, just one that the OS recommended renaming in a popup warning during installation, which was an external HD.
(d) gstreamer-fluendo-mp3 was the only one installed.
My personal preference for user desktops or laptops is to treat external HDs as “pluggable” devices – not mounted at system boot time – let the user’s desktop auto-mount the external device as needed.
The only exception that I can think of is, standalone boxes with an external (USB) drive permanently connected.
I remember having issues like that when the first time i switch from emacs to vi in the readline interactive editing mode in bash.
I did edited ~/.inputrc and made a mess