Occasional issue with wine64-preloader (proton-cachyos)

Issues & Assistance
1

Hi,

I frequently use this command => journalctl -p 3 -xb to make sure my system is healthy and I have noticed this error to happen randomly (doesn’t happen every time I boot the PC):

❯ journalctl -p 3 -xb
Sep 28 09:31:38 gaming systemd-coredump[1702]: [🡕] Process 1700 (wine64-preloade) of user 1000 dumped core.
                                               
                                               Stack trace of thread 1700:
                                               #0  0x00006fffe39f1026 n/a (/usr/share/steam/compatibilitytools.d/proton-cachyos/files/bin/wine64-preloader + 0x1026)
                                               ELF object binary architecture: AMD x86-64

The stack trace ain’t very useful except that it point towards proton-cachyos.

I’ve noticed it twice in the last ~8 days or so.

Let me know if I could be of any help regarding this issue.

Thank you!

2

This doesn’t seem to have an impact on useability right? I assume the core dump is produced when you stop playing a game, i.e. wine64-preloader is terminated. This should be fine unless you experience instability and breakage with proton-cachyos.

3

I’m pretty sure it happen during the boot sequence since I use the flag -b on journalctl. I didn’t launched games after noticing the error, I just reboot. I’ll try to launch a game next time. But your right, gaming session are great. I’ll just ignore these errors then. I was mainly currious because those errors happen during boot.

4

per the man page:

-b [[ID][±offset]|all], --boot[=[ID][±offset]|all]
           Show messages from a specific boot. This will add a match for "_BOOT_ID=".

           The argument may be empty, in which case logs for the current boot will be shown.