On 7/12/24 00:45, Neal Becker wrote:
On Thu, Dec 5, 2024 at 7:37 PM Neal Becker wrote:
Did you find any problems other than the message?
I haven't seen any problems that were noticeable to me, and I've done
several updates since the one in question and as yet haven't had a
re-occurrenc
I got the same message again with dnf update this morning. Journalctl
shows this:
Dec 06 08:44:03 nbecker0 systemd[531438]: Reached target exit.target - Exit
the Session.
Dec 06 08:44:03 nbecker0 systemd[1]: user@0.service: Deactivated
successfully.
Dec 06 08:44:03 nbecker0 systemd[1]: Stopped use
Did you find any problems other than the message?
On Thu, Dec 5, 2024 at 4:04 PM Stephen Morris
wrote:
> On 6/12/24 02:09, Barry Scott wrote:
>
>
>
> On 5 Dec 2024, at 13:22, Neal Becker
> wrote:
>
> I didn't check the logs because I'm not sure what log to look for.
>
>
> Try the system journa
On 6/12/24 02:09, Barry Scott wrote:
On 5 Dec 2024, at 13:22, Neal Becker wrote:
I didn't check the logs because I'm not sure what log to look for.
Try the system journal.
But give you should reboot to have systemd update take effect you
could just check
that all services are running aft
> On 5 Dec 2024, at 13:22, Neal Becker wrote:
>
> I didn't check the logs because I'm not sure what log to look for.
Try the system journal.
But give you should reboot to have systemd update take effect you could just
check
that all services are running after the reboot. `systemctl --failed`
>>> Running trigger-install scriptlet:
systemd-0:256.9-2.fc41.x86_64c41.x86_64h46_64
>>> Finished trigger-install scriptlet: systemd-0:256.9-2.fc41.x86_64
>>> Scriptlet output:
>>> Failed to start jobs: Failed to enqueue some jobs, see logs for
details: Invalid argument
>>>
I didn't check the logs
