First of all, I just installed Fedora (KDE) a couple months ago on my desktop and now for university on my new laptop (amd cpu w/ integrated graphics). As you may guess, I and am pretty much clueless on many things with Linux.
Now, just as the title states, I have a weird issue with unresponsive writing since like three days on my laptop. It already starts when typing the password at login. I say “weird” because I noticed some things:
The issue only persists in certain programs. For example using a browser, I don’t have this issue. But typing something in the console or searchbar, the issue is there
In some apps, the unresponsiveness is extremely predictable. I.e. at login, when typing the full password, it always show only one character but (and only) after moving the mouse, it showes everything. I noticed this behaviour in the searchbar and console as well.
In (2.) I said “some apps”. This is because in other apps (i.e. Obsidian), the unresponsiveness has nothing to do with moving the mouse (as far as I’ve noticed)
When having System Monitor open, the issue completely perishes from every app and comes up again just after closing it.
After looking at some graphics information, I found this in the “OpenGL (EGL)” tab: “_amdgpu_device_initialize failed”. I searched for this on the internet and somehow doubt that this has something to do with my problem, but maybe you guys know better.
There are often issues with very new hardware unless the vendor supports linux (and even then they may provide a driver that is not yet available in linux distros). Some issues are fixed with firmware updates from the vendor. Since issues like this are rarely specific to a linux distro, searching vendor and other distro forums can be helpful.
Please post more details of the new laptop, e.g., by running inxi -Fzxx in a terminal (as searchable, pre-formatted text using the </> button from the top line of the text entry panel). This will help others with similar hardware and issues find this topic.
Alright, I don’t know why I didn’t have this idea before but I just booted the kernel version 6.11.7-300… and with this everything seems to be working fine. Maybe I just have to hope that this will be fixed with the next kernel upgrade.