| 2020-09-28 12:14:28 |
Paddy Landau |
bug |
|
|
added bug |
| 2020-09-28 14:01:15 |
Paddy Landau |
description |
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 folder ~/bin, or standard files such as ~/.bashrc. Even "sudo -H gedit /etc/fstab" doesn't work.
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 |
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 folder ~/bin or ~/.local or ~/.config, or standard files such as ~/.bashrc. Even "sudo -H gedit /etc/fstab" doesn't work.
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 |
|
| 2020-09-28 14:01:56 |
Paddy Landau |
description |
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 folder ~/bin or ~/.local or ~/.config, or standard files such as ~/.bashrc. Even "sudo -H gedit /etc/fstab" doesn't work.
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 |
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 or ~/.local or ~/.config, or standard files such as ~/.bashrc or ~/.profile. Even "sudo -H gedit /etc/fstab" doesn't work.
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 |
|
| 2020-09-28 14:25:54 |
Sebastien Bacher |
gedit (Ubuntu): importance |
Undecided |
Low |
|
| 2020-09-28 14:25:54 |
Sebastien Bacher |
gedit (Ubuntu): status |
New |
Incomplete |
|
| 2020-09-28 14:26:00 |
Sebastien Bacher |
tags |
|
snap |
|
| 2020-09-28 15:51:02 |
Paddy Landau |
attachment added |
|
Screenshot of error when trying to save https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+attachment/5414989/+files/Save%20to%20bin%20error.png |
|
| 2020-11-28 04:17:22 |
Launchpad Janitor |
gedit (Ubuntu): status |
Incomplete |
Expired |
|
| 2020-11-28 11:48:58 |
Paddy Landau |
gedit (Ubuntu): status |
Expired |
New |
|
| 2020-11-30 09:23:40 |
Sebastien Bacher |
gedit (Ubuntu): status |
New |
Triaged |
|
| 2020-11-30 19:56:20 |
Sebastien Bacher |
summary |
gedit needs classic confinement |
gedit snap fails to open fails in user dot directories |
|
| 2020-12-01 10:44:05 |
Paddy Landau |
summary |
gedit snap fails to open fails in user dot directories |
gedit snap fails to save or open files in miscellaneous directories including dot-folders, ~/bin, and system folders. |
|
| 2022-09-12 07:01:10 |
Paddy Landau |
description |
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 or ~/.local or ~/.config, or standard files such as ~/.bashrc or ~/.profile. Even "sudo -H gedit /etc/fstab" doesn't work.
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 |
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 or ~/.local or ~/.config, 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.
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 |
|
| 2022-09-15 07:37:18 |
Paddy Landau |
description |
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 or ~/.local or ~/.config, 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.
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 |
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.
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 |
|
| 2022-09-19 12:52:29 |
Paddy Landau |
description |
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.
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 |
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 |
|
