https://bugs.kde.org/show_bug.cgi?id=477805
Bug ID: 477805
Summary: Service start timeout is ridiculously short
Classification: Plasma
Product: policykit-kde-agent-1
Version: 5.27.9
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: stefan.bru...@rwth-aachen.de
CC: d...@kde.org, jgrul...@redhat.com, jrez...@redhat.com
Target Milestone: ---
SUMMARY
The start timeout (walltime) is 5 seconds, which is significantly too short in
an emulated virtual machine, especially during session start when many services
are causing CPU and disk load.
STEPS TO REPRODUCE
1. Create an emulated virtual machine, e.g. aarch64 on x86_64
2. (install/use a live distribution)
3. Start a Plasma session
OBSERVED RESULT
polkit-kde-agent-1 is starting and killed after 5 seconds, started again,
killed again, etc.
This can happen 100 times in a row. Sometimes other plasma services run into
the same problem, exaggerating the problem.
EXPECTED RESULT
All services are just started once, as fast or slow as the system permits.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15
ADDITIONAL INFORMATION
https://invent.kde.org/plasma/plasma-workspace/-/wikis/Plasma-and-the-systemd-boot
> The default timeout between quit signal and killing is ridiculously long
The "quit" timeout should be set with "TimeoutStopSec", not with "TimeoutSec".
Gnome services have this correctly set, all Plasma services have this wrong.
--
You are receiving this mail because:
You are watching all bug changes.
