desktop-packages team mailing list archive

["Alexander Chr. Tornow" <aquablue25@xxxxxxx>]

@teo1978:

Yeah, I fully agree. I recommended Ubuntu LTS to everyone I know that
has been willing to either give Ubuntu a try or to users that have
completely switched from Windows. My words, after they asked me why I
recommend LTS over normal Ubuntu: "Use LTS if you prefer stability,
support and reliability."

And now I am eating my own words.

It's nice to see this bug is getting fixed... finally... but it's sad it
took so long in the first place. A lot of my friends were left with an
unstable or malfunctioning system and that's a real show stopping issue,
especially because the issue came unexpected after updating the system
as usual. Ever since reporting this bug, I have switched to an AMD 6000
series GPU, using the open and free AMD drivers Ubuntu ships and
activates at default. It's been awesome so far, gaming-wise as well.

So, personally, I am not going to lose any sleep over this issue
anymore. But my friends are still using Nvidia hardware + Ubuntu
14.04.2/3 LTS and I'd like to know if the faulty Nvidia drivers (331.x?)
available via the Ubuntu repos have been replaced with the drivers
mentioned in this bug report that include the fix - or is the solution
to activate the unstable testing/proposed repo the only way out of this
mess?

Any kind of feedback is appreciated!

Thanks!

Cheers,
Alex

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 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:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

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