[Feature] the ability to set alternate install paths for browsers
Describe the feature
when setting cookies from browser, it will try to find the browser in the default location, but in some file systems the location is different. for example I installed chrome from flatpak, so chrome location is ~/.var/app/com.google.Chrome but parabolic looks for it in ~/.var/app/org.nickvision.tubeconverter/config/google-chrome
Same problem with Brave Browser. I think, the problem is that xdg-config in the Flatpak manifest maps to ~/.config on the host, but inside the Flatpak it appears as ~/.var/app/org.nickvision.tubeconverter/config/. For Firefox Browser, it works, because the path in the manifest uses ~.
Can you try with V2025.11.0 once it's available on Flathub and report back?
I forgot to set the new permissions in the flatpak manifest, hence the search paths were a little messed up. Try in this new version and let me know!
For me, it is still not working in V2025.11.0.
It still looks in the ~/.var/app/org.nickvision.tubeconverter/config/ directory.
I think you need to release a version bump which includes this commit (10de05a41f21d530da3069e226bb6e299bda22cf).
This has been added to the flatpak manifest here: https://github.com/flathub/org.nickvision.tubeconverter
Can you try running flatpak update and see if it chagnes anything?
It shows the changes here
I checked version 2025.11.0 and the problem is still there. Also i noticed that there is no google-chrome folder in my ~/.config/ either
I reinstalled: It asks for the permissions. But I think the app version V2025.11.0 still uses the wrong paths, because commit https://github.com/NickvisionApps/Parabolic/commit/10de05a41f21d530da3069e226bb6e299bda22cf is not included in this version!
$ flatpak install flathub org.nickvision.tubeconverter
Looking for matches…
org.nickvision.tubeconverter permissions:
ipc network fallback-x11 wayland x11 dri file access [1] dbus access [2]
[1] xdg-download, ~/.config/BraveSoftware/Brave-Browser:ro, ~/.config/chromium:ro, ~/.config/google-chrome:ro, ~/.config/microsoft-edge:ro, ~/.config/naver-whale:ro, ~/.config/opera:ro,
~/.config/vivaldi:ro, ~/.mozilla/firefox:ro, ~/snap/firefox/common/.mozilla/firefox:ro
[2] org.freedesktop.Notifications, org.freedesktop.ScreenSaver, org.freedesktop.secrets
ID Branch Op Remote Download
1. [✓] org.nickvision.tubeconverter.Locale stable i flathub 49,2 kB / 413,7 kB
2. [✓] org.nickvision.tubeconverter stable i flathub 277,0 MB / 283,6 MB
Installation complete.
because commit https://github.com/NickvisionApps/Parabolic/commit/10de05a41f21d530da3069e226bb6e299bda22cf is not included in this version!
This commit has no effect on the published Flatpak release. Editing the flatpak file in this repository is not what Flathub uses to build the app.
Flathub uses the flatpak file here for building Parabolic: https://github.com/flathub/org.nickvision.tubeconverter . And you can see that the paths are correct matching the commit you linked.
You can also see in the command output you posted:
~/.config/BraveSoftware/Brave-Browser:ro, ~/.config/chromium:ro, ~/.config/google-chrome:ro, ~/.config/microsoft-edge:ro, ~/.config/naver-whale:ro, ~/.config/opera:ro, ~/.config/vivaldi:ro, ~/.mozilla/firefox:ro, ~/snap/firefox/common/.mozilla/firefox:ro
That the paths are still correct and again match the commit you linked.
Something else is causing it not to use these paths correctly.
Thanks, I understand now, sorry.
Same problem with Opera browser.
I am on Linux, trying to use Google Chrome cookie... the cookies are held in a database (~/.config/google-chrome/Default/Cookies) and the selection box wants a .txt file?
I am on Linux, trying to use Google Chrome cookie... the cookies are held in a database (~/.config/google-chrome/Default/Cookies) and the selection box wants a .txt file?
Instead of the selecting a cookies file (requiring a txt) you should look above that setting and simply select chrome from the cookies from browser dropdown instead. This will automatically pull the cookies.
Ensure you are on the latest version of parabolic to see this feature.
you should look above that setting and simply select chrome from the cookies from browser dropdown instead. This will >automatically pull the cookies.
Ensure you are on the latest version of parabolic to see this feature.
I did exactly that... in fact, I didn't even try setting the "cookies file" at first. It was only after setting google-chrome from the dropdown, and it failing, that I attempted to select the cookie file.
I don't know why it's looking for the chrome cookies database in this odd, seemingly flatpak-oritented place...
"ERROR
Error during yt-dlp validation: ERROR: could not find chrome cookies database in "/home/merc/.var/app/org.nickvision.tubeconverter/config/google-chrome"