Created attachment 1274022 [details] lsusb, dmesg, ifconfig Description of problem: Networkmanager doesn't display any wifi network Version-Release number of selected component (if applicable): How reproducible: every time I try to connect to wifi or at the boot of fedora Steps to Reproduce: 1.open NManager 2.NManager can't display any wifi 3.Must create a masked/invisible manually to connect to my wifi Actual results: can't connect to my home wifi and doesn't shows any wifi network .Blank window Expected results: Would like NManager to connect automatically to my wlan without having to connect manually on the invisible/masked wlan I've had create Additional info: I just can see wifi network (mine or neighbour ssid) after I 'm connected to my wifi network. Nota: I have fedora installed on 3 machines on my home and only one find my ssid as masked and doesn't detect anything until I manually connect to my box. When I am connected I can see all neighbourhood wlan
NetworkManager itself is not a GUI application. Apparently you are looking somewhere and see something (or the lack of something). From the description it's unclear what you are doing, what you are clicking and what you are seeing. what's the output of `nmcli device` and `nmcli connection`? The logfile of NetworkManager is in the journal `journalctl -b 0 -u NetworkManager`
(a screenshot might also help)
Created attachment 1274257 [details] journalctl -b 0 -u NetworkManager
Created attachment 1274258 [details] nmcli device, nmcli connection
Created attachment 1274259 [details] connection wifi must always connect manually and don't have any connection detected. sorry it's a french fedora and for my bad english
Created attachment 1274260 [details] wifi masked/invisible I must create a masked wifi connection to have a connection. But my wifi isn't masked!? I have 2 others pc with fedora and they detect and connect automatically to the router.And I can see others wifi only when I am connected to my wifi/box. Hope I explained clearly. Thanks in advance
I've typed and saved the commands you told me, but before connecting manually to my wifi. Tell me if I must attach it here
It would be much better not to copy-and-paste the output of journalctl, but provide the full file. For that, redirect the output (and zip it) like journalctl -b0 -u NetworkManager | gzip > nm-rh1445496.log Preferably, do this with a reboot and reproduce the issue anew, in order to have a possibly clean logfile without noise. What is the output of nmcli connection show "SFR-47b8" Thanks
(In reply to Thomas Haller from comment #8) > It would be much better not to copy-and-paste the output of journalctl, but > provide the full file. > > For that, redirect the output (and zip it) like > > journalctl -b0 -u NetworkManager | gzip > nm-rh1445496.log > > Preferably, do this with a reboot and reproduce the issue anew, in order to > have a possibly clean logfile without noise. > > > What is the output of > > nmcli connection show "SFR-47b8" > > > > > Thanks I have done what you told me to do at the reboot but journalctl return isn't so heavy now (just 5kb). The command gave me a log file not a zip.
Created attachment 1274343 [details] journalctl -b0 -u NetworkManager | gzip > nm-rh1445496.log
Created attachment 1274346 [details] nmcli connection show
the logfile is full of warnings, due to the driver being unable to change the MAC address of your Wi-Fi interface. That is due to the used driver (r8712u). As such, this bug is a duplicate of bug 1382741. You should be able to workaround it by configuring [device-no-mac-rand] wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf. See `man NetworkManager.conf`. *** This bug has been marked as a duplicate of bug 1382741 ***
thank you very much