Dear Maintainer,
I have debian jessie installed on my lenovo y570 with Nvidia Geforce GT 555M. I installed bumblebee package (with nouveau drivers) and whenever I try to run something with optirun or primusrun, I get the following error:

crabman@DebianNotebook:~$ primusrun glxgears
Error: nConfigOptions (11) does not match the actual number of options in
__driConfigOptions (16).
glxgears: ../../../../../../src/mesa/drivers/dri/common/xmlconfig.c:1030: driQueryOptioni: Assertion `cache->info[i].name != ((void *)0)' failed.
Аварийный останов

Running with optirun gives the same error:
crabman@DebianNotebook:~/bumblebee_bugreport$ optirun glxgears
Error: nConfigOptions (11) does not match the actual number of options in
       __driConfigOptions (16).
glxgears: ../../../../../../src/mesa/drivers/dri/common/xmlconfig.c:1030: driQueryOptioni: Assertion `cache->info[i].name != ((void *)0)' failed.

I am sending the archive provided by bumblebee-bugreport attached

reassign 723733 primus 0~20130805-1
affects 723733 bumblebee
severity 723733 serious
notforwarded 723733
tags 723733 - upstream
thanks

Hi,

I also have this problem (Intel HD + Nvidia Geforce GT 555M + bumblebee
+ nouveau):

$ optirun glxgears
Error: nConfigOptions (11) does not match the actual number of options in
        __driConfigOptions (16).
glxgears:
../../../../../../src/mesa/drivers/dri/common/xmlconfig.c:1030:
driQueryOptioni: Assertion `cache->info[i].name != ((void *)0)' failed.

This is a bug in primus, since bumblebee works with virtualgl (not in
Debian any more), but not with primus, as indicated in the following
upstream bugs:
https://github.com/amonakov/primus/issues/107
https://github.com/amonakov/primus/issues/68

Furthermore these upstream bugs are closed, for the following reason
stated by the developer amonakov (
https://github.com/amonakov/primus/issues/68#issuecomment-14456073 ):
     "I previously told that other people are not seeing this because
Ubuntu enables assertions, but having looked at their debian/ files, I'd
say it probably due to their patches."

Since Ubuntu does not apply any patches to the Debian package (at least
they use a Debian version), this needs to be fixed in the
Debian-specific patches applied to primus. Therefore forwarding is of
little use here.

I'm setting the severity to serious, because this bug makes it
impossible to use bumblebee/primus with nouveau.

Best regards,
Andreas

# downgrade from RC severity
severity 723733 important
forwarded 723733 https://github.com/Bumblebee-Project/Bumblebee/issues/476
thanks

Hi,
Debian. AFAIU, upstream is referring to a patch or some other issue in
mesa, so it's out of my control anyways.

Just to quote upstream (#bumblebee-dev on freenode):
<amonakov> I'd rather prefer if people using Nouveau learned DRI_PRIME
and xrandr offload (less overhead!)

I would also recommend using DRI_PRIME [1] if you prefer using
nouveau, and take advantage of support directly in the kernel rather
than relying on bumblebee. The required userspace components,
including an up-to-date X server, have just recently made it into
testing/unstable, and there have been reports of other Debian users
getting it to work successfully [2].

Regards,
Vincent

[1] http://nouveau.freedesktop.org/wiki/Optimus/
[2] http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2013-October/009404.html

Hi,

thanks for looking into this.
It is a great idea to use nouveau with DRI_PRIME. The problem with this
is, that it does not really work, because power management is not (yet)
implemented. So this does not save any power, which was the whole idea
of the Optimus technology.

But I do not understand, why you think that this bug is not release
critical: It makes the package bumblebee completely unusable with
nouveau, although this worked in the past.

In my opinion one of the following actions should be take:
a) Fix bumblebee/primus/mesa/... so that primus works with nouveau.
b) Include the virtualgl package again in Debian, since
bumblebee/virtualgl/nouveau seem to work together.
c) Remove the nouveau support from the bumblebee package, because it
just does not work.

I would prefer option a), but b) is probably easier, since that was how
it worked in the past. If (in the long run) DRI_PRIME is improved, so
that it supports power management, option c) could be considered as well.

Best regards,
Andreas

Upstream has no plans to do so, and I myself don't have the
prerequisite knowledge to fix this. Changing the severity of this bug
report won't change the above.

On my todo list.

In the long run, c) (i.e. removal of bbswitch/bumblebee/primus) is
what will happen anyways; bumblebee is a hack-ish solution in place
until the kernel + userspace has proper Optimus support.

Vincent

Hi,

Sadly, I also don't have the knowledge to fix this.

I think this bug report can be closed, when virtualgl is back in Debian.
much better then none.

Best regards,
Andreas