Bug#898391:
This command effectively fixed my issue (I know this is really funny. lol)
sudo apt-get install
{nvidia-driver,xserver-xorg-video-nvidia,nvidia-driver-libs-nonglvnd,nvidia-driver-libs-nonglvnd-i386,nvidia-kernel-dkms}/buster
Bug#898391:
> I did an update just yesterday, and going > apt install -t stretch-backports > nvidia-driver nvidia-driver-libs-nonglvnd worked Thank you again. What repository do you get xserver-xorg-core from? The one in stretch depends on libegl1-mesa | libegl1 which conflict with nvidia-driver-libs-nonglvnd.
Bug#898391:
On Fri, 2018-06-01 at 02:59 -0700, Jorge Moraleda wrote: > > > aptitude will resolve it just fine, apt seems to need a helping hand > > depending on whether you want the glvnd or non-glvnd flavours, > > specify > > one of the nvidia-driver-libs* packages as well as nvidia-driver > > and it > > will upgrade it. > > Dear Luca, > > Thank you for your quick reply. When I try to use aptitude to resolve > the > conflicts, eventually I get to the following problem: > > NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries) > Some dependencies of nvidia-driver-libs (broken, 390.48-2~bpo9+1) are > not > satisfied: > > > * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) > conflicts with libegl1 (> 0) > * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) > conflicts with libegl1-mesa (>= 17) > * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) > conflicts with libgl1 (> 0) > * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) > conflicts with libgl1-mesa-glx (>= 17) > * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) > conflicts with libgles2 (> 0) > * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) > conflicts with libglvnd0 (> 0) > * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) > conflicts with libglx0 (> 0) > * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) > conflicts with libopengl0 (> 0) > > > > I get the same conflicts with the non-GLVND version. I could continue > manually removing the conflicting libraries, but I feel that is the > wrong > path because several unrelated applications complain of missing > dependencies. What do you think? I did an update just yesterday, and going apt install -t stretch- backports nvidia-driver nvidia-driver-libs-nonglvnd worked -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#898391:
> aptitude will resolve it just fine, apt seems to need a helping hand > depending on whether you want the glvnd or non-glvnd flavours, specify > one of the nvidia-driver-libs* packages as well as nvidia-driver and it > will upgrade it. Dear Luca, Thank you for your quick reply. When I try to use aptitude to resolve the conflicts, eventually I get to the following problem: NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries) Some dependencies of nvidia-driver-libs (broken, 390.48-2~bpo9+1) are not satisfied: * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) conflicts with libegl1 (> 0) * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) conflicts with libegl1-mesa (>= 17) * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) conflicts with libgl1 (> 0) * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) conflicts with libgl1-mesa-glx (>= 17) * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) conflicts with libgles2 (> 0) * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) conflicts with libglvnd0 (> 0) * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) conflicts with libglx0 (> 0) * nvidia-driver-libs (upgrade, 390.48-2~bpo9+1 -> 390.48-2~bpo9+3) conflicts with libopengl0 (> 0) I get the same conflicts with the non-GLVND version. I could continue manually removing the conflicting libraries, but I feel that is the wrong path because several unrelated applications complain of missing dependencies. What do you think?
Bug#898391:
On Thu, 2018-05-31 at 19:51 -0700, Jorge Moraleda wrote: > What is the state of this? I am on stretch backports trying to > upgrade > from 390.48-2~bpo9+1 (everything working fine) to 390.48-2~bpo9+3. > I am > experiencing something which is another symptom of this bug. Many > packets > are held back. I believe the fundamental problem lies with > > nvidia-driver : Depends: nvidia-driver-libs (= 390.48-2~bpo9+3) but > it is > not going to be installed or > nvidia-driver-libs-nonglvnd (= 390.48- > 2~bpo9+3) > but it is not going to be installed > > > I am on stretch backports trying to upgrade from 390.48-2~bpo9+1 > (everything working fine) to 390.48-2~bpo9+3 aptitude will resolve it just fine, apt seems to need a helping hand - depending on whether you want the glvnd or non-glvnd flavours, specify one of the nvidia-driver-libs* packages as well as nvidia-driver and it will upgrade it. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#898391:
What is the state of this? I am on stretch backports trying to upgrade from 390.48-2~bpo9+1 (everything working fine) to 390.48-2~bpo9+3. I am experiencing something which is another symptom of this bug. Many packets are held back. I believe the fundamental problem lies with nvidia-driver : Depends: nvidia-driver-libs (= 390.48-2~bpo9+3) but it is not going to be installed or nvidia-driver-libs-nonglvnd (= 390.48-2~bpo9+3) but it is not going to be installed I am on stretch backports trying to upgrade from 390.48-2~bpo9+1 (everything working fine) to 390.48-2~bpo9+3
Bug#898391: nvidia-driver-libs-nonglvnd: cannot upgrade due to libglvnd0 conflict
I'm also affected here: I'm trying to update to Mesa 17.3 after installing the 390.48.2~bpo9+3 drivers on my Stretch laptop (I'm using a hybrid graphics laptop so I need both drivers for my setup), but either I get updated Mesa or lose the nVidia blob due to conflicts with the new packaging specs (??), rendering my setup completely unupgradable and unusable.
Bug#898391:
Severity: grave Hi how is this issue going? I don't understand even why you need to add conflicts. If you care about glvnd so much, I even think you can migrate all existing installation to nonglvnd edition. I'm having segmentation fault on libgtk3 with glvnd edition, so nonglvnd is only my option. Anyway I have to update the severity to grave. Please consider to fix the issue soon.
