On Mon 2018-03-19 12:45:49, Dan Williams wrote: > On Mon, 2018-03-19 at 18:33 +0100, Pavel Machek wrote: > > On Mon 2018-03-19 10:40:08, Dan Williams wrote: > > > On Mon, 2018-03-19 at 10:21 +0100, Pavel Machek wrote: > > > > On Mon 2018-03-19 05:17:45, Woody Suwalski wrote: > > > > > Pavel Machek wrote: > > > > > > Hi! > > > > > > > > > > > > With recent linux-next, after resume networkmanager often > > > > > > claims > > > > > > that > > > > > > "network is disabled". Sometimes suspend/resume clears that. > > > > > > > > > > > > Any ideas? Does it work for you? > > > > > > > > > > > > > > > > > > Pavel > > > > > > > > > > Tried the 4.16-rc6 with nm 1.4.4 - I do not see the issue. > > > > > > > > Thanks for testing... but yes, 4.16 should be ok. If not fixed, > > > > problem will appear in 4.17-rc1. > > > > > > Where does the complaint occur? In the GUI, or with nmcli, or > > > somewhere else? Also, what's the output of "nmcli dev" after > > > resume? > > > > In the GUI. I click in place where I'd select access point, and menu > > does not show up, telling me that "network is disabled". > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
Broken state.
pavel@amd:~$ nmcli dev
DEVICE TYPE STATE CONNECTION
eth1 ethernet unavailable --
lo loopback unmanaged --
wlan0 wifi unmanaged --
pavel@amd:~$ nmcli radio
WIFI-HW WIFI WWAN-HW WWAN
enabled enabled enabled enabled
pavel@amd:~$ uname -a
Linux amd 4.16.0-rc5-next-20180314+ #31 SMP Thu Mar 15 14:27:19 CET
2018 i686 GNU/Linux
Let me suspend/resume. I was lucky and got it into working state:
pavel@amd:~$ nmcli dev
DEVICE TYPE STATE CONNECTION
wlan0 wifi connected openwireless.org
eth1 ethernet unavailable --
lo loopback unmanaged --
pavel@amd:~$ nmcli radio
WIFI-HW WIFI WWAN-HW WWAN
enabled enabled enabled enabled
pavel@amd:~$
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
signature.asc
Description: Digital signature
