journal is spammed every minute by: janv. 26 15:18:23 xdg-desktop-por[2019]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Impossible d’appeler la méthode ; le serveur est mandataire d’un nom connu org.gnome.Shell sans propriétaire alors que le proxy a été construit avec le marqueur G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START janv. 26 15:19:23 xdg-desktop-por[2019]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Impossible d’appeler la méthode ; le serveur est mandataire d’un nom connu org.gnome.Shell sans propriétaire alors que le proxy a été construit avec le marqueur G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START janv. 26 15:20:23 xdg-desktop-por[2019]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Impossible d’appeler la méthode ; le serveur est mandataire d’un nom connu org.gnome.Shell sans propriétaire alors que le proxy a été construit avec le marqueur G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START janv. 26 15:21:23 xdg-desktop-por[2019]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Impossible d’appeler la méthode ; le serveur est mandataire d’un nom connu org.gnome.Shell sans propriétaire alors que le proxy a été construit avec le marqueur G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START I didn't find any explanation except that xdg-desktop-portal 1.4.2 has to be updated to 1.5. https://github.com/flatpak/xdg-desktop-portal-gtk/issues/215 This happens for as long as the journal is recorded. I have flatpak installed through dependency of discover: rpm -qa --last|grep discover discover-5.15.4-2.mga7.x86_64 jeu. 12 nov. 2020 09:13:23 CET I will try to uninstall discover and flatpak.
Uninstalling flatpak and xdg-desktop-portal and rebooting, works around the problem.
Source RPM: (none) => xdg-desktop-portal-1.4.2-1.mga7
or pick this one: https://github.com/matthiasclasen/xdg-desktop-portal/commit/a3fd03f852a27ac45fbaf740a965ce45af5f5390
@Papoteur, How this become appearing? Installing flatpak?
CC: (none) => ouaurelien
I presume yes. I installed it in November, but my journal is not so old. Until I uninstalled xdg-desktop-portal, this was present in journal every minute.
And what about xdg-desktop-portal-1.4.2-1.1.mga7 in Core/Updayes_testing repo?
CC: (none) => geiger.david68210
Hi David, Installed and rebooted. In journal, I have nothing else than what follows: journalctl -b |grep xdg-desk janv. 29 09:13:17 YZenbook.home dbus-daemon[4512]: [session uid=1000 pid=4512] Activating via systemd: service name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service' requested by ':1.120' (uid=1000 pid=11146 comm="deja-dup --delay Pas de route vers l???h??te") janv. 29 09:13:17 YZenbook.home dbus-daemon[4512]: [session uid=1000 pid=4512] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.121' (uid=1000 pid=11149 comm="/usr/libexec/xdg-desktop-portal") janv. 29 09:13:17 YZenbook.home dbus-daemon[4512]: [session uid=1000 pid=4512] Activating service name='org.freedesktop.impl.portal.desktop.kde' requested by ':1.121' (uid=1000 pid=11149 comm="/usr/libexec/xdg-desktop-portal") janv. 29 09:13:17 YZenbook.home xdg-desktop-por[11149]: Failed connect to PipeWire: Couldn't connect PipeWire remote Thus I have no more the warning. Thus OK. I don't know the last message means. Failed connect to PipeWire: Couldn't connect PipeWire remote
Thanks both to DavidG for yet another fix; and papoteur for confirming its efficacity. That should do for MGA7-64OK (if 64-bit). Should this now go to QA with an advisory?
Silence... I invent an advisory: Advisory -------- Bug 28224 Type: bugfix Subject: Updated xdg-desktop-portal package stops it spamming the journal RPM: xdg-desktop-portal-1.4.2-1.1.mga7 in Core/Updates_testing SRPM: xdg-desktop-portal-1.4.2-1.1.mga7.src.rpm Description: xdg-desktop-portal would in some circumstances spam the journal every minute with "Failed to get application states ... Failed: Could not get window list" error messages. This update only warns once if it does not find the shell api. Refs : https://github.com/flatpak/xdg-desktop-portal-gtk/issues/215 https://github.com/matthiasclasen/xdg-desktop-portal/commit/a3fd03f852a27ac45fbaf740a965ce45af5f5390 --- Assigning to QA to get this on its way. I think papoteur's test comment 6 is good for 64-bit OK; it would be difficult to reproduce, the origin is uncertain. Test update, though.
Assignee: bugsquad => qa-bugs
(In reply to papoteur from comment #6) > Hi David, > Installed and rebooted. > In journal, I have nothing else than what follows: > > journalctl -b |grep xdg-desk > janv. 29 09:13:17 YZenbook.home dbus-daemon[4512]: [session uid=1000 > pid=4512] Activating via systemd: service > name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service' > requested by ':1.120' (uid=1000 pid=11146 comm="deja-dup --delay Pas de > route vers l???h??te") > janv. 29 09:13:17 YZenbook.home dbus-daemon[4512]: [session uid=1000 > pid=4512] Activating via systemd: service > name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' > requested by ':1.121' (uid=1000 pid=11149 > comm="/usr/libexec/xdg-desktop-portal") > janv. 29 09:13:17 YZenbook.home dbus-daemon[4512]: [session uid=1000 > pid=4512] Activating service name='org.freedesktop.impl.portal.desktop.kde' > requested by ':1.121' (uid=1000 pid=11149 > comm="/usr/libexec/xdg-desktop-portal") > janv. 29 09:13:17 YZenbook.home xdg-desktop-por[11149]: Failed connect to > PipeWire: Couldn't connect PipeWire remote > > Thus I have no more the warning. Thus OK. > I don't know the last message means. > Failed connect to PipeWire: Couldn't connect PipeWire remote MGA7-64-OK Validating, Advisory pushed to SVN.
Keywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugsWhiteboard: (none) => MGA7-64-OK
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2021-0019.html
Status: NEW => RESOLVEDResolution: (none) => FIXED