Hanzel
17 December 2022 23:07
18
Confirming that one is affected by this behavior without leaving information on what kind of system this occurs is only helpful if more info is posted about the system affected:
Difficulty: ★☆☆☆☆
Rather than providing the commercial reference of a computer or piece of hardware, it is usually better to directly ask the system to describe itself. On top of saving time to everyone, this also often provides more details, including something specific to the running system.
Below is a (not exhaustive) list of commands for retrieving system information.
If you don’t know how to use those commands, or how to provide them to support, see: [HowTo] Use the terminal / TTY …
and if possible some effort on find this cause would be furthering the cause of this issue:
Difficulty: ★☆☆☆☆
The first step for troubleshooting an issue is to find an error log: a trace produced by an application when failing/crashing, and providing the first trail a user/developer can follow to fix it.
1. Reach a usable system
Obviously, it will be impossible to acquire those logs if you can’t have access to a usable system.
See: [HowTo] Reach a minimal system
2. Find the faulty application
If you don’t know which application failed – this is usually the case on a system or gra…
So far the input of @jordanmiracle has narrowed it down for the issue experienced
Leaving answers to these questions could help narrow it down:
Yochanan:
Sounds like it could be a keyboard issue.
Have you tried another one?
Does it only happen with one letter?
How often does this issue occur?
Can you reproduce it on a live ISO?
Can you reproduce it with no extensions enabled?
Can you reproduce it on a new user account?