You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No sir. I was happily surprised it lasted 1 whole day up before Gupax crashed again. The crash log didn't update, so the aforeposted crash log is what I have to offer. And thank you.
OS & Version:
e.g: GNU/Linux Debian 12 "Bookworm", Gupax v1.3.9
Bug
What is the bug?
Steps
Steps to reproduce the behavior:
Screenshots
If possible, add screenshots to help explain the bug.
Crash report
If Gupax is crashing, you may have a file here:
C:\Users\YOUR_USER_NAME\AppData\Roaming\Gupax\crash.txt
/Users/YOUR_USER_NAME/Library/Application Support/Gupax/crash.txt
/home/YOUR_USER_NAME/.local/share/gupax/crash.txt
If you do, please upload or copy-paste
crash.txt
here:`PanicInfo {
payload: Any { .. },
message: Some(
failed printing to stderr: Broken pipe (os error 32),
),
location: Location {
file: "library/std/src/io/stdio.rs",
line: 1118,
col: 9,
},
can_unwind: true,
force_no_backtrace: false,
}
info:
OS | Linux
args | ArgsOs { inner: ["./gupax"] }
commit | ab9912f
gupax | v1.3.9
p2pool | v3.10 (bundled)
xmrig | v6.21.3 (bundled)
uptime | 60968.758 seconds
stack backtrace:
0:
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16: ```
The text was updated successfully, but these errors were encountered: