*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
I've tried suggested by pitti. After the first suspend and resume I get this:
Lid closed.
Suspending...
Failed to send delayed message: Message did not receive a reply (timeout by
message bus)
Lid opened.
Networking was disabled so I brought it back up with "nmcli nm sleep
false". Then I suspended again. After the second suspend trying to
resume just led to another suspend I didn't ask for. Had to force
another resume (power button) before the thing actually resumed:
Lid closed.
Suspending...
Failed to execute operation: Message did not receive a reply (timeout by
message bus)
Suspending...
Operation finished.
Lid opened.
Earlier today it happened to me that I couldn't resume at all because of
this problem happening many times in a row. I would get to the login
prompt but the machine would go back to sleep so fast that I wouldn't
even have time to enter my password. I had to power off and restart the
machine to take it out of that state. I'm on a Dell Latitude E6400.
BTW. Should I stop commenting here and switch to #1184262 instead?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234469
Title:
Network does not come up after resuming from suspend.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1234469/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
