Closed fedoranvar closed 2 years ago
Are you using wayland?
Im using wayland
It looks like chromium based browsers don't properly handle IMEs when using wayland. Apparently chrome was relying on gtk for its IME processing.
Using --gtk-version=4
, should restore support for this, provided you have gtk4 installed , though it seems to choke on the currently generated file. Running it under XWayland should also fix the problem. I will have to investigate the gtk issue further.
@rvaiya thank you!
i'll try it!
--gtk-version=4
- didn't worked.
also tried GDK_BACKEND=x11
- still issue persist.
Can you clarify by what you mean by 'doesn't work'? Adding --gtk-version=4
should cause it to try and use gtk to parse the compose file (provided you have gtk4 installed), which will in turn cause it to crash since the parsing logic doesn't like something about keyd's compose file.
I am in the process of trying to figure out what this is, but you can temporarily fix the issue by manually trimming the file to include only the definitions of interest.
Can you clarify by what you mean by 'doesn't work'?
i've installed gtk4
and launched brave --gtk-version=4
- and issue persist.
Does brave crash? (it should). If not, then it seems it isn't using gtk4 for parsing. It may be that you are running under X wayland. Can you try the following flags?
--enable-features=UseOzonePlatform --ozone-platform=wayland --gtk-version=4
tried
brave --enable-features=UseOzonePlatform --ozone-platform=wayland --gtk-version=4
didn't crashed and issue still persist here logs from terminal:
What distro are you using? What version of brave are you running? (brave --version
). Are you sure you have gtk4 installed?
version: Brave Browser 100.1.37.109
distro: NixOS
installed gtk4
by installing unstable.gtk4
I'm not terribly familiar with NixOS, but my understanding is that packages are hermetically sealed and contain all of their dependencies. Would your brave package have access to gtk4 on the system? I assume you would need to add gtk4 to the brave package itself.
Closing due to inactivity. Feel free to reopen it.
Were you ever able to get this to work? Another solution might be to try looking for any --ozone-*
flags in the brave wrapper scripts and removing them, or alternatively explicitly specifying --ozone-platform=x11
. See also #273.
Good day to you!
Unicode characters works good in terminals, telegram, firefox, thunderbird, etc. but for some reason it doesn't work in Brave. (but![image](https://user-images.githubusercontent.com/52028706/164817776-3d42f6e9-9d8b-4324-9c93-367ebbca1201.png)
xkbmap
works fine)Thank you!