You must log in or register to comment.
I created another one post about this theme: https://lemmings.world/post/28646761
And who knows, maybe it can solve this problem.
I think that this post can be closed.
Thanks to everyone! 😉
What games? Which Steam Proton and Wine-GE versions do we talk about?
BTW there is also a Proton GE and you can use it in Steam as well. Just saying. Some games do need a specific Steam Proton version, either an older or newer one, such as Proton Experimental. Some games are only working with Proton GE (or Wine GE).
And you can always lookup if the game works, by looking into reports from Protondb website (user generated).
Proton 8.0-5andWine-GE 8-26.Probably not the issue, but is there a reason you’re using such an old version of proton? Proton 10 is available in beta and proton 9 has been a smooth experience for most.
Now I’ve try Proton-GE 9-27 that I installed by ProtonUp-Qt. But it also gave me the same 😟
Are you recieving any error messages? Do you have logging enabled? (If you add “PROTON_LOG=1 %command%” to your launch options you can enable logging, they’re stored in /var/log/ and will be called [steamid].log
Enabling logging can tell you WHY things are breaking.
My personal theory, because it seems to happen a lot, is the libraries that should be linked automatically aren’t loading and proton doesn’t know where to find them, it happens sometimes!
If that’s the case, your log files will point to the missing libraries, install them or find them burried in your system and copy them to your game directory.
But for example I’ve try to launch a game through Steam Proton 8.0-5 via Steam from Flatpak now. How can I find here required libraries?
https://0.jaegers.net/?ae1611da37b8a25e#EFiVE6PGNBi4guHKZ56UKaWoGVoiZrf2GtsCDphEv95e
OHH you’re using flatpak!
Have you configured flatseal to allow steam access to your “/usr/lib/*”?
I didn’t notice any libraries failing to pull but you should give steam access there anyway to help get your Linux native games running easier. Allowing steam access outside its own container should fix most issues, but it doesn’t look like it will fix this one.
Additionally, I noticed issues with msaa happening, are you using an Nvidia GPU by chance? If so, I recommend Opening the Nvidia x-config app and overriding antialiasing and forcing 4x or 8x fxaa instead of msaa. Msaa is borked on Nvidia, renders basically any game using it unplayable.
Took me weeks to get Cities Skylines 2 working until I stumbled upon that accidentally.
Have you configured flatseal to allow steam access to your “/usr/lib/*”?
Yeap!
flatpak override --user --filesystem=/mnt/Games/Steam/ com.valvesoftware.Steam
The problem is almost certainly your OS.
Devuan does not use systemd, it uses … sysvinit, or OpenRC, or runnit.
Basically the entire linux ecosystem is built around and on top of systemd… other init based OSs that try to run most linux software… will encounter many absurd and esoteric problems, all of which ultimately stem from the fact that the vast majority of linux software is developed with systemd as the default, assumed, init system.
Basically, any Linux OS that doesn’t use systemd should be considered entirely experimental, beyond any software that the OS devs explicitly state they support.
Some non-systemd OS developers will dedicate time to either forking or patching certain, specific, existing software or libraries to be compatible with all the init systems their OS supports, but realistically, given the niche nature of such OSs and their small dev teams, they are always going to be months to years behind the current support level for systemd based OSs.
You could attempt to fix this specific issue you are having, but it would likely require you to essentially become an OS developer.
It would be vastly easier to simply switch from Devuan over to standard Debian, which runs Steam and Proton and such pretty much just fine.
…will encounter many absurd and esoteric problems, all of which ultimately stem from the fact that the vast majority of linux software is developed with systemd as the default, assumed, init system.
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.
Basically, any Linux OS that doesn’t use systemd should be considered entirely experimental, beyond any software that the OS devs explicitly state they support.
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:
PROTON_LOG=1 %command%The log file will be created in your home folder with the name scheme
steam-$STEAMID.log. For example:$HOME/steam-379720.logAnd the end of the log:
Modules: Module Address Debug info Name (23 modules) PE 00400000-00a8a000 Export megaserval PE 7b000000-7b2a0000 Deferred kernelbase PE 7b600000-7b65f000 Deferred kernel32 PE 7bc00000-7bcaa000 Export ntdll ELF 7d000000-7d005000 Deferred <wine-loader> ELF 7e9ff000-7eb86000 Export libwine.so.1 ELF f62ea000-f63d7000 Deferred ntdll.so ELF f78e7000-f78f6000 Deferred libmd.so.0 ELF f78f6000-f790d000 Deferred libbsd.so.0 ELF f790d000-f7914000 Deferred libxdmcp.so.6 ELF f7914000-f7919000 Deferred libxau.so.6 ELF f7919000-f7947000 Deferred libxcb.so.1 ELF f7947000-f7a99000 Deferred libx11.so.6 ELF f7a99000-f7ad5000 Deferred libglx.so.0 ELF f7ad5000-f7b51000 Deferred libgldispatch.so.0 ELF f7b51000-f7c56000 Deferred libm.so.6 ELF f7c58000-f7cc4000 Deferred libgl.so.1 ELF f7cc4000-f7cc9000 Deferred librt.so.1 ELF f7cc9000-f7ef1000 Deferred libc.so.6 ELF f7ef1000-f7ef6000 Deferred libdl.so.2 ELF f7ef6000-f7efb000 Deferred libpthread.so.0 ELF f7f07000-f7f99000 Deferred gameoverlayrenderer.so ELF f7f9b000-f7fd0000 Deferred ld-linux.so.2 Threads: process tid prio name (all IDs are in hex) 00000020 steam.exe 00000024 0 00000118 0 00000130 0 00000030 services.exe 00000034 0 00000038 0 wine_rpcrt4_server 00000044 0 wine_rpcrt4_io 00000048 0 wine_threadpool_worker 00000068 0 wine_rpcrt4_io 00000074 0 wine_rpcrt4_io 00000098 0 wine_rpcrt4_io 000000b0 0 wine_rpcrt4_io 000000c4 0 000000e4 0 wine_rpcrt4_io 000000e8 0 wine_threadpool_worker 0000003c winedevice.exe 00000040 0 0000004c 0 00000050 0 wine_sechost_service 00000054 0 00000058 0 0000005c 0 000000bc 0 000000c0 0 00000060 winedevice.exe 00000064 0 0000006c 0 00000070 0 wine_sechost_service 00000078 0 0000007c 0 00000080 0 00000084 0 0000008c 0 00000090 plugplay.exe 00000094 0 0000009c 0 000000a0 0 wine_sechost_service 000000a4 0 wine_rpcrt4_server 000000a8 svchost.exe 000000ac 0 000000b4 0 000000b8 0 wine_sechost_service 000000c8 explorer.exe 000000cc 0 000000d0 0 000000d4 0 wine_rpcrt4_server 000000dc rpcss.exe 000000e0 0 000000ec 0 000000f0 0 wine_sechost_service 000000f4 0 wine_rpcrt4_server 000000f8 0 wine_rpcrt4_server 000000fc 0 wine_rpcrt4_io 00000100 0 wine_threadpool_worker 00000104 tabtip.exe 00000108 0 00000110 0 wine_rpcrt4_server 00000114 0 0000011c 0 00000128 (D) Z:\mnt\Games\Steam\steamapps\common\Mega Serval\megaServal.exe 0000012c 0 <== 00000144 0 0000013c conhost.exe 00000140 0 System information: Wine build: wine-8.0 Platform: i386 (WOW64) Version: Windows 10 Host system: Linux Host version: 6.1.0-35-amd64 1057.067:0030:0148:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker" 1057.067:0030:014c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker" 1057.068:0030:0150:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker" pid 15809 != 15808, skipping destruction (fork without exec?)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.
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.
