KInfoCenter does not start on 20241013 nightly. When I try to start it, an application icon appears in the panel, but the application never starts and the panel icon is unresponsive. The openQA also sees this problem (https://openqa.fedoraproject.org/tests/2951499#step/infocenter/2) See screenshot. Nothing related seems to be shown in journalctl. Reproducible: Always Steps to Reproduce: 1. Boot the affected ISO, install KDE. 2. Start the installed system. 3. Try running infocenter. Actual Results: InfoCenter does not start. Expected Results: InfoCenter should start.
Created attachment 2052056 [details] Infocenter status pictured.
Proposed as a Blocker for 41-final by Fedora user lruzicka using the blocker tracking app because: Default application functionality
Same applies for System Settings on the same KDE nighthly.
Both apps start just fine for me, when using the same ISO in a VM on my local PC. Tested both the Live session and the installed system.
Discussed at a blocker review meeting [1], agreed on the following: AcceptedFreezeException (Final), punt (delay decision) on blocker status - this is fairly new and reproduction is inconsistent across testers and systems so far. We will delay the decision for further investigation. It is accepted as a freeze exception issue, though, as it's at least bad enough that we should fix it before release if possible [1] https://meetbot-raw.fedoraproject.org//meeting_matrix_fedoraproject-org/2024-10-14/
After some testing, we were able to reproduce this by reproducing as much as possible the OpenQA environment in virt-manager (3gb ram, Westmere CPU topology, 15gb HDD) and then this is decently easy to reproduce. Seems to be much harder to reproduce the faster the system is. We're still looking as to why this is happening.
I can confirm this is a regression from `qt6-qtwayland-6.7.1-1.fc41` to `qt6-qtwayland-6.7.2-4.fc41`. Will bisect later, if nobody does before me.
I would add to the above that today (20241015), same behaviour was with Akgregator in addition to System Settings and InfoCenter.
This may be substantially mitigated by the restoration of the fix for https://bugzilla.redhat.com/show_bug.cgi?id=2312900 , once that lands - it's in testing ATM and needs an FE to go in. For Rawhide it's stable already, but today's compose failed so it's not in the current repos.
Bisected to: https://codereview.qt-project.org/c/qt/qtwayland/+/574934 But the issue is indeed mitigated by the performance fix in kwin
Discussed during the 2024-10-21 blocker review meeting: [1] The decision to classify this bug as RejectedBlocker (Final) RejectedFreezeException (Final) was made: "This seems to be pretty much entirely mitigated by the fix for KDE performance under software acceleration (https://bugzilla.redhat.com/show_bug.cgi?id=2312900 ). there probably is still technically a bug here, and upstream is working on it, but it doesn't seem like we need to rush to pull it in for release." [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-10-21/f41-blocker-review.2024-10-21-16.00.log.html
FEDORA-2024-ced4c07da3 (qt6-qtwayland-6.8.0-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ced4c07da3
FEDORA-2024-da61e75151 (qt6-qtwayland-6.7.2-5.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-da61e75151
FEDORA-2024-ced4c07da3 (qt6-qtwayland-6.8.0-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
Re-opening for F41.
FEDORA-2024-da61e75151 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-da61e75151` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-da61e75151 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-da61e75151 (qt6-qtwayland-6.7.2-5.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.