On 2015-11-07 17:18, Alessio Gaeta wrote: > In attach the log you requested. Relevant part is right at the file > head (2015-11-03). The log is in Italian,
somehow I expected this :-) > but it should be quite simple > to guess what's happened... :) and that as well :-) > Reading the log I can see: > > a) errors about diversions while configuring glx-alternative-mesa > (0.7.0) (glx group damaged) > > b) right after, the configuration of glx-alternative-nvidia (0.7.0) > keeps complaining about glx group damaged and then it uses (translated > in English) "/lib/nvidia to supply /usr/lib/glx (glx) in automatic > mode" > > I'm not so expert about glx diversion dance so I cannot help you much, > but I guess that log confirms that the problem resides in a post- > install script of glx-alternative-nvidia 0.7.0. For some reason your nvidia alternative (from nvidia-alternative) had disappeared, cascading to glx-alternative-nvidia before it could be reinstated, therefore cancelling the bumblebee setting. Essentially it's reproducible with update-alternatives --remove-all nvidia dpkg-reconfigure glx-alternative-nvidia dpkg-reconfigure nvidia-alternative dpkg-reconfigure bumblebee-nvidia more realistic with one dpkg run doing configuration: update-alternatives --remove-all nvidia dpkg --unpack /var/cache/apt/archives/glx-alternative-nvidia_0.7.0_amd64.deb dpkg --unpack /var/cache/apt/archives/nvidia-alternative_340.93-7_amd64.deb dpkg --configure --pending dpkg-reconfigure bumblebee-nvidia (the last command is always to restore the initial state) Andreas