Bug#876033: primusrun doesn't find libGL.so.1
bluca at debian.org
Wed Oct 11 09:46:55 UTC 2017
On Thu, 2017-10-05 at 18:24 +0100, Luca Boccassi wrote:
> On Thu, 2017-10-05 at 19:08 +0200, Gunman wrote:
> > On 04.10.2017 00:22, Luca Boccassi wrote:
> > > Unfortunately the problem can't be reproduced on Stretch given
> > > there's
> > > no glvnd there. At the moment I do not have a Sid installation on
> > > hardware that supports optimus, unfortunately, sorry. I'll try to
> > > find
> > > time to install it on one of my laptops in the next couple of
> > > weeks.
> > Would probably be interesting to install Stretch and then update to
> > SID.
> > > Instead of symlinking the file, could you please try to edit the
> > > LibraryPath line in /etc/bumblebee/bumblebee.conf and add
> > >
> > > :/usr/lib/x86_64-linux-gnu:/usr/lib/i386-linux-gnu
> > >
> > > to it? Then systemctl restart bumblebeed.service
> > That works too, with the __GLVND_DISALLOW_PATCHING=1. Without it,
> > it
> > still gives a black screen/window.
> Great, thanks for confirming.
> > > It would be tricky to ship it in the packages, as without the
> > > glvnd
> > > it
> > > would actually break it.
> > Would it be easier/cleaner to create a second package? primus-glvnd
> > for
> > example? So for the legacy drivers one still could use primus and
> > for
> > the mesa-glvnd one would have to use primus-glvnd.
> The problem is that the config file belongs to bumblebee rather than
> primus. Also optirun -b primus will have the same problem. It also
> makes installing the whole stack more complicated - right now one can
> apt install bumblebee-nvidia and everything will be there.
> > > What if, as an interim solution to avoid breakages, I added a
> > > Conflicts
> > > with libgl1-glvnd-nvidia-glx on primuslibs, so that the non-glvnd
> > > packages will get pulled in automatically when using bumblebee?
> > For me that package is not installed and pretty much uninstallable
> > anyway. Or did you mean libgl1-nvida-glvnd-glx?
> Yes sorry, that one.
I've uploaded to Sid a change that adds this Breaks. I did a few tests
with upgrades and clean installs with apt and aptitude and it looked
like it was fine.
Please let me know if there are any issues.
Long term, the only easy to maintain solution I can see (until there is
proper support upstream for GLVND) would be to change the config in a
postinst, depending on what package is installed. But that feels very
wrong (changing config files) and very fragile.
What do you think?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: This is a digitally signed message part
More information about the pkg-nvidia-devel