On 14-08-15 10:52:23, teo1978 wrote: > > This, while unfortunate, is not a bug, > > Yes it is. You are only giving a diagnosis of the exact cause of the bug > (which by the way I already knew), but that doesn't make it less of a > bug. >
The alternatives switched back to automatic mode, and in automatic mode the nvidia alternative has a higher priority than mesa's (which is what you want). You can either select the mesa alternative, call ldconfig, and update the initramfs, or uninstall the nvidia package (as I recommended). > > and we cannot change it, due to > > the way alternatives work. > > I seriously doubt that's IMPOSSIBLE to fix. It may not be easy, but if you > can do it manually, it can be done automatically. You only need to produce a > script that looks at the settings (alternatives, or whatever) before > uninstalling the old package, and then applies them (with all the necessary > remappings and modifications) after installing the new one. > It may be a lot of work but it's NECESSARY and it was part of fixing > this issue. A part that hasn't been done. 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. -- 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
