| Summary: | Protocol 'plasmapackage' is not recognized in plasmoids anymore | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] libplasma | Reporter: | Martin Kostolný <clearmartin> |
| Component: | libplasmaquick | Assignee: | Marco Martin <notmart> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | lassana.nd, martin.blumenstingl |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Same problem here (I am also using Arch Linux). Is this desired behavior (= are plasmoids supposed to use relative imports instead of the plasmapackage prefix) or a bug (either in KF/Plasma or Arch Linux' packaging)? Yes, unfortunately the plasmapackage:/ scheme is not possible anymore since we switched to using a single QQmlEngine, so only relative paths do work now :/ It's unfortunate, but there is nothing we can do about it, becuase without relative or absolute paths we can't know anymore from what package the request comes |
With KF 5.12 update my plasmoids are not able to load anything starting with plasmapackage:/ anymore. That means they cannot load custom fonts, images etc. Reproducible: Always Steps to Reproduce: To reproduce this, create a very simple widget and paste this in it: FontLoader { source: 'plasmapackage:/fonts/custom-font.ttf' } ...of course place custom-font.ttf in proper folder. See plasma log, there will be a message: klauncher said: Unknown protocol 'plasmapackage'. The same message is shown when loading image: Image { source: 'plasmapackage:/images/picture.svg' } This looks like a regression introduced in KF 5.12. KF 5.11 was working fine. I've got: KF 5.12 Plasma 5.3.2 KDE Applications 15.04.3