Issues with `cargo doc --open`

[kaimast]

Hey all,

I am trying to understand how to use cargo doc locally and not sure if I am encountering a bug or just using it wrong.

When is run cargo doc --open my browser opens to some file store in /run/user/1000/doc/. However that folder only contains an index.html and nothing else.
As a result, I can look at the initial page of the documentation but all links it contains are broken and the style sheet does not seem to load properly either. See the image below:

Cargo version is 1.46.0-nightly (c26576f9a 2020-06-23) but I have experienced this with older versions as well.

[ehuss]

The path /run/user/1000/doc/ looks like something related to systemd?

Normally, when inside a project directory, there is usually a target directory where cargo stores all the output. So typically it would be something like /home/eric/foo/target/doc/…. It looks like maybe you have something intercepting that?

Do you have some sort of nonstandard configuration? I'm not too familiar with systemd.

[kaimast]

It's a standard Ubuntu install. My browser (firefox) is installed through flatpak, but I just switched to a different default browser (epiphany) and have the same issue.

If do cd target/doc/package_name && xdg-open index.html I get the same issue. However cd target/doc/package_name && epiphany index.html works.

Does cargo use xdg-open (or gio open in my case) internally? If so, that might be the culprit.

[ehuss]

Ah, it does use xdg-open. It looks like there is some flatpack-specific code there. Unfortunately I'm not too familiar with flatpack. Maybe this is an issue for the opener package? (Which is what Cargo uses to open the browser.)

[aryzing]

Seems the issue still exists. Default installation of Ubuntu 22.10 + Brave browser flatpak.