Note the states NM_STATE_CONNECTED_GLOBAL and NM_STATE_CONNECTED are
essentially the same. Work is still needed to revise that patch but I
think it also needs work at the application level to check how available
the network is before trying to do stuff.
I'll need to know more about what's going
I cannot reproduce this anymore. I have no issues when resuming from
standby.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805140
Title:
NM fakes a CONNECTED state during resume
To manage
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805140
Title:
NM fakes a CONNECTED state during resume
To manage notifications
Yup. We still need that patch but there's clearly something wrong there, so
I will investigate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805140
Title:
NM fakes a CONNECTED state during resume
** Attachment added: NM Log from suspend/resume
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/805140/+attachment/2189309/+files/nm-resume.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
