

I’ve never had issues like that on Kubuntu, Debian, or EndeavourOS. KDE is great and I love it.
I’ve never had issues like that on Kubuntu, Debian, or EndeavourOS. KDE is great and I love it.
I use Debian on machines I don’t want to fuck with or have change much.
I use Endeavour because it was recommended to me for the bleeding edge hardware I had just bought for gaming.
I decided to ditch Helix and stick with vim, my main code editor is Kate anyway lol.
Damn now you got me trying to get used to it. It’s hard when vim is so ingrained in my habits. And Helix isn’t in the Debian stable repos yet. It does seem faster and better though!
That stops it from being Free, which is freedom 0. From GNU.org:
A program is free software if the program’s users have the four essential freedoms:
- The freedom to run the program as you wish, for any purpose (freedom 0).
- The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
- The freedom to redistribute copies so you can help others (freedom 2).
- The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.
A program is free software if it gives users adequately all of these freedoms. Otherwise, it is nonfree. While we can distinguish various nonfree distribution schemes in terms of how far they fall short of being free, we consider them all equally unethical.
What you’re talking about is changing Free software to be non-Free. No thanks.
These are FOSS projects, not open source. They’d no longer be FOSS and that would be bad. Freedom 0 is important.
I play Starcraft 2 through Proton, it works pretty well. These days pretty much all distros are perfectly fine for gaming, maybe with the exception of Debian stable. If you’re new, I’d recommend staying away from Arch and derivatives like Manjaro. Also try to keep things simple for yourself and avoid flatpaks, snaps, and appimages.
I saw this problem for the first time yesterday. Run dmesg
to look for errors from the kernel, for me I had amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
. I took this to mean that my system couldn’t communicate with the monitor to change brightness anymore. When my system is idle, it first dims the monitor before turning it off, so when I wake it back up it’s stuck on low brightness like this. Simply turning my monitor off and back on seemed to fix it.
Yes, most people aren’t aware of it as they’ve seen inside Program Files and assumed that was all the program’s data.
Bro you’re messing with wine prefixes? You already know more than most and clearly have the motivation and ability to do what you want. You’ll go far, just google what you need when you need it like the rest of us :)
It’s the price of bleeding edge :) Hope you find what you’re looking for in Nobara, my dude.
I’ve had the same issues with Endeavour, sometimes you get buggy software and need to roll back. I do a full system backup once a week and update once or twice a day (I like updating frequently as it makes it obvious which package broke your system). When I get a bad package I just restore from backup but exclude /home. Then from there I install packages one at a time until I find that bad one and then just ignore it for a while. It really hasn’t been too bad. I don’t think you’ll find anything like the AUR if you start distrohopping. Debian is the king of set it and forget it, but it might be a shock to go back older packages of everything.
Rule 8? This has nothing to do with PC gaming. Glad he got banned though, fuck 'em.
I wish everything was put into ~/.config or whatever the proper place was. Oh you’re used to your ssh config being ~/.ssh as it has for years? So make a symlink! Everyone wins.
protip: put bind -s 'set mark-symlinked-directories on'
in your ~/.bashrc
and also bind -s 'set completion-ignore-case on'
because why not :)
Use it and redshift anyway, what kind of exploitable vuln could possibly be found in it?
It hasn’t broken gzdoom, the only thing I use sdl2 for.
What about this one that you’re on right now?
Slashdot
On The Metal
This Week In Linux
Destination Linux
[https://linuxgamecast.com/feed/lgcweeklyaudio](Linux Game Cast)
Arch Linux Security Advisories