** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- network-manager has decided that networking is disabled, cannot be re-enabled
from lightdm
+ [logind] stuck in PrepareForSleep, causing network and other services to not
resume
** Changed in: sy
Somebody marked this as a duplicate to bug 1234469, which simply isn't
the case, bug 1234469 is a duplicate of this one (as others already
stated), just look at the creation dates, this one is the original, so,
people need to use launchpad correctly ;) And why is it that everyone
(like me) has the
I have the same bug in 13.10, and I tried to run "nmcli nm sleep false"
in a terminal, and this is the error message I got:
Error in sleep: Rejected send message, 8 matched rules;
type="method_call", sender=":1.304" (uid=1000 pid=3927 comm="nmcli nm
sleep false ") interface="org.freedesktop.Networ
*** This bug is a duplicate of bug 1234469 ***
https://bugs.launchpad.net/bugs/1234469
** This bug has been marked a duplicate of bug 1234469
Network does not come up after resuming from suspend.
--
You received this bug notification because you are a member of Desktop
Packages, which is
While inspecting the logind D-Bus object I've noticed that
"PreparingForSleep" is still set to "true" after the suspend/resume
cycle.
$ gdbus introspect --system --dest org.freedesktop.login1 --object-path
/org/freedesktop/login1
--
You received this bug notification because you are a member of
I've just found it: it's probably this bug: https://bugs.launchpad.net
/ubuntu-gnome/+bug/1187005
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
network-manager
I had the exact same bug a few months ago. The issue was that
NetworkManager is supposed to work with systemd, but Ubuntu chose to
implement its own replacement to systemd instead (libsystemd-daemon0 I
think). The issue I had previously was caused by libsystemd-daemon0 not
sending the "resume" even
Yes, looks like a dupe.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
network-manager has decided that networking is disabled, cannot be re-
enabled from lig
It looks like bug 1234469 might be a duplicate of this one.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
network-manager has decided that networking is disabl
What component is *supposed* to be sending it that signal? I have
noticed that in cases where this bug appears, other power management
options also fail - trying to suspend again from the gear menu does
nothing, I have to run pm-suspend from the cli. This indicates to me
that some whole underlying
We can send such signals using pm-utils . Needs testing .
ritz: right, so pm-utils package has direcotries with scripts that are
executed on suspend/resume, hibernate/thaw.
aah, thanks
ritz: so network-manager or user should just add scripts there.
ritz: see /usr/share/doc/pm-utils/README
Maybe network-manager should ship shell snippet in pm-utils
configuration directory to issue sleep false on resume/thaw?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1184262
T
Interesting, so it's not even a NetworkManager bug - whatever is
supposed to be sending that signal to nm isn't sending it sometimes, or
is sending it before nm can receive it or something?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Not sure why my comment on my report of this bug didn't get merged into
this one.
The work-around is to issue
nmcli nm sleep false
This tells NetworkManager to leave "sleep" mode. Restarting
NetworkManager _happens_ to do this, but only by chance. I'd actually
argue that restarting NetworkManage
First I ran "sudo stop network-manager" then ran "sudo NetworkManager
--no-daemon --log-level=DEBUG >nm.log 2>&1" and then I reproduced the
issue. I have attached the complete log output of network-manager from
the initial receive of the "suspend" signal to the point I ctrl-C'ed it
after experienci
I still see this fairly frequently, and it is strictly a network-manager
problem. "sudo restart network-manager" causes it to reconnect
gracefully without any problems or kernel magic.
I suspect a race condition, since it only happens about 1/3 of the time
I suspend.
FWIW, I have a totally differ
Sameer Morar's workaround worked like a charm on my Ubuntu Studio 13.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
network-manager has decided that network
A work around that works for me is killing the NetworkManager process
using "sudo killall NetworkManager". The daemon re-starts and the
network is restored.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchp
19 matches
Mail list logo
