Leebra
login register
That post seems to be missing.
load all comments
Fryboyter 18 points 3 years ago

Ran sudo pacman -Syu; sudo pacman -Syy like I do every few days

Syy forces the package database to be updated even if no updates are available.

In my opinion, this makes no sense, especially after you have already run pacman -Syu before. Basically, you only generate additional, unnecessary traffic on the mirror you are using. Pacman -Syu is normally always sufficient.

The journal was really long so I moved past it

The display of the systemd journal can be easily filtered. For example, with journalctl -p err -b -1, all entries of the last boot process that are marked as error, critical, alarm or emergency are displayed.

Has anyone else ran into this issue when updating?

Not me. But other users do. Some of them also use a distribution other than Arch (or a distribution based on it). When I look at the problems, the current kernel is probably quite a minefield as far as problems are concerned.

Any advice for preventing future crashes or issues like this so I don’t fear updating?

As other users have already recommended, you could additionally install the LTS kernel. And if you use BTRFS as a file system, create snapshots before an update (https://wiki.archlinux.org/...).

And it should be obvious that important data should be backed up on a regular basis.

save

path: 0 1365897, hotness: undefined, score: 18, children: 3
procrastinator 2 points 3 years ago

What if i run

pacman -Syyu

?

save

path: 0 1365897 1377006, hotness: undefined, score: 2, children: 2
Zenzio 4 points 3 years ago

I guess that's a bit better than the original command in question. But from what I understand it's still unnecessary and there is simply no need to force the refresh. A regular pacman -Syu is all you need and will refresh all databases that need it.

save

path: 0 1365897 1377006 1386829, hotness: undefined, score: 4, children: 1

thanks for using Leebra!

go to feed...