error: failed retrieving file 'garuda-qtile-settings-3.1.0-1-any.pkg.tar.zst' from geo-mirror.chaotic.cx : OpenSSL SSL_read: Connection reset by peer, errno 104
error: failed retrieving file 'libpcap-1.10.1-2-x86_64.pkg.tar.zst' from america.mirror.pkgbuild.com : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
error: failed retrieving file 'lcms2-2.13.1-1-x86_64.pkg.tar.zst' from america.mirror.pkgbuild.com : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
error: failed retrieving file 'libxkbcommon-1.4.0-1-x86_64.pkg.tar.zst' from america.mirror.pkgbuild.com : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
warning: too many errors from america.mirror.pkgbuild.com, skipping for the remainder of this transaction
error: failed retrieving file 'pipewire-pulse-1:0.3.45-1-x86_64.pkg.tar.zst' from america.mirror.pkgbuild.com : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
(86/86) checking keys in keyring [--------------------------------------------------------------------------------------] 100%
(86/86) checking package integrity [--------------------------------------------------------------------------------------] 100%
(86/86) loading package files [--------------------------------------------------------------------------------------] 100%
(86/86) checking for file conflicts [--------------------------------------------------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
expat: /usr/lib/cmake/expat-2.4.4/expat-config-version.cmake exists in filesystem
expat: /usr/lib/cmake/expat-2.4.4/expat-config.cmake exists in filesystem
expat: /usr/lib/cmake/expat-2.4.4/expat-none.cmake exists in filesystem
expat: /usr/lib/cmake/expat-2.4.4/expat.cmake exists in filesystem
expat: /usr/lib/libexpat.so.1.8.4 exists in filesystem
Errors occurred, no packages were upgraded.
Instead of pacman -Syu, can you try garuda-update?
The latter does all the mirrorlist update, syncing and keyrings stuff for you and may fix what you are experiencing
saibot@Saibot in ~
λ garuda-update
[sudo] password for saibot:
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck
--> Refreshing mirrorlists using rate-mirrors, please be patient..
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)
Failed to update mirrorlist
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck
--> Applying keyring updates before starting full system update..
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck
saibot@Saibot in ~ as 🧙 took 36s
[🔴] ×
First try removing the lock and repeat the update.
Should the garuda-update not work, I think you could consider restoring the latest working snapshot.
λ garuda-update
[sudo] password for saibot:
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck
--> Refreshing mirrorlists using rate-mirrors, please be patient..
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)
Failed to update mirrorlist
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck
--> Applying keyring updates before starting full system update..
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck
saibot@Saibot in ~ as 🧙 took 37s
[🔴] ×
im new user i star using linux recently so take it easy for me pls
thank you for your reply i really appreciate it really
you don't know what i'm going through this week just to find a good distro for me and i lost all my data
because i ask questions in linux community and people just dont give a *
actually it's a new installation and i think update successful from garuda repository i don't know why or how !!! it show me 3 errors after to tell me restart ?
saibot@Saibot in ~
λ yay -Syu
[sudo] password for saibot:
:: Synchronizing package databases...
core is up to date
extra is up to date
community 6.1 MiB 883 KiB/s 00:07 [--------------------------------------] 100%
multilib is up to date
chaotic-aur is up to date
:: Starting full system upgrade...
there is nothing to do
:: Looking for AUR upgrades
:: Looking for devel upgrades
there is nothing to do
saibot@Saibot in ~ as 🧙 took 10s
λ
