Ecco Mandian ho riprovato ancora ed ecco che il risultato mi sembra diverso.
[omv-giorgio@new-host-4 ~]$ journalctl -a
-- Logs begin at Fri 2017-06-16 18:49:19 CEST, end at Fri 2017-07-21 20:48:43 CEST. --
Jun 16 18:49:19 linux-giorgio-pc systemd-timesyncd[2257]: Network configuration changed, trying t
Jun 16 18:49:19 linux-giorgio-pc kernel: wlp2s4: Setting MAC to c2:ca:a0:e9:27:e4
Jun 16 18:49:19 linux-giorgio-pc kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
Jun 16 18:49:19 linux-giorgio-pc kernel: wlp2s4: Setting MAC to c2:ca:a0:e9:27:e4
Jun 16 18:49:19 linux-giorgio-pc kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
Jun 16 18:49:19 linux-giorgio-pc kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
Jun 16 18:49:19 linux-giorgio-pc NetworkManager[2840]: <warn> [1497631759.3811] device (wlp2s4):
Jun 16 18:49:19 linux-giorgio-pc systemd-timesyncd[2257]: Synchronized to time server 85.254.217.
Jun 16 18:49:19 linux-giorgio-pc NetworkManager[2840]: <info> [1497631759.4663] device (wlp2s4):
Jun 16 18:49:19 linux-giorgio-pc NetworkManager[2840]: <info> [1497631759.4750] device (wlp2s4):
Jun 16 18:49:19 linux-giorgio-pc systemd-timesyncd[2257]: Network configuration changed, trying t
Jun 16 18:49:19 linux-giorgio-pc NetworkManager[2840]: <warn> [1497631759.6952] device (wlp2s4):
Jun 16 18:49:19 linux-giorgio-pc NetworkManager[2840]: <info> [1497631759.7071] device (wlp2s4):
Jun 16 18:49:20 linux-giorgio-pc firewalld[2494]: ERROR: UNKNOWN_INTERFACE: 'wlp2s4' is not in an
Jun 16 18:49:19 linux-giorgio-pc NetworkManager[2840]: <info> [1497631759.7151] device (wlp2s4):
Jun 16 18:49:19 linux-giorgio-pc plasmashell[4101]: file:///usr/lib/qt5/qml/QtQuick/Controls/Butt
Jun 16 18:49:19 linux-giorgio-pc systemd-timesyncd[2257]: Synchronized to time server 85.254.217.
Jun 16 18:49:19 linux-giorgio-pc systemd-timesyncd[2257]: Network configuration changed, trying t
Jun 16 18:49:19 linux-giorgio-pc NetworkManager[2840]: <info> [1497631759.9098] device (wlp2s4):
Jun 16 18:49:19 linux-giorgio-pc systemd-timesyncd[2257]: Synchronized to time server 85.254.217.
Jun 16 18:49:19 linux-giorgio-pc systemd-timesyncd[2257]: Network configuration changed, trying t
Jun 16 18:49:19 linux-giorgio-pc NetworkManager[2840]: <info> [1497631759.9414] device (wlp2s4):
Jun 16 18:49:19 linux-giorgio-pc systemd-timesyncd[2257]: Synchronized to time server 85.254.217.
Jun 16 18:49:20 linux-giorgio-pc NetworkManager[2840]: <info> [1497631760.2908] device (wlp2s4):
Jun 16 18:49:20 linux-giorgio-pc NetworkManager[2840]: <info> [1497631760.2921] device (wlp2s4):
Jun 16 18:49:20 linux-giorgio-pc NetworkManager[2840]: <warn> [1497631760.2932] firewall: [0x9f8
Jun 16 18:49:20 linux-giorgio-pc plasmashell[4101]: file:///usr/lib/qt5/qml/QtQuick/Controls/Butt
Jun 16 18:49:20 linux-giorgio-pc plasmashell[4101]: file:///usr/lib/qt5/qml/QtQuick/Controls/Butt
Jun 16 18:49:20 linux-giorgio-pc plasmashell[4101]: file:///usr/lib/qt5/qml/QtQuick/Controls/Butt
C’'e anche un errore nell’interfaccia wlp2s4 riguardo al firewall.
Forse potrebbe essere interessante:
Cosa ne pensi Mandian?
Grazie
Ciao
Scusa Mandian e scusate tutti, ho visto che l’output della console che ho postato era solo un primo pezzo, il report è molto più lungo e quindi l’ho salvato in un file che provo ad allegare,
Mi pare che ci siano molti errori sulla wlp2s4 che potrebbero darci qualche informazione utile.
Ho troncato il file nelle date entecedenti il 18 luglio perchè era enorme.
Le date utili sono quindi quelle del 19 o meglio 20 e 21 luglio,
Ho visto anche che /keyring.bkp è una directory vuota
Ho fatto logout e login ma non è stata ricreata la directory /keyring
ho visto inoltre che ho due file con la chiave wpa del wifi, uno in /etc/sysconfig/networkscripts/ e l’altro è /etc/wpa_supplicant.conf che contiene la personalizzazione con la chiave del mio wifi.
Network manager usa anche wpa_supplicant?
Grazie
Ciao
Giorgio
L’errore di keyring non c’e piu perche il reporto si ferma al giorno 22 luglio scorso.
pero purtroppo non si collega il maledetto!!!
[omv-giorgio@linux-giorgio-pc ~]$ journalctl -a |grep gnome-keyring
Jul 14 21:04:08 new-host-4 gnome-keyring-daemon[4118]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 14 21:04:08 new-host-4 gnome-keyring-d[4118]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 14 21:04:08 new-host-4 gnome-keyring-daemon[4118]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 14 21:04:08 new-host-4 gnome-keyring-d[4118]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 14 21:04:08 new-host-4 gnome-keyring-daemon[4118]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 14 21:04:08 new-host-4 gnome-keyring-d[4118]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 14 21:12:27 new-host-4 gnome-keyring-daemon[4073]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 14 21:12:27 new-host-4 gnome-keyring-d[4073]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 14 21:12:27 new-host-4 gnome-keyring-daemon[4073]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 14 21:12:27 new-host-4 gnome-keyring-d[4073]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 14 21:12:27 new-host-4 gnome-keyring-daemon[4073]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 14 21:12:27 new-host-4 gnome-keyring-d[4073]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 17 18:02:32 localhost.localdomain gnome-keyring-daemon[4290]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 17 18:02:32 localhost.localdomain gnome-keyring-d[4290]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 17 18:02:32 localhost.localdomain gnome-keyring-daemon[4290]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 17 18:02:32 localhost.localdomain gnome-keyring-d[4290]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 17 18:02:32 localhost.localdomain gnome-keyring-daemon[4290]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 17 18:02:32 localhost.localdomain gnome-keyring-d[4290]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 19 19:44:13 new-host-4 gnome-keyring-daemon[4538]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 19 19:44:13 new-host-4 gnome-keyring-d[4538]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 19 19:44:13 new-host-4 gnome-keyring-daemon[4538]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 19 19:44:13 new-host-4 gnome-keyring-d[4538]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 19 19:44:13 new-host-4 gnome-keyring-daemon[4538]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 19 19:44:13 new-host-4 gnome-keyring-d[4538]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 20 20:30:10 new-host-4 gnome-keyring-daemon[4153]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 20 20:30:10 new-host-4 gnome-keyring-d[4153]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 20 20:30:10 new-host-4 gnome-keyring-daemon[4153]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 20 20:30:10 new-host-4 gnome-keyring-d[4153]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 20 20:30:10 new-host-4 gnome-keyring-daemon[4153]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 20 20:30:10 new-host-4 gnome-keyring-d[4153]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 22 21:26:15 linux-giorgio-pc gnome-keyring-d[4728]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 22 21:26:15 linux-giorgio-pc gnome-keyring-daemon[4728]: couldn't access control socket: /run/user/1001/keyring/control: No such file or directory
Jul 22 21:26:15 linux-giorgio-pc gnome-keyring-daemon[4728]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 22 21:26:15 linux-giorgio-pc gnome-keyring-d[4728]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 22 21:26:15 linux-giorgio-pc gnome-keyring-daemon[4728]: Gkm: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Jul 22 21:26:15 linux-giorgio-pc gnome-keyring-d[4728]: using old keyring directory: /home/omv-giorgio/.gnome2/keyrings
Forse ho dimenticato di dirti di riavviare NetworkManager, riproviamo. Prima, però,
prova ad aggiungere le seguenti righe al file di configurazione /etc/NetworkManager/NetworkManager.conf:
new-host-4 NetworkManager[2884]: <warn> [1500664115.1620] device (wlp2s4): set-hw-addr: new MAC address 42:FC:1C:C8:3B:9B not successfully set (scanning)
new-host-4 NetworkManager[2884]: <warn> [1500664431.1379] device (wlp2s4): set-hw-addr: new MAC address E6:53:9A:63:0D:0A not successfully set (scanning)
new-host-4 NetworkManager[2884]: <warn> [1500664431.1379] device (wlp2s4): set-hw-addr: new MAC address E6:53:9A:63:0D:0A not successfully set (scanning)
Ho notato parecchie segnalazioni come le precedenti nel tuo file di log e i è venuto il dubbio che la tua scheda wifi (o i ldriver) potrebbe non supportate la modifica dell’indirizzo MAC. Nel caso puoi provare ad aggiungere la seguente configurazione nel file /etc/NetworkManager/NetworkManager.conf (purtroppo la versione presente in lx3.0 di networkmanager-applet non permette di farlo per via grafica)
[device]
wifi.scan-rand-mac-address=no
e riavviare il servizio (o direttamente il sistema)
sudo systemctl restart NetworkManager
Le informazioni le ho tratte da questo interessante articolo.
Purtroppo senza notizie positive.
Niente anche con la modifica al file /etc/NetworkManager/NetworkManager.conf nulla il wifi non si collega.
Ho provato oltre che a riaprire il sistema anche a cancellare la connessione.
la lunghezza della passfrase potrebbe essere critica? Anche se deve essere riconosciuta potrebbe essere una criticità dato che è abbastanza lunga.