This seems to be be the same as bug #436039. The simplest fix would be to explicitly set a permissive umask in the beginning of the DKMS script itself.
Sudo does not reset umask, so if you run "sudo apt-get upgrade" with a restrictive umask set, DKMS will create directories with restricted permissions. DKMS does explicitly set "chmod a+rx" for the *deepest* level of directories in the tree, but this is not enough: if the parent directory is not readable to nobody, then it cannot access any of the sub- directories either. -- DKMS privilege de-escalation breaks compilation https://bugs.launchpad.net/bugs/454577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
