Dear Alberto and others, Could you please please backport this fix to the 331 driver, which is the most recent one available for 14.04 LTS (Trusty)? Or at the very least explain why this might not be as trivial as it sounds? This bug impacts a massive amount of Trusty users, and failing to get a graphical interface every time the kernel is upgraded is quite high-profile; a lot of people are abandoning Ubuntu altogether for it. Our whole workplace may do so soon because one of the programs we use professionally requires the proprietary Nvidia driver and our support people cannot afford the time commitment to have everyone use the non-LTS branches.
I also feel I need to point out that the "users affected" and bug heat of this report ( lp:1431753 ) are misleadingly low. Most of the users who trigger this bug land at lp:1268257 . If you look at the stats of *that* bug and all the recent comments, the whole affair starts to look like a trainwreck. We tried to make lp:1268257 a duplicate of this bug ( lp:1431753 ), which would presumably bump the latter to the top of the priority list, but were prevented from doing so by a bug in Launchpad itself ( lp:1450251 ). -- 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
