this issue has been happening for a 2 months now, at first I thought it was a flatpak issue (as the app I have is a flatpak version) but after I investigated, the app runs fine when I switch to X11 so it could be either the app itself no longer being optimized for
wayland (which I highly doubt since it worked fine before these 2 months), or it could be something with the Kwin window manager that made the app run like that, idk I’m hoping I could find answers by asking here, thanks in advance!
@Ace120C Investigate the application options/setting in flatseal. Next, start the application from the command line to see what potential errors are exposed, eg flatpak run com.notesnook.Notesnook
1 Like
@Ace120C I’m on GNOME it does take awhile to start, but had to enable dbus sessions… seems to have a certificate issue for me…
1 Like
flatpak run com.notesnook.Notesnook
App ready. Opening window.
https protocol inteception "successful"
Intercepting request: https://app.notesnook.com/
Intercepting request: https://app.notesnook.com/assets/index-Bqexw7zW.js
Intercepting request: https://app.notesnook.com/assets/index-Cfyt6DXBJL3k.css
Intercepting request: https://app.notesnook.com/assets/_en-CPfk3hwcEQII.js
Intercepting request: https://app.notesnook.com/assets/root-DRsbyIR7Rl3J.js
Intercepting request: https://app.notesnook.com/assets/task-scheduler.worker-DvYHqXlL.js
Intercepting request: https://app.notesnook.com/assets/index-BzxHSQZCFGvg.js
Intercepting request: https://app.notesnook.com/assets/nncrypto.worker-CWnPWl7b.js
Intercepting request: https://app.notesnook.com/assets/use-mobile-BuKMUSgYQ2BW.js
Intercepting request: https://app.notesnook.com/assets/app-DxFwIY3H658L.js
Intercepting request: https://app.notesnook.com/assets/user-store--oZ4vMUKdyi_.js
Intercepting request: https://app.notesnook.com/assets/internal-link-CaYkAyYKuyUv.js
Intercepting request: https://app.notesnook.com/assets/user-store-CktUmpzi3ufr.css
Intercepting request: https://app.notesnook.com/assets/index-BgLotEXcAuzY.js
Intercepting request: https://app.notesnook.com/assets/app-D_2-meMWYdTT.css
Intercepting request: https://app.notesnook.com/assets/sqlite.worker.desktop-BUoPLsZa.js
Intercepting request: https://app.notesnook.com/assets/hack-regular-Dv5unGLzuLVH.woff2
Intercepting request: https://app.notesnook.com/assets/network-check.worker-BcN_3Xjw.js
Intercepting request: https://app.notesnook.com/assets/sqlite.worker.desktop-BUoPLsZa.js
Intercepting request: https://app.notesnook.com/assets/open-sans-v34-vietnamese_latin-ext_latin_hebrew_greek-ext_greek_cyrillic-ext_cyrillic-regular-BtCV9HBQDlM5.woff2
Intercepting request: https://app.notesnook.com/assets/open-sans-v34-vietnamese_latin-ext_latin_hebrew_greek-ext_greek_cyrillic-ext_cyrillic-600-BaohRB0RafMI.woff2
Intercepting request: https://app.notesnook.com/assets/index-99SZHWeNqyIJ.js
APPIMAGE env is not defined, current application is not an AppImage
[3:0327/171856.196795:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
This is what it printed out while I was using it (it froze 3 seconds in)
APPIMAGE env is not defined, current application is not an AppImage
[3:0327/172242.515081:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[3:0327/172300.222237:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[3:0327/172337.444717:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
I wonder what exit code 139 means…
@Ace120C likely need to disable gpu acceleration in flatseal for the application.
1 Like
weird, why does it work in X11 and used to work just fine with wayland before?
I have an AMD card, the drivers should work just fine.
anyways so far, no freezes on wayland yet with me disabling GPU acceleration, I’ll keep you posted should something happens, thanks a lot btw
@Ace120C No idea, I use GNOME/Wayland with it on Intel ARC, also ran on my Nvidia GPU via prime render offload… It is slow to start though. When you start it up and see the warning does it return control to the terminal, or still running?
1 Like
for me It launches quickly, my issue was only freezing which I guess it’s solved again, however I need around a day to see if there are anymore problems to make sure, thanks again
1 Like