Description of problem: If I start Discover, go to Installed tab, and try to launch some of the preinstalled applications using the Launch button in the top right corner, most apps simply don't launch. For example, none of these can be started: Akregator Ark Dolphin Fedora Media Writer Gwenview KAddressBook Kate KCalc (and probably many more) On the other hand, these apps can be started just fine: Elisa Firefox Help (GNOME) I tried to install new applications, instead of testing existing ones, and it seems to behave the same way. I couldn't start KMyMoney and GCompris, but I could start Gedit. So far, it seems to me that KDE or QT-related apps mostly can't be started (Elisa works...) and other apps can. When looking into the system journal and trying to start some of those non-starting apps, I see only this printed (not sure if it is relevant): Oct 11 13:37:36 fedora runservice[6245]: QSocketNotifier: Can only be used with threads started with QThread Oct 11 13:37:36 fedora systemd[1118]: Started app-org.kde.akregator-fe0dad2ffc59406c8306db58b5dc5bbe.scope - Akregator - Feed Reader. Oct 11 13:37:36 fedora akregator[6250]: QSocketNotifier: Can only be used with threads started with QThread //EDIT: This only affects virtual machines together with Wayland sessions! See comment 6 and comment 8. Version-Release number of selected component (if applicable): plasma-discover-5.25.5-1.fc37.x86_64 How reproducible: always Steps to Reproduce: 1. start Discover 2. go to Installed 3. click on different apps and hit Launch in the top right corner
Created attachment 1917288 [details] rpm -qa output
Created attachment 1917289 [details] system journal
Proposing for a blocker discussion. Seems to be violating: > The default graphical package manager for a given software type must appropriately: > Start the selected installed software https://fedoraproject.org/wiki/Fedora_37_Final_Release_Criteria#Installing,_removing_and_updating_software
For comparison, I tested this on an F36 KDE Live image with plasma-discover-5.24.3-1.fc36, and the situation is better there, but also more unpredictable. The first few launch attempts (Akregator, Ark) didn't start anything, but I tested Dolphin, which worked, and Ark and Akregator started working as well. Afterwards several new apps launched correctly, just to discover KCalc to not start. After several more unsuccessful attempts, a different apps could be launched, and then KCalc started working as well. So in F36, there seems to be some race or something, and launching apps works just sometimes. In F37, it seems to consistently not work at all (for affected apps).
FYI: plasma-discover-5.26.0-1.fc38 is affected too, the same way.
So, a new discovery. This only affects virtual machines without 3D acceleration (3D off is the default state in virt-manager). If I enable 3D acceleration, I can run all apps just fine (except Fedora Media Writer, for some reason, but that will be unrelated to this). Also, on bare machines, I can start all apps (even when running with nomodeset).
(In reply to Kamil Páral from comment #6) > So, a new discovery. This only affects virtual machines without 3D > acceleration (3D off is the default state in virt-manager). If I enable 3D > acceleration, I can run all apps just fine (except Fedora Media Writer, for > some reason, but that will be unrelated to this). Also, on bare machines, I > can start all apps (even when running with nomodeset). Kamil, when I tested the same thing on a F37KDE vm upgraded from a F36KDE (the same VM I used to test version upgrade) all seems working fine, despite its a standart virt-manager uefi vm, without acceleration. plasma-discover-5.25.5-1.fc37.x86_64
Ahhh, I found the difference: Plasma-Wayland => Bug happens X11 session => No bugs I tested two others F37 KDE images on default UEFI vms and both the bugs only show itself at Plasma-wayland sessions. And at my F36=>F37 upgraded VM too, the diference was X11 session. When I change it to plasma-wayland the bug is present.
-7 blocker (+1, -8) in https://pagure.io/fedora-qa/blocker-review/issue/966 , marking rejected. bcotton gets the "I told you so" card. Marking as a proposed FE as there is FE discussion going on in the issue already.
Discussed during the 2022-10-17 blocker review meeting: [0] The decision to classify this bug as a "RejectedFreezeException (Final)" was made as, while there would be value in fixing this for installs of apps on first boot before updating, it seems too dangerous to risk poking the software installer this late. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-10-17/f37-blocker-review.2022-10-17-16.01.txt
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.