Crash on launch: “Error in Surface::configure: parent device is lost”

Version v1.0.2 for Linux, downloaded from the website, extracted and ran directly (using Linux Fedora Linux 37 KDE) The crash report:

name = 'Hyperspeedcube'
operating_system = 'unix:Unknown'
crate_version = '1.0.2'
explanation = '''
Panic occurred in file '/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.13.1/src/backend/direct.rs' at line 281
'''
cause = 'Error in Surface::configure: parent device is lost'
method = 'Panic'
backtrace = '''

   0: 0x556239780949 - wgpu::backend::direct::Context::handle_error_fatal::h3b5e2cc268bd7d09
   1: 0x556239781663 - <wgpu::backend::direct::Context as wgpu::Context>::surface_configure::h18c1a85f680b04e9
   2: 0x5562392563f5 - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h22a4bc87f0c383e1
   3: 0x556239418bfb - pollster::block_on::h13997f0d11e9fe56
   4: 0x55623922e1fb - hyperspeedcube::main::h11e4eaabd6ff8448
   5: 0x5562393d4363 - std::sys_common::backtrace::__rust_begin_short_backtrace::h2e626bdd61a55e10
   6: 0x55623921a419 - std::rt::lang_start::{{closure}}::h1ee27baed795d130
   7: 0x556239c28f2b - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h072eb4cd8da964ba
                at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:286
                 - std::panicking::try::do_call::h8eca204fe9266946
                at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:483
                 - std::panicking::try::h12574e1b7b2cbacb
                at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:447
                 - std::panic::catch_unwind::hf71522d4448329d6
                at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panic.rs:137
                 - std::rt::lang_start_internal::{{closure}}::h65b66ac9bff580f8
                at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/rt.rs:148
                 - std::panicking::try::do_call::hfff61e33ca3db9f1
                at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:483
                 - std::panicking::try::he48c8ecead279cad
                at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:447
                 - std::panic::catch_unwind::hd510a26bfc950ccc
                at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panic.rs:137
                 - std::rt::lang_start_internal::hc680b25eab888da9
                at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/rt.rs:148
   8: 0x5562392443e5 - main
   9: 0x7fd4cdf65510 - __libc_start_call_main
  10: 0x7fd4cdf655c9 - __libc_start_main_alias_2
  11: 0x5562391e543e - _start
  12:        0x0 - <unresolved>'''

Is this fixed with v1.0.5?

Any update on this?

Closing as stale. Feel free to reopen if you're able to reproduce it with the latest version