https://archlinux.org/packages/extra/x86_64/flatpak-kcm/

Looks like its only optionally required by plasma-meta. I’m not familiar with it but it looks like a GUI for editing settings rather than something fundamental so I’d be surprised if uninstalling it is the source of your issues.

They’re useful for templates because the trailing version is resolved later

One thing that holds people back sometimes is that bash scripts that set environment variables don’t work by default. https://github.com/edc/bass is an easy solution

A wild gunnerkrig fan!

There have been plenty of cases of windows messing up boot configuration if dual boot over the years, though it’s pretty rare more recently. The last one was only a few months ago and affected systems using secure boot https://www.zdnet.com/article/windows-update-breaks-linux-dual-boot-but-there-is-a-fix-for-some-users/

I never used npp as my code editor but as a secondary program that i kept notes in and would paste text in to manipulate then move back into code editor. It had a rich plugin ecosystem way before that was common. I use Kate for those purposes instead now

https://archlinux.org/packages/extra/any/kde-applications-meta/ ?

https://logseq.com/

The way that rust attempts to prevent this class of error is not by making an implementation of free that is safe to call twice, but by making the compiler refuse to compile programs where free could be called twice on a pointer.

Anyway, use after free doesn’t depend on a double free. It just means that the program frees memory but keeps the pointer (which now points at memory that could contain unrelated data at some future point in time) and if someone trying to exploit the program finds a way to induce the program to read or write to that memory they may be able to access data they are not expected to, or write data to be used by a different part of the program that they shouldn’t be able to