desktop-packages team mailing list archive

["rbscycle@xxxxxxxx" <rbscycle@xxxxxxxx>]

That may be so.  However, I care.  I use Linux as my everyday computer 
at home for everything.  I use the "LTS" version because I expect less 
problems, and don't really know a hell-of-a-lot about the "underneath" 
workings of Linux.  If this means I have to go to another distribution, 
so be it.


On 15-06-18 03:09 PM, Kristian Erik Hermansen wrote:
> No vendor cares about linux
> On Thu, Jun 18, 2015 at 11:46 AM Heath <HeathNaylor@xxxxxxxxx> wrote:
>
>> This seems to me like a trivial bug fix, is this just nVidia not wanting
>> to devote time to a fix?
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1405694).
>> https://bugs.launchpad.net/bugs/1431753
>>
>> Title:
>>    Nvidia binary driver FTBS due to DKMS layer violation
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
>>

--


** Attachment added: "ronnie6.png"
   https://bugs.launchpad.net/bugs/1431753/+attachment/4416893/+files/ronnie6.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions