Hello,
I’ve been using Kicksecure for the past few months and I have recently encountered an issue that I have never seen before. I had rebooted my workstation after being in live mode and went into my persistent session. After logging in I was not able to open Qterminal via the user panel nor the hotkey CTRL+ALT+t. As of now I have installed a new terminal emulator but Qterminal still doesn’t work.
Has anyone encountered this issue or know of how to fix it? Thank you for the all help!
EDIT: After installing a new terminal from a TTY session (foot terminal), the command qterminal responds with the following
zsh: segmentation fault (core dumped) qterminal
You don’t happen to use Google Chrome or Chromium do you? If you do, you might be running into this mess:
Running rm -rf ~/.cache/fontconfig may fix the issue.
1 Like
Hi,
I don’t use Chrome or Chromium but I use Brave Browser along Mullvad browser, I’m guessing this would still be an issue right?
Brave Browser is based on Chromium, and the bug was introduced in Chromium, so yes, it is very likely the issue.
Keep in mind that every time you open Brave, it will (likely) re-create the bad fontconfig cache, and you’ll need to remove it again. If you find this too annoying, you can create empty /home/user/.cache/fontconfig and /home/user/.fontconfig directories, then use sudo chattr +i on both of them to prevent Brave (or anything else) from writing to them. (You’ll have to do this from sysmaint mode unless you removed user-sysmaint-split.) This will break the fontconfig cache, but in my experience this doesn’t result in any real issues. There might be a loss in performance when starting apps, but if there is, I haven’t noticed it.
1 Like
Thank you very much for assisting me, I’m gonna try this out now thanks.
1 Like
Did as you said and now I can open Brave and Qterminal, thanks for the help!
1 Like