[BUG] Missing ibus input capability

[EPOCHvoyager]

[BUG] Missing ibus input capability

[EPOCHvoyager]

Congrats on GoofCord, by the way. Fastest client I've tried as of yet.

[Milkshiift]

It's probably being run in Wayland native mode. Try --ozone-platform-hint=x11 flag.
I can't really provide support for this issue since it's a problem with Chromium/Electron, because of that I'm also closing the issue.
You can track progress of supporting Ibus input under native Wayland here electron/electron#33662 and here https://issues.chromium.org/issues/40113488

[Milkshiift]

Does this occur specifically in the flatpak distribution?

[Milkshiift]

Do you have examples of working flatpak apps?

[EPOCHvoyager]

Does this occur specifically in the flatpak distribution?

I was fairly certain of so when writing due to the Flatpak sandbox, but I've now downloaded the AppImage version to be sure:

Do you have examples of working flatpak apps?

Of the ones that I've used - Firefox, LibreWolf, Brave, Signal(Electron), Buffer, and Stremio all work with ibus. For an example of a non-working one, there's the Bitwarden Flatpak - which I believe also uses Electron.

[Milkshiift]

This seems to be due to this Chromium bug https://issues.chromium.org/issues/40113488
Try running GoofCord with --gtk-version=4, --enable-wayland-ime (separately) or disabling the Wayland socket for GoofCord through, for example, Flatseal.
Signal works because by default it runs in XWayland mode, which doesn't have the issue

[EPOCHvoyager]

Tried both launch flags, no avail. Disabling the Wayland socket makes GoofCord fail to launch with the following error:

[2:0622/162232.964059:ERROR:wayland_connection.cc(200)] Failed to connect to Wayland display: No such file or directory (2)
[2:0622/162232.964073:ERROR:ozone_platform_wayland.cc(265)] Failed to initialize Wayland platform
[2:0622/162232.964077:ERROR:env.cc(258)] The platform failed to initialize.  Exiting.
[0622/162232.966857:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)

Setting --ozone-platform-hint=x11 with the Wayland socket disabled leads to this other error:

[2:0622/162442.512663:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[2:0622/162442.512672:ERROR:env.cc(258)] The platform failed to initialize.  Exiting.
[0622/162442.515330:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)

[Milkshiift]

Try enabling the Wayland socket and running with --ozone-platform-hint=x11

[EPOCHvoyager]

Same outcome:

[2:0622/172324.386460:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[2:0622/172324.386469:ERROR:env.cc(258)] The platform failed to initialize.  Exiting.
[0622/172324.389299:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)

[EPOCHvoyager]

Affects the AppImage build as well after the 1.5.0 update.

[EPOCHvoyager]

It's probably being run in Wayland native mode. Try --ozone-platform-hint=x11 flag.

That did work, and should be recommended workaround for now(though only in the AppImage version, for reasons shown some comments above). Fair to close this if it's an upstream issue; happy to see this client is being actively maintained.