[Bug]: Starting flatpak from menu causes an uncaught exception error #2381

Closed
opened 2026-02-28 20:12:21 -06:00 by GiteaMirror · 10 comments
Owner

Originally created by @HyperEye on GitHub (Aug 11, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I updated the flatpak on my desktop today and upon opening Actual Budget from my KDE application menu an error dialog popped up with a JavaScript error due to an uncaught exception. If I hit Ok on the error dialog it will reappear. Hitting Ok a few times will allow the application window to appear but the error dialog continues to display. This error does not occur when the flatpak is launched from a shell. The error can also be eliminated by editing the menu entry and setting it to run in a terminal.

Image

How can we reproduce the issue?

Start the latest flatpak using the desktop's application launcher.

Where are you hosting Actual?

Desktop App (Electron)

What browsers are you seeing the problem on?

No response

Operating System

Linux

Originally created by @HyperEye on GitHub (Aug 11, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I updated the flatpak on my desktop today and upon opening Actual Budget from my KDE application menu an error dialog popped up with a JavaScript error due to an uncaught exception. If I hit Ok on the error dialog it will reappear. Hitting Ok a few times will allow the application window to appear but the error dialog continues to display. This error does not occur when the flatpak is launched from a shell. The error can also be eliminated by editing the menu entry and setting it to run in a terminal. <img width="683" height="476" alt="Image" src="https://github.com/user-attachments/assets/8e7edf24-24cc-444a-8b30-c3b181f2eaec" /> ### How can we reproduce the issue? Start the latest flatpak using the desktop's application launcher. ### Where are you hosting Actual? Desktop App (Electron) ### What browsers are you seeing the problem on? _No response_ ### Operating System Linux
GiteaMirror added the needs infobug labels 2026-02-28 20:12:21 -06:00
Author
Owner

@youngcw commented on GitHub (Aug 11, 2025):

what distro/version are you using?

@youngcw commented on GitHub (Aug 11, 2025): what distro/version are you using?
Author
Owner

@HyperEye commented on GitHub (Aug 11, 2025):

I am on Gentoo and the flatpak is 25.8.0 downloaded from the Actual Budget website. My desktop is KDE Plasma 6.4.2 running on wayland.

@HyperEye commented on GitHub (Aug 11, 2025): I am on Gentoo and the flatpak is 25.8.0 downloaded from the Actual Budget website. My desktop is KDE Plasma 6.4.2 running on wayland.
Author
Owner

@youngcw commented on GitHub (Aug 11, 2025):

Does this happen on other installs of KDE? I would bet that its something specific with your system

@youngcw commented on GitHub (Aug 11, 2025): Does this happen on other installs of KDE? I would bet that its something specific with your system
Author
Owner

@HyperEye commented on GitHub (Aug 11, 2025):

I do not have other KDE installs to try but I can say that I was running the flatpak just fine before I updated it. I will try downgrading the flatpak and see if I can determine the version of regression.

@HyperEye commented on GitHub (Aug 11, 2025): I do not have other KDE installs to try but I can say that I was running the flatpak just fine before I updated it. I will try downgrading the flatpak and see if I can determine the version of regression.
Author
Owner

@youngcw commented on GitHub (Aug 11, 2025):

This may have been the first release that uses node 20.

@youngcw commented on GitHub (Aug 11, 2025): This may have been the first release that uses node 20.
Author
Owner

@HyperEye commented on GitHub (Aug 11, 2025):

25.4.0 is the first flatpak that produces this error. 25.3.1 does not produce an error.

@HyperEye commented on GitHub (Aug 11, 2025): 25.4.0 is the first flatpak that produces this error. 25.3.1 does not produce an error.
Author
Owner

@youngcw commented on GitHub (Aug 11, 2025):

I think 25.4 is the first version to included a bundled sync server. I wonder if its a permissions issue. But that wouldn't make sense if it works sometimes...

@youngcw commented on GitHub (Aug 11, 2025): I think 25.4 is the first version to included a bundled sync server. I wonder if its a permissions issue. But that wouldn't make sense if it works sometimes...
Author
Owner

@HyperEye commented on GitHub (Aug 11, 2025):

Based on the exception text, and the fact that starting it in a terminal corrects the issue, I wonder if it has to do with having no console for stdout/output. I have OpenSUSE KDE in a VM that I can try it on as well.

@HyperEye commented on GitHub (Aug 11, 2025): Based on the exception text, and the fact that starting it in a terminal corrects the issue, I wonder if it has to do with having no console for stdout/output. I have OpenSUSE KDE in a VM that I can try it on as well.
Author
Owner

@HyperEye commented on GitHub (Aug 11, 2025):

I tried the latest flatpak on OpenSUSE Tumbleweed with Plasma 6 and the error does not occur. I will try updating my Gentoo system sometime within the next few days to see if the issue is resolved.

@HyperEye commented on GitHub (Aug 11, 2025): I tried the latest flatpak on OpenSUSE Tumbleweed with Plasma 6 and the error does not occur. I will try updating my Gentoo system sometime within the next few days to see if the issue is resolved.
Author
Owner

@youngcw commented on GitHub (Aug 11, 2025):

Ill close this off for now. If you cant get it fixed try reaching out on discord for support there.

@youngcw commented on GitHub (Aug 11, 2025): Ill close this off for now. If you cant get it fixed try reaching out on discord for support there.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2381