Changing global theme erases latte-dock autostart
This has also been posted in the kde forum, but I'm getting no traction there. I'm hoping y'all might have some real insight into this issue.
I'm running on Arch linux, using plasma v5.26.2.
I've built/coded a number of global themes for my users by coding up a layout template which is common to all, and for each theme a separate look-and-feel. My themes use an autostarted instance of latte-dock which, until one of the recent plasma updates, would remain in place through the change of themes. Now, when a theme is changed, not only is the latte-dock process killed, the ~/.config/autostart/org.kde.latte-dock.desktop entry is deleted. I've been able to force the restart after a logout/login by using either 1) /etc/xdg/autostart; or 2) adding some shell scripted logic to .xinitrc that checks the look-and-feel name for my signature, then checks if an org.kde.latte-dock.desktop entry exists in ~/.config/autostart, creating one if one should be there. I consider these to be heavy-handed solutions, especially given that this requires the user to logout and login to restore the dock.
What I'd like to do is to handle this via the look-and-feel org.kde.plasma.desktop-layout.js file or via the layout-template's layout.js file. However, there doesn;t appear to be any way to create a symlink or copy a file from the javascript used in these 2 files. What I'd like to know is whether or not there is some way I have yet to find or figure out to perform file operations from these scripts, or if there's some entry that can be created in a config file to make sure that the dock is autostarted after a change in theme. Or is there a way to do this using the metadata.desktop file? Using the defaults file? Changing one of the qml source files? I'm at a loss at this point.
Any chance anyone here has some insight into this issue, and potentially some advice on how to resolve this?