Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #269225 > unrolled thread

debian bookworm japanese kana input disabled

Back to article view | Back to linux.debian.user

Contents

  debian bookworm japanese kana input disabled 冨澤守治 <molitz@coffee.ocn.ne.jp> - 2024-05-08 23:00 +0200
    Re: debian bookworm japanese kana input disabled Richard <rrosner5@gmail.com> - 2024-05-09 08:10 +0200
    Re: debian bookworm japanese kana input disabled Florent Rougon <f.rougon@free.fr> - 2024-05-09 09:20 +0200
      Re: debian bookworm japanese kana input disabled Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-05-09 12:10 +0200
        Re: debian bookworm japanese kana input disabled Eike Lantzsch ZP5CGE / KY4PZ <zp6cge@gmx.net> - 2024-05-09 15:40 +0200
          Re: debian bookworm japanese kana input disabled 冨澤守治 <molitz@coffee.ocn.ne.jp> - 2024-05-11 01:20 +0200

#269225 — debian bookworm japanese kana input disabled

Hellow!

Thanks you for your supprting everyday.

Last night (JST) I did some apt update && apt upgade.
But all of sudden I can't input kana and even print any editer or calc cell.
(Roman alphabet has no problem on printing.)

yours sincerely

--
Moriharu Tomizawa<molitz@coffee.ocn.ne.jp>

[toc] | [next] | [standalone]

#269227

[Multipart message — attachments visible in raw view] — view raw

/var/log/apt/history will tell you what apt also has been showing you
during that process. Never just mindlessly agree to what apt tells you it's
about to do, especially pay attention to the app list for "remove" and
"auto-remove". Things can always go wrong. So if apt told you it will
remove some package for whatever reason that's needed for kana, it will
have done so. So check the history and have a look at any packages from
that timestamp that where set to be removed.

Best
Richard

Am Do., 9. Mai 2024 um 03:45 Uhr schrieb 冨澤守治 <molitz@coffee.ocn.ne.jp>:

> Hellow!
>
> Thanks you for your supprting everyday.
>
> Last night (JST) I did some apt update && apt upgade.
> But all of sudden I can't input kana and even print any editer or calc
> cell.
> (Roman alphabet has no problem on printing.)
>
> yours sincerely
>
> --
> Moriharu Tomizawa<molitz@coffee.ocn.ne.jp>
>
>

[toc] | [prev] | [next] | [standalone]

#269228

Hi,

Le 09/05/2024, 冨澤守治 <molitz@coffee.ocn.ne.jp> a écrit:

> Hellow!
>
> Thanks you for your supprting everyday.
>
> Last night (JST) I did some apt update && apt upgade.
> But all of sudden I can't input kana and even print any editer or calc cell.
> (Roman alphabet has no problem on printing.)

This may be due to a recent glib2.0 update:

  https://lists.debian.org/debian-security-announce/2024/msg00094.html

“The update for glib2.0 released as DSA 5682-1 caused a regression in
 ibus affecting text entry with non-trivial input methods. Updated
 glib2.0 packages are available to correct this issue.”

Hopefully, you just need to update again.

Regards

-- 
Florent

[toc] | [prev] | [next] | [standalone]

#269229

On 9 May 2024 09:14 +0200, from f.rougon@free.fr (Florent Rougon):
>> Last night (JST) I did some apt update && apt upgade.
>> But all of sudden I can't input kana and even print any editer or calc cell.
>> (Roman alphabet has no problem on printing.)
> 
> This may be due to a recent glib2.0 update:
> 
>   https://lists.debian.org/debian-security-announce/2024/msg00094.html

That was my thought as well.


> “The update for glib2.0 released as DSA 5682-1 caused a regression in
>  ibus affecting text entry with non-trivial input methods. Updated
>  glib2.0 packages are available to correct this issue.”
> 
> Hopefully, you just need to update again.

However, I seem to have had a similar issue even after upgrading to
the first regression-fixed glib2.0 packages on Bookworm. Specifically,
dead keys no longer working with the Swedish keyboard layout, and
instead acting as though I didn't press any key at all.

The key press did show up in xev:

KeyPress event, serial 33, synthetic NO, window 0x2a00001,
    root 0x6aa, subw 0x0, time 1153798, (397,298), root:(1268,818),
    state 0x10, keycode 35 (keysym 0xfe57, dead_diaeresis), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x2a00001,
    root 0x6aa, subw 0x0, time 1153862, (397,298), root:(1268,818),
    state 0x10, keycode 35 (keysym 0xfe57, dead_diaeresis), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

but despite my attempts nothing showed up in any input field; trying
with both Xfce's Mousepad text editor, KeepassXC and gnome-terminal to
cover various UI toolkits, with the same result everywhere. The
combination of the key press showing up in xev and nothing showing up
in any application I tried with running under X pointed strongly
toward the input translation layer.

However, another physical computer also running Bookworm which I
upgraded to latest at around 09:40 May 9 UTC _didn't_ seem to have the
same issue, despite being set up similarly.

Turned out that there is _another_ upgrade to libglib2.0-0 and friends
taking those packages to package version 2.74.6-2+deb12u2; after
installing _that_ upgrade and rebooting, dead keys again seem to work
normally. (It's entirely possible that the reboot wasn't needed, but
as I had only just rebooted the system and so didn't have much of
anything already open, it seemed an easy enough way to actually ensure
that everything was running at the newly upgraded version.)

So if you're still having the same issue, _try once more_ apt-get
update && apt-get -u dist-upgrade; double-check that you get the
+deb12u2 or newer glib package versions; and see if that fixes the
problem before you poke around too much with the configuration (and
risk breaking something else in the process). Then let us know whether
you're still having the same issue or whether that resolved it.

-- 
Michael Kjörling                     🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

[toc] | [prev] | [next] | [standalone]

#269231

[Multipart message — attachments visible in raw view] — view raw

On Donnerstag, 9. Mai 2024 08:48:03 -04 Brad Rogers wrote:
> On Thu, 9 May 2024 10:06:29 +0000
> Michael Kjörling <2695bd53d63c@ewoof.net> wrote:
> 
> Hello Michael,
> 
> >However, I seem to have had a similar issue even after upgrading to
> >the first regression-fixed glib2.0 packages on Bookworm.
> >Specifically, dead keys no longer working with the Swedish keyboard
> >layout, and instead acting as though I didn't press any key at all.
> 
> Is it possible that, without at least logging out and back in, the
> broken version of the library is still in use?

Hi Michael
and hello 

冨澤守治[1]


I don't know if it was related but with the same Debian Sid upgrade Firefox (and only 
Firefox) lost the ability to enter äöüáéí€ß ... that is it ignored anything which was not pure 
ASCII, however entering the accented characters in a terminal or other applications (here 
KDE) still worked.
After today's upgrade everything was back to normal but I *had* to reboot.
So logging out and back in again might work although I suspect that at least restarting the 
X server will be necessary. I didn't try it because I had to reboot anyway.

All the best to you all
-- 
Eike Lantzsch KY4PZ / ZP5CGE


--------
[1] mailto:
%3D%3Futf-8%3FB%3F5Yao5r6k5a6I5rK7%3F%3D%20%3Cmolitz%40coffee.ocn.ne.jp%3E

[toc] | [prev] | [next] | [standalone]

#269248

Hi

Updated and upgraded,autoremoved. This matter has been fixed.
The problem is currently resolved.

Nice follow up! I appreciate it.
Best wishes

--
Moliharu  Tomizawa<molitz@coffee.ocn.ne.jp>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web