From: Yasuaki Kudo <yasu@yasuaki.com>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: help guix <help-guix@gnu.org>
Subject: Re: Can't type Japanese anymore
Date: Tue, 27 Dec 2022 07:17:26 +0900 [thread overview]
Message-ID: <94A6BAA2-A78A-4168-B1AA-8BAD6DD2B21B@yasuaki.com> (raw)
In-Reply-To: <hm2kyfhRcAR75Sz164COnwK6-F5E2n48smXIQZYOQMeJ28CSXTbzUKSGhH9bqlCqW_y-ulPba7P2L_h-9ry0nObNX1ftaP4ugG-W2fq6RLg=@protonmail.com>
It has been a long time since I switched to Ubuntu (and I use Guix as an additional package manager in Ubuntu - this way I get maximum mainstream compatibility, which is very helpful for work, and the flexibility that comes with Guix! ) but just one thing I vaguely remember for situations like this - if you create another fresh user and try with almost no specific configuration in /home/another-user , would the problem still persist?
When I used to use Guix, I almost continuously ran guix pull and rebuilt the system so I could immediately find when things broke! 😅
-Yasu
> On Dec 27, 2022, at 01:34, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
>
> Hello,
>
> After upgrading recently to Guix System 9cb42f7, I can't type Japanese anymore. It disappeared from the list, even though I still have ibus-anthy installed.
>
> Also, the workaround in https://issues.guix.gnu.org/35610 does not work anymore.
>
> If you are using a more recent version of the system, can you type Japanese normally?
>
>
> ---
> Luis Felipe López Acevedo
> https://luis-felipe.gitlab.io/
> <publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc>
next prev parent reply other threads:[~2022-12-26 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 16:33 Can't type Japanese anymore Luis Felipe
2022-12-26 22:17 ` Yasuaki Kudo [this message]
2022-12-28 21:07 ` Luis Felipe
2022-12-28 23:16 ` Luis Felipe
2022-12-27 3:42 ` Maxim Cournoyer
2022-12-28 21:14 ` Luis Felipe
2023-01-29 19:20 ` Luis Felipe
2023-01-31 13:54 ` Maxim Cournoyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94A6BAA2-A78A-4168-B1AA-8BAD6DD2B21B@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=help-guix@gnu.org \
--cc=luis.felipe.la@protonmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.