When upgrade succeeds but warnings/errors scrolled by and are missed

When an upgrade succeeds, but you saw errors or warnings for some packages scroll by…

(Or didn’t see because you were doing something else and only saw that it succeeded)

Including but not limited to .pacnew files and messages about “manual intervention required,”

Is there a way to show the existing warnings/errors, without manually scrolling back pages and pages in terminal output? (Possibly losing some if buffer is low? Not mine, but could be an issue for some.)

I’ve always found it odd that pacman will emit these messages yet succeed, when often people may not watch the output anyway, except the end where it’s successful or not.

A few excerpts from my latest update. I know how to solve these, that’s not the question, it’s how to be alerted of them when you didn’t notice them scrolling by and the upgrade succeeded.

Error! nvidia/565.77: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!
==> dkms remove --no-depmod nvidia/580.95.05 -k 6.17.3-arch2-1

Error! nvidia/565.77: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!
==> dkms remove --no-depmod nvidia/580.95.05 -k 6.12.53-1-lts
==> depmod 6.17.3-arch2-1
==> depmod 6.12.53-1-lts

warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew

( 72/237) upgrading grub [---------------------------------------------------------------------------------------] 100%
:: To use the new features provided in this GRUB update, it is recommended
to install it to the MBR or UEFI. Due to potential configuration
incompatibilities, it is advised to run both, installation and generation
of configuration:

grub-install …

grub-mkconfig -o /boot/grub/grub.cfg

Look at /var/log/pacman.log. All pacman transactions are recorded there, including errors and warnings.

You can filter it in various ways, in the same way you can filter any text file.

2 Likes

Wow. I’ve been using Arch or Arch-based distros for several years, and somehow never picked up on that, even though looking in /var/logs for other stuff is standard. Thanks for the n00b lesson. :slight_smile: (No, seriously, that’s not sarcastic, you gave the answer, and it’s something I should have known.)

1 Like

please mark @Stagger_Lee thread as the solution for others looking for the same info. Thank you. Happy Endeavour

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.