Bugzilla – Bug 1222025
Discover reported errors
Last modified: 2024-04-16 18:35:10 UTC
Created attachment 873844 [details] Discover6 (6.0.2-2.1) error message Since some time Discover(6) shows at any update following error Message if "updateing" was selected (in additon to the root password request) a message will be provided like this (you need to cloth each of them): 1/4 Aborted due to failure (Flatpak system operation Deploy not allowed for user) 2/4 Aborted due to failure (Flatpak system operation Deploy not allowed for user) 3/4 Aborted due to failure (Flatpak system operation Deploy not allowed for user) 4/4 Aborted due to failure (Flatpak system operation Deploy not allowed for user) After (now failed) Update, and new start of the "update" the root key was requested again and the window will shown 3 times: 1/3 Aborted due to failure (Flatpak system operation Deploy not allowed for user) 2/3 Aborted due to failure (Flatpak system operation Deploy not allowed for user) 3/3 Aborted due to failure (Flatpak system operation Deploy not allowed for user) Now the update of (in my case 4 packages) it was gone. See attachment with the 4/4 message and the packages to be updated. $ zypper se -s discover Repository-Daten werden geladen... Installierte Pakete werden gelesen... S | Name | Type | Version | Arch | Repository ---+-----------------------------------------+-------+--------------+--------+----------------------- | aws-sdk-java-discovery | Paket | 1.11.3-11.1 | noarch | Haupt-Repository (OSS) i+ | discover6 | Paket | 6.0.2-2.1 | x86_64 | Haupt-Repository (OSS) i | discover6-backend-flatpak | Paket | 6.0.2-2.1 | x86_64 | Haupt-Repository (OSS) i | discover6-backend-fwupd | Paket | 6.0.2-2.1 | x86_64 | Haupt-Repository (OSS) i | discover6-backend-packagekit | Paket | 6.0.2-2.1 | x86_64 | Haupt-Repository (OSS) i | discover6-lang | Paket | 6.0.2-2.1 | noarch | Haupt-Repository (OSS) i+ | discover6-notifier | Paket | 6.0.2-2.1 | x86_64 | Haupt-Repository (OSS) | eclipse-p2-discovery | Paket | 4.15-13.1 | noarch | Haupt-Repository (OSS) | jakarta-commons-discovery | Paket | 0.5-1.5 | noarch | Haupt-Repository (OSS) | jakarta-commons-discovery-javadoc | Paket | 0.5-1.5 | noarch | Haupt-Repository (OSS) | kdsoap-ws-discovery-client-devel | Paket | 0.3.0-1.1 | x86_64 | Haupt-Repository (OSS) i | libKDSoapWSDiscoveryClient0 | Paket | 0.3.0-1.1 | x86_64 | Haupt-Repository (OSS) | netdiscover | Paket | 0.10-1.6 | x86_64 | Haupt-Repository (OSS) | python39-azure-mgmt-springappdiscovery | Paket | 1.0.0~b1-1.1 | noarch | Haupt-Repository (OSS) | python310-azure-mgmt-springappdiscovery | Paket | 1.0.0~b1-1.1 | noarch | Haupt-Repository (OSS) | python311-azure-mgmt-springappdiscovery | Paket | 1.0.0~b1-1.1 | noarch | Haupt-Repository (OSS) | python312-azure-mgmt-springappdiscovery | Paket | 1.0.0~b1-1.1 | noarch | Haupt-Repository (OSS)
I'm surprised that the flatpak applications are installed system-wide instead of per-user, but it should work anyway. Is polkit-kde-authentication-agent-1 running?
(In reply to Fabian Vogt from comment #1) > I'm surprised that the flatpak applications are installed system-wide > instead of per-user, but it should work anyway. Seems to be depending at the package and/or date of installation. > Is polkit-kde-authentication-agent-1 running? $ ps ax | grep polkit 1097 ? Ssl 0:00 /usr/libexec/polkit-1/polkitd --no-debug 4975 ? Ssl 0:00 /usr/libexec/polkit-kde-authentication-agent-1 Seams to be.
I also get it on 2 laptops running Tumbleweed and 1 running Leap 15.6 Beta. Speaking of polkit... It always comes up when I even open Discover and will clicking on Network it pops up too many times.
This resolved the issue for me on multiple laptops. https://forums.opensuse.org/t/discover-flatpak-update-error-message-aborted-due-to-failure-flatpak-system-operation-deploy-not-allowed-for-user/174151/6
Remove Flathap Repo at Discover have the negative side effect, that all installed Flatpacks are removed :-( But afterwards the as user installed flathub flatpak remote-add --if-not-exists --user flathub https://dl.flathub.org/repo/flathub.flatpakrepo seams to fix the issue, at least with only some flatpacks.