Ubuntu install fail

[fwedler]

Anyone know why this is happening un Ubuntu 24.04?

$ sudo ./install-linux.sh
Using adb at ./platform-tools/adb
Force a switch into the debug mode to enable ADB
adb enabled, waiting for reboot... it's alive!
waiting for atfwd_daemon to startup... done!
./rootshell: 1 file pushed, 0 skipped. 1537.9 MB/s (927624 bytes in 0.001s)
uid=0(root) gid=0(root)
we have root!
./config.toml.example: 1 file pushed, 0 skipped. 5.8 MB/s (389 bytes in 0.000s)
./rayhunter-daemon: 1 file pushed, 0 skipped. 1.6 MB/s (11619420 bytes in 6.849s)
./scripts/rayhunter_daemon: 1 file pushed, 0 skipped. 3.3 MB/s (580 bytes in 0.000s)
./scripts/misc-daemon: 1 file pushed, 0 skipped. 76.5 MB/s (2302 bytes in 0.000s)
waiting for reboot...
thread 'main' panicked at serial/src/main.rs:79:10:
Failed to read response: Timeout
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Here is the same with the backtrace enabled.

$ sudo RUST_BACKTRACE=full ./install-linux.sh
Using adb at ./platform-tools/adb
Force a switch into the debug mode to enable ADB
Device already in command mode. Doing nothing...
adb enabled, waiting for reboot... it's alive!
waiting for atfwd_daemon to startup... done!
./rootshell: 1 file pushed, 0 skipped. 2451.0 MB/s (927624 bytes in 0.000s)
uid=0(root) gid=0(root)
we have root!
./config.toml.example: 1 file pushed, 0 skipped. 3.7 MB/s (389 bytes in 0.000s)
./rayhunter-daemon: 1 file pushed, 0 skipped. 1.6 MB/s (11619420 bytes in 6.830s)
./scripts/rayhunter_daemon: 1 file pushed, 0 skipped. 10.1 MB/s (580 bytes in 0.000s)
./scripts/misc-daemon: 1 file pushed, 0 skipped. 87.6 MB/s (2302 bytes in 0.000s)
waiting for reboot...
thread 'main' panicked at serial/src/main.rs:79:10:
Failed to read response: Timeout
stack backtrace:
   0:     0x60e62c9cda8a - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::he089f96442833f67
   1:     0x60e62c9e9173 - core::fmt::write::h2f210ed4c94745cb
   2:     0x60e62c9cb443 - std::io::Write::write_fmt::h7de08171ab770fb2
   3:     0x60e62c9cd8d2 - std::sys::backtrace::BacktraceLock::print::h810fbd31421329e6
   4:     0x60e62c9ce930 - std::panicking::default_hook::{{closure}}::hbaad47ed9dc6356d
   5:     0x60e62c9ce710 - std::panicking::default_hook::h24e207139139d40a
   6:     0x60e62c9cefa2 - std::panicking::rust_panic_with_hook::ha9131beeb2ddc506
   7:     0x60e62c9cee3a - std::panicking::begin_panic_handler::{{closure}}::h1bba0eaeb6da506f
   8:     0x60e62c9cdf89 - std::sys::backtrace::__rust_end_short_backtrace::h1d1ca3eade483f4c
   9:     0x60e62c9ceacd - rust_begin_unwind
  10:     0x60e62c99f9a0 - core::panicking::panic_fmt::h896a0727a1a943f9
  11:     0x60e62c99fd46 - core::result::unwrap_failed::h1b5ed8541c7bebd6
  12:     0x60e62c9a11ee - serial::main::h5bab284546c49a33
  13:     0x60e62c9a1b53 - std::sys::backtrace::__rust_begin_short_backtrace::h6d62b7b5c10bcc0e
  14:     0x60e62c9a1b49 - std::rt::lang_start::{{closure}}::hf4a959b91339f209
  15:     0x60e62c9c8e87 - std::rt::lang_start_internal::hbb268f70c879621d
  16:     0x60e62c9a1b35 - main
  17:     0x79465722a1ca - <unknown>
  18:     0x79465722a28b - __libc_start_main
  19:     0x60e62c99ff15 - _start
  20:                0x0 - <unknown>

[wgreenberg]

the good news is, despite the panic rayhunter should now be installed -- can you confirm whether a green line appears on the top of the device's screen?

the bad news is this is a known bug with the installation process: #88

[psthi]

I had a near identical error. Install completed from current stable Linux Mint and Rayhunter active 💯.