I can confirm that the command 'sudo nmcli nm sleep false' works as a
temporary fix (it only works when running it using sudo).
--
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/118
I'd just like to add that I have this problem, not on suspend (which I
haven't tried since upgrading) but each and every time I resume from
hibernate. I have to 'killall NetworkManager' to get networking back -
every time.
nmcli nm sleep false - didn't work for me.
--
You received this bug notif
Ian, just checked and no I didn't! I'll try it again next resume.
--
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:
[logind] stuck in PrepareForSleep, causing netw
I've just validated that
sudo nmcli nm sleep false
works for me after suspend
--
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:
[logind] stuck in PrepareForSleep
I am also having this issue after upgrading from Lubuntu 13.04 to 13.10.
However, I have my power settings to just turn off the screen when my
laptop is closed. Sleep and hibernate are disabled unless I manually
select them from the logout menu. But the logout menu is having its own
issues on anoth
Ok. I closed my lid and quickly opened it back up. The network was
disabled and I was unable to open it.
Running | sudo nmcli nm sleep false | does infact work as a temp fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manage
I have found a serious issue now with the suspend.
The video card's fan (it is an x1300) will sometimes not spin up again!
I was using the PC and was getting video corruption then I looked down and the
video fan is off.
It is free spinning so not stuck. I have the cover off as I was setting up
13
I started experiencing this same problem immediately after upgrading to
saucy. Happens like clockwork every time my netbook wakes from suspend.
Hardware: MSI WIND U230
Ubuntu version: 13.10
Network driver: rt2800pci
I found a workaround on this thread:
http://askubuntu.com/questions/362933/networ
General question: since Ubuntu seems to not support reverting dist-
upgrades, is there any collection of packages I can restore to their pre
13.10 working state to avoid this horrible problem? (If not I'll
seriously consider switching distribution; this is just too much)
--
You received this bug
I created an executable desktop file. Click on it and network comes up for me
Single line in the file says " gksu restart network-manager". I think putting
"gksu nmcli nm sleep false" would also work.
For my video card fan not respinning from suspend, I unplugged fan wire
from video card board
I don't know whether this means anything, but thought that it was worth
mentioning. When using 13.04 I had previously had some problems with a
kernel update and had gone back to using 3.8.0-30.44-generic. I noticed
today however that despite upgrading to 13.10 several days ago, the
kernel wasn't up
I occasionally have another suspend-related proble that might be related
to this one somehow: after opening my lid, sometimes the laptop resumes,
then suspends again automatically after a few seconds. If I then press
the power button to resume again, it does the same again and again. And,
after 3 o
@Pablo180 (paultait22) #30: I'm already running 3.11.0-12-generic, so
changing to that can't be the fix.
@Julien Olivier (julo) #33: I also have this probably related problem, and so
far I found no workaround for that, other than trying to resume again and again
until it eventually works. I've a
Hello,
I have the same bug. But there is no problem of network if you activate
XMIR.
--
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:
[logind] stuck in PrepareFo
@Catalin you're right, it happened again. That is one in five resumes
that the network fails to resume though, rather than every time like it
did before, but still annoying.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager
I have the same problem as #33 (julo), where my laptop automatically
goes back to suspend after waking up. I can reproduce this as follows:
I start up my laptop, suspend it the first time, wake it up again and I
can work on it just fine (except for this bug causing me to have no
internet connectio
I observed the same bug with current Saucy. Hardware is Lenovo TP x201
using iwlwifi.
After resume from suspend, networking is disabled. Enabling it in nm-
applet has no effect.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-man
***UPDATE***
Yesterday morning I decided to re-install Lubuntu. I spent a good time
prepping/reformatting an HDD to backup all the files I wanted to save.
I burned the Lubuntu 13.10 ISO in preparation to perform a fresh install
seeing as how the upgrade from .04 to .10 had plagued me with many bu
I have this problem, despite starting with a clean install.
However, I'm very rarely getting it since changing my disk setup: I
moved /home off my netbook's main (very slow) SSD onto a separate SD
card. I suspect that this has reduced demand on disk I/O, moving my
netbook mostly beyond the theshol
I am also experiencing this bug. I wonder what is wrong with you to
release Ubuntu when such a huge bug is present. The bug was alraedy
reported like in May. I doesn't even work on clean install.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
I'm just going to list the symptoms I'm experiencing on Ubuntu 13.10
after most, but not all, sleep-resume cycles:
- Network Manager in sleep mode (fixable by executing: 'nmcli nm sleep false',
works without sudo for me)
- System menu items for shutdown, reboot and sleep do nothing
- Sleep mod
I am reproducing similar symptoms as hife, but I have also problems
with resuming bluetooth after suspend. Maybe the problem is unrelated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.n
Contrary to #16 and the bug summary, for me PreparingForSleep is
actually set to false when this occurs to me (at least this most recent
time around). The commands and output below show how I observe this and
wake Network Manager up.
--
You received this bug notification because you are a member
Same problems here after suspend.
I use "sudo nmcli nm sleep false" to restore the connection, "sudo
reboot" to reboot, "sudo shutdown -h now" to shutdown and "sudo pm-
suspend" to suspend.
Regards.
--
You received this bug notification because you are a member of Desktop
Packages, which is sub
After resuming, I got this bug. I tried $ sudo service networking
restart => it crashed compiz. Apparently it seems to kill dbus but I
don't know why. Am I the only one in this case ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to networ
Contrary to Alfredo Pacheco's announce, my Lubuntu 13.10 is a fresh
install from downloaded ISO, after reformatted the HDD partition, yet I
get the same problem: wired & wireless network was not available. That's
why I'm here.
The 1st solution in the thread, killing the NetworkManager process usin
I am having similar issues with networking, and sometimes the sound
card, and the video drivers. I also noticed that the time for this
computer to boot, log-out, and log in is significantly (5-10 times)
longer than it was when I was running 13.04. At first I had upgraded
without a re-format. Today
I remember reading the following but it took me more than 3 rounds of
careful reading to find it again. So, re-posting again:
Evan Huus (eapache) wrote:
> it's not even a NetworkManager bug - whatever is supposed to be
> sending that signal to nm isn't sending it (correctly...)
>
> I have notice
I am experiencing some of the same problems as reported by Hife above.
The disabled network problem doesn't happen every time I wake my machine
up, but on some of the occasions when it does I also find that sleep is
disabled from the menu and from the function key, although I can still
"sudo pm-sus
** Attachment added: "strace-logind.log"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+attachment/3893752/+files/strace-logind.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
ht
** Attachment added: "systemd-shim-debug.log"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+attachment/3893753/+files/systemd-shim-debug.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
** Attachment added: "dbus-monitor-system.log"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+attachment/3893749/+files/dbus-monitor-system.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager i
The pm-utils and its configuration is fine, and maybe so of the network-
manager.
I am able to further decouple the problem -- If I boot into text mode
console, I am able to do "close the lid then open & wake it up" many
many times without interruptting my wired & wireless network, while
under Xor
The log files indicate that there is a problem with the D-Bus
communication between systemd-logind and systemd-shim. Following entry
is missing the systemd-shim log file:
GDBus-debug:Call:
ASYNC COMPLETE org.freedesktop
Something just crossed my mind: gnome-settings-daemon does some
necessary things to work with logind's own lid switch/power button
handling. Is any reporter here running Unity or GNOME who sees this? If
not, then that would explain why I or my colleagues never see this, and
it would be bug 1222021
I was seeing this on Unity before I decided to roll back to my backed-up
13.04 installation.
--
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:
[logind] stuck in Pr
Martin, I am seeing this regularly under Unity. Smells like a race
condition to me.
--
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:
[logind] stuck in PrepareForS
@Martin (#59) I am also experiencing the bug under Unity.
--
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:
[logind] stuck in PrepareForSleep, causing network and
I'm getting this all the time with GNOME Shell.
--
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:
[logind] stuck in PrepareForSleep, causing network and other serv
I too am using Unity.
--
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:
[logind] stuck in PrepareForSleep, causing network and other services
to not resume
Stat
Hi,
I've also this problem. I upgraded yesterday to 13.10 and after suspend
the network was gone. Then, I looked for the bug and I found it here.
Applying the nmcli command fixes it, however, if I suspend the machine
again and resume it, after few seconds it starts again to suspend
without me doin
Ohh, and I'm using Unity too.
--
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:
[logind] stuck in PrepareForSleep, causing network and other services
to not resu
@Daniel Lombraña González (teleyinex) #66
> however, if I suspend the machine again and resume it,
> after few seconds it starts again to suspend without me doing anything,
> leaving the machine in an unusable state.
Just try resuming again and again. For me this eventually works, but it
sometimes
I'm using Lubuntu 13.10 on an HP G62 and also have this issue.
When mine wakes from suspend it comes back, then very quickly switches
back to a bash screen with a few lines that don't appear for long enough
for me to read, then goes back to whetever I was doing.
Sometimes it has network and somet
I'm using gnome-settings-daemon with my fluxbox as WM, and I have this
problem.
--
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:
[logind] stuck in PrepareForSleep
I am experiencing this bug after upgrade to Xubuntu 13.10 from Xubuntu
13.04.
- Network manager is often disabled after resume;
- The menu item for Suspend creates a `Do you want to suspend to RAM?'
dialog, but after confirming, seems to only disable the Network manager
(does not actually suspend
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
--
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:
[logind] stuck in PrepareForSleep, causing
Wrt comment 57:
> Conclusion: I think the problem has something to do with Xorg.
In particular, if other people can confirm this, it seems related to the
logind inhibitor that gnome-settings-daemon sets so that logidn does not
handle the lid event by itself. But as people also confirmed that this
We have one theory what the problem could be (shim times out before finishing
the method call). To test this, it would be great if affected people could
install the systemd-shim version from my PPA:
https://launchpad.net/~pitti/+archive/sru-test:
sudo add-apt-repository ppa:pitti/sru-test
On 10/22/2013 05:50 PM, Pablo180 wrote:
> I'd just like to add that I have this problem, not on suspend (which I
> haven't tried since upgrading) but each and every time I resume from
> hibernate. I have to 'killall NetworkManager' to get networking back -
> every time.
>
> nmcli nm sleep false - d
I'm also having issues with shutdown/reboot. Menu doesn't work at times;
have to run shutdown or reboot -- and even that doesn't always work.
On 10/23/2013 09:27 AM, Alfredo Pacheco Jr wrote:
> I am also having this issue after upgrading from Lubuntu 13.04 to 13.10.
> However, I have my power sett
On 10/23/2013 11:27 AM, Alfredo Pacheco Jr wrote:
> Toshiba Satellite A135-S4427
That's funny, I have a Satellite L875D-S7111.
--
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/1184
This does work for me, every time:
sudo nmcli nm sleep false
On 10/24/2013 06:14 PM, Alexander List wrote:
> I observed the same bug with current Saucy. Hardware is Lenovo TP x201
> using iwlwifi.
>
> After resume from suspend, networking is disabled. Enabling it in nm-
> applet has no effect.
> I wonder what is wrong with you [...]
What's wrong ith us? Nothing. What about you? Please read and
understand points 1, 2 and 3 of
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
This kind of hateful comments is so wrong. It just shows your (lack
of) respect for others’ work. Let’s wor
I'm having the same issues. I'm most concerned at this point about the
inability to shut down properly.
On 10/27/2013 09:46 AM, hife wrote:
> I'm just going to list the symptoms I'm experiencing on Ubuntu 13.10
> after most, but not all, sleep-resume cycles:
>
> - Network Manager in sleep mode (f
I'm getting this with GNOME classic.
On Mon, Oct 28, 2013 at 4:19 PM, Evan Huus <1184...@bugs.launchpad.net> wrote:
> Martin, I am seeing this regularly under Unity. Smells like a race
> condition to me.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug re
56 matches
Mail list logo
