Bug 1468239
| Summary: | discover crashes in setupFlatpakInstallations() | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> |
| Component: | plasma-discover | Assignee: | Rex Dieter <rdieter> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | afolger, aleixpol, awilliam, fedora, jgrulich, kde-sig, lonelywoolf, luigi.toscano, mattdm, rdieter, robatino, swagstaff2 |
| Target Milestone: | --- | Keywords: | CommonBugs |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedBlocker https://fedoraproject.org/wiki/Common_F26_bugs#discover-crash-flatpak | ||
| Fixed In Version: | plasma-discover-5.10.2-1.fc26 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-18 22:23:35 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1396704 | ||
|
Description
Kamil Páral
2017-07-06 12:33:12 UTC
Seems to be a blocker: "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test. " https://fedoraproject.org/wiki/Fedora_26_Final_Release_Criteria#Default_application_functionality Some likely duplicates, bug #1461670 and bug #1463419 From the latter, this warning may be relevant: (process:4109): flatpak-WARNING **: Unable to create FlatpakInstallation for: mkdir(/var/lib/flatpak): Permission denied KCrash: Application 'plasma-discover' crashing... I'll see about getting a plasma-discover-5.10.3 build to test, I see there's been over 200 commits in upstream 5.10 branch since 5.10.1 release. -1 to blocker for time-related reasons. Hopefully the fix Rex is looking at can be a zero day -- going to something with over 200 commits seems like too big of a risk for last-minute blocker. Hi, Discover maintainer here. I just pushed this, can you see if it makes it any better? https://commits.kde.org/discover/e062f0e946489d8c10c656379b229de1c117e21b Also a backtrace with symbols could be useful, as well as any errors that could be seen in stdout/stderr. Discussed at 2017-07-06 Fedora 26 Final Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-2/2017-07-06/f26_final_gono-go_meeting.2017-07-06-17.00.html . We agreed that by rights, this is a clear criteria violation and ought to block F26 Final. However, we did note a few things: * Fedora 26 is considerably behind its expected release cadence (in theory we still want to be on April / October or May / November) * Both our major downstream (RH) and Fedora itself has strong reasons not to want F26 delayed further (for Fedora, F27 is going to be a major cycle with huge changes landing, and every delay to F26 is effectively time stolen from F27's cycle) * This bug was discovered extremely late, when it could have been discovered and dealt with far earlier if the testing had been done * Fedora's release approach is officially neither entirely determined by time ('release on the chosen date regardless of quality') or quality ('release when we reach a specific quality standard regardless of time'), but a hybrid of both, as stated at https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Development_Schedule * The app in question is not of vital importance at release time; it's likely to be rarely used in live sessions, and is not required to update the system. This means we can ship an update for it which should prevent it causing many real practical problems Taking all these factors into consideration, as we have previously done once or twice for similar extremely-late-discovered bugs, we decided to make this a Fedora 27 blocker instead. We also agreed we will produce a formal policy for this kind of 'waive' going forward, to ensure we implement it consistently and it is not used excessively in future. We also agreed to make efforts to ensure KDE testing (particularly the 'run all the applications' test) will be done earlier in the cycle in future. Apparently plasma-discover-5.10.2-1 does not crash; it was built on koji some time ago: https://koji.fedoraproject.org/koji/buildinfo?buildID=908393 Only problem: it has a unversioned dependency on kf5-kirigami2, but it really depends on the version 2.1.0: https://koji.fedoraproject.org/koji/buildinfo?buildID=885203 It's possible it is crashing because of missing flatpak as dependency because it was added later. Can someone else verify that installing flatpak makes thing suddenly work? I have one confirmation from this bugzilla https://bugs.kde.org/show_bug.cgi?id=382188. Flatpak should be automatically installed with plasma-discover-5.10.1-2 and newer, which means that fix for this issue is already in updates. (In reply to Jan Grulich from comment #9) > Can someone else verify that installing flatpak makes thing suddenly work? I can confirm this. plasma-discover-5.10.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-4adf59bd1c I installed flatpack, but did not resolve the problem. "flatpack" with 'c' is some XML library, you need "flatpak" WITHOUT 'c'. Doh! I'll try and let you know installing flatpak fixed it, thanks plasma-discover-5.10.2-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-4adf59bd1c plasma-discover-5.10.2-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. I am running Fedora 27, which includes plasma-discover-5.11.4-1.fc27.x86_64, and the issue persists. |