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

X11_BACKEND.lock() fails #3870

Closed
L3P3 opened this issue Aug 15, 2024 · 0 comments · Fixed by #3885
Closed

X11_BACKEND.lock() fails #3870

L3P3 opened this issue Aug 15, 2024 · 0 comments · Fixed by #3885
Labels
B - bug Dang, that shouldn't have happened DS - x11

Comments

@L3P3
Copy link

L3P3 commented Aug 15, 2024

Description

When I try to run the last version of lapce, I get:

thread main panicked at <unknown> | file://.//usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/floem-winit-0.29.4/src/platform_impl/linux/mod.rs:787:62
   0: lapce_app::app::logging::panic_hook::{{closure}}
   1: std::panicking::rust_panic_with_hook
   2: std::panicking::begin_panic_handler::{{closure}}
   3: std::sys_common::backtrace::__rust_end_short_backtrace
   4: rust_begin_unwind
   5: core::panicking::panic_fmt
   6: core::result::unwrap_failed
   7: floem_winit::platform_impl::platform::EventLoop<T>::new
   8: lapce_app::app::launch
   9: std::sys_common::backtrace::__rust_begin_short_backtrace
  10: main
  11: <unknown>
  12: __libc_start_main
  13: _start

The unwrap in question is that one behind X11_BACKEND.lock(). Any idea why this happens?

OS and window mananger

Debian testing i386/qemu, mate desktop, x11

Winit version

0.29.4

@L3P3 L3P3 added B - bug Dang, that shouldn't have happened DS - x11 labels Aug 15, 2024
notgull added a commit that referenced this issue Aug 22, 2024
A panic doesn't really put any of the fields in XConnection into an invalid
state, so there is no real reason to panic when poisoning is detected.
So just ignore the poison.

Closes #3870

Signed-off-by: John Nunley <[email protected]>
raphamorim pushed a commit to raphamorim/winit that referenced this issue Aug 24, 2024
A panic doesn't really put any of the fields in XConnection into an invalid
state, so there is no real reason to panic when poisoning is detected.
So just ignore the poison.

Closes rust-windowing#3870

Signed-off-by: John Nunley <[email protected]>
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 - x11
Development

Successfully merging a pull request may close this issue.

1 participant