On 3/31/21 11:30 PM, Qiyu Yan wrote:
Just now during a routine update using `dnf update` my desktop process gnome-shell crashed. Afterwards, I checked dnf history and /var/log/dnf.log to see if any inconsistency is present. dnf.log didn't report the last transaction as completed, but `dnf history info last` report the action was successful. luckily, I didn't see any inconsistency in my system. I just have to manually clean rpm files left in cache. Seems that dnf is killed just when transaction done, before it can write to dnf.log? While is it possible that dnf gets killed during transaction and breaks the system when desktop session dies? Do we have a approach to avoid this? Like telling dnf to ignore signals when doing important things (does dnf have this already?)
There is always a risk when doing live upgrades. That's why the preferred method is offline upgrades. The Software application has done that for a long time and now dnf has support as well. If you have the system-upgrade plugin installed, you can do "dnf offline-upgrade" with the same options as "system-upgrade".
If you really don't want to do offline upgrades then you can run dnf in a screen or tmux session to protect it.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
