-
Notifications
You must be signed in to change notification settings - Fork 11
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
Issue opening file in Flatpak-based browser #23
Comments
The |
I was running into this same issue. On my system, xdg-open is configured to run the flatpak version of Firefox. I suspect that whatever logic is doing this is taking the one html file passed on the command line and sandboxing it into a temporary directory, then passing that to Firefox. I don't know if this is a bug or a WAI from the point of view of flatpak. I also found https://wiki.debian.org/DefaultWebBrowser#Opening_the_default_browser_from_a_script. So, at least on Debian systems, it is most "sensible" to open a browser with pprof, a program run by Google, does something completely different that has always worked for me (but hard codes a preference for Chrome...): https://github.com/google/pprof/blob/f7f687d19a9829062f02a2dd6e9a6fb527dbf143/internal/driver/commands.go#L354 So, my workaround is running commands like The current contens of the
|
Was redirected here from rust-lang/cargo#8428. Given
cargo doc --open
uses this tool internally, seems like taking a look atopener
could help resolve that issue. I'm not familiar with how the two tools interact, although if it helps, when trying to open rust docs, the path that actually loads into the browser looks something like,instead of the locally generated html file.
Using Ubuntu 22.10 with Brave browser flatpak.
The text was updated successfully, but these errors were encountered: