-
Notifications
You must be signed in to change notification settings - Fork 892
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
Comments
Cc @vberger |
Okay, this is awfully similar to Smithay/wayland-rs#75 |
@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 ? |
I actually just shipped my laptop in for battery repairs so I can't test it anymore. Try cloning the conrod repo at https://github.com/pistondevelopers/conrod.git and running the old_demo example: `cargo run --example old_demo`
If that doesn't panic for you, I'll look in my backups for the code I used.
…On December 5, 2016 1:29:44 PM PST, Victor Berger ***@***.***> wrote:
@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 ?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#97 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
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? |
Yes, Gnome 3.22
…On December 5, 2016 2:01:05 PM PST, Victor Berger ***@***.***> wrote:
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?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#97 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
This was just fixed in wayland-window 0.4.3, see: Smithay/wayland-rs#75 |
…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 -->
…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 -->
This should have been closed long ago |
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:
Is it a problem with this crate, or something else? Thanks! :)
The text was updated successfully, but these errors were encountered: