[GH-ISSUE #6635] [Bug]: Misleading (wrong?) full path name for files outside of /home/user/Documents for Linux Desktop users #80241

Closed
opened 2026-05-19 03:47:15 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @larryanta on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6635

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Linux Mint 22.2. Actual Budget v26.1.0. Desktop version; no server. My home directory is /home/lanta. Actual's data directory on my system defaulted to /home/lanta/Documents/Actual. If I attempt to move it to a higher up directory (eg. /home/lanta/xyz), the full path shown for /home/lanta/xyz is displayed as /run/user/1000/doc/54a872c9/xyz.

How can we reproduce the issue?

Click on My Finances -> Switch file and then click on the gear icon beside Files. Then click the pencil icon. This starts a File picker within Linux Mint. Navigate to a subdirectory inside your home directory (but one that is not within Documents) and click Select. Then note the /run/user/... full path name in the To: field

Where are you hosting Actual?

local linux desktop

What browsers are you seeing the problem on?

No browser. AB desktop app.

Operating System

Linux Mint 22.2

Originally created by @larryanta on GitHub (Jan 12, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/6635 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Linux Mint 22.2. Actual Budget v26.1.0. Desktop version; no server. My home directory is /home/lanta. Actual's data directory on my system defaulted to /home/lanta/Documents/Actual. If I attempt to move it to a higher up directory (eg. /home/lanta/xyz), the full path shown for /home/lanta/xyz is displayed as /run/user/1000/doc/54a872c9/xyz. ### How can we reproduce the issue? Click on My Finances -> Switch file and then click on the gear icon beside Files. Then click the pencil icon. This starts a File picker within Linux Mint. Navigate to a subdirectory inside your home directory (but one that is not within Documents) and click Select. Then note the /run/user/... full path name in the To: field ### Where are you hosting Actual? local linux desktop ### What browsers are you seeing the problem on? No browser. AB desktop app. ### Operating System Linux Mint 22.2
GiteaMirror added the bugelectron labels 2026-05-19 03:47:15 -05:00
Author
Owner

@larryanta commented on GitHub (Jan 12, 2026):

Not that I think this is a Linux Mint issue, but I just want to point out that the same thing is happening in Linux Mint 22.3.

<!-- gh-comment-id:3740918587 --> @larryanta commented on GitHub (Jan 12, 2026): Not that I think this is a Linux Mint issue, but I just want to point out that the same thing is happening in Linux Mint 22.3.
Author
Owner

@MikesGlitch commented on GitHub (Jan 13, 2026):

Hey, are you using the appimage or did you get the app from flathub?

It's it's from Flathub I'm thinking this may a side-effect of the sandboxing. Flatpaks hook into the file picker and create virtual paths to enforce sandboxing.

I'm not sure if there's anything we can do about it, it's just how flatpaks work. The virtual path should still point to the right place, it acts as a proxy.

If it bothers you, one thing to try is you could use Flatseal (it's available on flathub) to explicitly trust the directory you're trying to move the files to. It might know it doesn't need a virtual path and can use the trusted directory instead.

<!-- gh-comment-id:3746879134 --> @MikesGlitch commented on GitHub (Jan 13, 2026): Hey, are you using the appimage or did you get the app from flathub? It's it's from Flathub I'm thinking this may a side-effect of the sandboxing. Flatpaks hook into the file picker and create virtual paths to enforce sandboxing. I'm not sure if there's anything we can do about it, it's just how flatpaks work. The virtual path should still point to the right place, it acts as a proxy. If it bothers you, one thing to try is you could use Flatseal (it's available on flathub) to explicitly trust the directory you're trying to move the files to. It `might` know it doesn't need a virtual path and can use the trusted directory instead.
Author
Owner

@larryanta commented on GitHub (Jan 13, 2026):

Flathub (via Linux Mint's Software Manager). And you're right, the virtual path does point to the right place--- I completed the move and I see the files in the new location in my filesystem.

I'll consider Flatseal, but meanwhile I'll consider the "bug" closed. Thanks for your help!

<!-- gh-comment-id:3746961468 --> @larryanta commented on GitHub (Jan 13, 2026): Flathub (via Linux Mint's Software Manager). And you're right, the virtual path _does_ point to the right place--- I completed the move and I see the files in the new location in my filesystem. I'll consider Flatseal, but meanwhile I'll consider the "bug" closed. Thanks for your help!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#80241