desktop-packages team mailing list archive

[Simon Reed <Xubuntu@xxxxxxxxxxxxx>]

"To be fair it is an annoying issue but not one that is so fatal one
would not be able to recover a system."

It leaves the system not working.  That's is more than just annoying.
Also, I actually did re-install the operating system at least once
because of this bug to try to get this PC working again.  I actually
spent about three days struggling with driver versions and trying to
work out what the real problem was.  I was also swopping out video cards
to see if that helped.  Any sane person would have gone out and bought a
Windows licence and installed that instead.

"By now I just made it a habit of doing the following…"

Sadly, those instructions are the sort of reason people say Linux is not
ready for the mainstream.  How do I tell Auntie Margaret over the phone
she just needs to "sudo dkms install -m <module> -v <module version> -k
<kernel version>" ?

It might be trivial to an operating systems programmer with a computer
science degree.  But some of us want to USE Ubuntu-based operating
systems for work purposes, not for working on.

I am sorry to add a whinge to this saga, but to imply it's just a
nuisance and there's an easy workaround is not how it feels to some of
the user community.

-- 
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