Opera creating strange paths to files on the computer

[E-opera]

E-opera @burnout426 last edited by

@burnout426 flatpak

[leocg]

leocg Moderator Volunteer @E-opera last edited by

@E-opera It means that it's something from Chromium and not from Opera. So, if it needs to be fixed, Chromium needs to do that.

[E-opera]

E-opera @leocg last edited by

@leocg So, is Opera based on chromium?

[leocg]

leocg Moderator Volunteer @E-opera last edited by

@E-opera Yes. I guess 8 out of 10 browsers are based on Chromium nowadays

[E-opera]

E-opera @leocg last edited by

@leocg To review: my original question was, why does Opera show this strange path when I load an image from my computer and then Opera is not abe to re-open the image when I restart?
The answer is that it's a bug in Chromium, on which Opera is based?

[leocg]

leocg Moderator Volunteer @E-opera last edited by

@E-opera Based on what your are saying, it seems to be a Chromium issue.

How are you opening the image on the browser? Are you opening from inside the browser? Are you dragging the file to the browser window?

[leocg]

leocg Moderator Volunteer @E-opera last edited by

@E-opera I can't reproduce it on Windows, so it may be a Linux specific bug.

[E-opera]

E-opera @leocg last edited by

@leocg To open the image in Opera, I right-click the file in "files" (nemo) and choose 'open with Opera.'

When I try to paste in the full path into the Opera search bar, to open inside Opera, it tells me:

Your file couldn’t be accessed
It may have been moved, edited, or deleted.

 ERR_FILE_NOT_FOUND

Pasting in the full path in Firefox works right.

[burnout426]

burnout426 Volunteer @E-opera last edited by

@E-opera it might be sue to how Flatpak packages handle things. To test, try to see if it happens with the RPM package of Opera too or not.

[E-opera]

E-opera @burnout426 last edited by

@burnout426 I wondered if there was something about the directory the strange path points to, and I asked DuckDuckGo, "fedora what is the "/run/user/1000/doc" directory for"

I got this answer, which seems to clear things up:

"The /run/user/1000/doc directory is a portal that allows applications to access files outside of their sandbox in Fedora, particularly for applications installed via Flatpak. It is used to manage temporary file access for user applications."

However, it doesn't explain why Chromium and Opera can't reopen the file after the browser reopens. It remembers the path but can't open the image at that location. Presumably that's a feature (a "temporary" file) and not a bug. I'll have to trust Flatpak on that.

Thanks to all for your suggestions.