After an update from 16.04 to 16.10 a transitional package for nvidia-361 driver start giving an error.  This is the message (some data is translated to EN from BG):  Preparation for the unpacking of nvidia-352_361.45.11-0ubuntu4_amd64.deb ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: warning: under process old pre-removal script returned error status out of 5  dpkg: trying script from the new package instead ... dpkg: error processing archive /tmp/apt-dpkg-install-9wUQ2T/8-nvidia-352_361.45.11-0ubuntu4_amd64.deb (--unpack):  no script in the new version of the package - I surrender (or something like it) Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it. Error in the process:  /tmp/apt-dpkg-install-9wUQ2T/8-nvidia-352_361.45.11-0ubuntu4_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)   EDIT: Seems i forgot some data (added in the prevous text):  Preparation for the unpacking of nvidia-352_361.45.11-0ubuntu4_amd64.deb ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: warning: under process old pre-removal script returned error status out of 5
122798
I am using the  ppa. I got an update dialogue today which stated that I can update my nvidia driver to 367.18 (~gpu16.04.6). I started the update just like every time, but it failed with  Failed to get unit file state for var-lib-snapd-lib-gl.mount  After rebooting, my graphics driver was broken and I was forced to go into recovery mode.  As usually when my Nvidia driver breaks, I just uninstall it with  sudo apt purge nvidia* to reinstall it clean afterwards.   Doing this in recovery mode uninstalled all except the nvidia-opencl-icd-367 package which failed with the error above.   Trying to manually uninstall this package ends with these errors:       Update @20160605 - Solution:  Following Videonauth's answer below solves the issue. Please go through all the steps and make sure to reboot after removing everything of NVIDIA via sudo apt purge nvidia* succeeded without issues and after reinstalling the driver via sudo apt install nvidia-367.  This shall get your driver working again.   If this does not help, try to manually remove all old xorg configs sudo rm /etc/X11/xorg.conf* &amp;&amp; sudo rm /etc/X11/xorg.conf and reinstall the driver again sudo apt install nvidia-367 --reinstall.  If this still does not let you log back in (Typical error: Logins screen --> password has been entered, enter pressed --> goes back to login screen) try completely removing your Nvidia driver again from by switching into text console from the logscreen with Ctrl+Alt+F1, login with you account name and password, donwload the appropriate driver for your graphics card from  within console, stop lightdm:  sudo service lightdm  Install Nvidia's binary driver using sudo ./NVIDIA-VERSION...  and reboot system:  sudo reboot now  System:  Ubuntu 16.04 64bit  Linux 4.4.0-22
31287
Since my previous questions were not answered I will try to ask again more precisely.  I previously had the Nvidia driver installed and working correctly.  Then the ubuntu software update did something which broke it.  In fact, it completely de-configured it so that the standard display driver is used when the computer reboots.  I would like to re-enable the existing Nvidia  driver without re-installing the Nvidia driver.  How do I do that?  This machine is no longer connected to the internet.  NOTE: I am not asking how to disable automatic updates in this question.  I asked that elsewhere (and it wasn't answered).  NOTE: I am not asking how to stop the Ubuntu software updater from breaking the Nvidia driver the next time it updates the system.  That would be nice to know, but I asked that already and did not receive the correct answer either.  NOTE: Please don't make this as duplicate simply because someone else asked a question about Ubuntu and the software updater.  Try to read the actual question and see how it's different and try to realize how annoying it is when users have to spend hours of their own time to correct the problems that other people causing by incorrectly designing software updaters.
311
For  I need to install libpng12-0 package on the Ubuntu 19.10 system.  I know that it is available .  So I have decided to download this package manually and install it by hand.  On previous Ubuntu versions (such as 18.04 LTS) this trick ends with success, but here on 19.10 it fails in very strange way:   wget http://mirrors.kernel.org/ubuntu/pool/main/libp/libpng/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb sudo apt-get install ./libpng12-0_1.2.54-1ubuntu1.1_amd64.deb  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/116 kB of archives. After this operation, 285 kB of additional disk space will be used. Get:1 /home/user/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb libpng12-0 amd64 1.2.54-1ubuntu1.1 [116 kB] Selecting previously unselected package libpng12-0:amd64. (Reading database ... 212864 files and directories currently installed.) Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ... Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) ...  dpkg: error processing archive /home/user/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):  unable to install new version of '/lib/x86_64-linux-gnu/libpng12.so.0': No such file or directory No apport report written because the error message indicates an issue on the local system                                                                                          Errors were encountered while processing:  /home/user/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)   What is wrong here? How can I get libpng12-0 installed on Ubuntu 19.10 system?    Note: the same happens on 19.04, but it is near EOL.
72963
I have been having some screen freezing issues on my new Ubuntu 16.04 system, and have been in the troubleshooting process for this issue. I thought it was a graphics driver problem, as I am running an AMD R9 380x card which was supposed to be fully supported by the open-source AMDGPU driver preinstalled with 16.04, but after looking around online, many people seem to have issues with. I thought the answer would be to install the recently released AMDGPU-Pro driver , following the instructions from . However, when I reboot I am getting a black screen. Is there an easy way to revert my changes back? My machine was semi-functional with the freezing issue but now with no video at all is useless to me. How to proceed?
88841
I'm trying to install the most up-to-date NVIDIA driver in Debian Stretch. I've downloaded NVIDIA-Linux-x86_64-390.48.run from , but when I try to do  sudo sh ./NVIDIA-Linux-x86_64-390.48.run   as suggested, an error message appears.  ERROR: An NVIDIA kernel module 'nvidia-drm' appears to already be loaded in your kernel.  This may be because it is in use (for example, by an X server, a CUDA program, or           the NVIDIA Persistence Daemon), but this may also happen if your kernel was configured without support for module unloading.  Please be sure to exit any programs              that may be using the GPU(s) before attempting to upgrade your driver.  If no GPU-based programs are running, you know that your kernel supports module unloading,             and you still receive this message, then an error may have occured that has corrupted an NVIDIA kernel module's usage count, for which the simplest remedy is to               reboot your computer.   When I try to find out who is using nvidia-drm (or nvidia_drm), I see nothing.  ~$ sudo lsof | grep nvidia-drm lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs       Output information may be incomplete. ~$ sudo lsof -e /run/user/1000/gvfs | grep nvidia-drm ~$   And when I try to remove it, it says it's being used.  ~$ sudo modprobe -r nvidia-drm modprobe: FATAL: Module nvidia_drm is in use. ~$    I have rebooted and started in text-only mode (by pressing Ctrl+Alt+F2 before giving username/password), but I got the same error.  Besides it, how do I "know that my kernel supports module unloading"?  I'm getting a few warnings on boot up related to nvidia, no idea if they're related, though:  Apr 30 00:46:15 debian-9 kernel: nvidia: loading out-of-tree module taints kernel. Apr 30 00:46:15 debian-9 kernel: nvidia: module license 'NVIDIA' taints kernel. Apr 30 00:46:15 debian-9 kernel: Disabling lock debugging due to kernel taint Apr 30 00:46:15 debian-9 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  375.82  Wed Jul 19 21:16:49 PDT 2017 (using threaded interrupts)
44769
I've recently updated to Ubuntu 15.04 and after installing the latest nvidia drivers (346.59) which worked on ubuntu 14.10 seems to have caused some trouble on boot.  All I get is the following when booting:   A purple screen for about a second and then  [0.514409] ACPI PPC Probe failed. Starting version 219  A black screen with a message of my monitor saying : No Signal detected.   I am using a GTX 970.
91322
This is the third reinstall of Ubuntu 14.04 I have done today.  I just bought a laptop with an Core i3 processor and an Nvidia GeForce GT 840M graphics card.  I have installed the Nvidia driver using their .run file, and also following tutorials, and it just doesn't work. When I check in the terminal which GPU I am using it says "i915" instead of "nvidia".
29478
I just finished the installation of the Ubuntu 18.04, but whenever I try to install any application from Ubuntu Software the same error occurs (for example "vlc"):     unable to install "vlc": snap "vlc" has "install-snap" change in progress   I hope somebody can tell me what I've done wrong.
30018
The proprietary NVIDIA drivers "disappeared" with my latest update:    The option of "Proprietary drivers for devices" is correctly set under the "Ubuntu Software" tab. I have the graphics-driver PPA (ppa:graphics-drivers/ppa) correctly added to my sources.  Any ideas on how to bring the proprietary drivers back?  PS1: I need them because some of the games I play under wine don't work without them, for whatever reason.  PS2: Also, this feels like it should have a straightforward answer, but I've been looking online for a while without luck.
99489
I got a new install of 18.04, and when I install en app from Ubuntu Software or snap it will not start. If I install the same app from a deb-package it works. What is going on? Kinda resembles a permissions problem or something...  Please help! :D
35615
From /var/log/dist-upgrade/apt.log:  Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) libgles1-mesa [ amd64 ] &lt; 12.0.6-0ubuntu0.16.04.1 &gt; ( libs ) Broken libgles1-mesa:amd64 Depends on libglapi-mesa [ amd64 ] &lt; 12.0.6-0ubuntu0.16.04.1 -&gt; 17.0.7-0ubuntu0.16.04.1 &gt; ( libs ) (= 12.0.6-0ubuntu0.16   .04.1)     Considering libglapi-mesa:amd64 64 as a solution to libgles1-mesa:amd64 2     Removing libgles1-mesa:amd64 rather than change libglapi-mesa:amd64 Investigating (0) vlc [ amd64 ] &lt; 2.2.2+git20170721+r59033+56~ubuntu16.04.1 &gt; ( video ) Broken vlc:amd64 Depends on libgles1-mesa [ amd64 ] &lt; 12.0.6-0ubuntu0.16.04.1 &gt; ( libs ) (&gt;= 7.8.1)     Considering libgles1-mesa:amd64 2 as a solution to vlc:amd64 1 Broken vlc:amd64 Depends on libgles1 [ amd64 ] &lt; none -&gt;  &gt; ( none )     Considering libgles1-mesa:amd64 2 as a solution to vlc:amd64 1     Or group remove for vlc:amd64 Done   Searching the web, I found that .  The VLC team have updated their dependencies from 2.2.2-5ubuntu0.16.04.2, but my system has apparently not caught up with that (I checked by running apt-cache depends vlc, and it shows a dependency on libgles1-mesa).  Now it happens that a couple of months ago I added the  (to get the latest, least buggy VLC).    That gave me VLC version 2.2.7 and fixed the VLC bug, and is what I have on my system today.  I know, because vlc --version tells me so.  apt-cache policy vlc says:  Installed: 2.2.2+git20170721+r59033+56~ubuntu16.04.1 Candidate: 2.2.2+git20170721+r59033+56~ubuntu16.04.1 Version table: *** 2.2.2+git20170721+r59033+56~ubuntu16.04.1 500     500 http://ppa.launchpad.net/videolan/stable-daily/ubuntu xenial/main amd64 Packages     100 /var/lib/dpkg/status  2.2.2-5ubuntu0.16.04.3 500     500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages     500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages  2.2.2-5 500     500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages   (It seems weird that apt-cache policy says that 2.2.2+git20170721+r59033+56~ubuntu16.04.1 is installed; I read that as vlc version 2.2.2, which conflicts with the 2.2.7 that vlc --version gives.)  Apparently I have Ubuntu version 16.04.2 LTS 64-bit installed (from System Details in the GUI Control Panel thing).  I suppose that I could disable the launchpad PPA, but in that case I would presumably revert to an older vlc binary which was crashing my system.  So my question is (at least I think this is the right question): How do I convince apt that it's ok that libgles1-mesa is old or missing?
41039
I'm running Ubuntu 13.04 on DELL XPS L501 - Nvidia GeForce GT 420M. I'm using kernel 3.9.0-030900-generic.  All kernel-headers are installed in the system.  and  I've tried the following.   Use apt-get to install nvidia-current (which download 304) &amp;&amp; load using modprobe Use apt-get to install nvidia-310 &amp;&amp; load using modprobe Download nvidia 64-bit driver nvidia-319.23 for 400M series and install Use swat-x repo to install nvidia driver   All of these failed. And I tested it everytime like this   After the module is loaded (checked from lsmod),  restarted lightdm tested from get.webgl.org  (Google-Chrome webgl support is enabled)    Problem faced with nvidia-xconfig   after running nvidia-xconfig (which writes to /etc/X11/xorg.conf), and restarting lightdm, my display res changes to 640x480. and had to remove this file to revert back to old setting Have also tried commenting out those two lines which adjusts Horizontal and Vertical Setting in xorg.conf. That just rectified the resolution. But still I wasn't able to use the graphics card (webgl).   EDIT 1: (nouveau)   Tried rebooting after each installation Removed (purge) all of nouveau* before starting.  Removed one more package (dont remember the exact name though) - xorg-xserver-blah-blah.   EDIT 2: (bitlbee)   I had bitlbee installed before. Removed that too before starting installation. When bitlbee was present, NVIDIA-3.9-x86.run (downloaded from nvidia) was not able to recognize graphics card. But it did when I removed bitlbee. (So I'm assuming here that it should work if graphics driver was installed properly)   EDIT 3: (software-properties-gtk)   sudo software-properties-gtk the Additional drivers tab is always NIL. (before and after installation) (even if the installation was successful)   Have been trying this the whole day, and done it quite a few times. None of them worked.  Need help! Is it the problem with kernel-3.9, that there are no updates for this ?
80599
I'm using Ubuntu 15.04. Whenever I tried to install any package, I got the error message in the title. How can I get rid of this annoying error message?  :~$ uname -a Linux LongerVision001 3.19.0-25-generic #26-Ubuntu SMP Fri Jul 24 21:17:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux   :~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:    Ubuntu 15.04 Release:        15.04 Codename:       vivid   Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up runit (2.1.2-3ubuntu1) ... start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused dpkg: error processing package runit (--configure):  subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing:  runit E: Sub-process /usr/bin/dpkg returned an error code (1)
81483
When I try to download some software from Ubuntu center or from Synaptic, I get package operation failed...    How to fix this?  edit:  I tried to install this game:    This is the details from the installation:  installArchives() failed: Selecting previously deselected package libbulletml0d2. (Reading database ... 100% (Reading database ... 239257 files and directories currently installed.) Unpacking libbulletml0d2 (from .../libbulletml0d2_0.0.6-4_i386.deb) ... Selecting previously deselected package tumiki-fighters-data. Unpacking tumiki-fighters-data (from .../tumiki-fighters-data_0.2.dfsg1-4_all.deb) ... Selecting previously deselected package tumiki-fighters. Unpacking tumiki-fighters (from .../tumiki-fighters_0.2.dfsg1-4_i386.deb) ... Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for desktop-file-utils ... Processing triggers for python-gmenu ... Rebuilding /usr/share/applications/desktop.en_US.UTF8.cache... Processing triggers for menu ... Processing triggers for man-db ... Processing triggers for python-support ... Setting up plymouth-theme-mib-ubuntu (0.5.0-2) ... update-alternatives: error: alternative path /lib/plymouth/themes/MIB-Ubuntu/MIB-Ubuntu.plymouth doesn't exist. dpkg: error processing plymouth-theme-mib-ubuntu (--configure):  subprocess installed post-installation script returned error exit status 2 Setting up libbulletml0d2 (0.0.6-4) ... Setting up tumiki-fighters-data (0.2.dfsg1-4) ... Setting up tumiki-fighters (0.2.dfsg1-4) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for menu ... Errors were encountered while processing:  plymouth-theme-mib-ubuntu Setting up plymouth-theme-mib-ubuntu (0.5.0-2) ... update-alternatives: error: alternative path /lib/plymouth/themes/MIB-Ubuntu/MIB-Ubuntu.plymouth doesn't exist. dpkg: error processing plymouth-theme-mib-ubuntu (--configure):  subprocess installed post-installation script returned error exit status 2
80247
I have been trying to get this to work for a couple days now. I have an EC2 P2 instance with NVIDIA CUDA configured by default, its a Deep learning Ubuntu AMI. This OS does not have a GUI so everything is via terminal.  I downloaded Blender's 2.8 TAR file for Linux and set it up on the EC2 instance. And ran the following command from the directory where the TAR file is extracted:   ./blender -b -noaudio /home/ubuntu/file.blend --render-output . --engine BLENDER_EEVEE --render-format PNG --verbose 4   All I see in the output is this:  Blender 2.80 (sub 75) (hash f6cb5f54494e built 2019-07-29 17:17:04) found bundled python: /mnt/blender/blender-2.80-linux-glibc217-  x86_64/2.80/python Read blend: /home/ubuntu/file.blend  Blender quit   Don't know why its quitting but I am unable to debug this any further. Any help would be appreciated.  UPDATE: As per @rjg's recommendation, ran the following command:  ./blender -b -noaudio /home/ubuntu/file.blend --render-output . --engine BLENDER_EEVEE --render-format PNG -f 1 --verbose 4   Got the following error:  Blender 2.80 (sub 75) (hash f6cb5f54494e built 2019-07-29 17:17:04) found bundled python: /home/ubuntu/blender/blender-2.80-linux-glibc217-  x86_64/2.80/python Read blend: /home/ubuntu/file.blend Unable to open a display Aborted (core dumped)
108446
I am using the official nVidia driver because my card (GeForce 750 Ti) isn't yet supported by the Ubuntu one. Every time the kernel updates, my system breaks.  I've formatted my system two-three times because of kernel updates and today I decided to try to fix it. I tried to fix it with this method and surprisingly it works.   Switch to console (After waiting for the nVidia driver to crash, as it does when you switch consoles :p) Run a complete uninstall  sudo ./&lt;DRIVER&gt;.run -uninstall  Reboot and switch to the on-board card Update  sudo apt-get update sudo apt-get dist-upgrade  Reboot again Reinstall driver  sudo ./&lt;DRIVER&gt;.run  Reboot and switch back to the NVIDIA GPU   Is there a better/easier/faster way to update without going through all this?
2360
I tried to install an nvidia driver and there was an error saying I must not be in an X terminal when doing so. So I did a Ctrl+Alt+F1.  The resulting terminal did not allow the nvidia driver to be installed and showed the same error message. How do I revert back to the Unity GUI?