home user:
> > The problem is I don't know that the kernel is going to update until it's
> > too late: when I run the "dnf upgrade".
Francis:
> I always do first a "dnf check-update", then if I agree:
>
> nohup dnf -y update &
>
> (a systemd-run will be even better/safer than nohup)
>
I *ne
Hi.
On Wed, 21 Aug 2024 19:58:11 -0600 home user via users wrote:
> The problem is I don't know that the kernel is going to update until it's
> too late: when I run the "dnf upgrade".
I always do first a "dnf check-update", then if I agree:
nohup dnf -y update &
(a systemd-run will be even b
(general response)
I realize this isn't my thread, and the symptoms I experience are partially
different from those that Francois is experiencing. But there is overlap.
I thank everyone who tried to help. The helpful posts were:
* Robert's: confirmed that the 6.10.x kernels are not yet suppor
On Wed, Aug 21, 2024 at 7:35 AM Patrick O'Callaghan
wrote:
> I keep getting this in the journal:
>
> Lockdown: systemd-logind: hibernation is restricted; see man
> kernel_lockdown.7
>
> and a glance at the man page reveals that hibernation and secure boot
> don't play nice unless the swap image f
I keep getting this in the journal:
Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
and a glance at the man page reveals that hibernation and secure boot
don't play nice unless the swap image filesystem is encrypted. My
immediate reaction is to disable Secure Boot,
