Guys it's a closed source driver. I'm being a hypocrite here, but chillax. On 14 Aug 2015 21:16, "teo1978" <teo8...@gmail.com> wrote:
> > > 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. > > > > Ok, that implies that all drivers are badly designed. It's your opinion. > > Don't pretend you are stupid when you aren't. This driver used to have an > option (nicely accessible through user interface) which allowed to just not > use it. It was *designed* to be either used or not used. And when not used, > it would do nothing and interfere with nothing. > So, the newer version doesn't that anymore? Then you can't replace one > version with another without performing some check. The update is > incomplete and buggy if it does that. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1411195). > 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 > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
