wgpu panics in Instance::create_surface

[lost ginkgo]

Spontaneously developed, presumably after an os update. backtrace attached.
using the same flake.nix that i've always used (don't quote the one in the book to me, i wrote it!)
Also happens to bevy examples.

no clue how to test if this is a wgpu issue or a bevy issue

(ping me when replying please)

[karmic pawn]

@lost ginkgo re the libX stuff in there, is that needed if you're on wayland? Isn't those for X11?

could you try running it with WINIT_UNIX_BACKEND=wayland defined before cargo run?

think that should force Wayland if it's currently being built for support of both

[lost ginkgo]

i'm moving the mouse around and i think that ends up going through xwayland

[karmic pawn]

try removing the X11 stuff (and I think you need to set default-features = false for Bevy, as it defaults to including X11)

[lost ginkgo]

no change

after

[dependencies]
bevy = { version = "0.13", features = [
  "animation",
  "bevy_asset",
  "bevy_audio",
  "bevy_gilrs",
  "bevy_scene",
  "bevy_winit",
  "bevy_core_pipeline",
  "bevy_pbr",
  "bevy_gltf",
  "bevy_render",
  "bevy_sprite",
  "bevy_text",
  "bevy_ui",
  "multi-threaded",
  "png",
  "hdr",
  "vorbis",
#   "x11",
  "wayland",
  "bevy_gizmos",
  "android_shared_stdcxx",
  "tonemapping_luts",
  "default_font",
  "webgl2",
  "bevy_debug_stepping",
], default-features=false }

no change

based on reading the code where it unwraps i don't think it's an x11/wayland problem, i think it's, like, "I can't find Vulkan"

[lost ginkgo]

bevy main branch throws a different, potentially more helpful, error

during compile it gives this a couple times

warning: non-local `impl` definition, they should be avoided as they go against expectation
   --> crates/bevy_reflect/src/impls/std.rs:220:13
    |
220 |               impl_type_path!($ty);
    |               ^^^^^^^^^^^^^^^^^^^^
...
344 | / impl_reflect_for_atomic!(
345 | |     ::std::sync::atomic::AtomicIsize,
346 | |     ::std::sync::atomic::Ordering::SeqCst
347 | | );
    | |_- in this macro invocation
    |
    = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
    = note: the macro `impl_type_path` may come from an old version of the `bevy_reflect_derive` crate, try updating your dependency with `cargo update -p bevy_reflect_derive`
    = note: `#[warn(non_local_definitions)]` on by default
    = note: this warning originates in the macro `impl_type_path` which comes from the expansion of the macro `impl_reflect_for_atomic` (in Nightly builds, run with -Z macro-backtrace for more info)

[lost ginkgo]

doesn't do it on latest so it's probably fine

these seem actually important

tried adding mesa to the flake but it didn't do anything