Since one of the latest updates/few days/weeks i have these problems:
When i update to the newest packages and newest linuks kernel (just default updates), when i power on my laptop, on page where i should input my luks password, keyboard seems not interacting with luks password, i input it and *** doesn’t show, like it was before. i can’t log in to kicksecure, something is broken, tried to input and enter but no it doesn’t work.
When i reinstall or downgrade to older linuks kernel, i can input my password, but just after i input it and click enter my pc immediately turns off (most of the times), just shuts down, no errors before.
I tried few things to find problems, some workarounds with drivers, but nothing helped.
btw i have asus laptop with amd cpu and amd igpu and nvidia dgpu. installed on nvme.
It worked perfectly before, now something broke in kicksecure, what can be a problem and solution?
The only thing in Kicksecure that I can immediately think of that could cause this is a hardening setting change, but there haven’t been any notable hardening setting changes recently.
It isn’t guaranteed that this is a Kicksecure bug, as it is theoretically possible that the hardware is failing. Some debugging steps to take are:
Download the Kicksecure ISO and boot from it. See if the system is usable in ISO live mode.
If the system is functional that way, install Kicksecure on a second drive and fully update it. See if the system is usable (perhaps you changed a configuration setting that broke something).
If the system is not functional after that, download and install a Debian live ISO, and install it to a second drive, enabling disk encryption in the process. Then fully update it. See if the system is usable. This will tell us if the issue is somehow specific to Kicksecure or not.
I tried many reinstalls so i don’t think it is configuration thing,
I also updated my Tails now and now i also can’t write anything in Tails password or other places on window there, so maybe it is something connected to keyboard drivers, but i’m not sure, how can this be fixed?
Until we know what’s wrong, it’s impossible to know how to fix it. The info you gave sounds like the same issue might be happening in Tails too, although it’s a bit unclear.
Could you please follow the exact steps given in my previous comment, and report in detail what the results were from following each step? More detail about how to provide a useful bug report is here:
(Sorry to be this particular about details, the problem is that computers are rather finicky and a seemingly very slight difference in behavior can indicate radically different underlying causes. For instance, if this behavior only occurs on security-focused operating systems like Kicksecure and Tails, perhaps a kernel setting or other configuration setting is triggering the issue, whereas if the issue happens on vanilla Debian as well, that potentially points to a kernel bug.)
ok,
Kicksecure 18 in newest version, after all updates.
My laptop is ASUS Rog strix g16 with AMD CPU and AMD iGPU and Nvidia dGPU + 2x Nvme.
After updating to linux kernel .113 it fixed problems with keyboard, but problem nr 2 still mantains.
After inputting password and clicking enter few seconds after my pc turns off, i set llog level to 7, but nothing worrying there before shutdown. I’m not sure but journalctl also don’t show anything too bad but i probably do’nt understand, tried with modprobe.blacklist=hid_asus, didn’t helped