On 05/13/2014 02:28 PM, Gunnar Hjalmarsson wrote:
On 2014-05-13 19:55, Swarup wrote:
I wasn't sure what to do with the terminal command you have given:
$ env GTK_IM_MODULE="xim" gedit
I tried pasting it into a terminal window and restarting scim, logging
out and back in-- but there was no change.
Right. It does not change the GTK_IM_MODULE variable persistently, so if
you re-login it's all reset. But if you simply start gedit with that
command and start typing, it should work.
One way to make the workaround persistent on an Ubuntu system (don't
know about Debian) is to put a wrapper in the ~/bin folder:
$ cat ~/bin/gedit
#!/bin/sh
export GTK_IM_MODULE=xim
exec /usr/bin/gedit "$@"
and make the file executable with
chmod +x ~/bin/gedit
Then, however gedit is started, the GTK_IM_MODULE will be 'xim' in the
gedit process instead of 'scim', and the backspace and delete keys will
work as expected.
I just tested this, and it works-- for about one to two minutes. That is
to say, the backspace and delete keys work; that was very exciting to
see! And everything else also works fine, as I say for one to two
minutes. Then gedit starts to lock up. There is a delay between hitting
a key and having it appear on the screen, and that delay quickly becomes
very prolonged. Then the scim typing system itself starts to not work,
giving results on the screen that differ in what seem to be erratic or
random ways from what was typed. And then the laptop fan starts to speed
up to a very high pitch, gedit freezes and has to be closed. After
closing gedit, the laptop fan immediately comes back to normal.
I tried opening gedit this way twice, and the same thing happened both
times-- this makes me think the workaround is not going to be functional.
From this I have the impression that to get a workable solution, the
bug in scim is going to need to be fixed.
Swarup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
