

My experience from two of his works is that he is fascinated by the west in the same way some westerners are fascinated by Japan as in the meme:
Thing -> boring face
Japanese thing -> face full of awe
Might be wrong though.
My experience from two of his works is that he is fascinated by the west in the same way some westerners are fascinated by Japan as in the meme:
Thing -> boring face
Japanese thing -> face full of awe
Might be wrong though.
My 2 cents. I started with Bazzite and switched to Fedora after some things broke. Fedora works for my use case and I don’t see any reason to switch further. Even upgrading from 40 to 41 worked without hickups.
Is there any write-up for the recent events around the kernel and Rust? Glancing over recent posts, it seems like new devs want to push Rust, but older maintainers don’t want to deal with it. Why do people love Rust so much? Is it just a loud minority or does it in fact offer substancial gains and safety over existing C code? Lqstly, can they simply fork the kernel and try their own thing? E.g. do a branch as a proof of concept and therefore convince them to migrate?
Yesterday I came back to my issue and decided to try LazyVim just to see what would happen since it comes with Mason. It worked, first try. Both on Linux and Windows. I seriously have no damn clue why it wasn’t working standalone… It has to be something with Plug
No, it works just fine. It finds Mason and does the check ehich returns OK results except the add-ons for specific languages (e.g. it deteckts python3, complains about misisng rails etc.)
No, no conflict whatsoever. Just an error mesaage that the command is not recognized/present. Telescope works just fine. The colorscheme as well.
That was the problem. Stupid me…
You are right. I messed it up adn didn’t put $ infront of PATH… Luckily I found an stackoverflow post with a similar issue and it suggested setting PATH to the default PATH=/usr/bin:/usr/sbin
that would alowe using commands again and it worked.
Yes, because if it didn’t happen in the season, it would make it an out-of-season depression.
Holy hell. Things went from pretty aweful to horendous. I regret having the abilty to read :-/
Fastboot was never enabled to begin with :-/
Ok, I foxed it! I looked around in the log of which I mostly understood nothing, but then I came acress the section where the kernel/shstemd mounts the drives and the error it spits out. Googling it gave me an arch forum post with the identical problem. Windows didn’t shutdown correvtly the last time I used it and did something to the partition table. I’ll update my post wiy the solution.
Tnx. I will report back tonight when I get around checking.
I touhgt the same, but connecting a new drive and getting the same “read-only file system” error is really strange. I used the other drive for qbittorrent and it worked flawlessly before the update. I haven’t come around to try any of the suggestions yet. I’ll report back tonight.
The KDE system settings have no such option :-/ All my google results for line spacing are regarding the terminal, non for my case. I guess there is some config file somewhere that I can edit, but sine I am still nee to Linux, I jave no idea where to start.
As a newbie in this space, I had interactions with a few distros over the years and lately switched (hopefully) permanently.
My first experience was with Mint 10 years ago. Installing it would cause some GPU driver defect (AMD card) and would turn the whole login screen into an epileptic checkerboard pattern with no way of doing anything. It took me a few reinstalls and a ungodly amount of googling to find a solution which involved opening the terminal at boot process. You can only imagine how frustating that can be for a newcomer.
Later in time I had Ubuntu on my laptop which had a bug that wouldn’t spin up the CPU fan and it would simply overheat and shutdown. I had to take it to a technician to find out what was causing the random shutdowns.
A year ago I decided to try Debian on my desktop PC as many have praized it for it’s rock-wolid stability. It didn’t want to work on my PC. No internet connection and some weird bugs. Took me two-three days to get ti to work and I still don’t know what exactly fixed it as I have applied every possible solition I came across.
Much later, aka now, I decided to go with Bazzite on my desktop as many have claimed excelent support. I wanted to install the mimalloc because I play Factorio a lot and a few reddit posts claimed 20% UPS improvement over the stock scheduler. After downloading the source code and following the 4 very easy steps, cmake would throw some random eerors at me claiming some critical files were missing, although they were right there in the usr directory. Turns us Bazzite some some issue and Fedora 40 compiled the code in seconds without any issues.
Conclusion: Linux users, which are very tech savvy or work in that space, know what to do when things don’t work out, while the rest of us keeps googling and crying over error messages for things that seem trivial. You never seem to know if it’s you, the system or your hardware.
I use goodreads to read reviews since they are plenty and longer. But I give ratings and track my progress only on StoryGraph.