FS#69534 - [uim] Missing fonts causes uim-xim to crash

Attached to Project: Arch Linux
Opened by RangHo Lee (rangho) - Thursday, 04 February 2021, 10:52 GMT
Last edited by Jelle van der Waa (jelly) - Tuesday, 25 July 2023, 06:52 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

There are certain X fonts that are hardcoded in uim when initializing a XIM bridge. Without these fonts, uim is unable to create font set, ultimately leading to segfault. These fonts can be found in extra/xorg-fonts-misc package.

I am fully aware that this is an upstream issue, but as there is a solution(workaround) available in the Arch repository, I think we should add that package (xorg-fonts-misc) as a dependency for this package -- at least as an optional one.

Additional info:
* package version(s): currently 1.8.8-5, but this bug has been around for quite a while
* config and/or log files etc.
* Relevant upstream issue: https://github.com/uim/uim/issues/156
* Related issue: https://github.com/rust-windowing/winit/issues/1813

Steps to reproduce:
1. Install uim.
2. Apply my uim configuration available at https://github.com/RangHo/dotfiles/tree/c23087b16fb17d74fa8e81654de3e41e73979f06/uim
3. Make sure uim-xim is running somewhere and XMODIFIERS environment variable is set to @im=uim
4. Start Alacritty or any X window powered by winit library (it is known to hang when uim-xim segfaults)
5. Press Shift+Space to enter "Hangul mode", and try typing any character
6. uim-xim should have segfaulted and Alacritty window should be unresponsive to any input
This task depends upon

Closed by  Jelle van der Waa (jelly)
Tuesday, 25 July 2023, 06:52 GMT
Reason for closing:  Deferred
Additional comments about closing:  Package was dropped to the AUR

Loading...