desktop-packages team mailing list archive

[teo1978 <teo8976@xxxxxxxxx>]

> Such work is not "necessary", as yours is really an unsupported corner
> case. If you insist on keeping the nvidia driver installed and disabled,
> against what we recommend, that is your problem.

And how was I supposed to know what you "recommend"?

Back in the days when I installed Ubuntu on my machine, there was a friendly interface somewhere like "Software & Updates" > "Additional Drivers" or something, where I could choose to install and use the NVidia drivers.
Then, when I saw they wouldn't work, I went to the same interface and chose not to use them. No warning appeared telling me that was "not recommended" or that I should uninstall the drivers.

Should I have read the whole Ubuntu documentation, like "Let's see if
what I just did through the standard interface is not recommended, and
if they recommend doing something else like uninstalling the driver".

It's not that I "insist" in keeping the driver installed and disabled. I
did that ages ago and forgot about it. And I very much doubt it's that
much of a "corner case". Right in this thread you have another user to
whom the exact same thing happened.

And even if we are few, we got in our situation by just using what then
was the user interface (I mean, we didn't tinkle and mess around with
stuff), so if we got to a situation that was not supported, something
was wrong in Ubuntu in the first place, and if we got into a situation
which was then supported and then stopped being, then it's Ubuntu
responsibility to make sure that automatic updates take that into
account and keep things working.


And also, if a piece of software is designed in such a way that if you stop using it yoy have to uninstall it otherwise it may be harmful, it is badly designed.

-- 
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:
  Invalid
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Invalid
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:
  Invalid
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Invalid
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