I did'nt go with both ways at the same time.
But I could not go the .deb only way, because the nvidia-glx-new 100.11.14 package is still incomplete (#98641) and I can see this one kind of depends on #98641 and perhaps other nvidia-glx-* bugs.
And there is of course the possibility that the final nvidia-glx-new package might fix this module problem, too.
Is there (in launchpad) a way to let this issue depend on i.e. #98641 (and put this "on hold") or do you prefer to close this bug and I just open a new bug in case an otherwise clean nvidia-glx-new/restricted-modules combination should not solve this old-module problem?
I did'nt go with both ways at the same time.
But I could not go the .deb only way, because the nvidia-glx-new 100.11.14 package is still incomplete (#98641) and I can see this one kind of depends on #98641 and perhaps other nvidia-glx-* bugs.
And there is of course the possibility that the final nvidia-glx-new package might fix this module problem, too.
Is there (in launchpad) a way to let this issue depend on i.e. #98641 (and put this "on hold") or do you prefer to close this bug and I just open a new bug in case an otherwise clean nvidia- glx-new/ restricted- modules combination should not solve this old-module problem?