SUMMARY Since first experiments on starting Plasma as systemd unit I've been hitting the same issue: conky doesn't get started despite the fact that it has a proper entry (and .desktop file accordingly) in Autostart section of Systemsettings when such unit (plasma-plasmashell.service) is enabled. STEPS TO REPRODUCE 1. Add conky app to Autostart section, enable systemd start of Plasma desktop 2. Write `conky` into the "Don't restore these applications" field in Desktop Session 3. Log out, log in OBSERVED RESULT No conky process observed OR Two (2) conky processes when it is NOT excluded from a session to be restored EXPECTED RESULT Having one conky process initiated by one desktop file according to Autostart entry SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
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 :)