*** This bug is a duplicate of bug 436039 ***
https://bugs.launchpad.net/bugs/436039
** This bug has been marked a duplicate of bug 436039
DKMS fails to build if a restrictive umask is set
--
DKMS privilege de-escalation breaks compilation
https://bugs.launchpad.net/bugs/454577
You receiv
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
permiss
Can you walk me through the specific commands you've ran from your fresh
install so we can see where the problem is coming up? Dpkg will normally
set permissions and what not itself. DKMS gives up it's permissions when it
runs as ''nobody''
On Sun, Oct 18, 2009 at 16:25, Tomi Pieviläinen
wrote:
It was a fresh install apart from home and hadn't touched anything
manually. I suspect that sudo is taking my users permission umask and
applies it when dkms/dpkg unpacks the headers.
--
DKMS privilege de-escalation breaks compilation
https://bugs.launchpad.net/bugs/454577
You received this bug n
I just looked and the files are yes owned by root, but they are readable by
anyone. Did you change your permissions at all?
On Sun, Oct 18, 2009 at 06:04, Tomi Pieviläinen
wrote:
> Running on Karmic with dkms: 2.1.0.1.
>
> --
> DKMS privilege de-escalation breaks compilation
> https://bugs.launc
Running on Karmic with dkms: 2.1.0.1.
--
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
ubuntu-bugs@lists.ubuntu.com
htt
