gedit snap fails to save or open files in miscellaneous directories including dot-folders, ~/bin, and system folders.

[Paddy Landau]

The snap version of gedit prevents viewing and editing files outside a strictly limited set of folders. For example, it cannot change files in standard folders ~/bin, ~/.local, ~/.config, ~/.ssh, or standard files such as ~/.bashrc or ~/.profile. Even "sudo -H gedit /etc/fstab" doesn't work. Using sudoedit doesn't work, as access to /var/tmp is rejected.

EDIT: ~/bin is now available to gedit. EDIT: Nope, not any more.

As there is a bug in the non-snap versions [1], the snap version is important, but sadly it is unusable for a certain number of cases.

I understand that the only solution is to make gedit available in classic confinement.

Please would you do this.

Thank you

[1] https://gitlab.gnome.org/GNOME/gedit/-/issues/361

[Sebastien Bacher (seb128)]

Thank you for your bug report, what error do you get when trying to edit a file in ~/bin? Standard folders in the userdir should be working. Restriction to dot directories is a know limitation though...

[Paddy Landau (paddy-landau)]

@seb128 — I can load files from ~/bin, but when I try to save, I get this error (screenshot attached):

Could not save the file "/home/paddy/bin/myscript".
You do not have the permissions necessary to save the file. Please check that you typed the location correctly and try again.

The same is true for others such as ~/.local/ or ~/.bashrc, and for system files loaded with "sudo -H gedit".

[Paddy Landau (paddy-landau)]

@seb128 — Correction to my previous post: For system folders, I cannot even load files.

[Launchpad Janitor (janitor)]

[Expired for gedit (Ubuntu) because there has been no activity for 60 days.]

[Paddy Landau (paddy-landau)]

Please don't expire this request.

The problem still exists in full.

[Sebastien Bacher (seb128)]

Using desktop portals would give access to the dot files, the fileselector changes needed were reverted in https://gitlab.gnome.org/GNOME/gedit/-/commit/74e0be7e though and need some extra work before landing again. While that would solve the described problem it would probably not cover people wanting to edit system files using sudo which would work under classic