dist-upgrade fails if /tmp is non-executable (mounted as noexec)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Fix Released
|
Medium
|
Michael Vogt |
Bug Description
Binary package hint: update-manager
On a Gutsy system where /tmp is non-executable (mounted with the noexec flag), update-manager refuses to upgrade to Hardy with the following error message on the command-line:
extracting '/tmp/tmp71EIa8
authenticate '/tmp/tmp71EIa8
Traceback (most recent call last):
File "/usr/lib/
fetcher.run()
File "/usr/lib/
self.
File "/usr/lib/
os.
OSError: [Errno 13] Permission non accordée
(Note that it works fine when upgrading normal packages.)
I suggest two things:
1- Check to see if the file can be executed and returning a more user-friendly error message when it isn't.
2- Create a temporary directory in the current directory as a fallback when /tmp cannot be used.
Of course, it would be nice if it did work (see #2), but I would also consider this problem solved if a nice (graphical) error message was displayed to the user (see #1).
Related branches
Changed in update-manager: | |
status: | Confirmed → Triaged |
Changed in update-manager: | |
assignee: | nobody → mvo |
milestone: | later → none |
status: | Triaged → Fix Committed |
Thanks for your bugreport.
This is indeed a problem, unfortunately we will not be able to fix it for hardy (too close to the release) but we will add a note into the release-notes.