Filling org.kde.plasma.quicklaunch per user

Ludwig Cornelius t_d_l_c at gmx.de
Fri Oct 13 09:45:11 UTC 2017


Am 12.10.2017 um 14:36 schrieb Marco Martin:
> On Thu, Oct 12, 2017 at 2:31 PM, Marco Martin<notmart at gmail.com>  wrote:
>> if the path of your script is in the updates list, has been executed.
>>
>>> b.) Is it possible at all to execute a javascript file on first login?
>> i am not sure that an update script would be executed at first
>> login... maybe you need to have a variation in the initial layout.js
> yes, the update scripts are definitely processed on first login as well...
> so, providing a file
> ~/.local/share/plasma/shells/org.kde.plasma.desktop/contents/updates/custom-quicklaunch-setup.js
> or something like that should definitely work
> (provided the file exists before the session is started up)
>
> --
> Marco Martin

Hi,

as soon as I create ~/.local/share/plasma/shells/org.kde.plasma.desktop/contents/updates/ (even when empty) I don't get a desktop anymore. I get a black screen with applications from my previous session and I can use Alt+F2. But no wallpaper or application menu. Tested with plasma 5.10.90/5.10.4/5.9.5. But when I copy /usr/share/plasma/shells/org.kde.plasma.desktop/ to this location I get my desktop back.

But do I really need to copy everything? Can I just use a metadata.desktop/metadata.json - file? Which is the correct value for X-KDE-ServiceTypes?


Cheers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/enterprise/attachments/20171013/20fc56ee/attachment.html>


More information about the Enterprise mailing list