bug: failed to run in Bazzite Os Fedora Silverblue

[yodatak]

Hi thanks for this nice projet

I cannot run verso because of this error

thread 'main' panicked at src/config.rs:55:24:
Can't read file: Os { code: 2, kind: NotFound, message: "No such file or directory" }
stack backtrace:
0: rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: <verso::config::ResourceReader as embedder_traits::resources::ResourceReaderMethods>::read
4: embedder_traits::resources::read_bytes
5: embedder_traits::resources::read_string
6: std::sys::sync::once::futex::Once::call
7: <servo_config::prefs::PREFS as core::ops::deref::Deref>::deref
8: verso::verso::Verso::new
9: verso::main
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.

[wusyong]

Thanks for reporting! Could you tell us how do you build it? Is it using flatpak or nix?

[yodatak]

I just use the binary release here https://web.crabnebula.cloud/verso/verso-nightly/releases
Maybe i have to try with flatpak version instead ?

[dannymate]

Can confirm the nightly release build binary causes that error. Also on Bazzite. The archive only has the binary file.

[wusyong]

We are currently moving to more stable sandbox toolings and have updated README.md . However, I'm still working on #99, so the nightly release hasn't been fixed yet. I'll let you know once it's ready.

[barolo]

Same error on Gentoo.

[wusyong]

We just updated the CI in #110
Could you test if the new flatpak bundle works.
You can install in via flatpak install

[barolo]

We just updated the CI in #110 Could you test if the new flatpak bundle works. You can install in via flatpak install

It launches successfully now. Although fails spectacularly after.
Had to take photo because I couldn't screenshot inside of the frame for some reason.
I don't expect it to work at this point just FYI ;)

It's a Wayland session (KDE/Plasma 6)

[wusyong]

Thanks! I'm updating the view spawning order in #109.
I'll close this issue since it can open the window at least.
I can open follow-up issue if the it still happens after #109.