[Bug] Flatpak manifest using EOL KDE 6.6 and Freedesktop 23.08 runtimes #5
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
spalencsar/bearwave#5
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The Flatpak manifest is currently specifying End-of-Life (EOL) runtimes for KDE and Freedesktop, which triggers warnings during a fresh installation.
Steps to Reproduce
flatpak remote-add --user bearwave-repo https://flatpak.bearwave.app/bearwave.flatpakrepoflatpak install --user bearwave-repo de.nerdbear.bearwaveExpected Behavior
The Flatpak manifest should ideally target supported, actively maintained runtimes (like the newer KDE and Freedesktop branches) so the underlying platform continues receiving security updates without throwing EOL warnings.
Actual Behavior
Flatpak prompts with warnings that
org.kde.Platformbranch 6.6,org.freedesktop.Platform.GL.defaultbranch 23.08, and23.08-extraare end-of-life and no longer receiving fixes.Environment
Logs or Screenshots
Thanks for the great app, by the way! I am really enjoying it. 😊
Hi @setzor,
This issue has been resolved. I have updated the Flatpak manifest (
de.nerdbear.bearwave.json) to target the KDE 6.10 runtime branch (org.kde.Platform), replacing the deprecated KDE 6.6 and Freedesktop 23.08 runtimes.The updated application package has been built, signed, and deployed to our repository.
What to do:
To apply the changes and pull the new runtime, simply run:
Important note on upgrades:
Because this changes the underlying runtime platform, local QML caches might occasionally mismatch. If you encounter any unexpected QML errors or crashes (like the About dialog crashing) after the update, please clear the stale QML disk cache and restart the application:
Thank you very much for reporting this issue! I'm closing it now.