On Sun, May 1, 2022 at 6:35 AM Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote:
On Sun, 2022-05-01 at 09:18 -0300, Patrick Boutilier wrote:
>
>
> On 5/1/22 09:08, Patrick O'Callaghan wrote:
> > On Sun, 2022-05-01 at 12:48 +0100, Colin J Thomson wrote:
> > > On Sunday, 1 May 2022 12:14:00 BST Patrick O'Callaghan wrote:
> > > > This has been happening for IIRC) several months now at least:
> > > >
> > > > $ journalctl --boot=-1 --reverse
> > > > ...
> > > > May 01 10:44:26 Bree systemd[1210]: plasma-kded.service:
> > > > Consumed
> > > > 18.380s
> > > > CPU time.
> > > May 01 10:44:26 Bree systemd[1210]: Stopped KDE Daemon.
> > > > May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Failed
> > > > with result
> > > > 'timeout'.
> > > May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Main
> > > > process exited, code=killed, status=9/KILL May 01 10:44:26 Bree
> > > > systemd[1210]: plasma-kded.service: Killing process 1791
> > > > (ProfilesWatcher)
> > > > with signal SIGKILL. May 01 10:44:26 Bree systemd[1210]:
> > > > plasma-kded.service: Killing process 1722 (kded5) with signal
> > > > SIGKILL. May
> > > > 01 10:44:26 Bree systemd[1210]: plasma-kded.service: State
> > > > 'stop-
> > > > sigterm'
> > > > timed out. Killing. <-----------------------* May 01 10:43:03
> > > > Bree
> > >
> > > > Any idea why? I see some apparently related BZ entries dating
> > > > back
> > > > a
> > > > couple of years, but nothing recently.
> > >
> > > There was an issue related to kde-connect that caused a similar
> > > issue. This
> > > has since been fixed though.
> > >
> > > Do you use kde-connect by any chance?
What was the solution/fix for kde-connect?
This might be related, and might need a similar fix.
> >
> > No. I don't think I've every used it and certainly don't now.
>
>
> Try pressing the up arrow when the gui shutdown screen with the
> spinner
> is up. That should show you what process is taking so long. I have
> seen
> dnf/policykit stuff still running before on a long shutdown.
"A stop job is running for User Manager for UID 1000 (1m 20s...)"
UID 1000 is my account, and the delay counter matches the interval in
the journalctl record.
poc
It's related to this.[1][2]
It's related to the kernel
version, but from what I see, everyone seems to just want to fix the
symptom, and not fix the real problem.
If you are running CentOS Stream 8, the problem is much worse.[3]
Troy
_______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-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/kde@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
