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! π
this post was submitted on 08 Jun 2025
2 points (100.0% liked)
Linux Gaming
18788 readers
8 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
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.log
And 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.
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:
chdir "/mnt/Games/Steam/steamapps/common/Super Blue Boy Planet"
Game Recording - would start recording game 560260, but recording for this game is disabled
Adding process 1300 for gameID 560260
ERROR: ld.so: object '/home/user/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/user/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
WARNING: discarding _NET_WM_PID 2416 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 2419 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 2731 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 3245 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 12018 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
Adding process 1301 for gameID 560260
Adding process 1302 for gameID 560260
Adding process 1390 for gameID 560260
Proton: Upgrading prefix from None to 8.0-103 (/mnt/Games/Steam/steamapps/compatdata/560260/)
Adding process 1391 for gameID 560260
Adding process 1392 for gameID 560260
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Adding process 1393 for gameID 560260
Adding process 1396 for gameID 560260
Adding process 1398 for gameID 560260
Adding process 1401 for gameID 560260
Adding process 1410 for gameID 560260
Adding process 1423 for gameID 560260
Adding process 1429 for gameID 560260
Adding process 1442 for gameID 560260
Setting breakpad minidump AppID = 560260
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198248711762 [API loaded no]
Adding process 1461 for gameID 560260
pid 1394 != 1393, skipping destruction (fork without exec?)
Game Recording - game stopped [gameid=560260]
Removing process 1461 for gameID 560260
Removing process 1442 for gameID 560260
Removing process 1429 for gameID 560260
Removing process 1423 for gameID 560260
Removing process 1410 for gameID 560260
Removing process 1401 for gameID 560260
Removing process 1398 for gameID 560260
Removing process 1396 for gameID 560260
Removing process 1393 for gameID 560260
Removing process 1392 for gameID 560260
Removing process 1391 for gameID 560260
Removing process 1390 for gameID 560260
Removing process 1302 for gameID 560260
Removing process 1301 for gameID 560260
Removing process 1300 for gameID 560260
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.
- What graphics card are you using?
- What is the output of
lspci -nnk | grep "Kernel driver in use" - What desktop environment?
- What filesystems for your root drive and mounted drive?
- Is your mounted drive able to be read, written to, and have programs run on it by your regular user account?
What graphics card are you using?
I'll tell you below.
What is the output of lspci -nnk | grep "Kernel driver in use"
Here's the output:
Kernel driver in use: qxl
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: pcieport
Kernel driver in use: lpc_ich
Kernel driver in use: ahci
Kernel driver in use: i801_smbus
Kernel driver in use: snd_intel8x0
Kernel driver in use: virtio-pci
Kernel driver in use: xhci_hcd
Kernel driver in use: virtio-pci
Kernel driver in use: virtio-pci
Kernel driver in use: virtio-pci
Kernel driver in use: virtio-pci
Kernel driver in use: virtio-pci
Kernel driver in use: virtio-pci
What desktop environment?
What filesystems for your root drive and mounted drive?
ext4.
Is your mounted drive able to be read, written to, and have programs run on it by your regular user account?
Yes. It can. I've check it firstly.
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 you! π