*** This bug is a duplicate of bug 1380480 ***
https://bugs.launchpad.net/bugs/1380480
BTW,
If I do "sudo iwlist wlp58s0 scanning" when the problem is present my
wifi starts working again.
/Jo Christian
--
You received this bug notification because you are a member of Desktop
Packages, whi
*** This bug is a duplicate of bug 1380480 ***
https://bugs.launchpad.net/bugs/1380480
Seeing the same problem on my Dell XPS13 (2016)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.
*** This bug is a duplicate of bug 1380480 ***
https://bugs.launchpad.net/bugs/1380480
** This bug has been marked a duplicate of bug 1380480
network disabled after suspend - resume
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
same on Lenovo Y70-70 16.04LTS
--
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/1286552
Title:
No wifi after suspend
Status in linux package in Ubuntu:
Confirmed
Status in ne
Following works for me for my Sony Vaio (even when enabling energy
saving option for ath9k driver). I collected the script information from
various sources - the last missing thing for my Vaio seemed to be the
timeout parameter. Since I added the timeout parameter it works:
case "$1" in
hibernate
Here is a solution that worked for me in Ubuntu 15.10:
http://askubuntu.com/questions/754913/wifi-doesnt-reconnect-after-
suspend-in-ubuntu-15-10-yet-again/754915#754915
sudo touch /lib/systemd/system-sleep/restart-networking.sh
sudo chmod +x /lib/systemd/system-sleep/restart-networking.sh
sudo na
is there any workaround resume script that is working for 15.10.+ and
systemd?
--
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/1286552
Title:
No wifi after suspend
Status in l
iwlwifi driver on Aspire 5930G and I solved in this way:
creating both /etc/pm/config.d/unload_modules and /etc/pm/sleep.d/wakenet.sh
the command that permit to connect wifi after resume is
sudo pkill -f wpa_supplicant
bye
--
You received this bug notification because you are a member of Desktop
still present in 15.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/1286552
Title:
No wifi after suspend
Status in linux package in Ubuntu:
Confirmed
Status in network
> nicolas kleinklaus (nknico) wrote on 2015-07-01: #109
> Solution is :
>
> sudo touch /etc/pm/sleep.d/wakenet.sh
>
> sudo chmod +x /etc/pm/sleep.d/wakenet.sh
>
> sudo gedit /etc/pm/sleep.d/wakenet.sh
>
> Insert the following lines:
>
> #!/bin/bash
> case "$1" in
> thaw|resume)
> nmcli nm
Solution is :
sudo touch /etc/pm/sleep.d/wakenet.sh
sudo chmod +x /etc/pm/sleep.d/wakenet.sh
sudo gedit /etc/pm/sleep.d/wakenet.sh
Insert the following lines:
#!/bin/bash
case "$1" in
thaw|resume)
nmcli nm sleep false
pkill -f wpa_supplicant
;;
*)
;;
esac
exit $?
And then save and exit.
--
same problem on a fresh ubuntu 14.04 on HP Pavilion 15. it's so
annoying.
--
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/1286552
Title:
No wifi after suspend
Status in linux
The solution in comment #92 worked for me and, in contrast with comment
#91, for me it was essential to keep the "pkill -f wpa_supplicant" line.
Using a Samsung NP530U3B laptop with 14.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to n
the latest kernel seems to be working much better for be, as even after resume
I get working wifi. Unfortunately it fails after a while again (without suspend
or power save, just in the middle of surfing). Likely my issue this is now more
related to i.e. Bug 1320070
Thanks for all your work.
PS
I tracked down the issue where WiFi would fail after suspend in that it
doesn't associate anymore (tries to connect but fails), and it's a bug
in wpa-supplicant that was fixed in the current version (Ubuntu uses
2.1, newest is 2.3). Replacing Ubuntu's wpa-supplicant 2.1 with Debian's
wpa-supplicant
As a further note, the script by aztecjoe works around the issue just
fine.
I would recommend delivering it via an updated network manager package
and not waiting for network manager to have the issue fixed. If and when
the issue is fixed in network manager, the redundant restart should not
be a b
I see it on a laptop that does not connect automatically to the wireless
network after wakeup. But I have the same issue also with a desktop with
wired ethernet. So a more appropriate title would be 'network manager
fails to reconnect after resume', because the issue is not wifi
specific.
After a
The issue started recently (early November 2014). I had been running
14.04 since July without this issue. So an automatic update has
infected my setup since early November.
The work around was to create the file 04_bug_network_manager_restart in
directory /etc/pm/sleep.d. See terminal listing
Lenovo Thinkpad 520 with the same issue here
T
--
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/1286552
Title:
No wifi after suspend
Status in linux package in Ubuntu:
C
I've found, as a work around, sending a "kill -hup" signal to the
wpa_supplicant process will 'wake' it up and network connectivity will
get restored again
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https:/
Wouldn't recommend the course of action in 92, I've broken wifi after
reboot it won't connect, I'm going to have to reinstall the operating
system.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.la
Seems to be working intermittently...
--
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/1286552
Title:
No wifi after suspend
Status in “linux” package in Ubuntu:
Confirmed
Sta
Sorry spoke too soon, it worked with a brief period of suspend (screen
did go blank) but is not working again. Tried #93 for what I thought
might be the equivalent file no joy.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-mana
#92 seems to have solved this bug for me. Thanks nknico. My Dad has
the same bug on OSX...
--
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/1286552
Title:
No wifi after suspen
I run Ubuntu 14.04 on a DELL XPS 13 notebook. I started having this
problem after I upgraded to kernel 3.13.0-37. Resume takes longer than
usual and I need to kill NetworkManager in order to restart it and be
able to get a connection.
--
You received this bug notification because you are a member
The problem seems to occur after kernel updates. NetworkManager needs to
be restarted ('sudo kill PIDforNetworkManager") after suspend.
uname -r
3.13.0-36-generic
apt-cache policy network-manager
network-manager:
Installed: 0.9.8.8-0ubuntu7
Candidate: 0.9.8.8-0ubuntu7
Version table:
*** 0.9
I was having this same problem on Ubuntu 14.04 and after a couple of days of
trying to fix it, I found a file inside /etc/pm/sleep.d/ which is called
99dw1704.
This file handles disabling and enabling the wl module on hibernate and
suspend. All I had to do to fix it is to run:
sudo chmod -x /et
Works for me too.
sudo touch /etc/pm/sleep.d/wakenet.sh
sudo chmod +x /etc/pm/sleep.d/wakenet.sh
sudo gedit /etc/pm/sleep.d/wakenet.sh
Insert the following lines:
#!/bin/bash
case "$1" in
thaw|resume)
nmcli nm sleep false
pkill -f wpa_supplicant
;;
*)
;;
esac
exit $?
And then save.
At least
Finally found a fix that worked for me: http://askubuntu.com/a/368836
Also, at http://ubuntuforums.org/showthread.php?t=2218043, there was the
following extra line in wakenet.sh:
pkill -f wpa_supplicant
...but I found I didn't need that. (But I'm posting that here in case someone
else will need
Does anyone know if Canonical or ubuntu developers will be trying to fix
this or a duplicate of it, please?
None of the suggested fixes apply or have worked for me on 14.04. I
won't be upgrading my other computer from 12.04 until this issue is
fixed. (When I tried that computer on the 14.04 Live
My issue was resolved after removing /etc/pm/config.d/config and a
RESTART.
That config file contained the line SUSPEND_MODULES="wl", which I had
added after the first time problems came up with suspend/resume about
half a year ago (using 12.04) and using these instructions to fix it:
http://ubunt
Problem is back. Obviously not a modules file issue. Though I wonder why
removing it worked the first time around?
On May 3, 2014 6:52 PM, "Adam Hicks" wrote:
> It works fine for me when plugged in. Definitely a wireless issue IME.
> On May 3, 2014 6:35 PM, "kylea" wrote:
>
>> I believe this
It works fine for me when plugged in. Definitely a wireless issue IME.
On May 3, 2014 6:35 PM, "kylea" wrote:
> I believe this problem is not a WIFI issue only - unless I have a new
> bug. My experience only started with 14.04 and the issue occurs on Wired
> Connection. Network Manager will not
I believe this problem is not a WIFI issue only - unless I have a new
bug. My experience only started with 14.04 and the issue occurs on Wired
Connection. Network Manager will not re-enable the network connection.
--
You received this bug notification because you are a member of Desktop
Packages,
I don't even have jupiter installed on my system, so that's obviously
not the issue.
--
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/1286552
Title:
No wifi after suspend
Statu
I solved the issue by removing jupiter 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/1286552
Title:
No wifi after suspend
Status in “linux” package in Ubuntu:
Confirme
Seems solution in #68 solved the problem for me.
I installed 14.04 recently and suffered from this problem along with the other
(often my Xubuntu failed to suspend/reboot/shutdown at all).
So the following steps let me comepletely get rid of these problems:
1. turn off Light Locker
2. uncheck All
Affects me on 14.04, 3.13.0-24 kernel.
Network card: Intel Corporation Centrino Wireless-N 2230 (rev c4)
Module: iwlwifi
--
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/1286552
I can also confirm that my issue is resolved after removing
/etc/pm/config.d/modules and a restart.
--
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/1286552
Title:
No wifi after
Suffered from the same Bug after upgrade 13.10 to 14.04
chipset:
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (rev 04)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor
Peak] (rev 34)
what caused the problem for me was an entry i
Removing Jupiter (as in comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/comments/60
) has solved the problem for me. Additionally, suspending is now back to
pre-13.04 speeds on my Thinkpad X220 (i.e. under 2 seconds).
--
You received this bug notification because you are a me
As I already said, for me, removing stuff in /etc/pm/config.d/modules
doesn't resolve the problem because my wifi chipset stays in hardblocked
mode...
nico@nico-portable:~⟫ sudo rfkill list
[sudo] password for nico:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
Ralink r
Ok, took alook inside /etc/pm/config.d/modules and found this line and ONLY
this line:
SUSPEND_MODULES="b43 bcma"
I removed the /modules file and now everything is peachy.
New to this process...what do we do to get Canonical to add this adjustment
to network-manager?
Also, is there any ill effe
I just re-installed network-manager. Took a look in /etc/pm/config.d and
there's no config file. Has this already been updated by you hard working
devs in the package? Or am I missing something?
Thanks for all the work.
On Fri, Apr 25, 2014 at 2:47 PM, punund <1286...@bugs.launchpad.net>
wrot
I would like to confirm having this bug after upgrade to 14.04 from 13.10, and
fixing it by removal of
"/etc/pm/config.d/config" which contained
SUSPEND_MODULES="rt61pci"
Apparently, what was helping to fight this problem in 13.10 is making it
reappear in 14.04, which is ironic.
--
You receive
I forgot to say that I do NOT have password required after waking from
suspend or returning from a blank screen.
--
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/1286552
Title:
** Attachment added: "after_reboot_no_wifi.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4096916/+files/after_reboot_no_wifi.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu
I seem to be in a similar position to Nicolas. Before a suspend, with
wifi working, WWAN is disabled according to 'nmcli nm'. Then, after
suspending, with wifi not working, WWAN is enabled.
However, sometimes wifi doesn't work even after restarting my Dell
laptop and WWAN is disabled after restart
** Attachment added: "after_reboot_wifi_working.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4096913/+files/after_reboot_wifi_working.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager
** Attachment added: "after_suspend_no_wifi.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4096911/+files/after_suspend_no_wifi.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubun
Humthe fact is that I need the lockscreen functionality...
But I am seeing something interesting related with the new unity
lockscreen. There is no NetworkManager indicator in it. It was present
before they introduce the new lockscreen. Maybe it is related ??
--
You received this bug notific
I mean turning off the security. That is to say have no password when
logging in after suspend.
Settings> security & privacy> Uncheck waking from Suspend & Returning
>From blank screen
I think the super user permission are getting screwy somewhere. It's
worth a shot nico. If it doesn't work nothi
What did you meen by "without login Passwords 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/1286552
Title:
No wifi after suspend
Status in “linux” package
did you try it without login Passwords after suspend? That's what fixed
it for me with the deletions...
--
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/1286552
Title:
No wifi
@justin parker as i said in my post #58 it's even worse if i delete
/etc/pm/config.d/config, because the wifi chipset keeps in hardblocked
mode.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.laun
Hey Guys Try this work around, It's the only one that worked on my
Toshiba NB505 With realtek drivers...
Settings> security & privacy> Uncheck waking from Suspend & Returning
>From blank screen
Delete the entire contents of the following files
"/etc/pm/config.d/config" & "/etc/pm/config.d/unload_
I never use jupiter on this machine. There is no relation with this problem
for me.
2014-04-25 1:57 GMT+02:00 Adam Hicks :
> I've always used TLP but this issue started before I installed it on this
> machine.
> On Apr 24, 2014 5:55 PM, "justin parker" <1286...@bugs.launchpad.net>
> wrote:
>
> >
I've always used TLP but this issue started before I installed it on this
machine.
On Apr 24, 2014 5:55 PM, "justin parker" <1286...@bugs.launchpad.net> wrote:
> s0m3f00l@Ubuntu-s0m3f00l:~$ sudo apt-get purge jupiter
> [sudo] password for s0m3f00l:
> Reading package lists... Done
> Building depend
s0m3f00l@Ubuntu-s0m3f00l:~$ sudo apt-get purge jupiter
[sudo] password for s0m3f00l:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package jupiter
s0m3f00l@Ubuntu-s0m3f00l:~$
Issue remains un-resolved for me friend cong
Found someting for me. I have the old package jupiter and remove it !
# sudo apt-get purge jupiter
Bingo, all run well !
For reference to jupiter http://www.webupd8.org/2010/07/jupiter-ubuntu-
ppa-hardware-and-power.html
--
You received this bug notification because you are a member of Desktop
3.13.0-24-generic
Ubuntu 14.04
Acer Aspire One 522
Neither ethernet nor wifi resumed from suspend after upgrading from 12.04.
NetworkManager was sleeping. Killing nm helped and solution described in
OssNass's post #32 put things right.
Thanks.
--
You received this bug notification because you
Removing the /etc/pm/config.d/config does'nt resolve the problem for me.
Even worse : the wifi chipset stays hardblocked after suspend :
nico@nico-portable:~⟫ sudo rfkill list
[sudo] password for nico:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
--
You received this
For me removing /etc/pm/config.d/config (I added in 13.10) also fixed the
issue. After waking from suspend and hibernate wifi reconnects nicely.
Ubuntu 14.04, upgraded from 13.10, Intel Corporation Centrino Wireless-N 2230,
iwlwifi driver.
--
You received this bug notification because you are a
My comment #41 above does not fully apply. It turned out that removing
"iwlwifi" from SUSPEND_MODULES="" in /etc/pm/config.d/config (I had to
add it in 13.10 in order to get it working) fixed the issue for me.
However this seems to imply that unloading the driver will break wifi,
even if network-ma
Obviously a different issue since nmcli would be stuck in sleep if it
worked for you. Why post that here if we've tried it already?
--
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
I had de same problem on 2 laptops after 14.04 install (was ok with 13.10).
Workaround in #32 solved the 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/1286552
Title:
This was already suggested and didn't work. If you scroll back you'll
see.
--
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/1286552
Title:
No wifi after suspend
Status in “linu
I have solved similar issue using this advice:
http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re-
connecting-after-suspend/368735#368735
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.
nmcli after suspend
Curiously we can see that WWAN is not activated before, but is activated
after.
** Attachment added: "nmcli nm after suspend"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4094123/+files/nmcli%20nm%20after%20suspend
--
You received this bug not
nmcli before suspend
** Attachment added: "nmcli nm before suspend"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4094122/+files/nmcli%20nm%20before%20suspend
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
lshw -C after suspend
** Attachment added: "lshw -C network after suspend"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4094113/+files/lshw%20%20-C%20network%20after%20suspend
--
You received this bug notification because you are a member of Desktop
Packages, whi
lshw -C before suspend
** Attachment added: "lshw -C network before suspend"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4094112/+files/lshw%20%20-C%20network%20before%20suspend
--
You received this bug notification because you are a member of Desktop
Packages,
@OssNass.
I already try the SUSPEND_MODULES=xxx in /etc/pm/config.d/load, instead
of /etc/pm/config.d/load/unloaded.modules (does it change something ?),
in 13.10 because the wifi card itself doesn't wake up.
But in the present case the card IS actualy wake up as you can see :
nico@nico-portable
Nmcli nm after suspend Complete and utter failure at the highest
level
** Attachment added: "Nmcli nm after suspend"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4094044/+files/nmcli_after_suspend
--
You received this bug notification because you are a mem
"lshw -C network" before suspend.
** Attachment added: ""lshw -C network" before suspend."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4094041/+files/lshw_output_before_suspend
--
You received this bug notification because you are a member of Desktop
Packages,
Tried editing "/etc/pm/config.d/config"
&"/etc/pm/config.d/unload_modules" like the
http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html
. Same issue after editing:
SUSPEND_MODULES="$SUSPEND_MODULES rtl8192ce"
SUSPEND_MODULES="$SUSPEND_MODULES r8169"
SUSPEND_MODULES="$SUSP
Nmcli nm before suspend. Everything is going good.
** Attachment added: "Nmcli nm before suspend"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4094043/+files/nmcli_before_suspend
--
You received this bug notification because you are a member of Desktop
Packages, w
"lshw -C network" after suspend. Network is not coming back at this
point and won't connect to anything
** Attachment added: ""lshw -C network" after suspend."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+attachment/4094042/+files/lshw_output_after_suspend
--
You received
Same problem here with iwlwifi driver and on kubuntu.
--
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/1286552
Title:
No wifi after suspend
Status in “linux” package in Ubuntu:
The output of "lshw -C network" and "nmcli nm" before and after the
suspending might be usefull, so please can you submit that ?
--
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/12
If the network manager is not asleep then try this, it might help
http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html
--
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/
Is the problem present in KUbuntu or XUbuntu or it is just for Ubuntu ?
--
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/1286552
Title:
No wifi after suspend
Status in “linux”
If the network manager is not asleep then try this, it might help
http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html
--
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/
Agreed NM not asleep I used to get a bad password error in 12.04
haven't seen that here
--
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/1286552
Title:
No wifi after suspen
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
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
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/1286552
Title:
No wifi after suspend
Stat
86 matches
Mail list logo
