Skip to main content

64位ubuntu下32位程序的输入法问题

我是64bit的ubuntu，有时会用到32bit的程序，如flock和qq，然后输入法就成了问题。

定义32位程序输入法加载模块的文件应该是/etc/gtk-2.0/gtk.immodules.32，默认安装情况下，里面只有scim没有scim-bridge。不过里面scim指向的模块/usr/lib32/gtk-2.0/2.10.0/immodules/im-scim.so并不存在。这样如果在程序用右键选择输入法为SCIM Input Method，会报找不到模块。

整个解决流程我参考了http://forum.ubuntu.org.cn/viewtopic.php?t=139907&start=0&postdays=0&postorder=asc&highlight

一开始我是想弄通im-scim.so，于是从源里下了32位的scim-gtk2-immodule, libscim8c2a等包，手工解压，之后虽然32位程序里能调出scim输入法了，但是没有中文输入法。在gtk.immodules.32中在scim对应行加"zh"也没用。

后来想想，我系统默认输入法是scim-bridge而不是scim，于是把目光转向了im-scim-bridge，从源里下来32位scim-gtk2-immodule，把im-scim-bridge.so放到/usr/lib32/gtk-2.0/2.10.0/immodules/，然后在/etc/gtk-2.0/gtk.immodules.32最后添加两行：

/usr/lib/gtk-2.0/2.10.0/immodules/im-scim-bridge.so"
"scim-bridge" "SCIM Bridge Input Method" "" "" ""

（链接里说的方法是用/usr/bin/gtk-query-immodules-2.0 > gtk.immodules.32，然后把/usr/lib都改成/usr/lib32，似乎是更佳的方法）

这样32位程序里就能输入中文了，之后发现把32位的scim那些文件删去也可以正常工作，因此看来只需要im-scim-bridge.so一个文件。
Labels:

Comments

Post a Comment

Popular posts from this blog

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...
3 comments
Read More »

Chasing an IO Phantom

My home server has been weird since months ago, it just becomes unresponsive occassionally. It is annoying but it happens only rarely, so normally I'd just wait or reboot it. But weeks ago I decided to get to the bottom of it. What's Wrong My system set up is: Root: SSD, LUKS + LVM + Ext4 Data: HDD, LUKS + ZFS 16GB RAM + 1GB swap Rootless dockerd The system may become unresponsive, when the IO on HDD  is persistantly high for a while. Also: Often kswapd0 has high CPU High IO on root fs (SSD) From dockerd and some containers RAM usage is high, swap usage is low It is very strange that IO on HDD can affect SSD. Note that when this happens, even stopping the IO on HDD does not always help. Usually restarting dockerd does not help, but rebooting helps. Investigation: Swap An obvious potential root cause is the swap. High CPU on kswapd0 usually means the free memory is low and the kernel is busy exchanging data between disk and swap. However, I tried the following steps, none of the...
Post a Comment
Read More »

Fix Google Security Code

Google Security Code (http://g.co/sc) is one type of 2-step verification. This is particularly useful when security keys and passkeys are not available. I have been using it in my LXC containers, until today I found out that it stopped working. It just kept saying "The code is invalid". It is easy to rule out some factors: The code works on other browsers on my laptop. The code works on other devices that are directly connected to the router. So it appears that Google also checks IP addresses besides the security code. Recently I have IPv6 enabled, so most devices that are directly connected to the router have both IPv4 and IPv6 addresses. But  I only enabled IPv4 for my LXC containers. So I guess when a code is generated by device A and used by device B, Google should be able to check that device A and device B are closely located. But in my case, IPv6 address appears on device A but not on device B, which may look suspicious. To fix the problem, I just needed to disable IPv...
Post a Comment
Read More »