Quassel client does not restore conncetion to core after network change
If the host's network connection is temporarily interrupted or altered (e.g. a network change from LAN to WLAN, or if the host goes into sleep mode and then reawakens), then Quassel client should seamlessly restore the connection to the core, or notify the user if the connection cannot be restored.
This does not seem to happen when running Quassel client on my laptop (Lenovo T14S, Debian Bullseye), and my colleagues report the same problem. Quassel client does not report a problem wit the network, but communication with the core appears to be broken, because no messages can be sent or received, until the client is restarted, or the core is manually disconnected and reconnected.
Looking at the code (https://github.com/quassel/quassel/blob/3778a12912369eb5add886bb65ca74e9df841744/src/client/coreconnection.cpp#L61), it appears that the client registers for the
onlineStateChanged signal, but perhaps it also needs to register for
configurationChanged, so that it can verify that a change of network configuration has not broken the connection to the Core.