Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

[Luca Boccassi]

On Tue, 2019-06-11 at 00:21 +0200, Andreas Beckmann wrote:
> On 07/06/2019 18.12, Luca Boccassi wrote:
> > Hi, this should be the list:
> > 
> > bbswitch bumblebee bumblebee-nvidia primus primus-libs primus-libs-
> > ia32 
> > nvidia-driver-libs-nonglvnd nvidia-driver-libs-nonglvnd-i386
> 
> Is this documented somewhere?
> 
> This can be minimized to
>   apt-get install --install-recommends \
>     nvidia-driver-libs-nonglvnd bumblebee-nvidia primus
> if i386 is available as a foreign architecture.
> 
> That makes me think: should we have a primus-nvidia metapackage that
> depends on these packages?
> 
> Which component in this stack did not work with libgl1-nvidia-glvnd-
> glx?
> According to the existing Breaks this should be primus ...
> 
> Running
>   apt-get install --install-recommends bumblebee-nvidia primus
> in a minimal *stretch* chroot results in the installation of
>   nvidia-driver nvidia-driver-libs libgl1-glvnd-nvidia-glx ...
> which does not give a working setup?
> 
> Running
>   apt-get install --install-recommends bumblebee-nvidia primus
> in a minimal *buster* chroot results in the installation of
> nvidia-kernel-dkms, but no driver or library components, which does
> not
> sound useful either.
> 
> I'll send some piuparts logs to this bug later, dropping all Cc:s.
> Testing stretch->buster upgrades with
> * foreign arch i386 enabled and
> * --install-recommends enabled
> of the package set nvidia-driver-libs-nonglvnd bumblebee-nvidia
> primus
> did not show problems. It pulled in some legacy-390xx packages, but
> not
> the 390xx driver itself. It will be hard to reproduce the problem
> people
> exerienced with some transient set of packages from testing
> installed.
> 
> We will probably have to review the Depends/Recommends/Suggests in
> the
> bumblebee and primus packages ... to better cope with the driver:i386
> removal.
> 
> 
> Andreas

In theory, "apt install bumblebee-nvidia" should do the right thing.
The problem is that we can't depend directly from primus-libs to
nvidia-driver-libs-nonglvnd as the former is in main and the latter in
non-free, so at the moment we try to "nudge" apt with breaks and
suggests:

Breaks:
 libgl1-nvidia-glvnd-glx (>= 0),
 nvidia-driver-libs (>= 0),
 libgl1-nvidia-legacy-390xx-glvnd-glx (>= 0),
 nvidia-legacy-390xx-driver-libs (>= 0),
Suggests:
 nvidia-driver-libs-nonglvnd | nvidia-legacy-390xx-driver-libs-nonglvnd

This obviously doesn't seem to work reliably all the time...

Originally the point of bumblebee and primus in main was that they were
needed for the noveau stack as well. But nowadays as far as I know
DRI_PRIME is the better choice for noveau, for recent hardware. I
wonder if we should simply move primus and bumblebee to non-free so
that we can have a working set of dependencies?

But also note that upstream is going to deprecate non-glvnd after 430,
so optimus users will be stuck with whatever legacy release we cut
before that:

https://devtalk.nvidia.com/default/topic/1032650/linux/unix-graphics-feature-deprecation-schedule/

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-nvidia-devel/attachments/20190611/8d2f8f90/attachment.sig>