[Critical] The 17.3 upgrade breaks nvidia-352-updates (and all the others nvidia proprietary drivers as well)

[Marcin Mielniczuk]

I've been happily running Mint 17.2 Cinnmaon with the proprietary nvidia driver. Yesterday I upgraded to 17.3. After a reboot I was greeted by a black screen.

After switching to tty and removing nvidia-352-updates I was able to log in back again. After installing the nvidia drivers back - a black screen again.

[Meiden (revolcon69)]

Same problem here. I've discovered that the black screen disappears after almost 10 minutes waiting, and then you're able to use the system as usually.

It boots normally adding 'nomodeset' on boot, but it sets fallback mode without hw acceleration.

It boots normally installing nouveau driver instead of nvidia-* proprietary driver.

[Hemanth Kumar (hemanthkumar)]

For me the nouveau driver gives problems and falls to rendering mode after upgrading 17.3 cinnamon. But i had no problems with nvidia proprietary driver in 17.2 or even after upgrading to 17.3 cinnamon.
Kernel: 4.2.0-19-generic x86_64 (64 bit)
Desktop: Cinnamon 2.8.6 Distro: Linux Mint 17.3 Rosa
NVIDIA 340.96 from driver manager

[Lucas (lagolucas)]

I can confirm the same issues after updating Mint 17.3 from 17.2 KDE. Running Nvidia PRIME with drivers 352, 340 (from Drivers Manager), and same as Hemanth Kumar with the nouveau.

I noticed that if you blindly type your password during the "black screen" you can login to your session. Then everything looks normal and works well with Nvidia drivers. I haven't waited for the 10min though.

[Marcin Mielniczuk (marmistrz)]

Reported against Bumblebee, some more details added here: https://github.com/Bumblebee-Project/Bumblebee/issues/734

[Marcin Mielniczuk (marmistrz)]

It comes out that Bumblebee has to be configured manually. Quoting my post on GH

Ok, found the reason myself. I had to adjust /etc/bumblebee/bumblebee.conf for nvidia-352-updates and blacklist the module in /etc/modprobe.d/bumblebee.conf. Now everything works ok.