Ubuntu

Network(Public network) get disconnected automaically again and again

Asked by Lalit Singh Dhidwal

Hi Team,

The network gets disconnected, again and again, I have to manually disable and re-enable the network setting to get it working. After checking the server logs It seems to be a DNS server issue. Below are the logs for your reference.

Aug 16 15:33:37 xxxxxxxx systemd-resolved[659]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 15:33:37 xxxxxxxx systemd-resolved[659]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 15:33:37 xxxxxxxx systemd-resolved[659]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 15:33:37 xxxxxxxx systemd-resolved[659]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 15:33:37 xxxxxxxx systemd-resolved[659]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 15:33:37 xxxxxxxx systemd-resolved[659]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 15:33:37 xxxxxxxx systemd-resolved[659]: Using degraded feature set (UDP) for DNS server 127.0.0.1.

root@xxxx:~# cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 8.8.8.8
nameserver 127.0.0.1
root@xxxxxx:~# ls -aril /etc/resolv.conf
359761264 lrwxrwxrwx 1 root root 32 Aug 16 15:41 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf
root@xxxxxx:~# cat /run/systemd/resolve/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 8.8.8.8
nameserver 127.0.0.1

I have checked some article and unlink the previous config file and relink it again with /run/systemd/resolve/resolv.conf

But the issue still persists, Also checked the systemd-resolve --status

 root@xxxxxx:~# systemd-resolve --status
Global
        DNS Servers: 8.8.8.8
                     127.0.0.1
         DNSSEC NTA: 10.in-addr.arpa
                     16.172.in-addr.arpa
                     168.192.in-addr.arpa
                     17.172.in-addr.arpa
                     18.172.in-addr.arpa
                     19.172.in-addr.arpa
                     20.172.in-addr.arpa
                     21.172.in-addr.arpa
                     22.172.in-addr.arpa
                     23.172.in-addr.arpa
                     24.172.in-addr.arpa
                     25.172.in-addr.arpa
                     26.172.in-addr.arpa
                     27.172.in-addr.arpa
                     28.172.in-addr.arpa
                     29.172.in-addr.arpa
                     30.172.in-addr.arpa
                     31.172.in-addr.arpa
                     corp
                     d.f.ip6.arpa
                     home
                     internal
                     intranet
                     lan
                     local
                     private
                     test
Link 2 (eno1)
     Current Scopes: none
      LLMNR setting: yes
MulticastDNS setting: no
     DNSSEC setting: no
   DNSSEC supported: no

Logs
-------

ug 16 16:07:00 xxxxxx dhcpcd[967]: eno1: carrier lost
Aug 16 16:07:00 xxxxxx kernel: e1000e: eno1 NIC Link is Down
Aug 16 16:07:03 xxxxxx dhcpcd[967]: eno1: carrier acquired
Aug 16 16:07:03 xxxxxx kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Aug 16 16:07:03 xxxxxx NetworkManager[890]: <info> [1565951823.1018] device (eno1): carrier: link connected
Aug 16 16:07:03 xxxxxx dhcpcd[967]: eno1: IAID d5:60:80:e0
Aug 16 16:07:03 xxxxxx dhcpcd[967]: eno1: rebinding lease of 192.168.1.31
Aug 16 16:07:04 xxxxxx dhcpcd[967]: eno1: soliciting an IPv6 router
Aug 16 16:07:06 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 8.8.8.8.
Aug 16 16:07:06 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:08 xxxxxx dhcpcd[967]: eno1: probing for an IPv4LL address
Aug 16 16:07:08 xxxxxx dhcpcd[967]: eno1: DHCP lease expired
Aug 16 16:07:08 xxxxxx dhcpcd[967]: eno1: soliciting a DHCP lease
Aug 16 16:07:10 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 16:07:11 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 8.8.8.8.
Aug 16 16:07:13 xxxxxx dhcpcd[967]: eno1: using IPv4LL address 169.254.129.33
Aug 16 16:07:13 xxxxxx dhcpcd[967]: eno1: adding route to 169.254.0.0/16
Aug 16 16:07:13 xxxxxx avahi-daemon[896]: Registering new address record for 169.254.129.33 on eno1.IPv4.
Aug 16 16:07:14 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:15 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 16:07:16 xxxxxx dhcpcd[967]: eno1: no IPv6 Routers available
Aug 16 16:07:20 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:25 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 16:07:25 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 8.8.8.8.
Aug 16 16:07:29 xxxxxx whoopsie[1260]: [16:07:29] Cannot reach: https://daisy.ubuntu.com
Aug 16 16:07:29 xxxxxx whoopsie[1260]: [16:07:29] offline
Aug 16 16:07:30 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:30 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 16:07:31 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 8.8.8.8.
Aug 16 16:07:32 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:33 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 16:07:34 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:36 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 16:07:41 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:42 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 8.8.8.8.
Aug 16 16:07:43 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 16:07:45 xxxxxx whoopsie[1260]: [16:07:45] Cannot reach: https://daisy.ubuntu.com
Aug 16 16:07:45 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:46 xxxxxx dhcpcd[967]: eno1: carrier lost
Aug 16 16:07:46 xxxxxx kernel: e1000e: eno1 NIC Link is Down
Aug 16 16:07:46 xxxxxx dhcpcd[967]: eno1: deleting route to 169.254.0.0/16
Aug 16 16:07:46 xxxxxx avahi-daemon[896]: Withdrawing address record for 169.254.129.33 on eno1.
Aug 16 16:07:49 xxxxxx NetworkManager[890]: <info> [1565951869.9299] device (eno1): carrier: link connected
Aug 16 16:07:49 xxxxxx kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Aug 16 16:07:49 xxxxxx dhcpcd[967]: eno1: carrier acquired
Aug 16 16:07:49 xxxxxx dhcpcd[967]: eno1: IAID d5:60:80:e0
Aug 16 16:07:50 xxxxxx dhcpcd[967]: eno1: soliciting a DHCP lease
Aug 16 16:07:50 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:50 xxxxxx dhcpcd[967]: eno1: soliciting an IPv6 router
Aug 16 16:07:53 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 16:07:53 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 8.8.8.8.
Aug 16 16:07:54 xxxxxx systemd-timesyncd[655]: Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com).
Aug 16 16:07:54 xxxxxx dhcpcd[967]: eno1: offered 192.168.1.31 from 192.168.1.98
Aug 16 16:07:54 xxxxxx dhcpcd[967]: eno1: probing address 192.168.1.31/24
Aug 16 16:07:56 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:56 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 16:07:57 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:57 xxxxxx systemd-resolved[29151]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 16 16:07:57 xxxxxx whoopsie[1260]: [16:07:57] online
Aug 16 16:07:58 xxxxxx systemd-resolved[29151]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 16 16:07:59 xxxxxx NetworkManager[890]: <info> [1565951879.0065] manager: NetworkManager state is now CONNECTED_SITE
Aug 16 16:07:59 xxxx dbus-daemon[820]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=890 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Aug 16 16:07:59 xxxxxx whoopsie[1260]: [16:07:59] offline
Aug 16 16:07:59 xxxxxx systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug 16 16:07:59 xxxxxx dbus-daemon[820]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 16 16:07:59 xxxxxx systemd[1]: Started Network Manager Script Dispatcher Service.
Aug 16 16:07:59 xxxxxx nm-dispatcher[31345]: req:1 'connectivity-change': new request (1 scripts)
Aug 16 16:07:59 xxxxxx nm-dispatcher[31345]: req:1 'connectivity-change': start running ordered scripts...
Aug 16 16:07:59 xxxxxx dhcpcd[967]: eno1: leased 192.168.1.31 for 28800 seconds
Aug 16 16:07:59 xxxxxx dhcpcd[967]: eno1: adding route to 192.168.1.0/24
Aug 16 16:07:59 xxxxxx dhcpcd[967]: eno1: adding default route via 192.168.1.98
Aug 16 16:07:59 xxxxxx avahi-daemon[896]: Registering new address record for 192.168.1.31 on eno1.IPv4.
Aug 16 16:08:02 xxxxxx dhcpcd[967]: eno1: no IPv6 Routers available

Please check and let me know the root cause of the issue.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

What is the output of:

sudo lshw -C network; lsb_release -a; uname -a

Thanks

Revision history for this message
Lalit Singh Dhidwal (lalitd) said : 		#2

Below are the stack for the same commands

root@xxxx:~# sudo lshw -C network; echo; lsb_release -a; echo; uname -a
  *-network
       description: Ethernet interface
       product: Ethernet Connection I218-V
       vendor: Intel Corporation
       physical id: 19
       bus info: pci@0000:00:19.0
       logical name: eno1
       version: 04
       serial: c0:3f:d5:60:80:e0
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.6-4 ip=192.168.1.122 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:42 memory:f7c00000-f7c1ffff memory:f7c3c000-f7c3cfff ioport:f080(size=32)

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic

Linux xxxx 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Please check.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

If you run:
sudo gedit /etc/resolvconf.conf

Comment out the line:
name_servers=127.0.0.1

Save the new file and then run:
resolvconf -

Does this help?

Source:
https://askubuntu.com/questions/932486/syslog-flooded-with-systemd-resolved-messages-using-degraded-feature-set

Revision history for this message
Lalit Singh Dhidwal (lalitd) said : 		#4

I have checked and there is no such file, below is the stack

root@xxxxxxx:~# ls -aril /etc/resolvconf.conf
ls: cannot access '/etc/resolvconf.conf': No such file or directory

Do I have create this file, my end?

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#5

Did you check update #2 in the resolution section of the post I gave a link to....

Revision history for this message
Lalit Singh Dhidwal (lalitd) said : 		#6

Yes, I have checked the reference link and as per it, due to an incorrect entry in the file, the network gets conflicted.

As per the link we have to comment it out and run resolvconf -u

Do this will auto-generate the recoresolvconf.conf file? Or do I have to create it manually?

As I am not sure about the second linking the file option? Can you please guide me through it.

So, I can Implement it.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#7

Yeah. Try creating it. It'll be an empty file but it's worth a go...

Revision history for this message
Lalit Singh Dhidwal (lalitd) said : 		#8

I have implemented the above steps and for a few minutes the network work properly and again it suddenly stop working.

Also, I have manually restart the NetworkManager service Or need to toogle the network On and Off switch to back the network.

Below are the stack, which may be helpful to track the root cause.

Aug 20 11:59:06 XXXXXX systemd-resolved[10894]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 20 11:59:06 XXXXXX systemd-resolved[10894]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 20 11:59:06 XXXXXX systemd-resolved[10894]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 20 11:59:06 XXXXXX systemd-resolved[10894]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 20 11:59:06 XXXXXX systemd-resolved[10894]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 20 11:59:06 XXXXXX systemd-resolved[10894]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 20 11:59:06 XXXXXX systemd-resolved[10894]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 20 11:59:06 XXXXXX systemd-resolved[10894]: Using degraded feature set (TCP) for DNS server 127.0.0.1.
Aug 20 11:59:06 XXXXXX systemd-resolved[10894]: Using degraded feature set (UDP) for DNS server 127.0.0.1.
Aug 20 11:59:06 XXXXXX NetworkManager[851]: <info> [1566282546.6613] device (eno1): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed')
Aug 20 11:59:06 XXXXXX NetworkManager[851]: <info> [1566282546.6617] manager: NetworkManager state is now DISCONNECTING
Aug 20 11:59:06 XXXXXX NetworkManager[851]: <info> [1566282546.6689] audit: op="device-disconnect" interface="eno1" ifindex=2 pid=4186 uid=1001 result="success"
Aug 20 11:59:06 XXXXXX NetworkManager[851]: <info> [1566282546.6702] device (eno1): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed')
Aug 20 11:59:06 XXXXXX avahi-daemon[841]: Withdrawing address record for fe80::61ca:e062:fcce:1ed7 on eno1.
Aug 20 11:59:06 XXXXXX avahi-daemon[841]: Leaving mDNS multicast group on interface eno1.IPv6 with address fe80::61ca:e062:fcce:1ed7.
Aug 20 11:59:06 XXXXXX avahi-daemon[841]: Interface eno1.IPv6 no longer relevant for mDNS.
Aug 20 11:59:06 XXXXXX avahi-daemon[841]: Withdrawing address record for 192.168.1.136 on eno1.
Aug 20 11:59:06 XXXXXX avahi-daemon[841]: Leaving mDNS multicast group on interface eno1.IPv4 with address 192.168.1.136.
Aug 20 11:59:06 XXXXXX avahi-daemon[841]: Joining mDNS multicast group on interface eno1.IPv4 with address 192.168.1.123.
Aug 20 11:59:06 XXXXXX avahi-daemon[841]: Withdrawing address record for 192.168.1.123 on eno1.
Aug 20 11:59:06 XXXXXX avahi-daemon[841]: Leaving mDNS multicast group on interface eno1.IPv4 with address 192.168.1.123.
Aug 20 11:59:06 XXXXXX gvfsd[2551]: mkdir failed on directory /var/cache/samba: Permission denied
Aug 20 11:59:06 XXXXXX avahi-daemon[841]: Interface eno1.IPv4 no longer relevant for mDNS.
Aug 20 11:59:06 XXXXXX NetworkManager[851]: <info> [1566282546.6810] manager: NetworkManager state is now DISCONNECTED
Aug 20 11:59:06 XXXXXX gvfsd[2551]: mkdir failed on directory /var/cache/samba: Permission denied
Aug 20 11:59:06 XXXXXX dnsmasq[1268]: setting upstream servers from DBus
Aug 20 11:59:06 XXXXXX dbus-daemon[808]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=
Aug 20 11:59:06 XXXXXX systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug 20 11:59:06 XXXXXX dbus-daemon[808]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 20 11:59:06 XXXXXX systemd[1]: Started Network Manager Script Dispatcher Service.
Aug 20 11:59:06 XXXXXX nm-dispatcher[11146]: req:1 'down' [eno1]: new request (1 scripts)
Aug 20 11:59:06 XXXXXX nm-dispatcher[11146]: req:1 'down' [eno1]: start running ordered scripts...
Aug 20 11:59:07 XXXXXX NetworkManager[851]: <info> [1566282547.1148] device (eno1): Activation: starting connection 'Wired connection 1' (f325dcd1-e56c-387a-82e3-492588f98997)
Aug 20 11:59:07 XXXXXX NetworkManager[851]: <info> [1566282547.1149] audit: op="connection-activate" uuid="f325dcd1-e56c-387a-82e3-492588f98997" name="Wired connection 1" pid=4186 uid=1001 result="suc
Aug 20 11:59:07 XXXXXX NetworkManager[851]: <info> [1566282547.1152] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 20 11:59:07 XXXXXX NetworkManager[851]: <info> [1566282547.1154] manager: NetworkManager state is now CONNECTING
Aug 20 12:02:05 XXXXXX NetworkManager[11337]: <info> [1566282725.5916] caught SIGTERM, shutting down normally.
Aug 20 12:02:05 XXXXXX NetworkManager[11337]: <info> [1566282725.5954] exiting (success)
Aug 20 12:02:05 XXXXXX systemd[1]: Stopped Network Manager.
Aug 20 12:02:05 XXXXXX systemd[1]: NetworkManager.service: Found left-over process 11357 (dnsmasq) in control group while starting unit. Ignoring.
Aug 20 12:02:05 XXXXXX systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Aug 20 12:02:05 XXXXXX systemd[1]: Starting Network Manager...
Aug 20 12:02:05 XXXXXX gnome-shell[2606]: Removing a network device that was not added
Aug 20 12:02:05 XXXXXX gnome-shell[1465]: Removing a network device that was not added
Aug 20 12:02:05 XXXXXX gnome-shell[2606]: Object NM.ActiveConnection (0x55bfc229da70), has been already finalized. Impossible to get any property from it.
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[2606]: == Stack trace for context 0x55bfc19c7330 ==
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[2606]: #0 0x55bfc1d732f0 i resource:///org/gnome/shell/ui/status/network.js:1999 (0x7fe05a41b3c8 @ 47)
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[2606]: #1 0x7fff753fd580 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe0945b5de0 @ 71)
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[2606]: #2 0x55bfc1d73270 i resource:///org/gnome/shell/ui/status/network.js:1950 (0x7fe05a41b120 @ 95)
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[2606]: #3 0x7fff753fe8e0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe0945b5de0 @ 71)
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[2606]: #4 0x7fff753ff110 b self-hosted:918 (0x7fe0945f12b8 @ 394)
Aug 20 12:02:05 XXXXXX gnome-shell[1465]: Object NM.ActiveConnection (0x556f87d99d50), has been already finalized. Impossible to get any property from it.
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[1465]: == Stack trace for context 0x556f85cd6340 ==
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[1465]: #0 0x556f8608c130 i resource:///org/gnome/shell/ui/status/network.js:1999 (0x7fdef3c162b8 @ 47)
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[1465]: #1 0x7fff6095c2b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fdf1c5b5de0 @ 71)
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[1465]: #2 0x556f8608c0b0 i resource:///org/gnome/shell/ui/status/network.js:1950 (0x7fdef3c14f78 @ 95)
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[1465]: #3 0x7fff6095d610 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fdf1c5b5de0 @ 71)
Aug 20 12:02:05 XXXXXX org.gnome.Shell.desktop[1465]: #4 0x7fff6095de40 b self-hosted:918 (0x7fdf1c5f12b8 @ 394)

Please check.

Can you help with this problem?

Provide an answer of your own, or ask Lalit Singh Dhidwal for more information if necessary.

To post a message you must log in.