libsoup warnings from flatpak command line operations

[TraceyC77]

Please confirm there isn't an existing open bug report

• [X] I have searched open bugs for this issue

Summary

When running flatpak from command line, there are libsoup warnings

Steps to reproduce

1. Run flatpak update

Expected result

The operation completes with no warnings or errors

Actual result

 ~  flatpak update        
Looking for updates…

Nothing to do.

(flatpak update:46219): libsoup-WARNING **: 11:24:18.645: (../libsoup/soup-session.c:334):soup_session_dispose: runtime check failed: (soup_connection_manager_get_num_conns (priv->conn_manager) == 0)

(flatpak update:46219): libsoup-WARNING **: 11:24:18.645: (../libsoup/soup-connection-manager.c:84):soup_host_free: runtime check failed: (host->conns == NULL)

(flatpak update:46219): libsoup-WARNING **: 11:24:18.646: Disposing connection 0x558f7af3a9e0 while still connected

(flatpak update:46219): libsoup-WARNING **: 11:24:19.874: (../libsoup/soup-session.c:334):soup_session_dispose: runtime check failed: (soup_connection_manager_get_num_conns (priv->conn_manager) == 0)

(flatpak update:46219): libsoup-WARNING **: 11:24:19.874: (../libsoup/soup-connection-manager.c:84):soup_host_free: runtime check failed: (host->conns == NULL)

(flatpak update:46219): libsoup-WARNING **: 11:24:19.874: Disposing connection 0x558f7af386c0 while still connected

Environment

• [X] Is system up to date?

Repo

Unstable

Desktop Environment

Plasma

System details

Operating System: Solus 4.5 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.10.9-302.current (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 17.5 GiB of RAM Graphics Processor: AMD Radeon Vega 10 Graphics Manufacturer: LENOVO Product Name: 81SS System Version: Lenovo IdeaPad FLEX-14API

Other comments

I don't see these warnings on my other laptop, running Plasma 6.1.5. The system with the warnings produces the warnings on Plasma 6.1.5 as well as the Dev / git-master Plasma build

I recall we had similar warnings in the past but I don't know what happened to resolve them