Bumblebee is not blacklisting all avaliable nvidia drivers

[Stunts]

In the Ubuntu repositories the following versions of the nvidia driver can be found (that are relevant for nvidia optimus support):
304
310
313
319
331
340
346
352

However, bumblebee is not blacklisting all of these modules (it only blacklists everything up to 331, leaving 340, 346 and 352 out).
This means that for any recent card that is not supported with 331 and below, where the more recent drivers are required, installing the nvidia driver (say - nvidia-346) to use with bumblebee will result in a black screen at boot, since X will try to start using the nvidia driver, which is not connected to a display.

Attached is a proposed "/etc/modprobe.d/bumbebee.conf" that contains the necessary blacklist items. Please let me know if you would prefer this to be in "patch" format.

This bug should affect any users with an nvidia optimus laptop with any cards above nvidia GT6xx (roughly, as marketing names are not always based on the same chips).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Vincent Cheng (vincent-c)]

Blacklist updated for nvidia versions up to 364 in bumblebee/3.2.1-11.

[Stunts (f-pinamartins)]

Will bumblebee 3.2.1-11 be available in Trusty and Xenial?

[Vincent Cheng (vincent-c)]

It's currently available from the bumblebee testing PPA (https://launchpad.net/~bumblebee/+archive/ubuntu/testing) and will be made available soon in the stable PPA, but no, I have no plans on pushing an update via trusty/xenial-updates.

[Stunts (f-pinamartins)]

Oh, that's too bad.
I guess Ubuntu will remain broken on any optimus laptop after Q4 2013...
Were there many changes besides this one?
Or it trying to push the package to trusty/xenial-updates just too much of an hassle?
(I remember submitting a patch to the clustalx package some years ago and it was *a lot* of work)
I'm no criticizing or anything, I'm very grateful you maintain the PPA. I'm just wondering about the "why?" of it.

[Vincent Cheng (vincent-c)]

I just don't think this bug is important enough to be worth cherrypicking back to pre-yakkety systems; there's frankly a host of other bumblebee and packaging related issues that are probably just as important, if not more so, and I think they fall out of scope of a SRU (and yes, there's been a ton of packaging changes, see http://metadata.ftp-master.debian.org/changelogs/main/b/bumblebee/unstable_changelog). For this particular bug, users who do not know what bumblebee is are unlikely to install it in the first place, and there's a simple workaround: "sudo apt-get purge bumblebee bumblebee-nvidia" instead of just "sudo apt-get remove bumblebee bumblebee-nvidia".

If you're interested in pushing this yourself for trusty/xenial, you can check out the SRU documentation at https://wiki.ubuntu.com/StableReleaseUpdates

[Stunts (f-pinamartins)]

Thank you, Vincent.
For both the explanation, and the links.
I completely understand the point you make.