Comment 4 for bug 1632317

Yes, that affects me too!
Nothing interesting in dmesg though:

[ 98.926095] Bluetooth: BNEP socket layer initialized
[ 103.721868] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 103.737027] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 103.740614] IPv6: ADDRCONF(NETDEV_UP): enp37s0: link is not ready
[ 104.110229] r8169 0000:25:00.0 enp37s0: link down
[ 104.110295] IPv6: ADDRCONF(NETDEV_UP): enp37s0: link is not ready
[ 105.925258] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 107.795972] wlo1: authenticate with 10:fe:ed:80:df:de
[ 107.815164] wlo1: send auth to 10:fe:ed:80:df:de (try 1/3)
[ 107.818403] wlo1: authenticated
[ 107.822100] wlo1: associate with 10:fe:ed:80:df:de (try 1/3)
[ 107.827017] wlo1: RX AssocResp from 10:fe:ed:80:df:de (capab=0x431 status=0 aid=3)
[ 107.827123] wlo1: associated
[ 107.827133] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
[ 113.340916] vboxdrv: Found 4 processor cores
[ 113.358285] vboxdrv: TSC mode is Invariant, tentative frequency 2294771026 Hz
[ 113.358288] vboxdrv: Successfully loaded version 5.0.32_Ubuntu (interface 0x00240000)
[ 113.396343] VBoxNetFlt: Successfully started.
[ 113.440206] VBoxNetAdp: Successfully started.
[ 113.505181] VBoxPciLinuxInit
[ 113.569007] vboxpci: IOMMU not found (not registered)
[ 163.273450] Bluetooth: RFCOMM TTY layer initialized
[ 163.273457] Bluetooth: RFCOMM socket layer initialized
[ 163.273464] Bluetooth: RFCOMM ver 1.11