Not a duplicate of 1585863, as
$ sudo wpa_cli scan
does not recover nm-applet functionality. There seem to be a number of similar
but different issues related to wifi.
** This bug is no longer a duplicate of bug 1585863
WiFi malfunction after suspend & resume stress
--
You received this
*** This bug is a duplicate of bug 1585863 ***
https://bugs.launchpad.net/bugs/1585863
** This bug has been marked a duplicate of bug 1585863
WiFi malfunction after suspend & resume stress
--
You received this bug notification because you are a member of Desktop
Packages, which is
Here is my syslog after resume. Sorry for so long time without reply.
And there are errors in log related to bluez service, as it don't work properly
after suspend either, so I need to use script to restart it automatically on
resume.
** Attachment added: "syslog debug"
@monte
Alright thanks for the test. Can you please add --log-level=debug to
/lib/systemd/system/NetworkManager.service at the end of the ExecStart= line.
So it looks like this
ExecStart=/usr/sbin/NetworkManager --no-daemon --log-level=debug
Then
- restart your machine.
- suspend the machine.
-
Ok, thanks for a hint. Found Intel Management Engine Firmware 8.1 for my
lenovo x230t, installed it on Windows 7, rebooted into Ubuntu, but bug
is still present, same as it was before.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
There is a firmware component for IMEI. If I'm not mistaken the IMEI
firmware is what is responsible for vpro / AMT functionality. According
to this FAQ https://software.intel.com/en-us/articles/intel-vpro-
technology-faq, it is capable of controlling a wireless card even while
in sleep states.
I think the IMEI firmware is a fluke, plus that is not really a solution
for everyone as it is just a windows driver, and not everyone is dual
booting. It's "Intel Management Engine Interface" only reference I can
find to "IMEI" that makes sense.
On a side note, I just deleted my windows
IMEI firmware update for wifi card? Do they even have IMEI, never heard
of it.
--
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/1576747
Title:
Network manager unable to control
So I don't seem to be able to reproduce this any more. I did recently
boot windows on my laptop, and then ran updates. I no longer seem to be
able to reproduce this issue.
One of the important updates was an update to the IMEI firmware on my
machine. Can someone else on this bug please upgrade
@cyphermox
Here's the debug output we worked on today. I removed most everything
from before I suspended the machine. Everything remaining is either
from the suspend or the resume.
The output was achieved by adding --log-level=debug to
/lib/systemd/system/NetworkManager.service at the
I went tested the patches for 1585863, but still saw the issue.
** This bug is no longer a duplicate of bug 1585863
WiFi malfunction after suspend & resume stress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
*** This bug is a duplicate of bug 1585863 ***
https://bugs.launchpad.net/bugs/1585863
This appears to be getting some progress via 1585863, so I'm marking it
as a dupe, even though this one is older.
** This bug has been marked a duplicate of bug 1585863
WiFi malfunction after suspend &
Have this bug on fresh install on Lenovo x230t, Intel 6205 card. Have to
restart nm-applet after every suspend. It seems that restart of network-
manager service produces same bug to applet. I mean doing "sudo service
network-manager restart" brokes nm-applet, so I need to restart it
manually.
--
Happening on an Asus N53 laptop. (AR9285 Wireless network adapter).
Problem is annoying to consider rolling back to previous version. Not an
easy job. Didn't have to do that in many years of upgrading.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I just tried 1.2.0-0ubuntu0.16.04.2, shutdown, started up, suspended
resumed, and still see this issue.
I'm sorry, I haven't had more time to debug this myself.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
can you try to xenial-proposed update and see if it improves things for
you?
--
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/1576747
Title:
Network manager unable to control
@aeaeaeaeaeae, virbr0 is owned/created by libvirt as the default network
for kvm. This issue very likely 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.net/bugs/1576747
is it possible that there is a link to the mysterious "vribr0"?
...it occurs both in the initial bug desription here, and on my laptop too (I
did not configure virbr0 anywhere, but its there since the installation of
16.04, when the wifi problem started)
--
You received this bug notification
Well under further review. Moving wifi zones does not seem to be
necessary, but sleeping for some extended time may be.
I can also confirm that killing and restarting nm-applet is another
less-hammerlike workaround.
--
You received this bug notification because you are a member of Desktop
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
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/1576747
Title:
Network manager unable to control wifi
So it looks as though I'm able to reproduce this by
1. Connecting to wifi access point
2. Suspend
3. Move out of range, but in range of another saved access point.
4. Resume.
My computer automatically connected to the new access point, but does
not show any information to that effect.
I'm not
It's possible. I'll mark this as a dupe once we know more.
--
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/1576747
Title:
Network manager unable to control wifi after suspend
Could be the same like this? https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1516153
--
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/1576747
Title:
Network
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.
24 matches
Mail list logo
