A few weeks ago I installed F32-KDE fresh on a workstation (a disk drive failed). All of a sudden last night Portal service was started (whatever that is). I did nothing that I know of to trigger this. Furthermore, since updating after installing this system, that service has never been started until now. Directly after the Portal service started, I see error messages coming from pipewire (whatever that is). Can anyone tell me what this is all about and why it happens now? (I'm especially concerned about why it started.) Jul 16 00:20:59 vfr systemd[1168]: Starting Portal service... Jul 16 00:20:59 vfr systemd[1168]: Starting flatpak document portal service... Jul 16 00:20:59 vfr systemd[1168]: Starting sandboxed app permission store... Jul 16 00:20:59 vfr systemd[1168]: Started sandboxed app permission store. Jul 16 00:20:59 vfr systemd[1168]: Started flatpak document portal service. Jul 16 00:20:59 vfr systemd[1168]: Starting Portal service (GTK+/GNOME implementation)... Jul 16 00:20:59 vfr systemd[1168]: Started Portal service (GTK+/GNOME implementation). Jul 16 00:20:59 vfr systemd[1168]: Created slice dbus\x2d:1.2\x2dorg.freedesktop.impl.portal.desktop.kde.slice. Jul 16 00:20:59 vfr systemd[1168]: Started dbus-:1.2-org.freedesktop.impl.portal.desktop.kde@0.service. Jul 16 00:20:59 vfr systemd[1168]: Started Multimedia Service. Jul 16 00:20:59 vfr systemd[1168]: Created slice dbus\x2d:1.2\x2dorg.freedesktop.secrets.slice. Jul 16 00:20:59 vfr systemd[1168]: Started dbus-:1.2-org.freedesktop.secrets@0.service. Jul 16 00:20:59 vfr rtkit-daemon[910]: Successfully made thread 199490 of process 199489 (/usr/bin/pipewire) owned by '1000' RT at priority 20. Jul 16 00:20:59 vfr gnome-keyring-daemon[199496]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Jul 16 00:20:59 vfr gnome-keyring-d[199496]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Jul 16 00:20:59 vfr systemd[1168]: Started Portal service. Jul 16 00:20:59 vfr pipewire[199489]: [E][000458567.198429][pipewire.c:118 open_plugin()] can't load /usr/lib64/spa-0.2/jack/libspa-jack.so: /usr/lib64/spa-0.2/jack/libspa-jack.so: cannot open shared object file: No such file or directory Jul 16 00:20:59 vfr pipewire[199489]: [E][000458567.198439][pipewire.c:254 pw_load_spa_handle()] can't load 'jack/libspa-jack': No such file or directory Jul 16 00:20:59 vfr pipewire[199489]: [E][000458567.198442][spa-device.c:144 pw_spa_device_load()] can't load device handle: No such file or directory Jul 16 00:20:59 vfr pipewire[199489]: [E][000458567.198444][module-device-factory.c:167 create_object()] can't create device: No such file or directory Jul 16 00:20:59 vfr pipewire[199489]: [E][000458567.198446][private.h:241 pw_core_resource_errorv()] resource 0x563498cde520: id:4 seq:4 res:-2 (No such file or directory) msg:"can't create device: No such file or directory" Jul 16 00:20:59 vfr pipewire[199492]: [E][000458567.198572][core.c:71 core_event_error()] core 0x559e4a521e00: proxy 0x559e4a54dbb0 id:4: seq:4 res:-2 (No such file or directory) msg:"can't create device: No such file or directory" Jul 16 00:20:59 vfr pipewire[199492]: [E][000458567.198579][media-session.c:1647 core_error()] error id:4 seq:4 res:-2 (No such file or directory): can't create device: No such file or directory Jul 16 00:20:59 vfr pipewire[199489]: [E][000458567.202044][alsa-pcm.c:33 spa_alsa_open()] hw:0,0: open failed: Device or resource busy Jul 16 00:20:59 vfr pipewire[199489]: [W][000458567.202053][adapter.c:175 find_format()] adapter 0x563498d30c90: can't get format: Device or resource busy Jul 16 00:20:59 vfr pipewire[199489]: [E][000458567.202056][module-adapter.c:231 create_object()] can't create node: Device or resource busy Jul 16 00:20:59 vfr pipewire[199489]: [E][000458567.202059][private.h:241 pw_core_resource_errorv()] resource 0x563498cde520: id:20 seq:74 res:-16 (Device or resource busy) msg:"can't create node: Device or resource busy" Jul 16 00:20:59 vfr pipewire[199492]: [E][000458567.218111][core.c:71 core_event_error()] core 0x559e4a521e00: proxy 0x559e4a56d5b0 id:20: seq:74 res:-16 (Device or resource busy) msg:"can't create node: Device or resource busy" Jul 16 00:20:59 vfr pipewire[199492]: [E][000458567.218124][media-session.c:1647 core_error()] error id:20 seq:74 res:-16 (Device or resource busy): can't create node: Device or resource busy Jul 16 00:21:29 vfr xdg-desktop-por[199455]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list -- Garry T. Williams _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
