Hi Sebastien thanks for your support, the problem occured at 13:57. Here part of the loh. Hope this might help
gen 18 13:51:38 R2D2 kernel: intel_powerclamp: Start idle injection to reduce power gen 18 13:53:16 R2D2 rtkit-daemon[1724]: Supervising 9 threads of 5 processes of 1 users. gen 18 13:53:16 R2D2 rtkit-daemon[1724]: Supervising 9 threads of 5 processes of 1 users. gen 18 13:53:26 R2D2 kernel: intel_powerclamp: Stop forced idle injection gen 18 13:55:01 R2D2 CRON[179442]: pam_unix(cron:session): session opened for user root by (uid=0) gen 18 13:55:01 R2D2 CRON[179443]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) gen 18 13:55:01 R2D2 CRON[179442]: pam_unix(cron:session): session closed for user root gen 18 13:55:25 R2D2 systemd[2368]: Started Application launched by gsd-media-keys. gen 18 13:55:25 R2D2 systemd[2368]: Started VTE child process 179579 launched by gnome-terminal-server process 167917. gen 18 13:55:25 R2D2 systemd[2368]: gnome-launched-x-terminal-emulator-179567.scope: Succeeded. gen 18 13:55:50 R2D2 systemd-resolved[1049]: Failed to send hostname reply: Invalid argument gen 18 13:55:52 R2D2 rtkit-daemon[1724]: Supervising 9 threads of 5 processes of 1 users. gen 18 13:55:52 R2D2 rtkit-daemon[1724]: Supervising 9 threads of 5 processes of 1 users. gen 18 13:55:54 R2D2 rtkit-daemon[1724]: Supervising 9 threads of 5 processes of 1 users. gen 18 13:55:54 R2D2 rtkit-daemon[1724]: Supervising 9 threads of 5 processes of 1 users. gen 18 13:55:56 R2D2 NetworkManager[1490]: <info> [1610974556.9734] manager: NetworkManager state is now CONNECTED_SITE gen 18 13:55:56 R2D2 whoopsie[2206]: [13:55:56] offline gen 18 13:55:56 R2D2 dbus-daemon[1489]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=1490 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") gen 18 13:55:56 R2D2 systemd[1]: Starting Network Manager Script Dispatcher Service... gen 18 13:55:56 R2D2 dbus-daemon[1489]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' gen 18 13:55:56 R2D2 systemd[1]: Started Network Manager Script Dispatcher Service. gen 18 13:56:03 R2D2 systemd-resolved[1049]: Failed to send hostname reply: Invalid argument gen 18 13:56:03 R2D2 systemd-resolved[1049]: Failed to send hostname reply: Invalid argument gen 18 13:56:03 R2D2 systemd-resolved[1049]: Failed to send hostname reply: Invalid argument gen 18 13:56:06 R2D2 systemd[1]: NetworkManager-dispatcher.service: Succeeded. gen 18 13:56:09 R2D2 systemd-resolved[1049]: Failed to send hostname reply: Invalid argument gen 18 13:56:15 R2D2 systemd-resolved[1049]: Failed to send hostname reply: Invalid argument gen 18 13:56:23 R2D2 syncthing.desktop[2866]: [2Z4JW] 13:56:23 INFO: Disconnected from relay relay://176.9.147.217:22067 gen 18 13:56:27 R2D2 syncthing.desktop[2866]: [2Z4JW] 13:56:27 INFO: Could not connect to relay relay://51.255.75.9:22067/?id=4Y2VEN4-7NRYXYG-64X6KIU-B26R7LT-QPERGZI-4ZZ3MBR-DFKKAOE-EFT24Q6&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=www.agdi.info AGDI Data Recovery Services: dial tcp 51.255.75.9:22067: connect: no route to host gen 18 13:56:33 R2D2 systemd-resolved[1049]: Failed to send hostname reply: Invalid argument gen 18 13:56:37 R2D2 syncthing.desktop[2866]: [2Z4JW] 13:56:37 INFO: Could not connect to relay relay://5.9.154.53:22067/?id=4QJTDBX-5V56432-ZZZ5UXG-Z7PMWP7-ZFKB5OJ-PSKVII6-SROJDM5-SIZVCQK&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=: dial tcp 5.9.154.53:22067: i/o timeout gen 18 13:56:47 R2D2 syncthing.desktop[2866]: [2Z4JW] 13:56:47 INFO: Could not connect to relay relay://178.63.79.89:22067/?id=ANQMPFG-MGRLECJ-GJDGIK3-GYKXD5Q-GY6MIO6-OFEIXGL-POB4FI7-G7VTYAN&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=freifunk-3laendereck.net: dial tcp 178.63.79.89:22067: i/o timeout gen 18 13:56:48 R2D2 syncthing.desktop[2866]: [2Z4JW] 13:56:48 INFO: Could not connect to relay relay://89.42.31.58:22067/?id=A62AIM2-X6THY3I-EPB5AAA-P6N3K2D-TVKBKEE-6LJQGHD-3JMRZOB-YWYG3QJ&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=TUSIEK-UK: dial tcp 89.42.31.58:22067: connect: no route to host gen 18 13:56:48 R2D2 systemd-resolved[1049]: Failed to send hostname reply: Invalid argument gen 18 13:56:51 R2D2 syncthing.desktop[2866]: [2Z4JW] 13:56:51 INFO: Could not connect to relay relay://85.143.216.244:22067/?id=ZZH75EM-CQTOHQW-ZNYHBFF-VDNIX62-WCOSHLF-RDWCR36-HZD5OZK-GZ4TUAD&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=1500000&statusAddr=:22070&providedBy=667BDRM-Delfin: dial tcp 85.143.216.244:22067: connect: no route to host gen 18 13:56:54 R2D2 syncthing.desktop[2866]: [2Z4JW] 13:56:54 INFO: Could not connect to relay relay://89.14.194.61:22067/?id=DNNRZEH-YJMQ62S-LZ4ATBN-TYIOESN-24DXP6K-IBWXR5Q-XNG6UNS-VLOVAAF&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=: dial tcp 89.14.194.61:22067: connect: no route to host gen 18 13:56:58 R2D2 syncthing.desktop[2866]: [2Z4JW] 13:56:58 INFO: Could not connect to relay relay://88.86.115.98:22067/?id=Q75Z43J-XB56AZD-EKOJO7H-LMN2LXR-ZOG66JX-2GKCWH4-REGM3PJ-F4Y2DAQ&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=10000000&statusAddr=:22070&providedBy=https://datahoarder.dev/: dial tcp 88.86.115.98:22067: connect: no route to host gen 18 13:57:01 R2D2 syncthing.desktop[2866]: [2Z4JW] 13:57:01 INFO: Could not connect to relay relay://176.123.4.66:22067/?id=LAPNLXK-CHJ5GUO-HKP4GQK-J7THWTN-OV72HAC-ES77G6I-VSMCVD2-2WNDKAF&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=: dial tcp 176.123.4.66:22067: connect: no route to host gen 18 13:57:04 R2D2 syncthing.desktop[2866]: [2Z4JW] 13:57:04 INFO: Could not connect to relay relay://54.38.139.153:22067/?id=HIS4SL4-CLZPXPL-PNBALMH-BZETYFA-CIIBDSB-RTFTJ6Y-VQTFQ3F-JRYDFAA&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=: dial tcp 54.38.139.153:22067: connect: no route to host -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1911903 Title: Auto-reconnection of wifi doesn't work Status in network-manager package in Ubuntu: Incomplete Bug description: Hi everyone :) It's a problem that occurs without any possible correlation with other event (wake up, sleep etc). In the middle of a session the Wi-Fi simply stop working and not only the system doesn't reconnect automatically, but you need to turn off and back on the Wi-Fi to be able to continue your activities. IDK if it's related, but sometimes also happens that the other Wi-Fi networks around me are not visible in the setting. If I can help in any way with logs of any other information please contact me Antonio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 12:56:08 2021 InstallationDate: Installed on 2020-11-03 (73 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.178.1 dev wlp2s0b1 proto dhcp metric 20600 169.254.0.0/16 dev br-90c79c39374f scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-90c79c39374f proto kernel scope link src 172.18.0.1 linkdown 192.168.178.0/24 dev wlp2s0b1 proto kernel scope link src 192.168.178.52 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1911903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
