Same experience. The updated completed though, but I had to pull up htop
to make sure it was. I’m glad you posted something because it removed my confusion.
edit:
$ pamac-manager --version
Pamac 10.7.0
Same experience. The updated completed though, but I had to pull up htop
to make sure it was. I’m glad you posted something because it removed my confusion.
edit:
$ pamac-manager --version
Pamac 10.7.0
oddly… as i was reviewing my sshd pacnew file… i had a hard reboot… no errors… came up fine though. on 6.14. Other than that, no issues.
I only use pamac-gui to update individual packages like the web browser. If a bigger update comes, I fire up pacman in the terminal emulator. This strategy has never failed me yet and I recommend it to all of you.
Better still — especially when there are updates to packages for your GUI — is to log out of the GUI and run the update process from a tty
. That way you reduce the amount of shared libraries that are still in use while they are being updated and thus overwritten.
See…
Before each big update I even run systemctl isolate multi-user.target
to be completely out of the desktop environment. Many updates since then installed without problem.
That’s not necessary. You can also do…
sudo systemctl stop sddm
… or likewise for gdm
or lightdm
.
noticed there seems to be an issue for install-grub with the recent grub update. it keeps failing with:
(2/4) Installing Grub to MBR/EFI
WARNING: Grub is not properly installed, system may not be bootable or other bootloader is used
error: command failed to execute correctly
was able to manually update grub with:
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi
though it still fails if trying to run the hook again via reinstalling the grub package
I didn’t know this one. I’ll write it down.
If you run this from a terminal, do you simply drop into a TTY?
Yes, but it would be advisable not to run this from a terminal window, and to log out of the GUI completely first — meaning that you have to be looking at the login screen before switching to a tty
— because if you don’t, then anything still running in your GUI session (or even the session itself) may not necessarily get shut down properly.
So, first log out, then switch to a tty
, log in there, and then issue the command. Replace sddm
with gdm
for GNOME and with lightdm
for Xfce.
Dolphin crashing on smb shares.
Workaround:
smb://192.168.2.150 or smb://nas crashes Dolphin
smb://192.168.2.150/ or smb://nas/ works fine.
A post was split to a new topic: Issues after an improper shutdown
You may look here for updating the generic EFI-Bootloader too.
i use update-grub to deal with the grub update after grub-install
EDIT: took me a minute to realize you were pointing to the fix sorry
I used Pamac GUI (Add/Remove Software), to perform the update, as did my partner (pamac-gtk3) now version 10.7.0-1.
Neither of us experienced any issues, while updating on KDE Plasma.
There were a number of new Orphans, 2 on my partner’s machine, and 6 on mine, that did not appear anywhere in the GUI, the cache showed 0 to be removed. I found them in the CLI pamac list -o
and removed them on both machines pamac remove -o
. That appears to be the only issue I have with the pamac GUI.
I’ll write a small script so my partner can easily find them, when she has to.
ADDITIONALLY: We had zero pacnew files… pacdiff -o
== no results listed
seems my issue with grub-install is because it is reading the efi partition on a older OS hardrive i use for the files on it, instead of reading the efi boot partition on my main drive
Welcome back to Europe! Update seems to be flawless from my point of view.
Researching such Things is what i used Supergrubdisk for. How did you find the different Bootloaders?
The last few updates I had pamac gtk 3 to crash but the update would finish successfully, after reading your comment I’ve installed pamac-gtk version 11 like you said and then performed the update, it crashed like the other version but the update went well anyways. I excluded AUR packages from the update, I update those after.
Latest update should include updates for lib32 packages
https://gitlab.manjaro.org/-/snippets/1107/raw
PACKAGE 20250412 20250504 ------------------------------------------------------------------------------- alsa-lib 1.2.13-1 1.2.14-1 lib32-alsa-lib 1.2.13-1 1.2.14-1
Or pacman-mirrors
to check system mirrorlist