Package: network-manager Version: 1.30.6-1+deb11u1 While going though the journal log, I found, amoing other weird stuff, that P2P, whatever it might be, has failed: Mai 10 21:01:20 AnonymizedComputerName gnome-session[973]: gnome-session-binary[973]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mai 10 21:01:20 AnonymizedComputerName gnome-session[973]: gnome-session-binary[973]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mai 10 21:01:20 AnonymizedComputerName gnome-session-binary[973]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mai 10 21:01:20 AnonymizedComputerName gnome-session-binary[973]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mai 10 21:01:20 AnonymizedComputerName wireplumber[956]: SPA handle 'api.bluez5.enum.dbus' could not be loaded; is it installed? Mai 10 21:01:20 AnonymizedComputerName wireplumber[956]: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported. Mai 10 21:01:20 AnonymizedComputerName dbus-daemon[962]: [session uid=119 pid=962] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Started Virtual filesystem service - disk device monitor. Mai 10 21:01:20 AnonymizedComputerName dbus-daemon[962]: [session uid=119 pid=962] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.3' (uid=119 pid=955 comm="/usr/libexec/tracker-miner-fs ") Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Starting Virtual filesystem service - Apple File Conduit monitor... Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: <info> [1683745280.8952] device (wlp179s0): supplicant interface state: internal-starting -> disconnected Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: <info> [1683745280.8954] Wi-Fi P2P device controlled by interface wlp179s0 created Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: <info> [1683745280.8962] manager: (p2p-dev-wlp179s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5) Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: <info> [1683745280.8970] device (p2p-dev-wlp179s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: <info> [1683745280.8985] device (wlp179s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: <info> [1683745280.9002] device (p2p-dev-wlp179s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: <warn> [1683745280.9007] sup-iface[64aeaff5d52037a3,0,wlp179s0]: call-p2p-cancel: failed with P2P cancel failed The last line is yellow. The output of nmcli says, in red: p2p-dev-wlp179s0: nicht verbunden "p2p-dev-wlp179s0" wifi-p2p, hw As this is a warning I feel, ergo, warned. What is it, in plain English, that I am warned about? I use Wi-Fi on wlp179s0 (the connection had its issues, but they seem to be mitigated now, so that I can send and receive e-mails such as this one) but hate to be warned about non-issues. Or, if the warning shows a real issue (about the stuff I'm not using or not knowing to be using), it should be fixed. Any remedy? Any bugfix? Gratefully, AlMa
