https://bugs.kde.org/show_bug.cgi?id=528003
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #197797|0 |1 is obsolete| | --- Comment #4 from [email protected] --- Created attachment 198013 --> https://bugs.kde.org/attachment.cgi?id=198013&action=edit Patch v2: also removes After=default.target from the .service (covers bug 528249) Updated patch attached. It now also removes After=default.target from drkonqi-coredump-cleanup.service, which Tobi S. identified in bug 528249. That unit is ordered Before=plasma-core.target, so with After=default.target the whole Plasma session ends up waiting for default.target. On my machine nothing in default.target is slow so it costs nothing visible, but the ordering is there: before: After=-.mount basic.target default.target app.slice drkonqi-coredump-cleanup.timer after: After=basic.target -.mount app.slice drkonqi-coredump-cleanup.timer Before=plasma-core.target is unchanged. I checked all eight drkonqi user units. Besides the three in the patch, only drkonqi-coredump-launcher.socket has After= on a generic target (sockets.target), but socket units don't get an implicit Before=sockets.target in the user manager, so there's no contradiction there. The remaining units have no After= on generic targets. Still no ordering cycles after a reboot with the extended patch. -- You are receiving this mail because: You are watching all bug changes.
