Mark,

I searched for "input method" but I couldn't find anything relevant (at
least not for me).

In Gnome Control Center -> Region & Language
I have two Input Sources:  Portuguese (Brazil)  and  English (US)

In Input Source Options I have "Use the same source for all windows"
checked.

In Gnome Control Center -> Devices - > Keyboard -> Keyboard Shortcuts ->
Typing
Switch to next input source =  Super + Space
Switch to previous input source = Shift + Super + Space


Patrick also suggested the problem was with the input method and mentioned
the same issue with Japanese
and that it could be the IM  editor activated.
I found 2 INPUT METHOD tools in the menu: Applications ->  System Tools ->

The first one (blue icon) opens the uim-pref-gtk.
In the Global Settings there was a check box "Input method toggle" checked
with
Input method toggle key set to: "<Meta>space"

I disabled it, but the behavior persisted.

The second tool is the Input Method Configuration (im-config)

It starts with the following text:

"Current configuration for the input method:
 * Active configuration: missing (normally missing)
 * Normal automatic choice: none (normally ibus or fcitx or uim)
 * Override rule: zh_CN,fcitx:zh_TW,fcitx:zh_HK,fcitx:zh_SG,fcitx
 * Current override choice:  (en_US)
 * Current automatic choice: none
 * Number of valid choices: 1 (normally 1)
The override rule is defined in /etc/default/im-config.
The configuration set by im-config is activated by re-starting X.
Explicit selection is not required to enable the automatic configuration if
the active one is default/auto/cjkv/missing."

And after I went to the steps of configuration selecting the
recommendations, it outputs:

"Keeping the user configuration /home/myuser/.xinputrc as missing.
Automatic configuration selects: none
This does not set any IM from im-config.
This is the automatic configuration choice if no required IM packages are
installed.
If a daemon program for the previous configuration is re-started by the X
session manager, you may need to kill it manually with kill(1).
See im-config(8) and /usr/share/doc/im-config/README.Debian.gz for more.


Everything was working fine 1 week ago.
I could type SHIFT + SPACE and a space character would appear.
I just updated the system.

Any more ideas?

Thanks in advance.

Regards.



On Sun, Dec 10, 2017 at 2:22 PM, Mark Fletcher <mark2...@gmail.com> wrote:

> On Thu, Dec 07, 2017 at 11:03:04PM +0000, Paulo Roberto wrote:
> > Roberto, I figure out how to trigger and disable the problem and I think
> > it's a BUG.
> >
> > The problem occurs when I press SHIFT + SPACE (together).
> >
> > I went though the list of shortcuts in the Gnome Control Center under
> > Devices ->Keyboard. No shortcut is set for SHIFT + SPACE
> >
> > As I told you before, Input Source Options is set to: "Use the same
> source
> > for all windows"
> > But the shortcuts to change input, in case it was set otherwise are:
> SUPER
> > + SPACE and SHIFT + SUPER + SPACE.
> >
> > Before yesterday when I typed SHIFT + SPACE I'd got a space character,
> now
> > I have this weird behavior that I don't even know what it means.
> >
>
> The more you describe this issue, the more it sounds like an input
> system for some other language. What you are describing is EXACTLY the
> behaviour I get (and want) when typing in Japanese. To know what kanji
> character to use for what I am typing, the input system has to see
> several keypresses' worth of input. It lets me type that input,
> underlining the part that it is watching, waiting until I have typed
> enough for it to figure out what I mean, or until I press the space bar
> to say "that is all you are getting, go figure it out" or Enter which
> means "I want you to keep this text exactly as I typed it, don't try to
> interpret". I use the input system Anthy which I believe works with
> multiple languages. There are others though.
>
> And SHIFT + SPACE is the default method for switching between English
> and Japanese input on such systems.
>
> It doesn't have to be something obvious like Japanese -- you'd know
> immediately if it were because it would replace the regular alphabet
> characters with Japanese hiragana characters as you type -- but maybe
> some language with lots of accents etc that needs to see more than one
> letter you are typing before knowing what character to use for what you
> are typing? Or an input method that chooses to work that way even if
> that isn't the only way that could work for that language?
>
> What languages do you have installed? And what do you find if you search
> your system for "input method"?
>
> Mark
>
>

Reply via email to