-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Description
Service seems to be hit or miss if it applies.
One possible cause I've seen is that setting the client to Beta will often forget that it's Beta and start redownloading updates every couple or so boots.
I'm assuming it's doing the "update" whenever steam-patcher tries to run and thus can't find the files it needs.
Maybe some detection for if Steam is in the middle of an update?
× steam-patch.service - Steam Patches Loader
Loaded: loaded (/etc/systemd/system/steam-patch.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: core-dump) since Thu 2023-08-10 17:52:50 EDT; 6min ago
Duration: 15min 52.843s
Main PID: 1223 (code=dumped, signal=ABRT)
CPU: 651ms
Aug 10 17:51:59 nobara-pc steam-patch[1223]: Show QAM
Aug 10 17:51:59 nobara-pc steam-patch[1223]: Show Menu
Aug 10 17:51:59 nobara-pc steam-patch[1223]: Show QAM
Aug 10 17:52:10 nobara-pc steam-patch[1223]: Steam unpatched
Aug 10 17:52:12 nobara-pc steam-patch[1223]: Steam patched
Aug 10 17:52:49 nobara-pc steam-patch[1223]: Steam unpatched
Aug 10 17:52:50 nobara-pc steam-patch[1223]: thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/steam.rs:198:78
Aug 10 17:52:50 nobara-pc steam-patch[1223]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aug 10 17:52:50 nobara-pc systemd[1]: steam-patch.service: Main process exited, code=dumped, status=6/ABRT
Aug 10 17:52:50 nobara-pc systemd[1]: steam-patch.service: Failed with result 'core-dump'.
Metadata
Metadata
Assignees
Labels
No labels