View previous topic :: View next topic |
Author |
Message |
ololoshwin n00b
Joined: 25 Nov 2021 Posts: 7
|
Posted: Fri Dec 24, 2021 9:56 pm Post subject: [SOLVED] systemd KDE Plasma/Kickoff create failed units |
|
|
$ systemctl --user status
● localhost
State: degraded
Jobs: 0 queued
Failed: 4 units
Failed unit counter increments on application launch by Plasma/Kickoff.
Application works without issues.
Failed unit example:
Code: | systemctl --user status app-org.kde.kate-0ba03c5f0ffa4bd19bee81c96441bfa3.scope
x app-org.kde.kate-0ba03c5f0ffa4bd19bee81c96441bfa3.scope - Kate
Loaded: loaded (/home/user/.local/share/applications/org.kde.kate.desktop; transient)
Transient: yes
Active: failed (Result: resources)
Tasks: 8 (limit: 18882)
Memory: 89.5M
CPU: 1.104s
CGroup: /user.slice/user-2020.slice/user@2020.service/app.slice/app-org.kde.kate-0ba03c5f0ffa4bd19bee81c96441bfa3.scope
`-3774 /usr/bin/kate -b --tempfile
Dec 25 01:07:16 localhost systemd[441]: app-org.kde.kate-0ba03c5f0ffa4bd19bee81c96441bfa3.scope: No PIDs left to attach to the scope's control group, refusing: Success
Dec 25 01:07:16 localhost systemd[441]: app-org.kde.kate-0ba03c5f0ffa4bd19bee81c96441bfa3.scope: Failed with result 'resources'.
Dec 25 01:07:16 localhost systemd[441]: Failed to start Kate |
How to solve No PIDs left to attach to the scope's control group error?
Last edited by ololoshwin on Sat Dec 25, 2021 10:02 am; edited 1 time in total |
|
Back to top |
|
|
ololoshwin n00b
Joined: 25 Nov 2021 Posts: 7
|
Posted: Fri Dec 24, 2021 10:20 pm Post subject: |
|
|
alt+f2 command line create active scope and launch application in the scope. |
|
Back to top |
|
|
sam_ Developer
Joined: 14 Aug 2020 Posts: 1678
|
Posted: Sat Dec 25, 2021 12:45 am Post subject: |
|
|
See bug 829596. Stabilisation of fixed systemd is underway in bug 829887. |
|
Back to top |
|
|
ololoshwin n00b
Joined: 25 Nov 2021 Posts: 7
|
Posted: Sat Dec 25, 2021 10:04 am Post subject: |
|
|
Thanks. Systemd update fixes error. |
|
Back to top |
|
|
|