-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why did the flatpak for Notesnook stop opening? #23
Comments
Same problem here, I think it is because of Wayland, I also enabled A workaround is launching the app with this command but I don't know where to put this options on Flatseal to make these parameters permanent. flatpak run com.notesnook.Notesnook --enable-features=UseOzonePlatform --ozone-platform=x11 EDIT: In the meantime you can use the AppImage, that still works. System infoOS: openSUSE Tumbleweed x86_64 Logs/core dump infoWithout the workaround the core dump info looks like this:
|
This basically forces flatpak to run Notesnook on X11 instead of Wayland. |
This app used to work for me with no modifications on my system. I didn't have to force it into using X11 or anything like that. Is this something that needs to be updated in Notesnook to fix? Was anything changed in the app about a couple of months ago that might affect this? |
A few weeks ago I updated my Fedora Kinoite system like I normally do. After rebooting I noticed that my Notesnook flatpak no longer launches. It will start trying to launch but then fails. I try opening it in from my admin account and it works as expected, but it won’t launch when I’m in my user account, which is where I do most of my work. All my other flatpaks like LibreOffice and Brave work like they did before, so it’s just this one app that doesn’t. I tried asking the developer of Notesnook and he said he didn’t know what it could be. Did something change in the settings for flatpaks in a previous update?
Below is what I get when I try running the app in the terminal:
The text was updated successfully, but these errors were encountered: