861–870 of 1001 posts
Earlier quoted context omitted.
Yep, I've been gaming exclusively on Ubuntu (mainly because I want my desktop to match my servers) for several years. If you aren't playing the latest AAA FPS, then everything pretty much works.
How much work is it to get snaps out of your way? Canonical seems to be going all in on them as their business strategy.
Earlier quoted context omitted.
I have been working professionally on Linux for many years. But about once a year I have to reinstall the os because it craps out for various reasons. The same story goes for most of my team, but for some reason they seem ok with this. My issue with Linux is this: I don’t feel like a consumer, but a janitor. I don’t want this. Yes you can do whatever you want, but I don’t want to do those things. I want to write code…
> it craps out for various reasons. What does that even mean though? Under what circumstances? In what way? > working professionally on Linux for many years. Not enough to say which distribution... or do you mean you do kernel development work?
Earlier quoted context omitted.
I don't know what you are doing but I have my Arch Linux running since about 2013. I needed to intervene a few times, I think 4 times in total but the base installation in from 2013, now nearly 13 years ago.
I share the same sentiment. I've had the same Arch install running since ~2016 and have been using Arch since about 2013 and the number of times I've needed to chroot from a live image is under 10 and were mostly related to systemd breaking things during an update which is pretty much entirely no longer an issue these days. Compared to Windows-land where nuking and reinstalling the entire OS is a routine maintenance…
Yet I've never had to reinstall windows on any of my devices ever. I've never had things behave in unusual or unpredictable ways.
Meanwhile, a highly suggested utility (on reddit, SE/SO, and even a few distro forums) for touchpad gestures borked my gnome setup. (Uninstalling it, as you might have guessed from my story and tone, did diddly squat.)
Just today I manually flushed my dnf packages (or clear them? Not sure of the terminology.) In the past, I had to debug manually because apparently the default timeout for Fedora was causing timeout issues with a few 100ms internet latency. That was a fun rabit hole "why can't I install an app that's only available via dnf install" "Oh, because Fedora assumes you have good internet. But don't worry if you have Ubuntu, because that doesn't have these issues!".
...I've never even been made aware what download timeouts windows has. As it should be for a user.
I could go on and on. My windows partition goes nearly months without sleep, typically only rebooting if I run out of battery or want to install an update. Linux... doesn't have hibernate yet. Fortunately it doesn't matter! ...Because some odd memory leak (and gpu driver stuff perhaps?) forces me to shut down ever so often. Oh well.
Earlier quoted context omitted.
It's not just Ubuntu, Arch is just as bad. The primary problem is systemd, which provided an adequate OOMd for daemons, but then all the distributions seem to be using it for interactively launched processes If anybody can help me out with a better solution with a modern distribution, that's about 75% of the reason I'm posting. But it's been a major pain and all the GitHub issues I have encountered on it show a big r…
It's funny how you say the way it used to be was better when people always complained about the OOM killer waiting until the system had entirely ground to a halt before acting, to the point some preferred to run with 0 swap so the system would just immediately go down instead. Regardless, I believe EarlyOOM is pretty configurable, if you care to check it out.
The problem is not that OOM killing happens earlier under memory pressure, but rather the problem is what gets killed. Previously an offending process would get killed. Now it's an entire cgroup. So if you are using process isolation to run a batch of computation jobs, each of which takes different amounts of memory and it is not foreseeable which will take too much memory until runtime, the OOM killer takes out the batch manager and its shell and everything. So the process can't know ahead of time if it's taking too much memory, because allocations never fail, and the process itself shouldn't be monitoring what is going on the rest of the system to make run time decisions to quit. The entire batch of jobs is killed, rather than a single process dying (as happens for any number of errors) and continuing in with the rest of the batch of jobs. In fact, without interacting directly with systemd-run to create a new cgroup, it's impossible to monitor WTF happened to your process because of this new "nuke it from orbit" behavior.
During my searches on this another common error case is in an IDE where one process goes wild and takes too much memory, and then the whole IDE gets killed silently instead of single process killing allowing the app to save state.
This is a very fundamental change to how Linux has worked, it's a novel concept unfamiliar to long time users (who the fuck actually knows about cgroups or uses them extensively except for people heavy int containerization?), and workarounds for the behavior require introducing heavy dependency on systems in order to get basic functionality, making my code far less portable. I can understand being dependent on GNU, and some linuxisms in syscalls, but changing the basic semantics of launching new processes such that new code dependencies are needed for intricate cgroup control, well, that's a bit much for me. Leave systems-oomd to manage cgroups and containers, but having it manage desktop apps and standard Unix process launching leads to bad code.
Still running windows 10 here, since my hardware isn't compatible with windows 11. I wouldn't mind replacing it with Linux. What Linux distros are recommended for gaming? All my games are on Steam. Dual monitor setup with game on main screen and browser on the second one.
Earlier quoted context omitted.
Install an old GPU, Connected a monitor to the extra GPU, connect mouse and keyboard, Use the loginctl command to list available devices/usb ports and attach them to a seat. I suggest using Arch linux although loginctl should be available in all distributions using SystemD now. If you don't have enough USB ports you can use a USB hub, some monitors comes with USB hub. And some with built in sound, or you can use wire…
Sorry being IT guy I wondered about the logic. I understand the need to align. But if one fail all fail and children like customers … not the patient kind? Or you have two system within each … then across the …. Sorry cannot stop my mind spinning.
Earlier quoted context omitted.
I have been working professionally on Linux for many years. But about once a year I have to reinstall the os because it craps out for various reasons. The same story goes for most of my team, but for some reason they seem ok with this. My issue with Linux is this: I don’t feel like a consumer, but a janitor. I don’t want this. Yes you can do whatever you want, but I don’t want to do those things. I want to write code…
> janitor Perfect analogy. I'm using Debian for a few months now on my main laptop, and everything is flawed. Seriously, everything. - Hybrid graphics simply doesn't work. The exception is when it works. Don't even try Wayland with it. - Graphics card handling is still full with race conditions. It's random when everything works as intended without manual intervention. - Switching monitors is pain. Sometimes works, s…
I had to run Ubuntu 22.04 on a laptop for a while and encountered similar monitor switching and bluetooth issues. Eventually I figured out I could get the latest version of most desktop packages from the KDE Neon repos since they were also based on 22.04 at the time.
Running the latest KDE Plasma desktop with the latest mesa and pipewire made a huge difference. Monitor switching now works every time, all the bluetooth features worked, battery life improved, and Firefox stopped crashing when using webgl.
I'm not saying it'll fix all your problems, but most of these problems are being actively worked on and I think its worth trying a distro that actually keeps up with the pace of that work.
Earlier quoted context omitted.
> The best Valve could do is offer a special locked down kernel with perhaps some anticheat capabilities and lock down the hardware with attestation. That would require essentially turning it into a console or Android.
Not really. Measured boot and remote attestation are a thing. Couple with reproducible builds to address security and privacy concerns. Hardware support would inevitably be somewhat limited but that's still better than the situation with either consoles or kernel anticheat.
I can't move until the software I've invested in moves too. There are no Linux alternatives.
Earlier quoted context omitted.
It's not just Ubuntu, Arch is just as bad. The primary problem is systemd, which provided an adequate OOMd for daemons, but then all the distributions seem to be using it for interactively launched processes If anybody can help me out with a better solution with a modern distribution, that's about 75% of the reason I'm posting. But it's been a major pain and all the GitHub issues I have encountered on it show a big r…
Interesting, either I haven't run into it much or I haven't recognized the source of it when it's something I have encountered.