Bug 404507

Summary:	Look & Feel script issue with launchers
Product:	[Plasma] plasmashell	Reporter:	Lt-Henry <quiqueiii>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED FIXED
Severity:	normal	CC:	hein, nate, notmart, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.18.0
Target Milestone:	1.0
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Lt-Henry 2019-02-18 08:02:44 UTC

SUMMARY
When Plasma dumps current layout javascript, launchers are exported as a single string. However, any attempt to import the script (either from dbus or look&feel tools) will fail to import launchers, creating a single broken launcher.

"launchers": "applications:org.kde.dolphin.desktop,applications:org.kde.konsole.desktop,applications:firefox.desktop,applications:org.kde.ksysguard.desktop,applications:systemsettings.desktop"

STEPS TO REPRODUCE
1. Attach some launchers to panel (firefox, konsole,...)
2. Dump layout:
qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.dumpCurrentLayoutJS

3. Create a look and feel package, and put dumped layout there.
4. Apply the package. 

OBSERVED RESULT
A single broken launcher is created.

EXPECTED RESULT
Expected launchers are not there.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.15
(available in About System)
KDE Plasma Version: 5.15
KDE Frameworks Version: 
Qt Version: 5.12

ADDITIONAL INFORMATION

Import expect launchers as an array of strings, can be easily solved with a text editor:

"launchers": ["applications:org.kde.dolphin.desktop", "applications:org.kde.konsole.desktop", ... ]

Comment 1 Marco Martin 2019-02-19 14:43:47 UTC

Eike: i an see problems there as favorites here are per activity.

any idea? maybe we need dedicated scripting bindings for this?

Comment 2 Nate Graham 2025-10-21 16:14:07 UTC

This is working in my testing today. The exported JS file can be used in a global theme to create a layout as expected.