Piston-Tutorials icon indicating copy to clipboard operation
Piston-Tutorials copied to clipboard

Wayland connection unexpectedly lost

Open SrTobi opened this issue 9 years ago • 0 comments

Hi,

I get the following error when running the getting-start example (after building with no problems) and then touching the window with the spinning red rectangle with the mouse:

wl_display@1: error 1: invalid method 9 (since 3 < 4), object wl_surface@25
thread 'main' panicked at 'Wayland connection unexpectedly lost: Error { repr: Os { code: 22, message: "Invalid argument" } }', src/libcore/result.rs:799

I am on an ArchLinux. Here are my package versions regarding wayland:

local/lib32-wayland 1.12.0-1
local/wayland 1.12.0-1
local/wayland-protocols 1.7-1
local/xorg-server-xwayland 1.18.4-1 (xorg)

Here is the output after starting the application with cargo run:

[~/workspace/rustgame]$ cargo run
    Finished debug [unoptimized + debuginfo] target(s) in 0.0 secs
     Running `target/debug/rustgame`
xkbcommon: ERROR: Key "<LFSH>" added to modifier map for multiple modifiers; Using Lock, ignoring Shift

Everything works fine... I see the spinning rectangle and can close the application with ESC. A can also tab to other windows and back. But when I move the mouse over the window, the application crashes with the following output:

wl_display@1: error 1: invalid method 9 (since 3 < 4), object wl_surface@25
thread 'main' panicked at 'Wayland connection unexpectedly lost: Error { repr: Os { code: 22, message: "Invalid argument" } }', src/libcore/result.rs:799
note: Run with `RUST_BACKTRACE=1` for a backtrace.
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', src/libcore/result.rs:799
stack backtrace:
   1:     0x55e2bf80c8bf - std::sys::backtrace::tracing::imp::write::h6f1d53a70916b90d
   2:     0x55e2bf80fb5d - std::panicking::default_hook::{{closure}}::h137e876f7d3b5850
   3:     0x55e2bf80ee50 - std::panicking::default_hook::h0ac3811ec7cee78c
   4:     0x55e2bf80f458 - std::panicking::rust_panic_with_hook::hc303199e04562edf
   5:     0x55e2bf80f2f2 - std::panicking::begin_panic::h6ed03353807cf54d
   6:     0x55e2bf80f230 - std::panicking::begin_panic_fmt::hc321cece241bb2f5
   7:     0x55e2bf80f1b1 - rust_begin_unwind
   8:     0x55e2bf849e6f - core::panicking::panic_fmt::h27224b181f9f037f
   9:     0x55e2bf71ce3c - core::result::unwrap_failed::h633555c406da6a87
                        at /build/rust/src/rustc-1.13.0/src/libcore/macros.rs:29
  10:     0x55e2bf710a50 - <core::result::Result<T, E>>::unwrap::h840ed26dfa269622
                        at /build/rust/src/rustc-1.13.0/src/libcore/result.rs:737
  11:     0x55e2bf7317c4 - winit::api::wayland::context::WaylandContext::prune_dead_windows::h2d38d3a6e09b0d04
                        at /home/tobi/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.5.6/src/api/wayland/context.rs:274
  12:     0x55e2bf7373cf - <winit::api::wayland::window::Window as core::ops::Drop>::drop::hdf7929756b6f4e1e
                        at /home/tobi/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.5.6/src/api/wayland/window.rs:296
  13:     0x55e2bf668240 - drop::hdc031453f99b2105
  14:     0x55e2bf667227 - drop::h01cd2eeb44185356
  15:     0x55e2bf6681b8 - drop::hca8eda852a01406b
  16:     0x55e2bf6677f0 - drop::h52fb734eb8d14be1
  17:     0x55e2bf667468 - drop::h16f2b861534ef50b
  18:     0x55e2bf6683a0 - drop::heb76908293844c9d
  19:     0x55e2bf671598 - rustgame::main::hdb7023e4c00c99f5
                        at /home/tobi/workspace/rustgame/src/main.rs:53
  20:     0x55e2bf8174b6 - __rust_maybe_catch_panic
  21:     0x55e2bf80e6c1 - std::rt::lang_start::h538f8960e7644c80
  22:     0x55e2bf67eee3 - main
  23:     0x7f72fb698290 - __libc_start_main
  24:     0x55e2bf663299 - _start
  25:                0x0 - <unknown>
thread panicked while panicking. aborting.
[1]    6225 illegal hardware instruction (core dumped)  cargo run

SrTobi avatar Dec 24 '16 10:12 SrTobi