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 on before I can fix anything.
Could you reproduce the issue and attach all of /var/log/syslog, and
probably include the error message from DejaDup or let me know roughly
where in the code this is happening?
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Triaged
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
--
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/805140/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
