Не удалось установить chromium snap chromium has install snap change in progress
after an initial attemp to install where the progress got stuck at 20%, i rebooted as there were a bunch of other system updates that had been applied after a fresh isntall.
Now chromium wont install
dantheperson@ danski: ~$ sudo apt install chromium-browser
Reading package lists. Done
Building dependency tree
Reading state information. Done
The following packages will be upgraded:
chromium-browser
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 48.4 kB of archives.
After this operation, 164 kB of additional disk space will be used.
Get:1 http:// nz.archive. ubuntu. com/ubuntu focal-updates/ universe amd64 chromium-browser amd64 81.0.4044. 129-0ubuntu0. 20.04.1 [48.4 kB]
Fetched 48.4 kB in 0s (1,527 kB/s)
Preconfiguring packages .
(Reading database . 185728 files and directories currently installed.)
Preparing to unpack . /chromium- browser_ 81.0.4044. 129-0ubuntu0. 20.04.1_ amd64.deb .
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
error: snap "chromium" has "install-snap" change in progress
dpkg: error processing archive /var/cache/ apt/archives/ chromium- browser_ 81.0.4044. 129-0ubuntu0. 20.04.1_ amd64.deb (--unpack):
new chromium-browser package pre-installation script subprocess returned error exit status 10
Errors were encountered while processing:
/var/cache/ apt/archives/ chromium- browser_ 81.0.4044. 129-0ubuntu0. 20.04.1_ amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10
InstallationDate: Installed on 2020-07-06 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageV ersions:
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
SourcePackage: chromium-browser
Title: package chromium-browser 81.0.4044. 129-0ubuntu0. 20.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)
- Df.txtEdit (513 bytes, text/plain; charset="utf-8")
- Dmesg.txtEdit (73.4 KiB, text/plain; charset="utf-8")
- DpkgHistoryLog.txtEdit (118.0 KiB, text/plain; charset="utf-8")
- DpkgTerminalLog.txtEdit (485 bytes, text/plain; charset="utf-8")
- ProcCpuinfoMinimal.txtEdit (1.2 KiB, text/plain; charset="utf-8")
ok i found 'snap changes' and did snap abort.
Now stuck on 20% again.
antheperson@ danski: ~$ snap changes
ID Status Spawn Ready Summary
1 Done today at 23:24 NZST today at 23:26 NZST Initialize system state
2 Done today at 23:24 NZST today at 23:24 NZST Initialize device
3 Done today at 23:26 NZST today at 23:35 NZST Install "canonical- livepatch" snap
4 Doing today at 23:28 NZST - Install "pycharm-community" snap from "latest/stable" channel
5 Doing today at 23:32 NZST - Install "chromium" snap
dantheperson@ danski: ~$ sudo snap abort 5
dantheperson@ danski: ~$ sudo snap abort 4
dantheperson@ danski: ~$ sudo apt install chromium-browser
Reading package lists. Done
Building dependency tree
Reading state information. Done
The following packages will be upgraded:
chromium-browser
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/48.4 kB of archives.
After this operation, 164 kB of additional disk space will be used.
Preconfiguring packages .
(Reading database . 185728 files and directories currently installed.)
Preparing to unpack . /chromium- browser_ 81.0.4044. 129-0ubuntu0. 20.04.1_ amd64.deb .
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
ok after 20 mins i abort again. snap reports the following
==> Installing the chromium snap
error: cannot perform the following tasks:
- Download snap "chromium" (1213) from channel "stable" (context canceled)
dpkg: error processing archive /var/cache/ apt/archives/ chromium- browser_ 81.0.4044. 129-0ubuntu0. 20.04.1_ amd64.deb (--unpack):
new chromium-browser package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
/var/cache/ apt/archives/ chromium- browser_ 81.0.4044. 129-0ubuntu0. 20.04.1_ amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
W: Operation was interrupted before it could finish
Can you try installing the snap using the "snap install chromium" command?
Please let us know how this goes, and if it succeeds you should be able to safely install the deb wrapper ("apt install chromium-browser").
Changed in chromium-browser (Ubuntu): | |
status: | New → Incomplete |
ok thanks that worked a treat.
Running snap directly there was a progress indicator so i could see that snap downloads are very very very slow. 200kb/s. I'm on a a basic residential 100Mbits fibre line, so apt downloading deps from the ubuntu mirror is usually quick, 10MB/s. So the snap download is 50x slower than what i am used to.
So download 50x slower than usual, and no progress indicator, made me think it was hung when i probably should have just waited half an hour.
Normal download speed from apt upgrade straight after the snap install:
Changed in chromium-browser (Ubuntu): | |
status: | Incomplete → Opinion |
status: | Opinion → Invalid |
Have a feeling this will crop up a lot. I too am in NZ and was doing a routine apt upgrade of chromium-browser on Ubuntu 20.04 LTS.
First time, it decided to install the chromium snap and appeared stuck at 14%. (There was a bug, reporting identical symptoms, back in May. It's been expired because it's more than 60 days old but I'd bet that people will still be having the same problem.)
Next attempt - after much fixing-up having bombed out of what appeared to be a hung install - is showing exactly what the OP here describes: it's chosen first to install the chromium snap, with the progress bar appearing stuck at 20% for ages.
I'm prepared to wait . and wait, as it appears from comments above that eventually this will complete and normal apt upgrades will be restored. Doesn't change my opinion: regardless of whether this works in the end, it's badly broken.
I agree this isn't a good user experience. I'll look into what can be done to report more detailed progress.
summary: | - chromium wont install + the chromium snap takes a long time to install without visible user + feedback, seems stuck |
Changed in chromium-browser (Ubuntu): | |
status: | Invalid → Confirmed |
assignee: | nobody → Olivier Tilloy (osomon) |
importance: | Undecided → Medium |
Please put TNT on snap. This was a machine of stress on the most easy thing to do on any Linux OS, installing software.
Sorry, I'm not sure what you mean with that last comment. Can you please elaborate?
I reckon he means get rid of snap caused it turned a trivial task into a
difficult one.
On Fri, 7 Aug 2020, 08:10 Olivier Tilloy,
wrote:
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.
6 Answers 6
Snap is probably still working on something in the background (or at least it thinks so). Open a terminal and run snap changes so see a list of ongoing changes.
You can abort ongoing change(s):
Then you should be able to successfully install VLC through the software center, or through the command line using snap install vlc .
@Gambit - that probably means you ran it twice, or the active snap change process has already stopped for whatever reason
This happens because you click install, then put in your password, and it doesn't update the install button to let the user know that it is doing anything, so you click it again thinking, oh, maybe now that I've authenticated, I need to do it again. The reason for the OP is bad user experience, at least in 18.04.
Open your terminal and follow these steps.
2. Pick the ID of your VLC snap process
Pick the ID of your "vlc" snap process, for the example 8
Step 2: Note the SNAP process ID
In the above step’s screenshot, you can see the all process along with their status and ID. Now, you have to find out the package which is making our snap busy. For that simply select the one with “Doing” in the status. For example, in the above image, we have the VLC process of SNAP with Doing status. Thus, we note its ID which is “14“. In the same way, find the ID of tasks in your system.
error: snap “vlc” has “install-snap” change in progress
So, if you are facing the same problem then here are the steps to solve this “install-snap” change in progress error:
3. Abort the snap process by ID
Abort snap process by running command snap abort 8 . This action will abort your vlc snap installation process.
1. Abort the "vlc" snap process.
Inspect your snap "vlc" process by running command snap changes , this will show the status list of the snaps installations similar to this.
2 ответа
Команда snap на самом деле состоит из двух компонентов, сервер и клиент. Вы взаимодействуете с клиентом. Когда вы отменили операцию установки на стороне клиента, это единственное место, где вы ее отменили - клиент. Поэтому он перестал показывать вам, что он устанавливал, но все равно устанавливал (это ошибка ). (Обновление: Эта ошибка была исправлена в snapd v2.20.1.)
На стороне сервера все это происходит в "изменениях". Вы можете прочитать о них подробнее здесь, но для своих целей вы хотите просто прервать это специфическое изменение. Для этого запустите:
Обратите внимание на ID, 203, и тот факт, что это "Делаю" прямо сейчас. Чтобы прервать эту операцию, вы используете ID изменения:
И изменение должно остановиться. Однако, я должен сказать, что тот факт, что изменение "заморожено" не сулит ничего хорошего для вашей возможности прервать его. Если это не сработает, возможно, попробуйте перезагрузиться. Если это до сих пор не, кажется, исправили его, и вы в порядке, потеряв все свои оснастки и их данные, вы можете полностью сбросить состояние оснастки с помощью этот сценарий .
4. Open your Software Center or running snap installation by a terminal
Step 1: Find the SNAP ongoing processes
The first thing we need to know is what are the processes those keeping the SNAP busy? For that simply run command:
The above command will not only show the live process but also that are ended with or without some error.
Step 4: Again install the package
After forcefully ended the SNAP process, you can install the package either from the Software Center or directly from the command terminal using the SNAPD. This time you will not get any error.
I ran the command /usr/bin/chromium-browser it mentioned installing chromium using snap
When I did that, it threw a new error. The following is the output of the command snap version.
snap 2.51.1+20.04ubuntu2
snapd unavailable
series -
whereis chromedriver
chromedriver: /usr/bin/chromedriver /usr/local/bin/chromedriver
I ran into all these because I was trying to test out a simple selenium program:
Which threw the following error:
Not sure if these problems are coming because I am using WSL on windows-10
5. Wait for the installation until finished.
Open your terminal and type the below command in terminal.
you will see the following results
Note that id in this output . Here its 4(for sticky notes app). You need to abort that snap operation by running the below command.
After this try to install it again. If you still get that error restart your system and try again. And try to refresh your package also.
Thankyou , hope this helps!
In my case, you do not have to do anything, just wait until the application is getting installed. The installation process is not shown (I am not sure if it is some kind of a bug or feature) and it does the installation completely. Just sit tight and wait for it to get installed. It has happened and worked properly several times for me. Hope it works for others.
Same thing occured on my fresh 20.04 installation. Ubuntu asked to reboot while snap was installing two packages. Once the system has made its reboot, snap gui did not show any state of progress. With the snap changes cmd, you see that the state is "Doing" for the package that is installing. You can wait blindly 'till the end, or abort the activity with the id, and launch it again to see progress :
Just like did Aditya Kresna Permana
Hello and welcome on Ask Ubuntu :) May I suggest you to elaborate a bit and maybe add the exact commands you would enter to see progress / abort / relaunch a snap install?
I don't have any problem with the solutions above, but I have a suggestion according to my experiences.
If you use snap changes in the terminal, and you see that Status is Doing for vlc snap in your case, if you don't abort it, it'll probably install it.
And after the installation is done, Ubuntu Software will probably give you a notification that:
VLC is now installed.
Application is ready to be used.
Snap is a universal package manager developed by the Ubuntu’s canonical team to easily install software and packages regardless of the Linux operating system the users are using. It is possible because SNAP creates its own file to store the content of the packages. This means it doesn’t matter the system is using the RPM or APT package manager; the installation process and usage will be the same for both.
However, if you are installing any package using the SNAP and anyhow you deliberately stopped the process or accidentally it happened or the system lost the internet connection. Then when you try to install the package using the snapd, you would get an error. For example, I was installing VLC and suddenly, I lost the connection, however, the installation was still processing. So, when again I tried to install the same, I got:
Step 3: Abort the “Install “package Snap task
Finally, we have the ID or IDs, its time to abort them one by one. For that the command is:
For example, in our case the VLC ID is 14, therefore the command will be:
In this way, we can end all the active process IDs of the SNAP.
1 Answer 1
Not sure if these problems are coming because I am using WSL on Windows 10
Well, yes. While WSL is quite capable, it still has a few limitations that need to be understood in order to make full use of it. The primary one that you are running into at the moment is that WSL does not support Systemd out-of-the-box.
The second one that you haven't run into yet, but will, is that WSL on Windows 10 does not support GUI apps out of the box.
The second part is easiest to overcome for your particular use. Just run the browser in headless mode so that it doesn't try to output to a display. The code example for doing this is in this answer, and I have tested it out on a Windows 10 WSL/Ubuntu system.
Note that this isn't an issue under Windows 11, since the WSLg feature allows you to run GUI applications. It's also possible to overcome with other methods as I cover in this Super User answer. I've also run Selenium through xrdp without issues.
The first problem is a bit trickier. On Ubuntu, Chromium is installed via Snap, which pretty much requires Systemd. Systemd, unfortunately, insists on running as the main process (PID 1), or it just won't work. WSL needs its own PID1 ('/init') in order to provide its interoperability with Windows.
You still do have multiple alternatives, however. I'm going to list these in my order of preference:
Option 1: Use Google Chrome, rather than Chromium
I was able to run your sample code (with the modifications for headless) under Ubuntu using the official Google Chrome Debian package and the corresponding webdriver.
This is, by far, the easiest solution.
Option 2: Use a distribution that doesn't require Snap in order to install Chromium
I was also successful doing this using my custom Artix distribution, but I believe Arch Linux would work as well since, AFAIK, they use the same Chromium package.
As an added bonus, the chromium package also included chromedriver with no need to find a matching version to install separately.
On the downside, you'll need to manually wsl --import an Artix or Arch rootfs based on this Microsoft guide and learn how to configure it.
Option 3: Get Systemd running on WSL/Ubuntu
While I won't go through all the steps here, there are a number of Systemd helpers out there for WSL, including Genie, distrod, and others.
These all work the same way at their core, by using creating a new Linux PID namespace where Systemd is PID1, then putting you inside that namespace. I don't recommend it for new users, really. There are quite a few things that are changed on your WSL system, and it's best that you have a deep understanding of Systemd before using it with WSL, IMHO.
But, it's there as an option. I believe you can install Snaps with this in place, but I haven't tried it personally. On Windows 10, however, you might still have issues installing the Chromium snap due to a lack of display, and you'll need to resolve this separately if so.
Во-первых, предостережение: я понимаю, что этот вопрос касается Mate и Raspberry Pi, поэтому, если вы считаете, что это выходит за рамки этого форума, просто проигнорируйте его. Но на случай, если это может быть полезно или типично для чего-то, связанного со снимками или этой платформой, вот оно.
Я решил попробовать установить nextcloud snap. Он выдавал кучу ошибок и, казалось, завис в середине процесса (более часа). Убил и просто решил попробовать удалить. Установка выглядела так .
Когда я пытаюсь удалить nextcloud, я получаю
ошибку: не удается удалить "nextcloud": в snap "nextcloud" происходят изменения
В первую очередь я хотел бы сделать правильно удалите оснастку и восстановите пространство из созданного ею раздела. Правильный ли термин "раздел" ??
и получил ошибку
: не могу найти изменение с идентификатором nextcloud
Я также должен отметить, что он не отображается как установленный, так как я получаю только после
$ snap list
Название Версия Rev Примечания разработчика
ubuntu-core 16.04 + 20160531.12-01 120 canonical -
Хотя это действительно отображается в .. ..
$ snap interfaces
: network nextcloud
: network-bind nextcloud
Но раздел все еще существует.
** Обновление, я снова запустил весь процесс для отладки и просто оставил его после команды «snap abort 1». В какой-то момент кажется, что что-то завершилось в фоновом режиме, потому что lsblk ничего не показывает, а запрос интерфейсов привязки ничего не показывает.
Читайте также: