Overall I think it's not the good timing to enable wayland enable by default. I'm using Gnome 41, Here is the typora issue You can do this either via the override subcommand of flatpak itself or graphically via FlatsealĪbout fcitx, It seems this issue will be fixed in Chromium 98, maybe we should wait for typora update its Electron lib files. Simply have the XDG_SESSION_TYPE variable be something other than wayland for the Typora flatpak. In wayland it would need to go through the windows toolkit used, hence the reliance on these variables.ĮDIT2: completely forgot your question about how to disable wayland support. The title bar issue is strange what DE/WM are you using? From what I heard of other flatpaks some wayland compositors don't properly set things like GDK_BACKEND=wayland and QT_QPA_PLATFORM=wayland so they are available to flatpaks and they might behave strangely in wayland or even fail to start in wayland mode if they rely on these variables.ĮDIT: The environment variables referred to here might have sth to do with fctix not working for you: in the xmodifers thing is implicit fcitx works on x11 because Xorg handles it. If it does this would need to be added to the flatpak flags in the. You might want to try to simply add it via flatseal and test if it works. There it was enabled as dbus session-bus. I have no idea what this fcitx is but I have seen it used on the element (matrix protocol) chat app, which also uses electron. ![]() I did have the title bar and no problems writing files. In thanks for mentioning I had tested it on Plasmashell. The environment variables referred to here might have sth to do with fctix not working for you: IMO this should not be needed as setting these variables is the job of your host system. Some applications set them in the flatpak itself either via static variable setting (can be tested in flatseal too) or dynamically via script similar to what I've done with the -ozone-platform=wayland thing. The title bar issue is strange what DE/WM are you using?įrom what I heard of other flatpaks some wayland compositors don't properly set things like GDK_BACKEND=waylandĪnd QT_QPA_PLATFORM=wayland so they are available to flatpaks and they might behave strangely in wayland or even fail to start in wayland mode if they rely on these variables. ![]() ![]() Thanks for mentioning I had tested it on Plasmashell.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |