[Users] Browse Folder Window's Typing-Triggered Search Ignores First Key Entry

[Dustin Miller]

On Fri, 21 Jul 2017 16:15:39 +0600
Dustin Miller <dustbiz at gmail.com> wrote:

> On Mon, 10 Oct 2016 19:04:12 +0600
> Dustin Miller <dustbiz at gmail.com> wrote:
> 
> > Problem Example: I use 'Ctrl+O' (to move message to a folder) or
> > 'G' (to go to a folder). In the browse folder window that comes up I
> > type something like 'inb' for the 'Inbox' folder, but only 'nb'
> > shows up. (I think the one time when I typed it fast enough, it may
> > have ignored the first two letters, but I don't think it's strictly
> > a timing thing, since even when I waited for a bit, it would still
> > ignore the first letter.) The consistently successful workaround
> > that I'm using is to just type the initial character twice, once to
> > 'wake up' the feature and then once for the actual search.
> > 
> > Environment: Toshiba Netbook NB-305, Lubuntu 14.04, Claws 3.14.0
> > (built from tarball)
> > 
> > I did not experience this with the same version of Claws running on
> > Ubuntu 14.04 (with 'GNOME Flashback (Metacity)' desktop environment
> > [DE]) on two separate desktop PCs. So I'm wondering whether this
> > problem is associated with the LXDE DE? Or perhaps with the
> > different hardware? For that reason, I'm also not sure whether this
> > would qualify as a bug or not, but perhaps there is something that
> > could be done on the Claws side to make this work as it's supposed
> > to on this and similar systems.  
> 
> FWIW, this problem seems to be 'fixed' in Lubuntu 16.04 based on my
> recent experience with it on a different system. Based on my current
> experience and what others have reported, LXDE still seems to have
> some issues with the way it handles the focusing of windows for some
> programs on some systems some of the time, but I'm not sure what the
> problem is exactly or how to remedy it. But based on what I've read on
> this list, this type of issue as it relates to Claws is not a Claws
> issue. My guess is the best place for someone to start
> trouble-shooting this is in the LXDE docs, forums, and/or other
> resources available.

DM: I 'think' I've actually been able to shed some light on the
keyboard issue mentioned above (not sure if it's relevant to the
windows focusing issue, but I haven't seen that for awhile now -- I'm
currently on Lubuntu 18.04 64-bit on my main working systems).

DM: Anyway, I'm pretty sure the keyboard-related problem is caused when
'ibus' (a keyboard input method) is both installed AND selected as the
system input method (in 'Start'-Pref's-LangSupport) (there are other
ways to activate and de-activate this as well, depending on distro).
However, I do want to have 'ibus' activated so looked around for another
solution than just turning it off. (BTW, in the last months or so I
discovered that, besides Claws, ibus causes keyboard problems with both
Veracrypt [able to work around] and GnuCash [making it unusable, thus
prompting my most recent research].)

DM: As part of my ibus / language-related setup, one of the things I
installed was 'ibus-gtk' (based on fairly old instructions and I
haven't found newer ones online for my use case). Thus far, it appears
that if I also install 'ibus-gtk3', then the keyboard problems in the
above app's disappear (I also found at least a couple comments online
of people who noted that not having this package causes an activated
ibus to 'interfere' in various ways with certain app's.).

DM: As a result of my research above, I've also made a note that some
future programs I use may also require that 'ibus-qt4' be installed.
This is because I'll likely stick with Lubuntu and my current version
is the last one to use the LXDE desktop, with later versions switching
to the LXQt desktop. (I don't know much about 'Qt', but am assuming
that the ibus-related 'Qt' and the Lubuntu-related one are referring to
the same technology. :) ).

DM: Anyway, I've been noticing this issue with Claws since 14.04 and
am quite pleased to have come upon this solution (pretty much by
accident, as I had sort of given up on it awhile ago), so I thought I'd
share it here in case anyone else is dealing with this particular
problem currently or might in the future. Cheers, ---Dustin