this post was submitted on 08 Jun 2025
13 points (67.6% liked)
Linux Gaming
18450 readers
4 users here now
Gaming on the GNU/Linux operating system.
Recommended news sources:
Related chat:
Related Communities:
Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Unless the application in question is directly interacting with systemd, then I believe this is overblown.
Applications largely simply expect certain features to be supported. DNS, for example, could be provided by systemd-resolvd or by dnscrypt-proxy.
This isn't being built around systemd, this is being built around the expectation of a feature. This feature can be provided by different applications and still function.
In my experience, providing the features expected is far more important than providing specifically the systemd API.
Hard disagree.
I think the init system is more abstracted away from the developers of a game/typical user app than you are implying.
But if it will works π€. And what can I do to do now? Remains only to have try to install some other OS.
Also I've try this instruction: https://github.com/lutris/docs/blob/master/HowToEsync.md
But this also was be helpless π€·
I would look at the proton log of a game that doesn't work.
How do I create logs of a game I run with Proton?
Proton will create a log file for a particular game, if you set the launch parameter to:
The log file will be created in your home folder with the name scheme
steam-$STEAMID.log. For example:And the end of the log:
It doesn't seems that the problem in SystemD π€. Maybe...
Take the whole log and put it a pastebin like pastebin.com. Then reply with the link.
Can I use PrivateBin instead?
https://0.jaegers.net/?56551c15509bb58b#WwJnXzAmbJfk767Ac5NDykBUJndRG6nuoMmSu6ZxU1X
Try different versions of proton. Also try changing the version of steam to the flatpak version, or to the native version if you are already using flatpak.
So... The version from Flatpak (https://flathub.org/apps/com.valvesoftware.Steam) is not official?
But, anyway, I've try to set up Steam from Flatpak... But there's absolutely the same result:
Games still don't works π€·
Try setting
PROTON_USE_WINED3D=1 %command%as the game launch options for a few different games and launch them.I've try. There's the same:
https://0.jaegers.net/?cb95e3929290b0ce#FWhb5c12TyBMfuEMT22g4wyr26iLJMmaXBQpCR2gPruD https://0.jaegers.net/?e82cb333d18780f2#E9e8uYikArBrW8stWNWEuDGaoq1WtuxZfdg71aKNaebp https://0.jaegers.net/?834b61c0ef38da87#CXQM36RtENLoTZ28F1znjChkWBhcDBG3bzHkYKhGV2dj
lspci -nnk | grep "Kernel driver in use"There's
Unverifiedlabel...Here's the begin of the log:
Ok. I've cleaned that machine, but don't install there something yet π€. I'll try...
It takes about 30 minutes...
Which is why I said:
Your OS is software.
It is a gigantic maze for a non linux pro to try to figure out all of these alternate dependencies that are needed, need to be configured, and whether or not they even play nice with each other, whether or not they won't throw you into dependency conflict hell.
Generally speaking, when a normal person, who isn't a linux expert... installs an OS... they expect that it will more or less work out of the box at a fundamental level, that it will come pre-bundled with dependencies and configurations that allow them to use the software they want to use.
Ok, two responses to that:
You ever tried gaming on a non systemd OS?
Granted, its been a few years, but I have, and its a fucking nightmare along the lines I described.... tons of insane, esoteric nonsense going wrong all over the place, that requires you to functionally develop a solid workaround schema for everything you are trying to do, that may as well qualify you as a developer of or contributor to the OS.
I don't see anyone, anywhere, recommending a non systemd linux OS for gaming.
Second response: Okey dokey, then I'm sure you'll be able to prove that by solving this person's problem for them within Devuan.
Next quote I'll explain more.
Which more has to do with just being setup incorrectly, than missing systemd.
I do. It works.
Solving a random non-systemd user's issue is irrelevant, even if we knew a lot more about their setup.
Yep, here we are in a tech support thread for some person with some issue, I have provided a solution to that issue, you are arguing that solving the person's issue is irrelevant.
Okie dokie!
... You say you've gotten gaming on a non systemd os to work.
If ... it worked with Steam... and Proton... perhaps you could suggest that OS, and whatever custom config you used, to this person?
You know, as opposed to Devuan, which is apparently set up incorrectly, out of the box, for this user?
Irrelevant to proving. Context.
See, this is how a stubborn insecure person acts.
You, just now:
You, 3 months ago:
You know exactly the problem I am describing that comes along with trying to game on a non systemd OS, because you have experienced it yourself.
You get stuck in dependency hell because all the supporting software that is required for modern gaming... is a large mismatch, by default os config, with what is actually compatible with and developed for non systemd systems, and it requires a massive amount of effort to get anything into a reasonably stable and reasonably working state.
I ask you to provide your experience directly, which could genuienly help this person, and you instead want to nitpick vocabulary in a sophomoric manner so that you can feel you are more correct by virtue of 'well, ackshually'....
...and your approach to trying to solve the problem is robotic, run through standard error output log, identify error... theorize solution...
... even though you personally know that approach will be very time consuming and frustrating.
In conclusion; boy, you must be great at parties.
I know. But I want to solve this. It will gave me some experience in Linux Administration.
Thanks... So I don't visits parties, and I don't sees any sense in this.
Sorry, but that issue had nothing to do with systemd.
But if we get a fiasco - I'll try PikaOS.