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

Panic while using conrod in Fedora 25 (using Wayland) #97

Closed
AaronM04 opened this issue Dec 5, 2016 · 8 comments
Closed

Panic while using conrod in Fedora 25 (using Wayland) #97

AaronM04 opened this issue Dec 5, 2016 · 8 comments
Labels
B - bug Dang, that shouldn't have happened DS - wayland

Comments

@AaronM04
Copy link

AaronM04 commented Dec 5, 2016

Hi, I started a conrod app while running Wayland, and the window appeared, but as soon as I moved the mouse over the window, it panicked:

$ cargo run --bin client
    Finished debug [unoptimized + debuginfo] target(s) in 0.0 secs
     Running `target/debug/client`
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:837
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:837
stack backtrace:
   1:     0x55cdf5cc0fea - std::sys::imp::backtrace::tracing::imp::write::he3d1bfbdbf113480
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:42
   2:     0x55cdf5cc51af - std::panicking::default_hook::{{closure}}::h575f1b40d2e88f07
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:247
   3:     0x55cdf5cc34c6 - std::panicking::default_hook::h3d5dccce8125d0cf
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:263
   4:     0x55cdf5cc3b77 - std::panicking::rust_panic_with_hook::h00b81bb3dcbd51f2
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:451
   5:     0x55cdf5cc3a04 - std::panicking::begin_panic::ha6a0d553db9869ff
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:413
   6:     0x55cdf5cc3929 - std::panicking::begin_panic_fmt::h24d113aee3ee4081
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:397
   7:     0x55cdf5cc38b7 - rust_begin_unwind
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:373
   8:     0x55cdf5cff73d - core::panicking::panic_fmt::he441b2ea2036b98a
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libcore/panicking.rs:69
   9:     0x55cdf5be64fe - core::result::unwrap_failed::h327f68929ca5f690
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libcore/macros.rs:29
  10:     0x55cdf5bdae80 - <core::result::Result<T, E>>::unwrap::he114e0685fd77f9f
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libcore/result.rs:737
  11:     0x55cdf5bfb538 - winit::api::wayland::context::WaylandContext::prune_dead_windows::h0043fbe011f3d42e
                        at /home/aaron/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.5.5/src/api/wayland/context.rs:274
  12:     0x55cdf5c00f3f - <winit::api::wayland::window::Window as core::ops::Drop>::drop::h609c06892476c0ad
                        at /home/aaron/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.5.5/src/api/wayland/window.rs:296
  13:     0x55cdf58f0ba0 - drop::h53d13dfd33f73a71
  14:     0x55cdf58effc7 - drop::h3731c4444e92ec7f
  15:     0x55cdf58f17f8 - drop::h7c7eb2fb5546c331
  16:     0x55cdf58f3b90 - drop::hebc6ff9f4701a924
  17:     0x55cdf58f2838 - drop::haed05670111a409f
  18:     0x55cdf58f2930 - drop::hb4156e731b1ea966
  19:     0x55cdf58f2f70 - drop::hc5482f52e0a2442b
  20:     0x55cdf5983205 - client::main::h1b9234f28a4a1eba
                        at /home/aaron/dev/rust/conway/ConWaysteTheEnemy/src/client.rs:65
  21:     0x55cdf5cccc8a - __rust_maybe_catch_panic
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libpanic_unwind/lib.rs:97
  22:     0x55cdf5cc4595 - std::rt::lang_start::h74b3afbdd8daef1c
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:332
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panic.rs:351
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/rt.rs:57
  23:     0x55cdf59a5113 - main
  24:     0x7f6a199a5400 - __libc_start_main
  25:     0x55cdf5887998 - _start
  26:                0x0 - <unknown>
thread panicked while panicking. aborting.

Is it a problem with this crate, or something else? Thanks! :)

@tomaka tomaka added DS - wayland B - bug Dang, that shouldn't have happened labels Dec 5, 2016
@tomaka
Copy link
Contributor

tomaka commented Dec 5, 2016

Cc @vberger

@elinorbgr
Copy link
Contributor

Okay, this is awfully similar to Smithay/wayland-rs#75

@elinorbgr
Copy link
Contributor

@AaronM04 I suggest we continue this on the issue on my repo wayland-client-rs.

Would you by chance have a small code reproducing the error ?

@AaronM04
Copy link
Author

AaronM04 commented Dec 5, 2016 via email

@elinorbgr
Copy link
Contributor

Doesn't panic for me.

But if it is indeed the same issue as the other bug, it's caused by some subtlety of the system libraries. Apparently some combination of mesa and gnome on fedora 25 makes something go wrong.

Are you using gnome, by chance?

@AaronM04
Copy link
Author

AaronM04 commented Dec 5, 2016 via email

@nical
Copy link

nical commented Dec 24, 2016

This was just fixed in wayland-window 0.4.3, see: Smithay/wayland-rs#75

jrmuizel pushed a commit to jrmuizel/winit that referenced this issue Mar 29, 2017
…Input, r=nox

return coordinates in MouseInput events

Return mouse coordinates in MouseInput event.
Due to this [servo issue](servo/servo#11130)

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/glutin/97)
<!-- Reviewable:end -->
jrmuizel pushed a commit to jrmuizel/winit that referenced this issue Mar 29, 2017
…ouseInput, r=paulroget

fix return coordinates in MouseInput

It is a fix of rust-windowing#97
When working on [servo/#11794](servo/servo#11794). I found the previous PR rust-windowing#97 is wrong. This PR is a fix of that and is right when testing [servo/#11794](servo/servo#11794).
Actually, we should return the mouse movement position instead of actual coordination. So the previous PR's return value is wrong.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/glutin/99)
<!-- Reviewable:end -->
@elinorbgr
Copy link
Contributor

This should have been closed long ago

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B - bug Dang, that shouldn't have happened DS - wayland
Development

No branches or pull requests

4 participants