Bug 488259 - Documentation and implementation differ for installing KWin scripts
Summary: Documentation and implementation differ for installing KWin scripts
Status: REPORTED
Alias: None
Product: kwin
Classification: Plasma
Component: scripting (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-09 15:10 UTC by Matthias
Modified: 2024-06-09 15:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Screenshot 1 (360.11 KB, image/png)
2024-06-09 15:10 UTC, Matthias 		Details
Screenshot 2 (239.47 KB, image/png)
2024-06-09 15:10 UTC, Matthias 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias 2024-06-09 15:10:25 UTC 
Created attachment 170294 [details]
Screenshot 1

SUMMARY

The docs say I may import a KPackage via the systemsettings GUI
The KDialog window of said KCM asks for a .kwinscript instead. 

STEPS TO REPRODUCE
1. https://develop.kde.org/docs/plasma/kwin/#packaging-kwin-scripts
2. See screenshot

Operating System: Garuda Linux 
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.3-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics
Memory: 13,5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82L0
System Version: Yoga Slim 7 Carbon 14ACN6
Comment 1 Matthias 2024-06-09 15:10:43 UTC 
Created attachment 170295 [details]
Screenshot 2
Comment 2 Matthias 2024-06-09 15:14:21 UTC 
I should add, that I installed successful (but didnt bring my script to work, yet) via the also promoted kpackagetool. 

That means there could be the option to import via the KPackage format, as this seems to be supported on the command line already.