nvidia driver "update" removes too many packages

Dai_trying · 2018-08-06 18:42

I just noticed 7 updates for my Scorpion installation and they were

Upgrade: nvidia-vulkan-common:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), nvidia-kernel-dkms:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), nvidia-egl-common:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), nvidia-legacy-check:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), nvidia-egl-wayland-common:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), libnvidia-glcore:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), libnvidia-glcore:i386 (390.67-2~bpo9+1, 390.77-1~bpo9+1)

but when upgrading these packages it also removed the following :-

Remove: libgles-nvidia2:amd64 (390.67-2~bpo9+1), libgles-nvidia2:i386 (390.67-2~bpo9+1), tdelibs14-trinity-dev:amd64 (4:14.0.5~pre58-0debian9.0.1+5.1), nvidia-vulkan-icd:amd64 (390.67-2~bpo9+1), nvidia-vulkan-icd:i386 (390.67-2~bpo9+1), libegl1:i386 (1.0.0+git20180308-2~bpo9+1), nvidia-driver-libs-i386:i386 (390.67-2~bpo9+1), nvidia-egl-icd:i386 (390.67-2~bpo9+1), nvidia-driver:amd64 (390.67-2~bpo9+1), libtqtinterface-dev:amd64 (4:14.0.5~pre7-0debian9.0.0+1~a), libtqt3-mt-dev:amd64 (4:14.0.5~pre5-0debian9.0.0+1), kdevdesigner-trinity:amd64 (4:14.0.5~pre8-0debian9.0.0+0~a), libqt4-opengl-dev:amd64 (4:4.8.7+dfsg-11), libgl1-nvidia-glvnd-glx:amd64 (390.67-2~bpo9+1), libgl1-nvidia-glvnd-glx:i386 (390.67-2~bpo9+1), libglx-nvidia0:amd64 (390.67-2~bpo9+1), libglx-nvidia0:i386 (390.67-2~bpo9+1), libnvidia-egl-wayland1:amd64 (390.67-2~bpo9+1), tqt3-linguist:amd64 (4:14.0.5~pre5-0debian9.0.0+1), libegl-nvidia0:i386 (390.67-2~bpo9+1), libglu1-mesa-dev:amd64 (9.0.0-2.1), libnvidia-cfg1:amd64 (390.67-2~bpo9+1), nvidia-egl-wayland-icd:amd64 (390.67-2~bpo9+1), nvidia-egl-wayland-icd:i386 (390.67-2~bpo9+1), libglvnd-dev:amd64 (1.0.0+git20180308-2~bpo9+1), tqt3-designer:amd64 (4:14.0.5~pre5-0debian9.0.0+1), nvidia-driver-libs:amd64 (390.67-2~bpo9+1), nvidia-driver-libs:i386 (390.67-2~bpo9+1), libgl1-mesa-dev:amd64 (17.3.9-1~bpo9+1), nvidia-persistenced:amd64 (384.111-1~deb9u1), xserver-xorg-video-nvidia:amd64 (390.67-2~bpo9+1), tqt3-apps-dev:amd64 (4:14.0.5~pre5-0debian9.0.0+1), q4os-devpack:amd64 (2.2.4-a2), libdbus-1-tqt-dev:amd64 (4:14.0.5~pre7-0debian9.0.0+0~a), libarts1-trinity-dev:amd64 (4:14.0.5~pre8-0debian9.0.0+0)

I took this information from /var/log/apt/history.log after noticing a lot more activity than I was expecting. I rebooted and the system was back to using the nouveau driver.
I then re-installed the Nvidia driver from backports and everything seemed to be working fine.

Install: libgles-nvidia2:amd64 (390.77-1~bpo9+1, automatic), libgles-nvidia2:i386 (390.77-1~bpo9+1, automatic), nvidia-vulkan-icd:amd64 (390.77-1~bpo9+1, automatic), nvidia-vulkan-icd:i386 (390.77-1~bpo9+1, automatic), libegl1:i386 (1.0.0+git20180308-2~bpo9+1, automatic), nvidia-driver-libs-i386:i386 (390.77-1~bpo9+1, automatic), nvidia-egl-icd:i386 (390.77-1~bpo9+1, automatic), nvidia-driver:amd64 (390.77-1~bpo9+1), libgl1-nvidia-glvnd-glx:amd64 (390.77-1~bpo9+1, automatic), libgl1-nvidia-glvnd-glx:i386 (390.77-1~bpo9+1, automatic), libglx-nvidia0:amd64 (390.77-1~bpo9+1, automatic), libglx-nvidia0:i386 (390.77-1~bpo9+1, automatic), libnvidia-egl-wayland1:amd64 (390.77-1~bpo9+1, automatic), libegl-nvidia0:i386 (390.77-1~bpo9+1, automatic), libnvidia-cfg1:amd64 (390.77-1~bpo9+1, automatic), nvidia-egl-wayland-icd:amd64 (390.77-1~bpo9+1, automatic), nvidia-egl-wayland-icd:i386 (390.77-1~bpo9+1, automatic), nvidia-driver-libs:amd64 (390.77-1~bpo9+1, automatic), nvidia-driver-libs:i386 (390.77-1~bpo9+1, automatic), nvidia-persistenced:amd64 (384.111-1~bpo9+1, automatic), xserver-xorg-video-nvidia:amd64 (390.77-1~bpo9+1, automatic)
Upgrade: libnvidia-ml1:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), nvidia-egl-icd:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), update-glx:amd64 (0.8.3~deb9u1, 0.8.7~bpo9+1), nvidia-vdpau-driver:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), glx-alternative-nvidia:amd64 (0.8.3~deb9u1, 0.8.7~bpo9+1), libnvidia-egl-wayland1:i386 (390.67-2~bpo9+1, 390.77-1~bpo9+1), libegl-nvidia0:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), libnvidia-cfg1:i386 (390.67-2~bpo9+1, 390.77-1~bpo9+1), nvidia-kernel-support:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), glx-diversions:amd64 (0.8.3~deb9u1, 0.8.7~bpo9+1), nvidia-driver-bin:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), glx-alternative-mesa:amd64 (0.8.3~deb9u1, 0.8.7~bpo9+1), libnvidia-eglcore:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1), libnvidia-eglcore:i386 (390.67-2~bpo9+1, 390.77-1~bpo9+1), nvidia-alternative:amd64 (390.67-2~bpo9+1, 390.77-1~bpo9+1)

Then I noticed another update, I thought this a bit strange so ran a simulation first and got these results :-

dai@q4optiplex:~$ apt -s upgrade
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  binutils-dev checkinstall clang cmake cmake-data comerr-dev cvs gettext-kde icu-devtools krb5-multidev libacl1-dev libapr1 libaprutil1 libart-2.0-dev
  libartsc0-trinity-dev libasound2-dev libaspell-dev libattr1-dev libaudio-dev libaudiofile-dev libavahi-client-dev libavahi-common-dev libbotan-1.10-1 libbz2-dev
  libclang1-3.9 libcups2-dev libcupsfilters-dev libcupsimage2-dev libcvsservice0-trinity libdbus-1-dev libdrm-dev libesd0-dev libexpat1-dev libfontconfig1-dev
  libfontenc-dev libfreetype6-dev libglib2.0-bin libglib2.0-dev libglvnd-core-dev libgpgme11 libgssrpc4 libice-dev libicu-dev libidn11-dev libilmbase-dev
  libjasper-dev libjbig-dev libjpeg-dev libjpeg62-turbo-dev libkadm5clnt-mit11 libkadm5srv-mit11 libkdb5-8 libkrb5-dev liblcms2-dev liblua50 liblua50-dev
  liblualib50 liblualib50-dev liblzma-dev libmad0-dev libmng-dev libogg-dev libopenexr-dev libpciaccess-dev libpcre3-dev libpcre32-3 libpcrecpp0v5 libphonon4
  libpixman-1-dev libpng-dev libpng-tools libpthread-stubs0-dev libpulse-mainloop-glib0 libqbscore1.7 libqbsqtprofilesetup1.7 libqt4-opengl libqt5concurrent5
  libqt5designercomponents5 libqt5quicktest5 libqt5quickwidgets5 libqt5xmlpatterns5 libqtwebkit-dev libqtwebkit4 libr-dev libsasl2-dev libserf-1-1 libsm-dev
  libssl-dev libssl-doc libsvn1 libtiff5-dev libtiffxx5 libtqt3-compat-headers libtqt3-headers libtxc-dxtn-s2tc libudev-dev libuv1 libvorbis-dev libx11-dev
  libx11-doc libx11-xcb-dev libxau-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxcb-randr0-dev libxcb-render0-dev libxcb-shape0-dev
  libxcb-sync-dev libxcb-xfixes0-dev libxcb1-dev libxcomposite-dev libxcursor-dev libxdamage-dev libxdmcp-dev libxext-dev libxfixes-dev libxfont-dev libxfont1
  libxft-dev libxi-dev libxinerama-dev libxkbfile-dev libxml2-dev libxmu-dev libxmu-headers libxrandr-dev libxrender-dev libxshmfence-dev libxslt1-dev libxt-dev
  libxxf86vm-dev lua50 mc mc-data mesa-common-dev pkg-config qml-module-qtgraphicaleffects qml-module-qtqml-models2 qml-module-qtquick-controls
  qml-module-qtquick-layouts qml-module-qtquick-window2 qml-module-qtquick2 qmlscene qt3d5-doc qt4-demos qt5-doc qtbase5-dev-tools qtbase5-doc qtconnectivity5-doc
  qtcreator qtcreator-data qtcreator-doc qtdeclarative5-dev-tools qtdeclarative5-doc qtgraphicaleffects5-doc qtlocation5-doc qtmultimedia5-doc
  qtquickcontrols2-5-doc qtquickcontrols5-doc qtscript5-doc qtsensors5-doc qtserialport5-doc qtsvg5-doc qttools5-dev-tools qttools5-doc qtwayland5-doc
  qtwebchannel5-doc qtwebengine5-doc qtwebkit5-doc qtwebkit5-examples-doc qtwebsockets5-doc qtx11extras5-doc qtxmlpatterns5-dev-tools qtxmlpatterns5-doc reprepro
  tdecachegrind-trinity tdevelop-data-trinity tdevelop-trinity tdevelop-trinity-doc tqt3-assistant tqt3-dev-tools tqt3-doc tqt3-qtconfig uuid-dev valgrind
  valgrind-dbg x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-dri2-dev x11proto-dri3-dev x11proto-fixes-dev x11proto-fonts-dev
  x11proto-gl-dev x11proto-input-dev x11proto-kb-dev x11proto-present-dev x11proto-randr-dev x11proto-render-dev x11proto-resource-dev x11proto-scrnsaver-dev
  x11proto-video-dev x11proto-xext-dev x11proto-xf86bigfont-dev x11proto-xf86dri-dev x11proto-xf86vidmode-dev x11proto-xinerama-dev xfonts-encodings
  xfonts-terminus xfonts-utils xorg-sgml-doctools xserver-xorg-dev xtrans-dev zlib1g-dev
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  nvidia-persistenced
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Inst nvidia-persistenced [384.111-1~bpo9+1] (384.111-1~deb9u1 Debian:9.5/stable [amd64])
Conf nvidia-persistenced (384.111-1~deb9u1 Debian:9.5/stable [amd64])

and obviously any autoremove would uninstall a lot of packages, some of which I definitely do not want to be removed.
I noticed that the versions of this update seem to be (almost) the same

dai@q4optiplex:~$ apt policy nvidia-persistenced 
nvidia-persistenced:
  Installed: 384.111-1~bpo9+1
  Candidate: 384.111-1~deb9u1
  Version table:
     384.111-1~deb9u1 500
        500 http://ftp.debian.org/debian stretch/contrib amd64 Packages
 *** 384.111-1~bpo9+1 100
        100 http://ftp.debian.org/debian stretch-backports/contrib amd64 Packages
        100 /var/lib/dpkg/status

could this be causing the problem? Do I need to "pin" this particular version to avoid this upgrade?

I will likely be performing a fresh install on this partition so just want to know beforehand what I should/should not install. After posting this I will reboot into Debian Stretch and see what updates do on that one in case there are similarities and will report back.

Dai_trying · 2018-08-06 18:54

Debian updated without issue so I guess I may have had some sort of anomaly with this installation, I will perform a fresh install once I have backed everything up and see what happens.

q4osteam · 2018-08-06 20:52

We have performed a few quick tests. It seems like the package 'libnvidia-glcore:i386' from backports is the conflicting one, requesting to remove another set of packages, besides others the q4os-devpack dependencies. Those are in the list of 'to autoremove' packages. We would recommend you to check, if you could safely remove the 'libnvidia-glcore:i386' package first.

Dai_trying · 2018-08-06 23:11

Sorry guys, I backed up and re-installed so cannot check this.

The good news though is I ran the Q4OS Nvidia installer from this fresh install (after update & upgrade) and everything worked this time, so I now have the stable Nvidia driver installed and so should not face the problem again.

Thank you for your quick attention and sorry I could not test your recommendation.

dai@q4asusi3:~$ inxi -G
Graphics:  Card: NVIDIA GF106 [GeForce GTS 450]
           Display Server: X.Org 1.19.2 driver: nvidia Resolution: 1920x1080@60.05hz
           GLX Renderer: GeForce GTS 450/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 384.130

Q4OS Forum

#1 2018-08-06 18:42

nvidia driver "update" removes too many packages

#2 2018-08-06 18:54

Re: nvidia driver "update" removes too many packages

#3 2018-08-06 20:52

Re: nvidia driver "update" removes too many packages

#4 2018-08-06 23:11

Re: nvidia driver "update" removes too many packages

Board footer