Okay. You may find helpful info by dmesg or journalctl -f. Following threads may also be helpful for you. You may see some improvement by keeping your RPM packages to the latest packages by running dnf upgrade especially as Fedora 39 is a beta version.
Palm rejection is not very great, I find my cursor moves a lot when typing.
Gnome finder (press “super” key and starts typing) crushes A LOT (at least every two days), and it would crush the entire system. Edit: Seems like all the non-consistent/system-level crushes are fixed by BIOS 3.03.
Apps Quirks and Fixes:
Megasync flatpak package always crushes, at some point or another.
Megasync do not have RPM package for Fedora 39, so I downloaded the official RPM for 38, and it works flawlessly. However, it always to check update for fedora 39, which leads to a 404 error. But I avoid updating using the terminal, so it don’t bother me that much.Edit: Use the RPMfusion version solves the problem, you will need to enable RPMfusion and resolve a package conflict, just google the error message, there are solutions.
Slack flatpak works great. I just need to enable “fallback to x11” permission for it to not look blurry. It uses wayland session when given that permission.
Signal flatpak crashes when send in the ozone wayland cmd argument, or tweak any wayland related permissions (wayland window session, fallback to x11, etc)Signal uses wayland session when set environment variable SIGNAL_USE_WAYLAND=1 in flatseal, there are more config options here: GitHub - flathub/org.signal.Signal
Signal RMP provided by opensuse do not support fedora 39 (talking about missing dependency, and I am too lazy to track it down). So I have to deal with blurry signal. signal flatpak works flawlessly, hence RPM might not be recommended
zoom flatpak works with screen sharing after I give it the “session dbus” permission in flatsealZoom flatpak works with screen sharing when you go to setting > screen share > advanced > screen capture mode on wayland and change it to pipwire mode.
codium works great as RPM (since I need it to access my dev env). Just need to use the ozone wayland commandline arg in the desktop file, and set the window title bar to “custom” instead of native.
Hi, thank you for sharing your experience. Do you mind sharing exactly what you did to fix Slack? I’m not sure what this permission is and I’ve tried several solutions I’ve found related to fractional scaling on Wayland for electron apps and nothing worked so for now I’m just running it in the browser.
Of course! If you installed slack from the app store (which means you installed the flatpak version), you can install flatseal from the app store (I used the flathub version, but all versions should work).
Open flatseal, select slack on the left panel, there should be a permission called “fallback to x11 windowing system” on the right, enable that and restart slack.
If you installed slack from the official site (this means you installed the RPM version), then you will probably need to edit the slack desktop file.
I am happy to share more details, just let me know what do you need.
Thank you so much, that was it! I’m new to the flatpak world and whenever I heard of flatseal it was in the context of enabling access to the filesystem, so I had no Idea it can do so much more.
If you don’t mind, can you share the changes you made to the desktop file for Code?
For now i’ve resorted to add code --enable-features=UseOzonePlatform --enable-features=WaylandWindowDecorations --ozone-platform-hint=auto to a bash file and launch it like this, for some reason if I tried to add these to the .desktop file it was not working.
Flatseal is a GUI tool for flatpak permission management, it can manage most (if not all) the permissions of a flatpak app.
I use the RPM version of codium (a open-source fork of code), this means that the desktop can be found in /usr/share/applications/. I think you need to change both codium.desktop and codium-url-handler.desktop.
@ClaudiuIO, I think I mistyped he url-handler desktop file, “useOzonePlatform” should not be necessary, nor do I think “WaylandWindowDecorations” is necessary if you are using custom window title bar provided by vscode.
gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"
This assumes you’re on Fedora Workstation 39 (GNOME) and you have not changed your defaults away from Wayland.
Now, Electron applications are their own thing. You will likely have to make individual changes to their launchers as some were built with X in mind. Using --force-device-scale-factor flag to the .desktop file and so on. I personally avoid electron applications if I can.
I think the reason why you still see the issue in your environment is because Matt tested the issue on another BIOS unit while the AMD Batch 1 user’s BIOS version is still 3.02. You can check the following thread. This issue is already filed on the Fedora Bugzilla with the log file. So, maybe you don’t have to provide logs.