Summary: | Conky doesn't start when Plasma is started as a systemd unit | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Vladimir Yerilov <openmindead> |
Component: | kcm_autostart | Assignee: | Nicolas Fella <nicolas.fella> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | plasma-bugs |
Priority: | NOR | ||
Version: | 5.22.0 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Vladimir Yerilov
2021-06-10 03:45:18 UTC
Just to be clear, did you enable the experimental systemd support in Plasma or did you write your own systemd unit? conky seems to fork after start, so it sounds like the issues described in https://bugs.kde.org/show_bug.cgi?id=433299 *** This bug has been marked as a duplicate of bug 433299 *** You are right, that's exactly what has been discussed in 433299. Regarding your questions: Yes, I enabled systemd support in Plasma and I thought that since 5.22 is would properly handle all simple autostart .desktop files with commands like `conky -d` I had to make a simple conky.service unit and now playing with it. Thanks, I learned something new today :) |