[Trying to] Installing flatpak on Arch linux fails:
$ sudo pacman -S flatpak
resolving dependencies...
:: There are 3 providers available for xdg-desktop-portal-impl:
:: Repository extra
1) xdg-desktop-portal-gtk 2) xdg-desktop-portal-kde
:: Repository community
3) xdg-desktop-portal-wlr
Enter a number (default=1): 1
looking for conflicting packages...
Packages (11) appstream-glib-0.7.18-1 gcab-1.4-1 geoclue-2.5.7-3 geocode-glib-3.26.2-1
gnome-desktop-1:40.0-1 gnome-keyring-1:40.0-1 libstemmer-0+713-2 ostree-2021.1-1
xdg-desktop-portal-1.8.0-1 xdg-desktop-portal-gtk-1.8.0-1 flatpak-1.10.2-1
Total Download Size: 0.63 MiB
Total Installed Size: 29.29 MiB
:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
error: failed retrieving file 'ostree-2021.1-1-x86_64.pkg.tar.zst' from mirror.rackspace.com : The requested URL returned error: 404
error: failed retrieving file 'ostree-2021.1-1-x86_64.pkg.tar.zst' from mirrors.evowise.com : The requested URL returned error: 404
error: failed retrieving file 'ostree-2021.1-1-x86_64.pkg.tar.zst' from mirror.rackspace.com : The requested URL returned error: 404
error: failed retrieving file 'ostree-2021.1-1-x86_64.pkg.tar.zst' from mirror.rackspace.com : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.
What's the correct way to download and install flatpack on Linux?
Update the system with
pacman -Syu and try again
buy I highly recommend going with AUR packages
Note that it is not advisable to install an individual package after -Sy or -Syy. If you need to update your mirrors with -y to install a package, you should combine it with a full system upgrade -u:
sudo pacman -Syu flatpak
You might not see immediate breakage with -Sy <package>, but eventually something will break with continued use. If <package> happens to pull in new lib versions, then any program that depends on those libs will break since they will still be built against the old libs.
Solved it with running sudo pacman -Syy first
This is sometimes happen. you can solve it using pacman -Syu flatpak.
If it didn't solve then you have to change your repository server either from /etc/pacman or /etc/pacman.d/mirrorlist.
pI need to fix the following problems
I do not have experience in linux, so please possible give me simply explanations and the code to type in command line and fix the problems, please!
I checked other threads and I found similar problems but non the same.
Question
manolis#manolis-300-0xx:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
netplan.io
0 upgraded, 0 newly installed, 0 to remove and 1 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 grub-efi-amd64-signed (1.93.8+2.02-2ubuntu8.7) ...
Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
dpkg: error processing package shim-signed (--configure):
dependency problems - leaving triggers unprocessed
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Backgournd Informations
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
manolis#manolis-300-0xx:~$ echo ${BASH_VERSION%%[^0-9.]*}
4.4.19
manolis#manolis-300-0xx:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1,9G 0 1,9G 0% /dev
tmpfs 387M 2,0M 385M 1% /run
/dev/sda2 916G 207G 663G 24% /
tmpfs 1,9G 61M 1,9G 4% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 1,9G 0 1,9G 0% /sys/fs/cgroup
/dev/loop0 3,8M 3,8M 0 100% /snap/gnome-system-monitor/51
/dev/loop2 88M 88M 0 100% /snap/core/5742
/dev/loop1 15M 15M 0 100% /snap/gnome-logs/45
/dev/loop4 141M 141M 0 100% /snap/gnome-3-26-1604/70
/dev/loop6 13M 13M 0 100% /snap/gnome-characters/117
/dev/loop7 13M 13M 0 100% /snap/gnome-characters/124
/dev/loop9 140M 140M 0 100% /snap/gnome-3-26-1604/64
/dev/loop10 35M 35M 0 100% /snap/gtk-common-themes/319
/dev/loop8 2,3M 2,3M 0 100% /snap/gnome-calculator/238
/dev/loop5 128K 128K 0 100% /snap/tree/15
/dev/loop11 3,8M 3,8M 0 100% /snap/gnome-system-monitor/54
/dev/loop12 13M 13M 0 100% /snap/gnome-characters/139
/dev/loop13 88M 88M 0 100% /snap/core/5662
/dev/loop3 2,3M 2,3M 0 100% /snap/gnome-calculator/260
/dev/loop14 43M 43M 0 100% /snap/gtk-common-themes/701
/dev/loop15 15M 15M 0 100% /snap/gnome-logs/43
/dev/loop16 15M 15M 0 100% /snap/gnome-logs/40
/dev/loop17 141M 141M 0 100% /snap/gnome-3-26-1604/74
/dev/loop18 88M 88M 0 100% /snap/core/5548
/dev/loop19 2,3M 2,3M 0 100% /snap/gnome-calculator/222
/dev/loop20 3,8M 3,8M 0 100% /snap/gnome-system-monitor/57
/dev/sda1 511M 6,1M 505M 2% /boot/efi
tmpfs 387M 40K 387M 1% /run/user/1000
/dev/sdb1 1,9T 108G 1,8T 6% /media/manolis/Maxtor
tmpfs 387M 16K 387M 1% /run/user/120
manolis#manolis-300-0xx:~$ sudo apt install udo
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
udo
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
Need to get 205 kB of archives.
After this operation, 598 kB of additional disk space will be used.
Get:1 http://it.archive.ubuntu.com/ubuntu bionic/universe amd64 udo amd64 6.4.1-4 [205 kB]
Fetched 205 kB in 0s (1.520 kB/s)
Selecting previously unselected package udo.
(Reading database ... 168775 files and directories currently installed.)
Preparing to unpack .../archives/udo_6.4.1-4_amd64.deb ...
Unpacking udo (6.4.1-4) ...
Setting up udo (6.4.1-4) ...
Setting up grub-efi-amd64-signed (1.93.8+2.02-2ubuntu8.7) ...
Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
dpkg: error processing package shim-signed (--configure):
dependency problems - leaving triggers unprocessed
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Why I have all of these "/dev/loop" ???
How can I clean and increase the space: "Could not prepare Boot variable: No space left on device"
Is correct to do, or dangerous:
rm -r /dev/loop*
All the best!
The following worked well for me on Ubuntu 18.04LTS
on the following commands : use sudo or run as root
sudo apt-get purge grub\*
sudo apt-get install grub-efi
sudo apt-get autoremove
sudo update-grub
-or-
sudo su
enter your password then run
apt-get purge grub\*
apt-get install grub-efi
apt-get autoremove
update-grub
In my case, Ubuntu 18.04 installed on bare metal servers, I had to execute this command:
apt-get install -y grub-pc 'grub-efi*-'
which yielded this change:
The following additional packages will be installed:
grub-gfxpayload-lists grub-pc-bin
Suggested packages:
desktop-base
The following packages will be REMOVED:
grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed shim-signed
The following NEW packages will be installed:
grub-gfxpayload-lists grub-pc grub-pc-bin
After this, the error is gone.
These 2 lines of command worked for me.
apt install grub-efi-amd64-bin
apt upgrade
I don't have enough rep to add a comment, but the answer from "AAA SSS" worked for me. I found the same answer in the AskUbuntu forum. I was directed there by pasting this into a Google search.
Package grub-efi-amd64-signed is not configured yet.
My situation arose from both a fresh install to 18.04 and an upgrade from 16.04 to 18.04, the same errors printed by apt and booting failed. "dpkg -l" reported these errors.
iF grub-efi-amd64-signed (1.93.13+2.02-2ubuntu8.12)
iU shim-signed (1.37~18.04.3+15+1533136590.3beb971-0ubuntu1)
The above attempts were not working for me.
I was getting similar errors, not sure what happened on me, but my /etc/default/grub file had an extra line added during a recent update:
"/etc/default/grub" 34L, 1279C
was at the bottom of that file, I commented it out and things worked for me again!
Run this as one command and answer y (yes) when prompted:
sudo apt-get purge grub\*
sudo apt-get install grub-efi
sudo apt-get autoremove
sudo update-grub
This just a quicker way base off the answer given by AAA SSS. This worked for me.
I had problem which says
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess ret
urned error exit status 127
I found that It's beacuse of bugs which can solve installing mokutil
sudo apt-get install -y mokutil
It looks like you've installed OS with secure boot disabled, but now it is enabled.
Make sure you still have the secure boot option disabled in BIOS.
I am trying to upgrade my nodejs 6 to 8 in my arch linux. So I did:
$ sudo pacman -S nodejs npm
Result:
resolving dependencies...
looking for conflicting packages...
Packages (3) openssl-1.0-1.0.2.l-1 nodejs-8.1.3-1 npm-4.6.1-1
Total Installed Size: 39.22 MiB
Net Upgrade Size: 6.79 MiB
:: Proceed with installation? [Y/n] y
(3/3) checking keys in keyring [####################################################################] 100%
(3/3) checking package integrity [####################################################################] 100%
(3/3) loading package files [####################################################################] 100%
(3/3) checking for file conflicts [####################################################################] 100%
error: failed to commit transaction (conflicting files)
openssl-1.0: /usr/lib/libcrypto.so.1.0.0 exists in filesystem
openssl-1.0: /usr/lib/libssl.so.1.0.0 exists in filesystem
Errors occurred, no packages were upgraded.
And now my nodejs is broken I think!
$ node --version
node: error while loading shared libraries: libhttp_parser.so.2.7.1: cannot open shared object file: No such file or directory
Any ideas what should I do now?
I had same problem and this is how I solve it :
sudo pacman -S nodejs npm --force
Option --force will upgrade your package even if you get warning with existing files.
After this you need to install http-parser with pacman so :
sudo pacman -S http-parser --force
Finally, node -v will give you this error :
error while loading shared libraries: libicui18n.so.59: cannot open shared object file: No such file or directory
To fix it, install icu lib from pacman :
sudo pacman -S icu --force
Here we go, your node version is now v8.4.0.
Edited 17/01: --force was deprecated. Please use --overwrite
I am trying to do an rpm install of Node, but it is failing with the following error:
[xxxx#xxxxxxxx xxxx]# rpm -ivh Node-v0.10.33-RHEL.x86_64.rpm
Preparing... ################################# [100%]
file /usr/bin from install of Node-v0.10.33-RHEL.x86_64 conflicts with file from package filesystem-3.2-20.el7.x86_64
file /usr/lib from install of Node-v0.10.33-RHEL.x86_64 conflicts with file from package filesystem-3.2-20.el7.x86_64
I have been looking around the internet for the past two days but all the errors similar to mine (conflict with filesystem package) had been due to issues with the rpm package. In my case, I can rule that out as I have previously used the same rpm for node installation on other VMs successfully.
My user has root privileges and my OS is CentOS Linux release 7.2.1511 (Core)
I wonder who had such a experience.
We are using diskless linux servers. Before we use ramdisk, recently we are trying to make a diskless server with ramfs, and we successfully created the rootfs image and booted the server.
Then the issue here is that we can not install anything, because yum complains about no disk space. it is quite true that there is no disk thus no space, but for a ramfs, can we update the linux configuration to by pass this issue?
df -kh /
Filesystem Size Used Avail Use% Mounted on
- 0 0 0 - /
yum install w3m -y
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding Packages from Extra Packages for Enterprise Linux 5 - x86_64
Finished
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package w3m.x86_64 0:0.5.1-18.el5 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
====================================================================================================================
Package Arch Version Repository Size
====================================================================================================================
Installing:
w3m x86_64 0.5.1-18.el5 os 1.1 M
Transaction Summary
====================================================================================================================
Install 1 Package(s)
Upgrade 0 Package(s)
Total download size: 1.1 M
Downloading Packages:
Error Downloading Packages:
w3m-0.5.1-18.el5.x86_64: Insufficient space in download directory /var/cache/yum/os/packages
* free 0
* needed 1.1 M
update:
I checked the yum code, it is using statvfs system call to check the diskspace. So other than creating a "real disk", I have no idea how can I bypass this issue.
I have a similar use case. I found this article: but for some reason yum continued to check for free disk space before downloading even with
diskspacecheck=0
I eventually decided to workaround:
yum clean all
mount -t tmpfs -o size=5G tmpfs /var/cache/yum