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.

Sign up for GitHub

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

Jump to bottom

UnexpectedNull("XOpenIM") on winit 0.30.8 #4082

Closed
koute opened this issue Jan 14, 2025 · 0 comments · Fixed by #4108
Closed

UnexpectedNull("XOpenIM") on winit 0.30.8 #4082

koute opened this issue Jan 14, 2025 · 0 comments · Fixed by #4108
Labels
B - bug Dang, that shouldn't have happened DS - x11

Comments

@koute
Copy link

koute commented Jan 14, 2025

Description

winit 0.30.8 seems to be broken on my system, failing with the following error (it reproduces with the simple example copy-pasted from the toplevel page of crate docs):

called `Result::unwrap()` on an `Err` value: OsError { line: 533, file: "~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/winit-0.30.8/src/platform_impl/linux/x11/window.rs", error: XError(UnexpectedNull("XOpenIM")) }

If I pin winit to 0.30.7 then it works properly.

This is the culprit; if I revert that commit then it works properly again.

OS and window mananger

Arch Linux, StumpWM, using uim as my IME

Winit version

0.30.8
@koute koute added B - bug Dang, that shouldn't have happened DS - x11 labels Jan 14, 2025
@fredizzimo fredizzimo mentioned this issue Jan 16, 2025
Merged
kchibisov added a commit to kchibisov/winit that referenced this issue Jan 31, 2025
@kchibisov
x11: fix crash with uim
8e3a924 
Let's just not forward events to the IME once the user requested that
it should be disabled, though, still try to change its state explicitly.

Fixes rust-windowing#4082.
@kchibisov kchibisov mentioned this issue Feb 2, 2025
Merged
kchibisov added a commit that referenced this issue Feb 3, 2025
@kchibisov
x11: fix crash with uim
a6998af 
Let's just not forward events to the IME once the user requested that
it should be disabled, though, still try to change its state explicitly.

Fixes #4082.
kchibisov added a commit to kchibisov/winit that referenced this issue Feb 5, 2025
@kchibisov
x11: fix crash with uim
3912577 
Let's just not forward events to the IME once the user requested that
it should be disabled, though, still try to change its state explicitly.

Fixes rust-windowing#4082.
kchibisov added a commit to kchibisov/winit that referenced this issue Feb 6, 2025
@kchibisov
x11: fix crash with uim
e81cc6c 
Let's just not forward events to the IME once the user requested that
it should be disabled, though, still try to change its state explicitly.

Fixes rust-windowing#4082.
kchibisov added a commit that referenced this issue Feb 6, 2025
@kchibisov
x11: fix crash with uim
b77ea7d 
Let's just not forward events to the IME once the user requested that
it should be disabled, though, still try to change its state explicitly.

Fixes #4082.
richerfu pushed a commit to richerfu/winit that referenced this issue Feb 7, 2025
@kchibisov @richerfu
x11: fix crash with uim
a48fb43 
Let's just not forward events to the IME once the user requested that
it should be disabled, though, still try to change its state explicitly.

Fixes rust-windowing#4082.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
B - bug Dang, that shouldn't have happened DS - x11
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

x11: fix crash with uim kchibisov/winit
1 participant
@koute