*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
Dr. Dabbles [2013-10-20 18:47 -0000]:
> How was this not a blocker for release? We're talking about impacting
> every single Ubuntu user that suspends their computer, and the entire
> goal of Ubuntu is to make Linux easier for the average user!
Most certainly not. I haven't heard any complaints about this on
recent conferences where we had dozens of people in the same room
running saucy and suspending all the time, and I never saw that happen
either. Of course I do believe you that this is broken under some
conditions, but it hasn't been fixed yet precisely most people do not
have this, and thus it's not easily reproduced.
That said, if someone can reproduce this problem, it might be helpful
to do
$ sudo -i
# stop systemd-logind
# killall systemd-logind; /lib/systemd/systemd-logind
which starts logind in the foreground; then suspend/resume, try to
suspend again, and copy&paste the whole output. Hopefully there's some
error message which sheds some light on this.
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
