Invoke sudo and present password prompt when permission is denied to write to a file
Bug #782355 reported by
Mike Doherty
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Invalid
|
Undecided
|
Unassigned | ||
nano |
Unknown
|
Unknown
|
|||
vim |
New
|
Undecided
|
Unassigned | ||
nano (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
vim (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nano
If a user can read but not write a file, as often happens with system configuration files, then they need to be root or use sudo to edit the file. If they forget, they won't notice until they're presented with a permission error when attempting to save. This can result in lost work for new users who don't know how to save the edited file elsewhere.
Nano should offer to invoke sudo and present the password prompt to gain the elevated privileges needed in these cases.
description: | updated |
Changed in vim (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
Thank you for reporting this issue and bringing it to our attention. However, this bug is not a valid paper cut, as a paper cut should be a small usability issue, in the default or featured applications, that affects many users and is quick and easy to fix.
Therefore this bug cannot be addressed as part of the One Hundred Paper Cuts project.
Gedit 3 already pops up a proper dialog that 'the current user doesn't have permissions to edit this file'. And you filed this bug against nano. We don't expect end-users to go use Nano for text editing. /wiki.ubuntu. com/PaperCut>.
For further info about the paper cut criteria, please read <https:/
Don't worry though, This bug has been marked as "Invalid" ONLY in the One Hundred Paper Cuts project.