Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when runing appImage #4

Open
yechielw opened this issue Dec 9, 2024 · 1 comment
Open

Error when runing appImage #4

yechielw opened this issue Dec 9, 2024 · 1 comment

Comments

@yechielw
Copy link

yechielw commented Dec 9, 2024

Hi,

I tried using the appImage veriant on linux (nixOS) and im getting the following error:

`Option::unwrap()` on a `None` value

This does not seem to be a wayland issue as I managed to reproduce it on gnome X11.

Rust backtrace:

RUST_BACKTRACE=full ./Planck_0.0.14_amd64.AppImage
Planck_0.0.14_amd64.AppImage installed in /home/yechiel/.cache/appimage-run/1b031785c82654169557e3f56bb9ec9554b2bc62c40b2f11da5040c0bfa64bb4
Db directory: /home/yechiel/.planck
Database migrated
thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-22.0.0/src/gles/egl.rs:854:88:
called `Option::unwrap()` on a `None` value
stack backtrace:
   0:     0x55a45022c8fa - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h304520fd6a30aa07
   1:     0x55a45025ba3b - core::fmt::write::hf5713710ce10ff22
   2:     0x55a450227553 - std::io::Write::write_fmt::hda708db57927dacf
   3:     0x55a45022dd82 - std::panicking::default_hook::{{closure}}::he1ad87607d0c11c5
   4:     0x55a45022d9ee - std::panicking::default_hook::h81c8cd2e7c59ee33
   5:     0x55a45022e60f - std::panicking::rust_panic_with_hook::had2118629c312a4a
   6:     0x55a45022e2c3 - std::panicking::begin_panic_handler::{{closure}}::h7fa5985d111bafa2
   7:     0x55a45022cdd9 - std::sys::backtrace::__rust_end_short_backtrace::h704d151dbefa09c5
   8:     0x55a45022df84 - rust_begin_unwind
   9:     0x55a44e5a1da3 - core::panicking::panic_fmt::h3eea515d05f7a35e
  10:     0x55a44e5a1e2c - core::panicking::panic::h102d65dbfa674afe
  11:     0x55a44e5a1d09 - core::option::unwrap_failed::hfd32652cc6017653
  12:     0x55a44f54b6d0 - <wgpu_hal::gles::egl::Instance as wgpu_hal::Instance>::init::hb8c493c80aa44338
  13:     0x55a44f4e22ba - wgpu_core::instance::Instance::new::h473d9132e0dc3e15
  14:     0x55a44f4cfa78 - wgpu_core::global::Global::new::h9f4f94066b558676
  15:     0x55a44f307059 - wgpu::Instance::new::hea3745855d85395e
  16:     0x55a44eacb099 - planck_lib::utils::linux::nvidia_workaround::hb08663b5630d9143
  17:     0x55a44eb5d938 - planck_lib::run::h4405e9f60876bd9f
  18:     0x55a44e6384dc - planck::main::h32dfb33daa06c45a
  19:     0x55a44e622823 - std::sys::backtrace::__rust_begin_short_backtrace::h9caed765d7bd5bfa
  20:     0x55a44e638d09 - std::rt::lang_start::{{closure}}::hd1ff65f939b56fec
  21:     0x55a45021ec40 - std::rt::lang_start_internal::h4d90db0530245041
  22:     0x55a44e638cd5 - main
  23:     0x7f145803127e - __libc_start_call_main
  24:     0x7f1458031339 - __libc_start_main_alias_2
  25:     0x55a44e5a2865 - _start
  26:                0x0 - <unknown>
@randogoth
Copy link

I have the same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants