Slacko64-7.0: latest Chrome cannot use input method

[miltonx]

When using Chrome 100.0.4896.88 and previous versions on slacko64-7.0 and fossapup64, the input method, yong, worked fine.

After the latest update to Chrome 102.0.5005.61, input method cannot be activated for the Chrome window on slacko64-7.0. I tried three input method tools, ie, yong, fcitx and scim. None worked. But on fossapup64 everything is fine.

Trying to check the errors, I started chrome in terminal, and tried to activate input method on the Chrome window. The terminal showed this. Any ideas what is missing in slacko64-7.0?

Code: Select all

Fontconfig warning: "/etc/fonts/fonts.conf", line 102: unknown element "blank"
[18637:18721:0606/144430.153712:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[18637:18721:0606/144430.154106:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[18637:18721:0606/144430.154593:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[18668:18668:0606/144430.433236:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[18637:18637:0606/144433.524693:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144433.684547:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144433.807354:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144433.829416:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144434.120256:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144434.206690:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144434.302864:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144434.325700:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144435.222555:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144435.329398:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144435.403083:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144435.444429:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144435.615664:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144435.703120:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144435.776896:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[18637:18637:0606/144435.821428:ERROR:input_method_context_impl_gtk.cc(108)] Cannot translate a Keyevent to a GdkEvent.
[0606/144504.715703:ERROR:nacl_helper_linux.cc(315)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly

[thinkpadfreak]

I am experiencing the same problem.

I have tested several puppies:
Fossapup64 + fcitx ... OK
Jammypup64 9.7b + fcitx ... OK
Bionicpup64 + fcitx ... no good
DpupBuster64 + scim ... no good
Slacko64 7.0 + scim ... no good
ScPup64 + fcitx ... no good

I suspect that something has been changed in Chrome 102 as compared with older versions of Chrome.
Chrome claims to support ubuntu bionic, debian buster and later versions of the OS. So it is confusing that we cannot use input methods in Chrome 102 running on Bionicpup64 and DpupBuster64. AS far as I know, Fossapup64 is the only official puppy on which we can use input methods in Chrome 102.

[miltonx]

I am experiencing the same problem.

I have tested several puppies:
Fossapup64 + fcitx ... OK
Jammypup64 9.7b + fcitx ... OK
Bionicpup64 + fcitx ... no good
DpupBuster64 + scim ... no good
Slacko64 7.0 + scim ... no good
ScPup64 + fcitx ... no good

I suspect that something has been changed in Chrome 102 as compared with older versions of Chrome.
Chrome claims to support ubuntu bionic, debian buster and later versions of the OS. So it is confusing that we cannot use input methods in Chrome 102 running on Bionicpup64 and DpupBuster64. AS far as I know, Fossapup64 is the only official puppy on which we can use input methods in Chrome 102.

Thanks for the inclusive test.
Since Fossapup64 works, maybe the problem is not with chrome 102. Could be that chrome moved to some newer IM interface which is not yet supported by other pups. But that's just a guess.
At this moment fossapup64 seems to be the most well-rounded one among various pups, but I'm really reluctant to move away from slacko64-7.0 as it is super fast and stable.

[thinkpadfreak]

Instead of using the input method installed on the system, you can use the google input tools, one of the Chrome extentions.
I set "Ctrl + Space" to switch on and off the Japanese input. The combination can be either Alt or Ctrl plus any other key.

I uaually use Firefox. When I have to input Japanese on Chrome 102, the google input tools will do, though I would like to know what is different between Bionicpup64 and Fossapup64 in terms of input methods.

[miltonx]

Instead of using the input method installed on the system, you can use the google input tools, one of the Chrome extentions.
I set "Ctrl + Space" to switch on and off the Japanese input. The combination can be either Alt or Ctrl plus any other key.

I have briefly considered that option before, but did not really try it. I gotta try it and see.

...though I would like to know what is different between Bionicpup64 and Fossapup64 in terms of input methods.

Exactly, that's become an obsession now and has been gnawing the s**t out of me.

PS:
I just tried the input extension on chrome. It confirmed my previous concerns. The extension runs as a content script. That means, it can only be used after the webpage is loaded. It cannot be activated when trying to input characters in the address bar or in the chrome config pages. I don't understand why google did not design the input method as a higher level of plug-in component, rather than a regular extension. Extensions have a lot of limitations.

[Clarity]

There are 2 options, I can think of, that could help on this concern

1. The Chrome Forum

2. Join Chrome development community which gives access to Chrome code changes

Could this help?

[thinkpadfreak]

There are 2 options, I can think of, that could help on this concern

The Chrome Forum

Join Chrome development community which gives access to Chrome code changes

Could this help?

Thanks for your interest.

I am afraid that both Chrome and Puppy are responsible for this issue.

With Chrome 101 or earlier we could use input methods fine. So I suspect that something has been changed on the part of Chrome.

It seems that there has been some change on the part of Puppy, because newer Puppies such as Fossapup64 and Jammypup64 9.7b allow us to use input methods with Chrome 102.
A member of the Puppy Japanese Forum reports that he/she can use an input method with Chrome 102 on Bionicdog. On the other hand, Bionicpup64 does not allow us to use input methods with Chrome 102. When I search the Internet, there seem to be hardly any reports of Chrome 102 causing this kind of issue.

That is all i can think of. Unfortunately, I do not know much about the structure of Puppy, nor do I know of the build of Chrome.

[miltonx]

Probably Chrome adopted a new standard of input method communication mechanism. The "Cannot translate a Keyevent to a GdkEvent" error seems to be a new addition in Chrome's source code, as far as I can find out from searching by google.

Looks like the latest ubuntu/debian systems are fine with IM on latest Chrome.

Fossapup is the latest official ubuntu based pup.

Slacko64_7.0 is not older than fossapup64, but I suspect that it's the slackware (14.2) base that fails to meet the latest input method mechanism. That's a guess, though.

What drives me crazy is that there is nowhere to find systematic tutorial or information about linux input method architecture and its bus communication mechanism. Input method for Linux seems to be a whole mess. So it is very hard for us to track the cause of problem and find the lacking programs/libs that could make up for this bug. To make it worse, many of the best linux developers of the world do not feel an urgent need to develop input methods for non-English languages or write technical documents.

So I'd really appreciate it if someone can point me to some indepth technical readings about how input method works on current Linux.

[miltonx]

I tested slackel64 7.5 (based on slackware 15) and slackel64 7.4 (based on slackware 14.2). Both work fine with chrome 102.0.5005.61.

So the problem is not with slackware 14.2. Probably slacko64_7.0 is missing something from slackware 14.2.

[miltonx]

I tested fatdog64-812. It works with the latest chrome.

I tried to check what distro fatdog is based on, and was surprised to know that it's Linux from Scratch.

[thinkpadfreak]

I tested slackel64 7.5 (based on slackware 15) and slackel64 7.4 (based on slackware 14.2). Both work fine with chrome 102.0.5005.61.

I tested fatdog64-812. It works with the latest chrome.

As I wrote before, fossapup64 and jammypup64 9.7b work fine with Chrome 102 or later. I wonder what change has been added to woof-CE after the release of bionicpup64, if this issue should be related to woof-CE.

On the other hand, I cannot make fcitx work with Chrome 102 or 103 on Vanilla Upup, which is one of the latest Puppies. I wonder if someone of the Puppy Linux developers knows the reason.

[dimkr]

Let's try to isolate the problem.

Does this problem occur with latest Chrome (109?) in any of these?
- FossaPup64 9.5
- @radky's F96
- Vanilla Dpup 9.3.x
- S15Pup

All 4 options use X.Org, making X.Org vs. Wayland differences irrelevant.

3 out of 4 were built with a recent woof-CE, that will help us understand if something has changed in woof-CE. Vanilla Dpup uses GTK+ 3 almost universally and the problem could be GTK+ related. S15Pup is Slackware-based and uses GTK+ 2 almost universally, and maybe the problem originates in Debian and Ubuntu based builds inherit it.

[thinkpadfreak]

Does this problem occur with latest Chrome (109?) in any of these?
- FossaPup64 9.5
- @radky's F96
- Vanilla Dpup 9.3.x
- S15Pup

fossapup64 9.5 + fcitx ... OK
radky's F96 + fcitx ... no good
Vanilla Dpup 9.2.21 (64bit) + scim ... no good
S15Pup64 + scim ... no good

The iso of Vanilla Dpup 9.3.x is rather large in size. So I am reluctant to download it, sorry.

The way I activate input methods is always the same. It is surprising that fossapup64 9.5 complies with Chrome 102 or later, because the OS was developed before Chrome 102 came into existence. But it is natural at the same time, if fossapup64 9.5 is compatible with Ubuntu Focal Fossa.

[dimkr]

The iso of Vanilla Dpup 9.3.x is rather large in size. So I am reluctant to download it, sorry.

That's the price you pay for preinstalled multi-language support and CJK fonts