Code: Select all
Operating System: Fedora Linux Asahi Remix 41
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.4-400.asahi.fc41.aarch64+16k (64-bit)
Graphics Platform: Wayland
Processors: 4 × Apple Avalanche (M2), 4 × Apple Blizzard (M2)
Memory: 7.3 GiB of RAM
Graphics Processor: Apple M2
Product Name: Apple MacBook Air (15-inch, M2, 2023)
U-Boot Version: 2024.10
I'm using MBA M2 8GB model. Dual boot between Fedora 41 Asahi Linux and MacOS 15 Sequoia.
Couple of question and problem report about Korean text input and others.
box64 emulator comportability
It was working almost perfectly. Although not on par with MacOS build performance. FPS/UPS was 58,9/60.Last week? or more. After system update - I believe that include kernel + mesa - FPS/UPS became 10/30 like so. Plus, while running factorio - after loading progress done - whole Plasma desktop UI reponse is also sluggish. Like system CPU/RAM usage is hitting max. But htop shows CPU/RAM is ok. Factorio process takes approx. 12%/1.5% (CPU/MEM).
I'm wondering about factorio devs have any clue about this.
Attatched box64 ouput + config.ini + factorio-current.log (config.ini is default one. I backed up saves, mods, config then created each empty folder)
Input Method Support on Linux
Cannot input Korean in Linux. Playing in Korean translation has no problem.Should it be possible or not? Wondering my setup is not proper or it is cuerrent limitation.
MacOS Input Method support is working but...
Yes, it's working but with some glitch.- cmd + f
- Change to Korean input state
- Type some text. In this moment, last char is not showing on input box. Search is working but not include last char.
- If I change to English mode or press some key e.g. right arrow, can see last char. 'committed'
- cmd + f
- Change to Korean input state
- Type some text
- Close remote view (search state) [em]still in Korean input mode[/em].
- Press some shortcuts. e.g. 'e' -> it's working properly.
- Open another input box. e.g. 'change constant in combi.'
- When press number key, say 1, it became 'ㄱ1' not just '1'
- 'ㄱ' is 'e' equivalent key in Korean input mode. (Previously pressed while in Korean mode. So actual Korean glyph depends on what key was pressed between close/open input box).
That's all. I know box64 situation is quite niche area. But I think all CJK users have chance of meet Linux/MacOS input method problem.
Thanks for reading long boring report.
Feel free to request any log or something.
EDIT: Cannot attach screenshot. External link https://ibb.co/1dXGb09