[Bug 21959] New: adept package alterations fail when root doesn't have read access to homdir

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=21959
Ubuntu | adept

           Summary: adept package alterations fail when root doesn't have
                    read access to homdir
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: adept
        AssignedTo: jriddell at ubuntu.com
        ReportedBy: mr-russ at pws.com.au
         QAContact: kubuntu-bugs at lists.ubuntu.com


If you mount your home directory over NFS, which I do, and for security enable
root squash on that export, root does not have access to folders, he may not
even have access to read from some of those folders like my homedirectory, only
execute rights.

When adept installs packages and launches dpkg rm fails as below, and only the
first package is installed.  Either the error needs to be ignored, or the
command line part of adept run from a location that root has access to.

Starting adept in different ways stops the problem from happening.

eg.
Bug happens when:  mypc ~$ kdesu adept
Bug does not happen when: mypc /tmp$ kdesu adept

Output from command line follows, please ignore typos as you can't copy paste
from that terminal.

Preconfiguring packages ...
rm: cannot get current direcory: Permissions denied
dpkg: error processing /var/cache/apt/archives/hping2_2.rc3-3_i386.dev (--unpack):
 subprocess rm cleanup return error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/hping2_2.rc3-3_i386.deb
dpkg run finished!

...

Dialog from adept says

"There was an error commiting changes. Possibly there was a problem downloading
some packages or the commit would break packages."

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.