Error Code 256 on every Game

Monokel777 · April 17, 2022, 10:45pm

Hey there,

every game I qould like to start crashes with error code 256.
I’m a bit nooby with linux, so please tell me, what logs do you need and where I could find them. first I would like to provide you the following information:

one time, lutris works and I played GTAV, BattleFieldV and LoL.
after a long time I would like to play BF5
|__> Error for fsync could not load … something with kernel.
Updated the Kernel from 5.13 to 5.15
|__> Got the error 256

2022-04-18 00:33:33,075: No folder at /home/jp/.local/share/lutris/runners/retroarch/
2022-04-18 00:33:33,115: Running AMD Mesa driver 22.0.1 on AMD Radeon RX 6900 XT (sienna_cichlid, LLVM 13.0.0, DRM 3.42, 5.15.34-051534-generic) (0x73bf)
2022-04-18 00:33:33,115: GPU: 1002:73BF 1002:0E3A (amdgpu drivers)
skipping config: /usr/bin/MangoHud.conf [ not found ]
skipping config: /home/jp/.config/MangoHud/python3.9.conf [ not found ]
parsing config: /home/jp/.config/MangoHud/MangoHud.conf [ ok ]
2022-04-18 00:33:33,283: Startup complete
2022-04-18 00:33:35,770: Unable to load libGLX_nvidia.so.0
2022-04-18 00:33:35,770: Unable to locate libGLX_nvidia
Started initial process 4731 from mangohud /home/jp/.local/share/lutris/runners/wine/lutris-fshack-7.1-x86_64/bin/wine /home/jp/Games/battlefield-v/drive_c/Program Files (x86)/Origin/Origin.exe
Start monitoring process.
ERROR: ld.so: object 'libMangoHud_dlsym.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libMangoHud.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libMangoHud_dlsym.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libMangoHud.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
can't get dlopen()
Monitored process exited.
Initial process has exited (return code: 256)
All processes have quit
Exit with return code 256
2022-04-18 00:33:37,839: Game still running (state: running)
2022-04-18 00:33:37,839: Stopping Battlefield V (wine)
2022-04-18 00:33:37,840: The game has run for a very short time, did it crash?

So I did:

reinstalled Mesa-driver
installed WineHQ
reinstalled one Game (LoL)
reinstalled Lutris

I hope you could help me, I qil provide you any information you would like to have.
Many thanks!

[System]
OS:              Ubuntu 21.10 impish
Arch:            x86_64
Kernel:          5.15.34-051534-generic
Desktop:         KDE
Display Server:  x11

[CPU]
Vendor:          AuthenticAMD
Model:           AMD Ryzen 7 2700X Eight-Core Processor
Physical cores:  8
Logical cores:   16

[Memory]
RAM:             15.6 GB
Swap:            2.0 GB

[Graphics]
Vendor:          AMD
OpenGL Renderer: AMD Radeon RX 6900 XT (sienna_cichlid, LLVM 13.0.0, DRM 3.42, 5.15.34-051534-generic)
OpenGL Version:  4.6 (Compatibility Profile) Mesa 22.0.1 - kisak-mesa PPA
OpenGL Core:     4.6 (Core Profile) Mesa 22.0.1 - kisak-mesa PPA
OpenGL ES:       OpenGL ES 3.2 Mesa 22.0.1 - kisak-mesa PPA
Vulkan:          Supported

EDIT:

I should also let you know, that I tried to manipulate some settings like DXVK on/off or VKD3D on/off etc.
And Iḿ jusing fshack 7.2x86_64. (could I may reinstall this?)

Iḿ able to play games on Steam-launcher with proton!

LAST EDIT:

I tried to get back to 5,13 and started BF5. got the FSync-Error. Than I deactivated FSync (Error is gone) but Error 256 appeard again.
You guys should know, I’m on a LAN-Party in a week and I really really hope you could help me.

Autolycus · April 18, 2022, 7:46pm

Your post jogged a faint memory of a bug I remember seeing mentioned in the latest Manjaro patch notes. I haven’t looked into it, but perhaps it’s this bug with MangoHud?

owohnzimmer · April 18, 2022, 9:38pm

I searched for this and found the following link:

github.com/flightlessmango/MangoHud

MangoHud Currently Breaks 100% of Wine and Proton Applications (at least on Nvidia)

opened 09:59PM - 05 Mar 22 UTC

closed 09:20PM - 19 Mar 22 UTC

gardotd426

I can't test on AMD so I can't confirm whether or not this is universal, but I h…ave confirmed that this is universal on my machine, in every game I tested, on both Steam+Proton and Lutris+Wine. It started when I saw [this post on reddit](https://www.reddit.com/r/linux_gaming/comments/t63baf/lutris_sigsegv_error_and_protonwine_games_not/), where a user was claiming that native games were all working fine, but that all Wine and Proton games were refusing to launch, and they were on Arch+Nvidia+Plasma, as am I. I started to comment that I hadn't encountered that issue, because I had launched games in the 24 hours prior without issue. But I hadn't updated in a couple days, so I decided to run an update and reboot before commenting. Well, after rebooting, I noticed that I had the same problem. I wasn't getting the SIGSEV errors, but every single Windows game I tried to launch failed to actually open. `ps -ef | egrep -i ".exe|wine"` and similar commands would show that the game process would be running, along with all wine processes you would expect, but no window would show up (and no sound would play either). I would have to kill everything and try again, but no luck. I tried about 12 games, all games that I had launched in the last week with no issue. I tried both Lutris and Steam games, using a dozen or more different Wine and Proton builds (including wine tkg and ge, proton tkg and ge, and proton official builds). None of them worked. I tried several native games, all launched instantly. So I decided to launch a graphical program that wasn't a game, I chose Cinebench. It launched right away. So it wasn't a wine problem. The only difference between Cinebench and all the games was that I didn't have MangoHud enabled on Cinebench. I tried to run it with Cinebench, and got the same result as I got with the games. Cinebench would *run*, but it wouldn't actually open. The terminal output gave the following errors: ``` 0080:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet 0080:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet 0080:fixme:unwind:execute_cfa_instructions 7f6f2e0de469: unknown CFA opcode 2e 0080:fixme:unwind:execute_cfa_instructions 7f6f2e0de469: unknown CFA opcode 20 0080:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet 0080:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet 0080:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet 0080:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet 0080:fixme:unwind:execute_cfa_instructions 7f6f2e0de469: unknown CFA opcode 2e 0080:fixme:unwind:execute_cfa_instructions 7f6f2e0de469: unknown CFA opcode 20 0080:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet 0080:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet ``` None of these were present running Cinebench without MangoHud. So, I disabled MangoHud in Doom Eternal, and it launched immediately. I disabled it in Borderlands 3, and it launched immediately. I repeated the process with several Steam Proton games, and all worked without MangoHud, and failed with MangoHud. So then I moved to Lutris, and disabled MangoHud. Cyberpunk 2077 launched immediately. Control Ultimate Edition launched immediately. I uninstalled MangoHud completely, and now all Wine and Proton games run without issue. The weird thing, though, is that there had been no Nvidia driver update, no kernel update, and no MangoHud update (I was using the -git packages from chaotic-aur). There were some Plasma and X11 updates, but as far as anything display or rendering related, that was it. I tried using the non-git MangoHud packages from the AUR, to no avail. I tried building from source with the latest master code, and still all Wine/Proton games were broken. I explained my findings to the OP of the reddit post, and they thanked me and said that they too had MangoHud enabled on all the games that wouldn't launch, so it seemed to be the same problem. I don't know what else to add, but I can confirm that at least on Plasma+Nvidia+Arch, MangoHud breaks 100% of Windows games, regardless of Wine or Proton version. Those errors I got from Cinebench were the only messages out of the ordinary. Some games wouldn't even show those, they would just hang on the lines where MangoHud says it's parsing config files. I have GNOME installed on my daily driver rig as well, so I can test there to see if the issue persists (oh yeah, just to clarify, all this is with X11, no Wayland involved). You know I'm more than willing to help however I can in getting this fixed. MangoHud is one of the crown jewels of Linux gaming and you know I've been happy to go above and beyond to test and log and try and bisect whatever I have to. Last time with Doom Eternal crashing I was able to bisect before filing the bug report, but since there hadn't been any MangoHud updates between games working and breaking, I don't think it is a MangoHud regression. If you have anything you want me to test, let me know and I'll report back. I'll also try to keep investigating and if I find any more interesting information, I'll gladly add it here.

so yeah, it might be the mangohud, please disable it when trying to run this game and see what happens.