| Summary: | Config for offline updates no longer available | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Nicolas Fella <nicolas.fella> |
| Component: | Updates | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | akselmo, aleixpol, nate |
| Priority: | HI | Keywords: | regression |
| Version First Reported In: | 6.4.90 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/plasma/discover/-/commit/638c224f9916573ffe3dc6ca0ed3c49e8622b1d4 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
| Attachments: | Screenshot | ||
|
Description
Nicolas Fella
2025-09-29 21:05:19 UTC
This was cherry-picked to 6.5; raising priority to HI. Seems for me on Fedora 42 the ostree stuff is found -- Checking for module 'ostree-1' -- Found ostree-1, version 2025.6 -- Checking for module 'rpm-ostree-1' -- Found rpm-ostree-1, version 2025.10 A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/1166 Git commit 79df60ca93f554ed2078ffb855e4f1633cbd2dab by Arjen Hiemstra. Committed on 02/10/2025 at 12:37. Pushed by ngraham into branch 'master'. kcm: Restore runtime check for OSTree backend It's possible to build discover with the OSTree backend while running on a system that doesn't actually use OSTree. This would mean there's no option for selecting how system updates work even though the system supports choosing that, as the current logic is purely tied to a compile time check. This restores the runtime check if the OSTree backend was built. The systemd case is still based on a compile-time check as I don't know how to check that at runtime. M +6 -4 kcm/CMakeLists.txt M +7 -1 kcm/updates.cpp https://invent.kde.org/plasma/discover/-/commit/79df60ca93f554ed2078ffb855e4f1633cbd2dab Git commit 638c224f9916573ffe3dc6ca0ed3c49e8622b1d4 by Nate Graham. Committed on 02/10/2025 at 13:38. Pushed by ngraham into branch 'Plasma/6.5'. kcm: Restore runtime check for OSTree backend It's possible to build discover with the OSTree backend while running on a system that doesn't actually use OSTree. This would mean there's no option for selecting how system updates work even though the system supports choosing that, as the current logic is purely tied to a compile time check. This restores the runtime check if the OSTree backend was built. The systemd case is still based on a compile-time check as I don't know how to check that at runtime. (cherry picked from commit 79df60ca93f554ed2078ffb855e4f1633cbd2dab) Co-authored-by: Arjen Hiemstra <ahiemstra@heimr.nl> M +6 -4 kcm/CMakeLists.txt M +7 -1 kcm/updates.cpp https://invent.kde.org/plasma/discover/-/commit/638c224f9916573ffe3dc6ca0ed3c49e8622b1d4 |