After updating with pacman -Syu system fails to boot. ERROR: device '/dev/lvmSystemXXX/volRootXXX' not found. Skipping fsck. mount: /new_root: fsconfig() failed: /dev/lvmSystemXXX/volRootXXX: Can't lookup blockdev. ERROR: failed to mount '/dev/lvmSystemXXX/volRootXXX' on real root You are now being dropped into an emergecy shell. sh: can't access tty: job control truned off [rootfs ~]# Some background info Linux: [rootfs ~]# uname -a Linux archlinux 6.15.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 02 Aug 2025... x86_64 GNU/Linux Drives [rootfs ~]# blkid /dev/sdb2:UUID="A123456789" TYPE="crypto_LUKS" PARTUUID="A987654321" /dev/sdb1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="B123456789" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="B987654321" Is there a possibility to check if the kernel was updated and eventually downgrade from emergecy shell? mkinitcpio.conf file here # vim:set ft=sh # MODULES # The following modules are loaded before any boot hooks are # run. Advanced users may wish to specify all system modules # in this array. For instance: # MODULES=(usbhid xhci_hcd) MODULES=() # BINARIES # This setting includes any additional binaries a given user may # wish into the CPIO image. This is run last, so it may be used to # override the actual binaries included by a given hook # BINARIES are dependency parsed, so you may safely ignore libraries BINARIES=() # FILES # This setting is similar to BINARIES above, however, files are added # as-is and are not parsed in any way. This is useful for config files. FILES=() # HOOKS # This is the most important setting in this file. The HOOKS control the # modules and scripts added to the image, and what happens at boot time. # Order is important, and it is recommended that you do not change the # order in which HOOKS are added. Run 'mkinitcpio -H ' for # help on a given hook. # 'base' is _required_ unless you know precisely what you are doing. # 'udev' is _required_ in order to automatically load modules # 'filesystems' is _required_ unless you specify your fs modules in MODULES # Examples: ## This setup specifies all modules in the MODULES setting above. ## No RAID, lvm2, or encrypted root is needed. # HOOKS=(base) # ## This setup will autodetect all modules for your system and should ## work as a sane default # HOOKS=(base udev autodetect modconf block filesystems fsck) # ## This setup will generate a 'full' image which supports most systems. ## No autodetection is done. # HOOKS=(base udev modconf block filesystems fsck) # ## This setup assembles a mdadm array with an encrypted root file system. ## Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices. # HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck) # ## This setup loads an lvm2 volume group. # HOOKS=(base udev modconf block lvm2 filesystems fsck) # ## This will create a systemd based initramfs which loads an encrypted root filesystem. # HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck) # ## NOTE: If you have /usr on a separate partition, you MUST include the # usr and fsck hooks. HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck) # COMPRESSION # Use this to compress the initramfs image. By default, zstd compression # is used for Linux ≥ 5.9 and gzip compression is used for Linux Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default' [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf' [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.12.41-1-lts' [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] -> Running build hook: [base] ... [2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET] -> Running build hook: [modconf] [2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET] -> Running build hook: [block] [2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET] -> Running build hook: [encrypt] [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/13-dm-disk.rules': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/95-dm-notify.rules': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/11-dm-initramfs.rules': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/ossl-modules/legacy.so': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] install: error writing '/tmp/mkinitcpio.evH3PB/root/hooks/encrypt': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] -> Running build hook: [lvm2] [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/pdata_tools': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/11-dm-lvm.rules': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/13-dm-disk.rules': No space left on device ... [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/twofish_common.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/aegis128.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_raid6_recov.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/sm4-aesni-avx-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/curve25519-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast6_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast_common.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/hctr2.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/hid/hid-generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/ecrdsa_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/cdrom/cdrom.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/intel/iaa/iaa_crypto.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/nvme/host/nvme.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/wp512.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-raid.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/chelsio/chcr.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/scsi/virtio_scsi.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/fcrypt.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast5_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-mod.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/aegis128-aesni.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/des3_ede-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/crc32c-intel.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-thin-pool.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/camellia-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_pq.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/xxhash_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/vmac.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/raid456.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/crypto_null.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_xor.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/nvme/host/nvme-core.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cryptd.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/sm4_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cmac.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/xcbc.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/blake2b_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/sm3-avx-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-region-hash.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/padlock-sha.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/geniv.ko.zst': No space left on device ... [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/arch/x86/crypto/des3_ede-x86_64.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/crypto/seqiv.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/input/keyboard/applespi.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/fs/smb/common/cifs_arc4.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/mfd/max14577.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/vfio/vfio.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/fs/zonefs/zonefs.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: Could not create index 'modules.dep'. Output is truncated: No space left on device [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img' [2025-08-05T00:26:58+0200] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete. [2025-08-05T00:26:58+0200] [ALPM] running 'dbus-reload.hook'... [2025-08-05T00:26:58+0200] [ALPM] running 'detect-old-perl-modules.hook'... [2025-08-05T00:26:59+0200] [ALPM-SCRIPTLET] WARNING: '/usr/lib/perl5/5.40' contains data from at least 1 packages which will NOT be used by the installed perl interpreter. [2025-08-05T00:26:59+0200] [ALPM-SCRIPTLET] -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/5.40' [2025-08-05T00:26:59+0200] [ALPM] running 'fontconfig.hook'... [2025-08-05T00:26:59+0200] [ALPM] running 'fontconfig-32.hook'... [2025-08-05T00:27:00+0200] [ALPM] running 'gdk-pixbuf-query-loaders.hook'... [2025-08-05T00:27:00+0200] [ALPM] running 'ghc-register.hook'... [2025-08-05T00:27:13+0200] [ALPM] running 'glib-compile-schemas.hook'... [2025-08-05T00:27:13+0200] [ALPM] running 'gtk-update-icon-cache.hook'... [2025-08-05T00:27:14+0200] [ALPM] running 'texinfo-install.hook'... [2025-08-05T00:27:16+0200] [ALPM] running 'update-desktop-database.hook'... [2025-08-05T00:27:16+0200] [ALPM] running 'xorg-mkfontscale.hook'... [2025-08-05T00:27:18+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:18+0200] [PACMAN] synchronizing package lists [2025-08-05T00:27:21+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:21+0200] [PACMAN] synchronizing package lists [2025-08-05T00:27:24+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:24+0200] [PACMAN] synchronizing package lists [2025-08-05T00:27:27+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:27+0200] [PACMAN] synchronizing package lists [2025-08-05T00:28:00+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:28:00+0200] [PACMAN] synchronizing package lists [2025-08-05T00:29:00+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:29:00+0200] [PACMAN] synchronizing package lists

I have been getting the errors *Please switch to another Linux Mint mirror* and *Your APT configuration is corrupt* in Update Manager for the past week. I restored the default settings, so the error should not be due to the mirror. After reading a thread on forums.linuxmint.com about this issue, I ran a deep clean operation using BleachBit as suggested by a couple of users. Does this work? I tried refreshing Update Manager after the deep clean, but it's taking a long time and displaying *Updating cache: Waiting for mint-refresh-ca to exit*.

Some weeks ago, I updated and upgraded my Debian 11 system. My desktop environment is Cinnamon. Now, very often, the entire desktop freezes or displays strange graphical artifacts (like lines or glitches), and the system feels extremely laggy. I have to restart to fix it. What can I do to solve this problem?

I am still learning linux and have been running into a slight issue with my Raspbian OS system. I have uninstalled software like docker and vs code to clear up memory for my OMV NAS; however, they still show up when I run apt-get update. To be clear, everything is functioning properly. I have already tried the following commands: apt-get clean, apt-get autoremove, and reboot. I would like to clean up this part if at all possible. Cheers!

Is there a way to update the live system of Arch Linux? The reason I am asking this is because I absolutely need the newest version of archinstall, which currently is 3.0.8 and the current Arch ISO archlinux-2025.06.01-x86_64.iso only has version 3.0.7. Executing pacman -Syu in order to update all sources results in errors "could not extract ...tar.gz (Write failed)" which I interpret as not being able to update the live system (educated guess). Now, the next Arch ISO will be the one for 1st of July, but me being impatient would like to just bring all the necessary packages up-to-date and then run archinstall. Why do I need the current archinstall in at least version 3.0.8? Due to an error with a VirtualBox VM + enabled 3D acceleration, and a missing file xf86-video-vmware, it is not possible to install Arch with archinstall. Apparently, this error has been resolved in version 3.0.8.

The PackageKit Project dialog keeps popping up to prompt for the root password on my Debian Jessie desktop, apparently assuming that the logged in account has root permissions or knows the root password Is there someway to disable it in the desktop settings?

On several of my RHEL 9 machines managed by Ansible, the java-1.8.0-openjdk package is versionlocked: - name: java-1.8.0-openjdk-1:1.8.0.402.b06-2.el9 state: present However, Ansible tries to update it anyway, and this causes the Ansible Tower job to fail. Below are the corresponding commands when run via Bash shell. [myhost root ~]# dnf versionlock Updating Subscription Management repositories. rhel9flexnet 105 kB/s | 2.0 kB 00:00 rhel9checkmkagent 113 kB/s | 2.0 kB 00:00 rhel9elk8 97 kB/s | 1.7 kB 00:00 rhel9epel 127 kB/s | 2.3 kB 00:00 java-1.8.0-openjdk-1:1.8.0.402.b06-2.el9.* [myhost root ~]# dnf update Updating Subscription Management repositories. rhel9flexnet 112 kB/s | 2.0 kB 00:00 rhel9checkmkagent 122 kB/s | 2.0 kB 00:00 rhel9elk8 108 kB/s | 1.7 kB 00:00 rhel9epel 133 kB/s | 2.3 kB 00:00 Error: Problem: package java-1.8.0-openjdk-1:1.8.0.402.b06-2.el9.x86_64 from @System requires java-1.8.0-openjdk-headless(x86-64) = 1:1.8.0.402.b06-2.el9, but none of the providers can be installed - cannot install both java-1.8.0-openjdk-headless-1:1.8.0.442.b06-2.el9.x86_64 from rhel-9-for-x86_64-appstream-rpms and java-1.8.0-openjdk-headless-1:1.8.0.402.b06-2.el9.x86_64 from @System - cannot install both java-1.8.0-openjdk-headless-1:1.8.0.442.b06-2.el9.x86_64 from rhel-9-for-x86_64-appstream-rpms and java-1.8.0-openjdk-headless-1:1.8.0.402.b06-2.el9.x86_64 from rhel-9-for-x86_64-appstream-rpms - cannot install the best update candidate for package java-1.8.0-openjdk-headless-1:1.8.0.402.b06-2.el9.x86_64 - cannot install the best update candidate for package java-1.8.0-openjdk-1:1.8.0.402.b06-2.el9.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [myhost root ~]# dnf list installed java-1.8.0-* Updating Subscription Management repositories. Installed Packages java-1.8.0-openjdk.x86_64 1:1.8.0.402.b06-2.el9 @rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-headless.x86_64 1:1.8.0.402.b06-2.el9 @rhel-9-for-x86_64-appstream-rpms [myhost root ~]# dnf list available java-1.8.0-* Updating Subscription Management repositories. rhel9flexnet 111 kB/s | 2.0 kB 00:00 rhel9checkmkagent 122 kB/s | 2.0 kB 00:00 rhel9elk8 99 kB/s | 1.7 kB 00:00 rhel9epel 130 kB/s | 2.3 kB 00:00 Available Packages java-1.8.0-openjdk.x86_64 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-demo.x86_64 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-devel.x86_64 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-headless.x86_64 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-javadoc.noarch 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-javadoc-zip.noarch 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-src.x86_64 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms On a shell I would just run dnf update --exclude=java-1.8.0-* to bypass the problem and get a successful update. However, this needs to be done via Ansible playbooks. I am interested to know how would one do that via Ansible (workaround), and especially **why dnf tries to update versionlocked packages** (main issue). ---- EDIT 1 I've modified our update playbook: - name: Update packages yum: name: "{{ packages_name }}" state: latest exclude: "{{ (packages_donotupdate | default([])) | join(',') }}" so to exclude from the update the packages listed in the variable "packages_donotupdate" (if defined), but it does not work -- it does not update any package on the server. (Note: we use the "yum" Ansible module for backward compatibility reasons.)

Just trying to get a sanity check here. I've run several Ubuntu 22.04 servers for the past few years, configured for automatic security updates, and they have to reboot every 2 or 3 weeks. I've just run up my first 24.04, also on security-only, and it needs a reboot after 20 days. I occasionally get the feeling that I've mis-configured something. What uptime should I be expecting for security-only updates, given that some of those updates require a restart?

Desktop frozen after update installation. I was able to access Teletype screen but computer will not accept password. Any suggedtion to bypass? My software did come pre-installed. https://discuss.kde.org/t/kde-neon-6-cannot-login-after-update/12341

I am on Kubuntu 24.04 and I see when I open my Chrome browser the indication that New Chrome available and Chrome is out of date I don't see chrome reported in my software updates so I run the following command: $sudo apt-get update $ sudo apt-get --only-upgrade install google-chrome-stable Reading package lists... Done Building dependency tree... Done Reading state information... Done google-chrome-stable is already the newest version (129.0.6668.70-1). The following package was automatically installed and is no longer required: mailcap Use 'sudo apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. My browser was closed when I run this and when I reopened it I still see the indication on my top right part New Chrome available. When I check in the help menu the version reported is Version 129.0.6668.70 (Official Build) So what is the issue here? Is there a way to fix this? If not, how can I re-install Chrome and can I do it without losing my accounts that I log in? **UPDATE in response to the answer from user10489** There is a file named: google-chrome.list.distUpgrade and when I see the content it says: ### THIS FILE IS AUTOMATICALLY CONFIGURED ### # You may comment out this entry, but any other modifications may be lost. # deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main # deactivated during upgrade in noble

I have installed Debian 9 Stretch stable version today. I want to update my system. But I didn't find package list for sources.list. In the site, I found Debian 9 sources.list package. But this list for Debian 9 Testing. Can I use it for stable Debian 9? or where is Debian 9 sources.list? How can I update my system? Debian 9 was released yesterday. Do I need to update the system?

When I go to Update in the software Discover in Debian 12, I get the following error message: E: https://download.sublimetext.com apt/stable/ InRelease is not (yet) available (Could not connect to 160.86.242.23:8080 (160.86.242.23), connection timed out) E: http://security.debian.org/debian-security bookworm-security InRelease is not (yet) available (Could not connect to 160.86.242.23:8080 (160.86.242.23), connection timed out) E: https://deb.nodesource.com/node_22.x nodistro InRelease is not (yet) available (Could not connect to 160.86.242.23:8080 (160.86.242.23), connection timed out) E: https://linux.teamviewer.com/deb stable InRelease is not (yet) available (Could not connect to 160.86.242.23:8080 (160.86.242.23), connection timed out) E: http://debian.otenet.gr/debian bookworm InRelease is not (yet) available (Could not connect to 160.86.242.23:8080 (160.86.242.23), connection timed out) E: https://cli.github.com/packages stable InRelease is not (yet) available (Could not connect to 160.86.242.23:8080 (160.86.242.23), connection timed out) E: http://debian.otenet.gr/debian bookworm-updates InRelease is not (yet) available (Unable to connect to 160.86.242.23:8080:) Can someone tell me what is happening and how I can fix it? I don't have similar behavior when I do: sudo apt update && sudo apt upgrade or flatpak update. It is only through Discover and I need Discover because I use KDE and have addons. I would also appreciate if someone new how I can update KDE addons from the command line.

Current system Debian12. Sometimes (maybe 1 time in 100) during a boot, while the boot screen is still showing, downloads are occurring. How can I prevent that? One way is to always boot with LAN cable unplugged - however I would rather find the setting to control that. I don't even have the apt unattended-upgrades package installed, so it is not that.

I'm using Kali 2024, and trying to update but I receive the following errors. I tried everything mentioned on other's comments but I'm still unable to update. I'd appreciate it if anyone could help. ┌──(root㉿kali)-[~] └─# apt-get update Ign:2 http://http.kali.org/kali kali-rolling InRelease Err:3 http://http.kali.org/kali kali-rolling Release Redirection from https to 'http://kali.download/kali/dists/kali-rolling/Release ' is forbidden [IP: 18.211.24.19 443] Ign:1 http://www.kali.org/kali kali-rolling InRelease Err:4 http://www.kali.org/kali kali-rolling Release 404 Not Found [IP: 104.18.4.159 443] Reading package lists... Done E: The repository 'https://http.kali.org/kali kali-rolling Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://kali.org/kali kali-rolling Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. N: Repository 'Kali Linux' changed its 'firmware component' value from 'non-free' to 'non-free-firmware' N: More information about this can be found online at: https://www.kali.org/blog/non-free-firmware-transition/ This is also my sources.list: ──(root㉿kali)-[~] └─# cat /etc/apt/sources.list # See http://www.kali.org/docs/general-use/kali-linux-sources-list-repositories/ deb https://http.kali.org/kali kali-rolling main contrib non-free non-free-firmware # Additional line for source packages deb-src http://kali.org/kali kali-rolling main contrib non-free non-free-firmware and also there's nothing on my sources.list.d directory. Any idea?

I use various way of installing application - apt install - snap install - .deb But every time, when I need to update a program I struggled to find which method I use to install, therefore which method I need to use to update it. How can I know easily know which installation method I used ?

Total newbie here so please bear with me. I have a laptop on which I have installed Debian 11.6 I want to check if my OS has reached EOL. In the official Debian webpage, I see the following list (screenshot below). My question is "does 11.6 fall into LTS category"? How can I make sure my OS receiving security updates?

My goal is to give a laptop (with Debian) to a person who will only use it to browse the web. And who will not open the terminal to type sudo apt update...etc. I started looking and was told that gnome-software update does the job. But then here is my question: how is the reboot done ? I imagine it is often necessary. Is the need to reboot explicitly signaled to the user?

I know how check if new packages are available **with** root privilegies. But how can I do it from shell script without sudo or editing sudoers. I'm using Debian 12 with openbox. Thanks! PS. I know about package-update-indicator, but I'd like to use plain shell script solution.

So I'm currently in internship and we work with Linux Mint. I have never worked with Mint before, so I have no idea how some things work. My boss gave me a project to make a guide on how to update Libreoffice from the terminal, and eventually make it an executable file so people on other machines can simply click the executable file and have libreoffice instantly updated to the latest version. However, I do not know what the right commands are, I have tried this so far: sudo apt-get install libreoffice and sudo add-apt-repository ppa:libreoffice/ppa sudo apt-get update && sudo apt-get dist-upgrade They only work on Linux Mint version 18, but on version 17 I get errors. Sometimes it says it has been updated while it has not and I just get pretty frustrated because I want to show my potential to my boss, any help please?

Since at least yesterday, my Manjaro (kernel 6.1.112-1) fails to open the GUI of the software manager. It is however able to open it in other instances: when the little icon reminds me, that there are updates to be made, it opens the software manager GUI in the update tab and I can run updates, but it crashes when I try to switch to another tab. When there are no updates to be made, I cant open it by any of the usual mouse clicks - instead I just get a message "software adding/deleting is started (failed)" (roughly translated from my system language). However I am able to open it via terminal by pamac-manager %U and if opened this way I can freely switch tabs (I havent yet tried opening it this way, updating something and checking whether it still works, just because right now there are no updates to be made). sudo pacman -Syu reveals everything is up to date (since a google search revealed that was the problem for someone else). Maybe one of you can help me with where to look for the problem or what else to check or try out. I am thankful for any ideas.