8000 Error when opening a folder, because of missing `/app/share/ide-flatpak-wrapper` · Issue #438 · flathub/com.vscodium.codium · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Error when opening a folder, because of missing /app/share/ide-flatpak-wrapper #438

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.

Sign up for GitHub

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

Jump to bottom
Open
Ferenc- opened this issue Apr 29, 2025 · 13 comments
Open

Error when opening a folder, because of missing /app/share/ide-flatpak-wrapper #438

Ferenc- opened this issue Apr 29, 2025 · 13 comments
Assignees
@noonsleeper

Comments

@Ferenc-
Copy link
Contributor
Ferenc- commented Apr 29, 2025 
[270:0429/174642.548987:INFO:CONSOLE(35)] "%cTRACE color: #888 CommandService#executeCommand workbench.action.files.openFolder", source: vscode-file://vscode-app/app/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js (35)
[main 2025-04-29T15:46:42.550Z] [DialogMainService]: request to acquire file dialog lock {
  title: 'Open Folder',
  buttonLabel: undefined,
  filters: undefined,
  defaultPath: '/app/share/ide-flatpak-wrapper',
  properties: [ 'multiSelections', 'openDirectory', 'createDirectory' ]
}
[main 2025-04-29T15:46:42.550Z] [DialogMainService]: new file dialog lock created {
  title: 'Open Folder',
  buttonLabel: undefined,
  filters: undefined,
  defaultPath: '/app/share/ide-flatpak-wrapper',
  properties: [ 'multiSelections', 'openDirectory', 'createDirectory' ]
}

Image

This path obviously exists inside of the flatpak, but codium is looking for this path on the host...
@noonsleeper noonsleeper self-assigned this Apr 30, 2025
@noonsleeper
Copy link
Collaborator

Hi @Ferenc-, Could you add to your report distro, flatpak version, your flatpak overrides, and if you can run first flatpak repair and sudo flatpak repair?

@Ferenc-
Copy link
Contributor Author
Ferenc- commented May 2, 2025

@noonsleeper
Thanks for your answer.
I haven't noticed correlation with any of those, I have seen this with with Fedora 41 and 42.
It's the latest Flatpak 1.16.0 in all cases. There are no overrides. And flatpak repair made no difference.

BTW, after pressing "OK", on this initial error message, it is still possible to select a folder from the host filesystem,
and next time when opening a folder the error message doesn't appear, unless one restarts and removes rm -rf ~/.var/app/com.vscodium.codium.
Perhaps that helps with the reproduction.
If not, then I could put together a VM for reproducing if that would be useful.

@noonsleeper
Copy link
Collaborator

I'm currently developing this on F41/F42 (silverblue) and not see that, I will create a fresh F42 vm to see if I can replicate that behaviour, thanks for your report!

@jeromebrenier
Copy link
jeromebrenier commented May 3, 2025 •
edited
Loading

I have exactly the same problem on a fully updated Ubuntu 25.04 (flatpak 1.16.0).

@noonsleeper
Copy link
Collaborator

Test on a fresh F42 vm:
Image

and the same with ubuntu 25.04:

Image

Could both of you try to install flatseal and look if there is something messing within the PATH env variable, or maybe do you have a modified PATH env on your local?

@jeromebrenier
Copy link

I don't know what caused this, but I've checked and the problem is no more present here. Sorry for the noise.

@Ferenc-
Copy link
Contributor Author
Ferenc- commented May 4, 2025

@noonsleeper It is still 100% reproducible on my end. Are you clicking this button?

Image

Should I upload a video?

@noonsleeper
Copy link
Collaborator

@Ferenc- finally I reproduced the problem, is something that I saw on other flathub app, is a problem on portals side not on the app since the work directory is indeed /app/share/ide-flatpak-wrapper but portals do not have access inside the container.

@noonsleeper
Copy link
Collaborator
noonsleeper commented May 4, 2025 •
edited
Loading

@daiyam sorry to bother but did you know if there is a way to set up the default directory to maybe $HOME?

@daiyam
Copy link
Collaborator
daiyam commented May 5, 2025

I know about nothing about how flatpak and portals are working but I found this article: https://who-t.blogspot.com/2021/08/flatpak-portals-how-do-they-work.html
8000 Then I remembered that, a few months ago, we had an issue with XDG and it was fixed with an update of Electron.
I found 2 new PRs related to XDG:

I will have to track those and be sure that the next version use an Electron with those PRs.

Have you tried the Insiders if it has the issue?
I will try to push a new version with v35.2.2 (with first PR).

@daiyam
Copy link
Collaborator
daiyam commented May 6, 2025

Can you try https://github.com/VSCodium/vscodium-insiders/releases/tag/1.100.03044-insider?
It uses Electron-v34.5.4 (I mess up the version number in my previous message) and includes the first mentioned PR.
The second one seems to not apply to v34...

@Ferenc-
Copy link
Contributor Author
Ferenc- commented May 7, 2025

@daiyam I have tried flatpak install --user https://dl.flathub.org/build-repo/183301/com.vscodium.codium-insiders.flatpakref from flathub/com.vscodium.codium-insiders#95, makes no difference.

@noonsleeper
Copy link
Collaborator

Hi, sorry for the late response, thanks @daiyam again for your effort!
I found why this behaviour appeared.

  1. on first start the wrapper check if is the first time looking for .var/app/com.vscodium.codium-insiders/config/flatpak-vscodium-insiders-first-run if this file isn't found then open /app/share/ide-flatpak-wrapper/README.md like you notice, that set the default path to /app/share/ide-flatpak-wrapper/, these was set to help people to get easy first steps with codium under flatpak.

The most important thing here is the recent changes on Gnome file explorer, is the explorer that show that dialog complaining about not able to found the directory this did not happen as example on KDE file explorer, it did not complain about it at all and open / as default

Image

And that is why this happened on both distros, the same DE.
I don't know if this kind of behaviour could be disabled on gnome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@noonsleeper noonsleeper

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@daiyam @Ferenc- @jeromebrenier @noonsleeper
0