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一个文件。

Comments

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...

GameConqueror 0.09 -- Linux Game Hacking Tool

If you are a game hacker If you've been looking for a `CheatEngine for Linux` Then you can't miss this. ============================================== GameConqueror is a game hacking tool for linux, it's written in PyGTK and uses scanmem as its backend. It's supposed to be with most useful features of CheatEngine for Linux. Currently, I've implemented almost everything about scanning, involving variant data types and scan types: Data Types: int{8/16/32/64}, float{32/64}, unknown type(int or float) and unknown width(will try each of them), byte array and string Scan Types: equal, greater, less, changed, unchanged, increased(by), decreased(by) This should be enough for most cases, so I decided to release it at the current status. ============================================= Here's how you can get it PPA (for Ubuntu users) https://launchpad.net/~coolwanglu/+archive/scanmem (I've not test it in 32bit environments or Jaunty, do please inform me if it doe...

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...