Crash on Start / schedule_status.json is empty
An immediate crash on start, either from desktop icon or gnome-terminal. Version pika-backup 0.4.0.beta.3-1 - installed from the AUR
This issue did not occur with pika-backup 0.4.0.beta-1
Output of RUST_BACKTRACE=full:
thread 'main' panicked at 'Failed to load schedule status.: Custom { kind: UnexpectedEof, error: Error("EOF while parsing a value", line: 1, column: 0) }', src/ui.rs:93:10
stack backtrace:
0: 0x5624ffb084df - <unknown>
1: 0x5624ff7977ec - <unknown>
2: 0x5624ffad9a24 - <unknown>
3: 0x5624ffb0a8ba - <unknown>
4: 0x5624ffb0b874 - <unknown>
5: 0x5624ffb0b2e2 - <unknown>
6: 0x5624ffb0b256 - <unknown>
7: 0x5624ffb0b212 - <unknown>
8: 0x5624ff747232 - <unknown>
9: 0x5624ff747582 - <unknown>
10: 0x5624ff9973b7 - <unknown>
11: 0x7fecdd645f8f - g_closure_invoke
12: 0x7fecdd661ba8 - <unknown>
13: 0x7fecdd6635c7 - g_signal_emit_valist
14: 0x7fecdd663824 - g_signal_emit
15: 0x7fecdd763706 - g_application_register
16: 0x7fecdd764110 - <unknown>
17: 0x7fecdd76447a - g_application_run
18: 0x5624ff98507c - <unknown>
19: 0x5624ff75d343 - <unknown>
20: 0x5624ff75d6bb - <unknown>
21: 0x7fecdc8e1310 - __libc_start_call_main
22: 0x7fecdc8e13c1 - __libc_start_main@GLIBC_2.2.5
23: 0x5624ff75d255 - <unknown>
24: 0x0 - <unknown>
Edited by Sophie Herold