Hi, On Tue, Jun 04, 2013 at 12:51:53AM +0800, Aron Xu wrote: > On Sun, Jun 2, 2013 at 11:15 PM, Osamu Aoki <os...@debian.org> wrote: > > Hi, > > > > > > Here, I installed fcitx to wheezy while installing 0.22-2 of im-config. > > > > I do not see the problem. > > > > $ set|grep GTK > > GTK_IM_MODULE=fcitx > > $ set|grep fcitx > > GTK_IM_MODULE=fcitx > > QT4_IM_MODULE=fcitx > > XMODIFIERS=@im=fcitx > > $ dpkg -l im-config > > Desired=Unknown/Install/Remove/Purge/Hold > > | > > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > > ||/ Name Version Architecture Description > > +++-==============-============-============-================================= > > ii im-config 0.22-2 all Input method configuration > > framew > > > > Did you restarted X session before testing? I am a bit lost.... > > > > Osamu > > Got it working after rebooting the machine, restart X seems does not > work. I'm using systemd as init, but not sure whether this can be > related.
Well, this may be. We need to restart X start-up code. Systemd may require more than re-login to get X restarted. Anyway, this confirms im-config 0.22-2 fix issues. Question is what patch to push to stable. Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
