unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ison <ison@airmail.cc>
To: sirgazil <sirgazil@zoho.com>
Cc: 35610 <35610@debbugs.gnu.org>
Subject: bug#35610: Freshly installed IBus intput method is not listed as an input source
Date: Tue, 7 May 2019 14:15:46 -0600	[thread overview]
Message-ID: <20190507201545.jo6p6blwaa25xiav@cf0> (raw)
In-Reply-To: <16a9300a65c.12930628867901.4984278243957188837@zoho.com>

The only other thing I can think of right now which might be different is the
way I'm starting ibus. Instead of ibus-setup, what happens if you launch it with
ibus-daemon -drx
and then access the preferences by right clicking the tray icon (or perhaps
running ibus-setup _after_ the daemon is launched if you have no tray icon)

On Tue, May 07, 2019 at 04:26:29PM +0200, pelzflorian (Florian Pelz) wrote:
> What I said was incomplete.  I just tried again; ibus-anthy works fine
> for me only when e.g. entering text in GNOME Shell’s search bar, but
> not when entering text in the terminal.  Sorry.

If I recall correctly I had this issue as well, where input would not work in
the terminal even though it worked in other applications, until I changed some
of my environment variables to "xim" instead of "ibus".
According to the Arch Wiki here
https://wiki.archlinux.org/index.php/IBus
there are claims from some users that things don't work until they replace
"ibus" with "xim".

  reply	other threads:[~2019-05-07 20:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 21:21 bug#35610: Freshly installed IBus intput method is not listed as an input source sirgazil
2019-05-06 21:48 ` ison
2019-05-07  0:36   ` Chris Marusich
2019-05-07 15:24     ` sirgazil
2019-05-07 15:54   ` sirgazil
2019-05-07 20:15     ` ison [this message]
2019-05-09 12:35       ` pelzflorian (Florian Pelz)
2019-05-07  4:11 ` pelzflorian (Florian Pelz)
2019-05-07  4:51   ` pelzflorian (Florian Pelz)
2019-05-07 12:36     ` sirgazil
2019-05-07 14:26     ` pelzflorian (Florian Pelz)
2019-06-24 15:57 ` Chris Marusich
2019-06-24 22:26   ` sirgazil
2019-06-25 23:20   ` sirgazil
2023-06-18 23:16 ` Luis Felipe via Bug reports for GNU Guix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190507201545.jo6p6blwaa25xiav@cf0 \
    --to=ison@airmail.cc \
    --cc=35610@debbugs.gnu.org \
    --cc=sirgazil@zoho.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).