I am on Lubuntu 16.04.03 and I am having trouble with WIFI reconnection after
suspending the system. I opened
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719731 but without much
luck. Is there any chance that my issue is related or a dup of this one?
Has the fix been relseased for 16.0
Is it feasible to put NM 1.4 into -backports pocket?
--
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/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cl
For future reference, this is the list of upstream commits corresponding
to Aaron's patches, in the order they are being applied:
312cea870dfbc363da44074bd6f56ccd283c5420
shared: add nm_auto_close and nm_auto_fclose
ed299cc8605a8291a61b3a514f8dc20390b18c77
device/wwan: use nm_auto_close inste
Hi, I will close the request of SRU for oem-priority of this issue and
check if we can apply Aron's patches on other network-manager's bugs for
SRU.
** Changed in: oem-priority/xenial
Status: Triaged => Fix Released
** Changed in: oem-priority
Status: Triaged => Fix Released
--
Yo
Indeed, all the patches in Aaron's set are cherry-picked from upstream.
However I agree with Tony, we lack evidence that version
1.2.6-0ubuntu0.16.04.1 in xenial is still affected by the original bug.
> I still received some reports from my colleagues that it doesn't
> really fix the problem afte
IIRC, Aron's patches are from the upstream. That means we don't need to
submit those patches to the upstream.
--
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/1585863
Title:
WiF
My point is that we shouldn't release these patches as an SRU without
being able to reproduce the bugs that the patches claim to fix first.
Otherwise we risk introducing additional regressions.
So if we want to consider an SRU for NM with one or more of Aaron's
patches, then yes we need to go thro
There are many duplicated bugs.
Including this bug, all point to the race conditions, and Aron's patch set are
all about the solutions for those race conditions.
If we want to identify every race conditions and the logs, that will be
incredibly tedious workloads.
Imaging that we need to de-duplic
There's no evidence (ie. syslogs, package versions, output of wpa_cli)
provided which is a basis for re-opening the bug.
Also, please point us to the *exact* patch that is supposed to fix the
problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is su
We have tested Aron's patch on many OEM projects. The result is good and
it does fx the problem. At least it passed all QA tests.
--
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/1
Sorry. Comment #92 is not a good test.
I only tested it on my own laptop.
I still received some reports from my colleagues that it doesn't really fix the
problem after that comment.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network
This bug was marked FixReleased based on the upload of network-manager
1.2.6-0ubuntu0.16.04.1 to xenial updates and the comments from a many
people that the issue was resolved.
Recently there were two comments (#96 and #97) that claim that the bug
still exists. Comment #96 doesn't even list which
@fourdollars: have you observed yourself the bug with
1.2.6-0ubuntu0.16.04.1 on xenial? I'd like to make double-sure Aron's
patches are really needed. Comment #92 by you states that the bug was
fixed with 1.2.6.
--
You received this bug notification because you are a member of Desktop
Packages, w
While I don't have a xenial machine handy to test the bug and fix, I had a look
at the debdiff for the packages in Aron's PPA, for some sanity checks.
The following patches have been added:
# fix for LP: #1585863
shared-add-nm_auto_close-and-nm_auto_fclose.patch
device-wwan-use-nm_auto_close-inst
oem-priority needs to the SRU for xenial.
happyaron has finished the major work on
https://launchpad.net/~happyaron/+archive/ubuntu/nm-oem/+packages.
Please help to finish the remaining SRU process.
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
** Changed in: oem-priority/xenial
Status: Fix Released => Triaged
** Changed in: oem-priority
Status: Fix Released => Triaged
** Changed in: oem-priority
Status: Triaged => In Progress
** Changed in: oem-priority
Status: In Progress => Triaged
--
You received this
Also here Ubuntu 16.04, kernel 4.11.3, Asus UX303UB.
Probably related to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125
--
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
Confirmed Lenovo T440P
--
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/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
required to fix it.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
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/1585863
Title:
WiFi malfunction after suspend &
Could anyone make sure that this bug is also fixed for yakkety (the
original bug target) and zesty? In that case I suppose we could finally
close this bug and remove it from the sponsorship queue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
** Changed in: oem-priority/xenial
Status: Triaged => Fix Released
** Changed in: oem-priority
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpa
Since network-manager 1.2.6-0ubuntu0.16.04.1 was published in the
xenial-updates repository, I think the status can be set to fixed for
xenial.
code:
apt show network-manager 2>/dev/null | grep -E 'Version|APT-Sources'
Version: 1.2.6-0ubuntu0.16.04.1
APT-Sources: http://archive.ubuntu.com/ubuntu x
Also tested network-manager 1.2.6-0ubuntu0.16.04.1 from xenial-proposed for 15
days, and it didn't happen again.
Looks like the error is fixed in that version of network-manager.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-ma
I tested network-manager 1.2.6-0ubuntu0.16.04.1 from xenial-proposed for
100 cycles, and this issue didn't happen again.
--
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/1585863
T
For me the problem seems to be fixed with today update to network-
manager 1.2.6 in xenial-proposed. So far I did some 5-7 suspend/resume
cycles in different locations and everything seems to work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscr
The fix from the fourdollars ppa is also working for me: Lenovo x230.
I ran the stress test before applying the fix and confirmed that wifi
was non-functioning after the 30 suspend / wake cycles and needed the
"sudo wpa_cli scan" to activate it again.
I then added the ppa and applied the update t
Seems it works for my Lenovo x230t. Thanks for your effort!
--
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/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo
I missed this commit. It should work now.
>From 6eaded9071fbf868476255adb8ee5f416e7ad134 Mon Sep 17 00:00:00 2001
From: Thomas Haller
Date: Tue, 14 Feb 2017 12:45:38 +0100
Subject: [PATCH] device: add get_autoconnect_allowed() virtual function
It allows derived classes to override the autoconne
Oops, sorry. The package is built failed.
I need to revise the patch again.
--
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/1585863
Title:
WiFi malfunction after suspend & resu
I made a PPA at https://launchpad.net/~fourdollars/+archive/ubuntu/lp1585863 to
include comment #84.
You can try it and give some feedback.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad
@fourdollars does this commit get applied to 16.04 proposed and then to
backports? I (and I am sure others) would be happy to test this for
xenial but I am unclear as to the path the patches follow to get to the
main repositories.
--
You received this bug notification because you are a member of
This issue has been fixed by the following four commits.
>From 1b925c0028cdaaf14d4ebd1f07848ba5640915c6 Mon Sep 17 00:00:00 2001
From: Tony Espy
Date: Thu, 16 Jun 2016 15:07:33 -0400
Subject: [PATCH] wifi: clear WiFi requested_scan if suppl exits
It's possible for wpa_supplicant to exit wit
If network-manager 1.4.4 has fixed this issue, it then needs to be
backported to 16.04 LTS and 14.04 LTS.
--
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/1585863
Title:
WiFi ma
I can not reduplicate this issue on Ubuntu 17.04
It looks like that network-manager 1.4.4 has fixed this 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/1585863
Title:
W
** Changed in: oem-priority/xenial
Status: Confirmed => Triaged
** Changed in: oem-priority
Status: Confirmed => Triaged
--
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/
** Tags removed: somerville
** Changed in: oem-priority
Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)
--
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/1585863
Title:
** Tags added: somerville
--
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/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
required to fix it
** Changed in: oem-priority
Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)
--
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/1585863
Title:
WiFi malfunction after sus
** Changed in: oem-priority
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.launchpad.net/bugs/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo
** Description changed:
+ HOW TO REPRODUCE:
+ 1. Install fwts by `sudo apt-get install fwts`.
+ 2. Run the suspend & resume stress test.
+ sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5
--s3-delay-delta=5
+
+ RESULT:
+ The WiFi can not connect to any access point and we have to
Seems to me that if NM stalls due to a race condition, then restarting NM
*is* a workaround, so yes, adding additional scripts to systemd is a
solution, but not the "answer".
derek
On Fri, Feb 3, 2017 at 1:11 AM, Tony Espy <1585...@bugs.launchpad.net>
wrote:
> @Kevin
>
> NetworkManager already h
@Kevin
NetworkManager already has code to monitor system signals related to
suspend/resume, so no adding additional scripts to /usr/lib/systemd
/system-sleep isn't the answer.
@Dan
Different bug... this bug is caused by NetworkManager's WiFi scanning
logic stalling due to a race condition. You
#64 wrote "could this suggest this might be better fixed with a systemd
dependency?", well, http://man7.org/linux/man-pages/man8/systemd-
sleep.8.html says
Note that scripts or binaries dropped in
/usr/lib/systemd/system-sleep/ are intended for local use only and
should be con
"after resume, only a couple of wifi networks will be listed at most,
and never the one I use" - that's exactly the symptom I see after
resuming my DELL E7450. Also, the Wi-Fi icon is replaced with an "arrow
up arrow down" one. `sudo service network-manager restart` reconnects
most of the time, but
I confirm, sometime suspend fails and syslog says:
(my ubuntu is an upgrade from 15.10 to 16.04) model: asus-n551vw
Jan 29 19:46:39 asus-n551v systemd[1]: Reached target Sleep.
Jan 29 19:46:39 asus-n551v systemd[1]: Starting Suspend...
Jan 29 19:46:39 asus-n551v systemd-sleep[16200]: Failed to con
Just to confirm, about #60 and #65, the workaround does not work.
I also confirm that the script "/lib/systemd/system-sleep/wpasupplicant" never
runs, it is certainly a Systemd error.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to netwo
Ugh, and then I wake my Thinkpad 410s just now, and I hit the bug on the
201st cycle. ;(-
Guess I'll go back to dropping the patch again from 1.2.6 and see how
many cycles I can run on it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@taiebot65
Thanks. I'll take a look.
Regarding this bug, it turns out that when I was testing my version of
NM with the dropped 'ScanDone' patch (wifi-Signal-on-the-wifi-
device...), I'd been doing so on top of the newly re-based 1.2.6, and it
turns out there was an actual fix in 1.2.6 which see
** Changed in: oem-priority/xenial
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.launchpad.net/bugs/1585863
Title:
WiFi malfunction after suspend & resume stress
Sorry #1659058
--
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/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
required to fix it.
Status i
@Tony
i have opened #1659059 for my 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/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
I've reproduced this on a Thinkpad 410s running 16.04 LTS. The version
of network-manager I used is the latest from xenial-updates:
1.2.2-0ubuntu0.16.04.3.
A few comments:
1) The fwts s3 test uses a low-level API to exercise suspend/resume.
I've been working with the fwts maintainer on an extens
@deragon, here, the "$(sleep 10;/sbin/wpa_cli resume)&" doesn't work.
Somehow, I wonder if there is some black magic due to systemd, but it
doesn't seem that any command after the sleep is ever executed.
--
You received this bug notification because you are a member of Desktop
Packages, which is
BTW my bug seems to be different I seem to reconnect to the AP but i
have no internet connection so i still need to run sudo systemctl
restart network-manager.service to get an internet connection
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
I tried comment #60 and it does not work for me. My file looks like that
but after a restart i am still unable to connect.
My file looks like that now
#!/bin/sh
set -e
if [ "$2" = "suspend" ] || [ "$2" = "hybrid-sleep" ]; then
case "$1" in
pre) /sbin/wpa_cli suspend ;;
post)
Christian,the failure occurs to me even in a stationary scenario, it
does not occur at all suspend/resume cycles, but randomly. (I could not
establish a pattern anyway)
In fact, what you described never occured to me, the network-manager UI
doesn't show a stale list of wifi networks. In my case th
Hi @cascagrossa, just to clarify: my impression is that in order to
trigger the bug you'll need to suspend somewhere where the WLAN network
you want to connect to at resume time isn't available as it's the scan
aspect of things that appears to be inhibited. This is evidenced by the
fact that he ne
Still considering the suggestion of Hans Deragon (# 60), I am testing
with:
post) (sleep 1;/sbin/wpa_cli resume) & ;;
A reasonable number of suspend/resume cycles will be needed to make sure
it works, maybe a day or two of testing.
Dell Inspiron 5557
Kubuntu 16.04.1 fresh install
kernel 4.4.0-59
Also further to #60, I have put the following in mine (Thinkpad X1
Carbon 3) and it does indeed seem to fix the problem so far - been
testing over a few days:
/lib/systemd/system-sleep/wpasupplicant:
post) (sleep 3 ; /sbin/wpa_cli resume) & ;;
16.04.1 fresh install, kernel 4.4.0-59; netw
Hans Deragon, your suggestion in #60 fixes the issue for me, even if I
use sleep 5.
Thinkpad T420 with Intel Corporation Centrino Ultimate-N 6300 (iwlwifi
driver)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
I can confirm that after every resume my wifi is not working. I used to
"solve" it by network-manager restart but running "wpa_cli resume"
manually fixes the problem as well.
I tried the sleep workaround by Hans but it did not help. I can see this
in /var/log/syslog:
Jan 19 00:20:34 vaclav-ntb sy
So, this has been going on for quite a while and still hasn't been
fixed?
I've got an DELL E5450 with an Intel Corporation Wireless 7265 wifi
adapter.
After resume from sleep wifi network does not reconnect nor does my
wireless network show up in the NM gui. But one other strangely enough
does an
Éric Piel, add a sleep in that file and tell us if it fixes the problem
for you.
Something like:
post) $(sleep 10;/sbin/wpa_cli resume) & ;;
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchp
Interestingly, this "wpa_cli resume" command is precisely what does
/lib/systemd/system-sleep/wpasupplicant.
I've checked, this script is run at resume, as expected. However, it
seems wpa is called too early, and it doesn't have any effect.
--
You received this bug notification because you are a
As a side-note, as it seems it's been triggered for my laptop by the update to
network-manger 1.2.4, one of the few fixes included in 1.2.6 is the following:
* Fixed a bug that caused devices to stay unmanaged after resume from sleep.
So quite probably, updating network-manager to the latest stab
One more thing: contrarily to the title of this bug report, here "sudo
wpa_cli scan" doesn't help to get the list of network again. However,
"sudo wpa_cli resume" works.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in U
Same as comment #52 and #53, while it used to be just once in a while,
since a few weeks, it's now _every_ single time that my laptop resumes.
There are many similar bugs but with probably different causes. So to be
clear here is the symptoms I see much more recently since a few weeks
(on 16.04):
Just updated to NetworkManager version 1.2.6 on Yakkety and confirm that
the bug is still present
--
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/1585863
Title:
WiFi malfunctio
Fresh 16.04.1 install on ThinkPad X1 carbon 3 with stock Intel 7265
(802.11abgn) WiFi here; laptop also has a Sierra Wireless EM7345 4G LTE
WWAN integrate USB module.
Typical scenario: I use the WWAN when out and about, suspend the laptop,
come back to office and expect the laptop to re-connect to
This bug seems to affect a lot of people on Ask Ubuntu too: "Wifi
doesn't work after suspend after 16.04 upgrade"
http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
after-16-04-upgrade, including me.
I have a Thinkpad T440 where I previously ran Fedora for multiple
releases. Nev
** Tags added: papercuts2017
--
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/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
required to fix
I am having this problem now as well. A while back I used a script to
restart network manager service after resume and this fixed all issues.
Yesterday I tried to see if this issue has been fixed or not. After
disabling the service with systemd I tested it with a two hour or so
suspend. After wa
After an upgrade of network-manager to 1.2.4 (SRU bug #1645698) the
problem with wifi after suspend/resume on my Lenovo X220 now happens
every time, while previously it was less frequent. Perhaps this will
help to do something about this problem.
--
You received this bug notification because you
You're kidding? "no longer affects:network-manager"
It certainly did as recently as yesterday!
--
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/1585863
Title:
WiFi malfunc
** No longer affects: network-manager
--
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/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
requir
@deragon Yes, you are right, there is related bug, see bug #1589401. But
I'm pretty sure this have one origin and it is wifi driver, especially
for intel cards. If you look at the bottom of the discussion on the
mentioned bug, you'll find that problem remains even after change to
another network ma
@auspex In my experience the physical act of bringing a computer out of
suspend takes longer than network manager takes to restart and reconnect
(well under 0.5 seconds). It's not only negligible, but I think it's
inevitable that there will be some latency in reconnecting after
suspend.
I have to
@JaSauders I think the downside is that restarting NetworkManager, on a
system that doesn't have any problem with network connections after a
suspend event (and that surely must be most systems, or this would be
fixed already) will result in a much slower reconnection to the network.
--
You recei
@monte, I get the impression that you may suffer from more than one bug.
I have none of the symptoms you describe. I believe that this bug
report must remain focused on the resume issue. Any other issue should
be in another bug report (maybe already existing?).
In a sideline, sometimes I feel th
@jasauders
Problem is that bug is present not only for suspend/resume scenario, but also
for wifi on/off. And for me it even drop connection sometimes and can't
reconnect without wifi restart. It's a problem with wifi drivers and devs not
seems to care about it.
--
You received this bug notifi
I'm surprised this is still a thing. I added the common systemd "restart
network-manager on resume" script most folks with this issue have used.
I added it quite a while ago. My system has been working consistently
since then without issue... to the point I actually forgot that this bug
existed.
I
And coming back to my workaround script
NetworkManagerRestartWorkaroundForBug1380480.sh, I tried the more
friendly '(sleep 3;sudo wpa_cli scan)' solution, but it dit not always
work. The only solution I found to have networking working reliably
after resume is to have NetworkManager restarted.
--
btw, merely restarting Network Manager never worked for me. I have to
remove iwlwifi and reload it.
derek
On Thu, Nov 17, 2016 at 2:18 PM, Derek Broughton
wrote:
> We used to have this. I'm sure, a decade ago, I could actually tell
> whatever was managing the hibernate/suspend, in the gui, to r
We used to have this. I'm sure, a decade ago, I could actually tell
whatever was managing the hibernate/suspend, in the gui, to remove certain
kernel modules on suspend and load them on resume. Now we're right back to
needing it.
derek
On Thu, Nov 17, 2016 at 1:59 PM, Hans Deragon wrote:
> This
This serious issue is dragging to long. People want computers that
"just work". If pinpointing the source of the problem is difficult and
few resources are available, why not package a workaround that restarts
NetworkManager upon resume?
Attached is my workaround. Works nicely. Finally, I have
** Tags added: suspend-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/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
required to fi
I installed Fourdollars' PPA but I can see current version is higher
than that (1.2.4 vs 1.2.2 in the PPA).
I'm using yakkety right now.
How can I test the PPA's version?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager i
Thank you for the patches, glad there is some progress, since this
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401
seems to be "closed" now :/ - However, its now 20 days later, and I keep
seeing more and more people on askubuntu, IRC, reddit etc. have this
issue. How can we m
#36 is for 1.2.2 of yakkety!!
--
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/1585863
Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
required to fi
** Patch added: "network-manager_1.2.2-0ubuntu9.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/+attachment/4728649/+files/network-manager_1.2.2-0ubuntu9.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscr
This is for 1.2.2 of xenial.
** Patch added: "network-manager_1.2.2-0ubuntu0.16.04.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/+attachment/4728648/+files/network-manager_1.2.2-0ubuntu0.16.04.2.debdiff
--
You received this bug notification because you are
I noticed that NM 1.2.2 hit proposed yesterday. I pulled down proposed
but did not see a change with NM 1.2.2 (i.e. I was still seeing the
issue), though after re-reading Aron's message, it sounds like the fix
is not 1.2.2, but the fix can be applied to 1.2.2 once it becomes
available. Anyway, afte
same issue here on two laptops. This workaround seems to work for me
until I get a real fix.
http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
after-16-04-upgrade
-Mario
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed t
@fourdollars, I've pinged release team for twice but without response,
personally it's nice to be accepted asap.
--
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/1585863
Title:
Hi Aron,
I saw n-m/1.2.2 at https://launchpad.net/ubuntu/xenial/+queue?queue_state=1.
When do you expect it will be accepted?
--
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/1585
You can try having the script do "modprobe -r" and "modprobe" on your wifi
module. That should always work, but seemed like overkill in my case. In
any case, these are workarounds, not fixes.
On 4 Aug 2016 6:01 a.m., "Aleve Sicofante" wrote:
> @auspex: Your script doesn't work here. I just creat
btw, n-m/1.2.2 is in queue for Xenial SRU, fix for this issue can be
integrated once it's in -proposed.
--
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/1585863
Title:
WiFi malf
This is for yakkety.
** Patch added: "network-manager_1.2.2-0ubuntu7.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/+attachment/4713869/+files/network-manager_1.2.2-0ubuntu7.debdiff
--
You received this bug notification because you are a member of Desktop
Pac
Hi,
I made a testing PPA at ppa:fourdollars/lp1585863.
Please help to check if it can fix this issue for you.
If not, your problem may not be related to this issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubunt
This is for xenial.
** Patch added: "network-manager_1.2.0-0ubuntu0.16.04.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/+attachment/4713865/+files/network-manager_1.2.0-0ubuntu0.16.04.4.debdiff
--
You received this bug notification because you are a member
1 - 100 of 108 matches
Mail list logo