This is a bit borderline but since I guess everybody is using a PC here
(or a MAC...) you probably have a keyboard too...
I recently (less than a year) got a mechanical keyboard (Logitech G512 -
liked the 512 number...) and it's been complicated. I initially offered
one to my wife, she loved it and "forced" me to get one too.
I had to wash it dismantling the keys, putting them in soap and water,
drying them, etc. I also bought a small hover to suck the potential dust
creating problems (or ... something else). After less than a year both
keyboards have been back under warranty, one because of the RGB lights
breaking on some keys, the other one because of keys not working after a
few hours of work (that's mine).
When having problems (like the space bar, C key, arrows, etc stop
working) I eventually took other keyboards I already have, and then I
really missed the 'typing quality' of the mechanical one.
I also appreciate that the Logitech keyboard do have Free Software
projects allowing you to control each key and set up the lighting the
way you want. You can even do (keyboard) games with those.
I however suffered all those (un)typing issues and am disappointed by
the overall quality. 2 keyboards, 2 went back under warranty (1
replaced, 1... waiting for it).
So let's say I am hooked with the technology but...
Do you guys know of any keyboard with similar typing quality but with
durability and eventually free software driving the RGB lighting? I can
probably live without the RGB stuff as well ;-)
Oh .. I don't play games, just spend the whole day (and night?) behind
(in front of?) my PC.
ps: numeric pad is a must
At some point my Windows (Super) key stopped working.
Trying the following doesn't produce any output when the super key is
$ xinput list
WARNING: running xinput against an Xwayland server. See the xinput man page
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ xwayland-pointer:18 id=6 [slave pointer (2)]
⎜ ↳ xwayland-relative-pointer:18 id=7 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ xwayland-keyboard:18 id=8 [slave keyboard (3)]
$ xinput test 8
But pluggin my keyboard into my work laptop running windows it works fine.
Hello. I'm a potential new user, but I'm having trouble with the install.
I have Windows and Leap on one of the new on-board drives, and I
have added /dev/sda, a new Samsung 465 GiB ssd (ordinary type) to
the system. I formatted it to ext4 using GParted, and it's empty except
for 8.38 GiB at the beginning that GParted must have added. When I try
to add theFedora system to this, it says there is only 1.2 GiB available.
I went back and ran GParted on it again, but it still comes up the same way.
What am I doing wrong? Or is the drive defective? GParted doesn't
complain about it.
Thans for your assistance--doug
Fedora 34 / KDE / Plasma. Everything works great except that I can see the
Fedora 34 desktop wallpaper patterns in my application windows. The
desktop wallpaper is "bleeding through", like the application windows are
How do I fix this ? Is it an effect in Settings ?
Hardware: Asus A17 4800H with integrated GPU as well as a discrete
$ uname -a
Linux fedora 5.13.12-200.fc34.x86_64 #1 SMP Wed Aug 18 13:27:18 UTC 2021
x86_64 x86_64 x86
plasma-breeze.x86_64 5.22.4-1.fc34 @updates
Fedora rocks !
I'm using a Logitech G512 (wired) keyboard. Usually works perfectly in
the morning and little by little I get stuck with 'some' keys. I say
some because it's not regular. I press them and they don't seem to
work.. then work "if I press harder" ... or later?
When using the native laptop keyboard, or another BT Logitech K480
keyboard the problem is not there.
I am really hesitating to bring it back as I've noticed when in the
browser or some applications highlighting the blinking character cursor,
that it actually stops blinking at times, and then suddenly either gets
3 keys typed in a row, or just a 'huge' time delay between the moment I
typed that key and the moment it appears.
Are there any reliable ways to troubleshoot and pinpoint where the issue
could be coming from?