girish@girish-System-Product-Name:~$ sudo su
[sudo] password for girish:
root@girish-System-Product-Name:/home/girish# NetworkManager
root@girish-System-Product-Name:/home/girish# locate -b "\NetworkManager"
/etc/NetworkManager
/usr/lib/NetworkManager
/usr/lib/x86_64-linux-gnu/NetworkManager
/usr/sbin/NetworkManager
/var/lib/NetworkManager
root@girish-System-Product-Name:/home/girish# man NetworkManager
root@girish-System-Product-Name:/home/girish# NetworkManager -V
1.30.0
root@girish-System-Product-Name:/home/girish# NetworkManager
root@girish-System-Product-Name:/home/girish# which NetworkManager
/usr/sbin/NetworkManager
Strange behavior. Today morning when I switched on the PC, after around 10 seconds, network connected and worked fine automatically, I didn't changed anything, otherwise yesterday I got "Activation of Network connection failed" popped up and after that popup, it got connected automatically. So, in all I can say that this is somewhere bug in either kernel, userspace or NetworkManager program. Something need to be fix for sure.
girish@ girish- System- Product- Name:~$ sudo su System- Product- Name:/home/ girish# NetworkManager System- Product- Name:/home/ girish# locate -b "\NetworkManager" NetworkManager x86_64- linux-gnu/ NetworkManager NetworkManager NetworkManager System- Product- Name:/home/ girish# man NetworkManager System- Product- Name:/home/ girish# NetworkManager -V System- Product- Name:/home/ girish# NetworkManager System- Product- Name:/home/ girish# which NetworkManager NetworkManager
[sudo] password for girish:
root@girish-
root@girish-
/etc/NetworkManager
/usr/lib/
/usr/lib/
/usr/sbin/
/var/lib/
root@girish-
root@girish-
1.30.0
root@girish-
root@girish-
/usr/sbin/
Strange behavior. Today morning when I switched on the PC, after around 10 seconds, network connected and worked fine automatically, I didn't changed anything, otherwise yesterday I got "Activation of Network connection failed" popped up and after that popup, it got connected automatically. So, in all I can say that this is somewhere bug in either kernel, userspace or NetworkManager program. Something need to be fix for sure.