Airshipper panics with interrupted system call in winit when quitting Veloren
Describe the bug
When quitting Veloren after it has been launched through Airshipper, Airshipper panics. My airshipper has been built from source (commit db1bf950) on Linux Mint Debian Edition 4 because the executable from https://github.com/veloren/airshipper/releases/latest/download/airshipper-linux.tar.gz did not work on my machine.
The specific issue I get is:
[ERROR] Airshipper panicked:
called `Result::unwrap()` on an `Err` value: Os { code: 4, kind: Interrupted, message: "Interrupted system call" }: panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 4, kind: Interrupted, message: "Interrupted system call" }', /home/mint/.cargo/git/checkouts/winit-57d3141eaf559308/fea65a7/src/platform_impl/linux/x11/mod.rs:360:54
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 4, kind: Interrupted, message: "Interrupted system call" }', /home/mint/.cargo/git/checkouts/winit-57d3141eaf559308/fea65a7/src/platform_impl/linux/x11/mod.rs:360:54
To Reproduce
- Check out Airshipper from commit db1bf950 and run
cargo build --release
in the repository root (I needed to first install libxkbcommon-dev on my OS) - Run airshipper by running
RUST_BACKTRACE=full cargo run --release
in the repository root - When the Airshipper window launches, wait for the Play button in the lower right to become available
- Click it to launch Veloren
- After Veloren launches, wait 10 seconds without doing anything
- Click on the Quit button on the Veloren main menu
- Observe crash in Airshipper
Expected behavior
Veloren exits and Airshipper does not exit when I press the Quit button in the Veloren main menu.
Desktop
- OS: Linux Mint Debian Edition 4
- GPU: NVIDIA GM107 [GeForce GTX 750 Ti]
- Driver: nvidia version 450.66
Additional context
The bug does not reliably occur every time I follow the steps. It occurs about 50% of the time. I have two monitors. When Veloren launches, it runs as full screen on one monitor. I think the bug is more likely to occur when I click on a window that is present on another monitor during the ten seconds in step 5 or when I wait a longer amount of time.
More computer specs: inxi is output of inxi -F
stdout and stderr from RUST_BACKTRACE=full cargo run --release
: stdout_+_stderr