SCIM: kbd stops responding

Vivia Nikolaidou

unread,

Apr 8, 2008, 7:50:30 AM4/8/08

to

Hello,

I have a dual xkb layout, switching between us intl and Greek, and on
top of this I am running SCIM to switch between xkb and Japanese. Yes,
I do need to type in all of these languages. Generally, SCIM and xkb
cooperate perfectly, apart from aMSN. The problem with aMSN is that
the keyboard eventually stops responding and all I can do is to
restart it. Having ruled out aMSN configuration issues, I can only
assume that it comes from tk.

This might even happen when I am working on another virtual desktop,
leaving aMSN on its own, but one possible trigger is to try and type
an accented character (with deadkeys) on aMSN's console. I only tried
it 5-6 times in a row, but I could perfectly reproduce the freeze.

Any ideas anyone?

Thanx a lot in advance,

Vivia Nikolaidou
(developer of aMSN)

Andreas Leitgeb

unread,

Apr 9, 2008, 4:53:24 AM4/9/08

to

Vivia Nikolaidou <n.v...@gmail.com> wrote:
> Hello,
Geia sou

> I have a dual xkb layout, switching between us intl and Greek, and on
> top of this I am running SCIM to switch between xkb and Japanese. Yes,
> I do need to type in all of these languages. Generally, SCIM and xkb
> cooperate perfectly, apart from aMSN.

Only with aMSN, or tk generally?
can you reproduce it with just:
entry .e; pack .e

I also have greek among my xkb langs, but don't use scim (since
I have no use for japanese). I can type accented greek chars
perfectly well, even the iota and upsilon with both dots and tonos.

I did see similar symptoms, before my system encoding was finally
changed to utf-8. Especially, running wish with a non-unicode
"LANG" caused lots of problems with entering non-latin chars.

> This might even happen when I am working on another virtual desktop,
> leaving aMSN on its own, but one possible trigger is to try and type
> an accented character (with deadkeys) on aMSN's console. I only tried
> it 5-6 times in a row, but I could perfectly reproduce the freeze.

How does SCIM play in there? Xrhsimopoieis to SCIM kai gia ta ellhnika
grammata?

Vivia Nikolaidou

unread,

Apr 9, 2008, 3:01:32 PM4/9/08

to

Hi and thanx for your answer! :)

On Apr 9, 11:53 am, Andreas Leitgeb <a...@gamma.logic.tuwien.ac.at>
wrote:

> Vivia Nikolaidou <n.vi...@gmail.com> wrote:
> > I have a dual xkb layout, switching between us intl and Greek, and on
> > top of this I am running SCIM to switch between xkb and Japanese. Yes,
> > I do need to type in all of these languages. Generally, SCIM and xkb
> > cooperate perfectly, apart from aMSN.
>
> Only with aMSN, or tk generally?
> can you reproduce it with just:
> entry .e; pack .e

I just left the bare wish entry there standing. The problem is, I have
no idea how to reproduce the freeze unless on the aMSN console, so I
just have to leave the entry waiting. I'll get back to you on this.

> I also have greek among my xkb langs, but don't use scim (since
> I have no use for japanese). I can type accented greek chars
> perfectly well, even the iota and upsilon with both dots and tonos.

Same here. I had no problems at all before I started using SCIM, and I
have no problems at all with SCIM unless it freezes!

> I did see similar symptoms, before my system encoding was finally
> changed to utf-8. Especially, running wish with a non-unicode
> "LANG" caused lots of problems with entering non-latin chars.

Same here. There is quite a large Greek userbase in aMSN. There is no
problem unless you start SCIM.

> > This might even happen when I am working on another virtual desktop,
> > leaving aMSN on its own, but one possible trigger is to try and type
> > an accented character (with deadkeys) on aMSN's console. I only tried
> > it 5-6 times in a row, but I could perfectly reproduce the freeze.
>
> How does SCIM play in there? Xrhsimopoieis to SCIM kai gia ta ellhnika
> grammata?

SCIM plays perfectly in all other applications that I have tried -
it's not a long list, but it includes xterm, gnome/gtk apps and kde/qt
apps. I do not use SCIM for Greek characters, I have xkb for US intl
vs Greek and SCIM for whatever xkb says vs Japanese.

Thanx a lot for your answer!

Joe English

unread,

Apr 10, 2008, 11:26:15 AM4/10/08

to

Vivia Nikolaidou wrote:
>
> I have a dual xkb layout, switching between us intl and Greek, and on
> top of this I am running SCIM to switch between xkb and Japanese. Yes,
> I do need to type in all of these languages. Generally, SCIM and xkb
> cooperate perfectly, apart from aMSN. The problem with aMSN is that
> the keyboard eventually stops responding and all I can do is to
> restart it. Having ruled out aMSN configuration issues, I can only
> assume that it comes from tk.

That's a safe assumption -- Tk still has a number of problems
with XIM that have, so far, resisted all attempts at diagnosis
and cure.

Vivia Nikolaidou

unread,

Apr 11, 2008, 5:27:09 PM4/11/08

to

Hi and thanx for your reply! :)

I'm currently in a rush so I will try 8.5.2 with ximinfo.c later on :

On Apr 10, 6:26 pm, Joe English <jengl...@flightlab.com> wrote:

> Vivia Nikolaidou wrote:
>
> > This might even happen when I am working on another virtual desktop,
> > leaving aMSN on its own, but one possible trigger is to try and type
> > an accented character (with deadkeys) on aMSN's console. I only tried
> > it 5-6 times in a row, but I could perfectly reproduce the freeze.
>
> Others have managed to work around this sort of problem
> by changing the locale; finding the right LANG= setting,
> however, is still largely guesswork.

My LANG has to be el_GR.UTF-8 , anything else will mess up my system.
I have added both el_GR.UTF-8 and en_US.UTF-8 to SCIM's
SupportedUnicodeLocales , but it didn't seem to make any difference.

This might be relevant: I have overridden the Compose for el_GR.UTF-8
with the one from en_US.UTF-8 because I need a Greek locale
environment but I also do need to type more characters than it allowed
me. This might be relevant to the issue that very often I start tk
applications and deadkeys won't work. Restarting SCIM and/or aMSN a
few times fixes this.

I'll get back to you later when I do some debugging.

Thanx again,

Vivia

Andreas Leitgeb

unread,

Apr 24, 2008, 5:16:11 AM4/24/08

to

I'm just curious: did any insight result from your tests?
Does it work now? Was there a bug in aMsn, or is it a
problem outside your or Tk's reach?

Euxaristw gia perissotera nea.

Vivia Nikolaidou <n.v...@gmail.com> wrote:
> Hi and thanx for your answer! :)
> On Apr 9, 11:53 am, Andreas Leitgeb <a...@gamma.logic.tuwien.ac.at> wrote:
>> Only with aMSN, or tk generally?
>> can you reproduce it with just:
>> entry .e; pack .e

> I just left the bare wish entry there standing. The problem is, I have
> no idea how to reproduce the freeze unless on the aMSN console, so I
> just have to leave the entry waiting. I'll get back to you on this.

...

Vivia Nikolaidou

unread,

Apr 24, 2008, 9:15:10 AM4/24/08

to

On Apr 12, 12:27 am, Vivia Nikolaidou <n.vi...@gmail.com> wrote:
> On Apr 10, 6:26 pm, Joe English <jengl...@flightlab.com> wrote:
>
> > Vivia Nikolaidou wrote:
>
> > > This might even happen when I am working on another virtual desktop,
> > > leaving aMSN on its own, but one possible trigger is to try and type
> > > an accented character (with deadkeys) on aMSN's console. I only tried
> > > it 5-6 times in a row, but I could perfectly reproduce the freeze.
>
> > Others have managed to work around this sort of problem
> > by changing the locale; finding the right LANG= setting,
> > however, is still largely guesswork.

Hi again,

Sorry it took me so long to reply. I've just been extremely busy
lately. Anyway, I think the problem is fixed now! I just had to add
this line:

/DefaultConfigModule = kconfig

to .scim/global . It works perfectly so far!

I still have no idea what this might have to do with Tk, it seems
related to KDE only. I found out by starting kaffeine from the
console, and this came as a warning message.

Thanx to everyone who tried to help,

Vivia