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 user@0.service - User Manager for UID 0. Dec 06 08:44:03 nbecker0 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=user@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 06 08:44:03 nbecker0 systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0... Dec 06 08:44:04 nbecker0 systemd[1]: run-user-0.mount: Deactivated successfully. Dec 06 08:44:04 nbecker0 systemd[1]: user-runtime-dir@0.service: Deactivated successfully. Dec 06 08:44:04 nbecker0 systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0. Dec 06 08:44:04 nbecker0 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=user-runtime-dir@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 06 08:44:04 nbecker0 systemd[1]: Removed slice user-0.slice - User Slice of UID 0. Dec 06 08:44:04 nbecker0 systemd[1]: user-0.slice: Consumed 6.907s CPU time, 439.6M memory peak. Dec 06 08:44:04 nbecker0 systemd-logind[1174]: Removed session 48. Dec 06 08:44:06 nbecker0 wireplumber[2033]: wp-event-dispatcher: <WpAsyncEventHook:0x563a541849d0> failed: failed to activate item: Object activation aborted: proxy destroyed
On Thu, Dec 5, 2024 at 7:37 PM Neal Becker <ndbeck...@gmail.com> wrote: > Did you find any problems other than the message? > > On Thu, Dec 5, 2024 at 4:04 PM Stephen Morris <steve.morris...@gmail.com> > wrote: > >> On 6/12/24 02:09, Barry Scott wrote: >> >> >> >> On 5 Dec 2024, at 13:22, Neal Becker <ndbeck...@gmail.com> >> <ndbeck...@gmail.com> 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` is >> usually sufficient. >> >> I reported the same issue on this list a little while ago, but didn't >> really get a solution to this either. >> >> regards, >> Steve >> >> >> Barry >> >> >> >> -- >> _______________________________________________ >> users mailing list -- users@lists.fedoraproject.org >> To unsubscribe send an email to users-le...@lists.fedoraproject.org >> 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@lists.fedoraproject.org >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> > > > -- > *Those who don't understand recursion are doomed to repeat it* > -- *Those who don't understand recursion are doomed to repeat it*
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
