[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
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 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 in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: Triaged Status in network-manager package in Ubuntu: Confirmed Bug description: 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 execute `sudo wpa_cli scan` manually to make it work again. WORKAROUND: (http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade) SYSTEM INFO: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release
I tested 1.2.6-0ubuntu0.16.04.1 from xenial-proposed and it works for me with no problems and it also seems to fix #1585863 ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1645698 Title: [SRU] Upgrade network-manager to latest point release Status in OEM Priority Project: Triaged Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Yakkety: Fix Released Bug description: [Impact] This SRU would try to have the latest well-tested upstream point release (1.2.6) of 1.2.x land in Xenial, which is the successor of the current 1.2.2 version, fixing quite some bugs that's suitable to land in the stable branch. https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2 [Test Case] After installing the updated version, users should be able to avoid some mem leaks in some cases and have generally improved DNS related experiences. Also, as this is a general point release update, cases described in https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used for smoke testing. [Regression Potential] This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite complete. [Other Info] The first attempt at SRUing this to xenial was for 1.2.4 but it failed verification. This second attempt matches yakkety with 1.2.6. Parallel building was enabled in xenial to keep the diff between xenial and yakkety minimal since they are basically in sync now. Parallel building was enabled in the yakkety package in May 2016 so it's been working fine for a while. needed by: lp #1647283 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
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 systemd[1]: Reached target Sleep. Jan 19 00:20:34 vaclav-ntb systemd[1]: Starting Suspend... Jan 19 00:20:34 vaclav-ntb systemd-sleep[6171]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory Jan 19 00:20:34 vaclav-ntb systemd-sleep[6173]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255. Jan 19 00:20:34 vaclav-ntb systemd-sleep[6171]: Suspending system... [snip] Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]: [1484781657.4625] manager: waking up... Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]: [1484781657.4626] device (wlan0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] ... Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]: [1484781657.8564] manager: NetworkManager state is now CONNECTED_LOCAL Jan 19 00:20:57 vaclav-ntb wpa_supplicant[1606]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none Jan 19 00:20:57 vaclav-ntb wpa_supplicant[1606]: dbus: Failed to construct signal Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]: [1484781657.9052] device (wlan0): supplicant interface state: starting -> ready Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]: [1484781657.9053] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Jan 19 00:20:57 vaclav-ntb kernel: [138425.339676] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready -- 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 in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 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 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390709] Re: Wifi doesn't reconnect after waking from sleep
There are so many open bugs on network-manager, wifi and resume that
it's difficult to find the right one to comment on. Anyway, trying e.g.
this one. Can the people having this problem comment on whether there is
Docker installed on their system?
I am specifically asking this question because a colleague of mine
claimed not have any problems with WiFi in Ubuntu but since he installed
Docker, the WiFi became so unusable that he was forced to use wired
connection. On my system network manager never worked good (being it
14.04 or 16.04) but I cannot comment on Docker as it was installed from
the very beginning.
--
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/1390709
Title:
Wifi doesn't reconnect after waking from sleep
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Upgraded from 14.04 to 14.10. Before Wifi would reconnect after waking
up from sleep mode. After Update reconnect fails with wlan0: aborting
authentication with 1c:c6:3c:95:e7:74 by local choice (Reason:
3=DEAUTH_LEAVING).
I worked around this by killing wpa_supplicant with a script in
/etc/pm/sleep.d
#!/bin/sh
case "$1" in
thaw|resume)
{ killall wpa_supplicant ; } 2>/dev/null
;;
*)
;;
esac
exit $?
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu28
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Nov 8 11:43:15 2014
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-04-19 (567 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
IpRoute:
default via 192.168.138.251 dev wlan0 proto static
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
192.168.138.0/24 dev wlan0 proto kernel scope link src 192.168.138.143
metric 9
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to utopic on 2014-11-07 (0 days ago)
nmcli-nm:
RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.8.8connected enabled enabled
enabledenabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1390709/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1594715] Re: wifi does not work roughly half of the times
Is there any plan to update network manager in Xenial to 1.2.6. In the changelog at https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=1.2.6 I can see * Fixed a bug that caused devices to stay unmanaged after resume from sleep. Not sure if it helps but maybe worth trying. -- 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/1594715 Title: wifi does not work roughly half of the times Status in network-manager package in Ubuntu: Confirmed Bug description: After booting, roughly half of the times, wifi doesn't work: The nm- applet menu looks as if no wifi would exist. Instead, it lists the a non-existing cable network device called "Marvell 88W8897 [AVASTAR] 802.11ac Wireless". (The network manager seems to be trying to connect to that device, but fails.) After doing /etc/init.d/network-manager restart the wifi device is always recognized properly, so I guess it's something happening in the wrong order during booting. (Alternatively, unloading and reloading the kernel module mwifiex_pcie also always helps.) The problem did not exist in ubuntu 15.10. Some more information: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 When the bug is there: $ nmcli d show wlp1s0 GENERAL.DEVICE: wlp1s0 GENERAL.TYPE: ethernet GENERAL.HWADDR: 50:1A:C5:E8:2F:09 GENERAL.MTU:1500 GENERAL.STATE: 70 (connecting (getting IP configuration)) GENERAL.CONNECTION: Kabelnetzwerkverbindung 2 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/7 WIRED-PROPERTIES.CARRIER: on $ ifconfig -a loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:3380 errors:0 dropped:0 overruns:0 frame:0 TX packets:3380 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:251184 (251.1 KB) TX bytes:251184 (251.1 KB) wlp1s0Link encap:Ethernet HWaddr 50:1a:c5:e8:2f:09 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) After restarting the network manager: immi@flunder:~$ nmcli d show wlp1s0 GENERAL.DEVICE: wlp1s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 50:1A:C5:E8:2F:09 GENERAL.MTU:0 GENERAL.STATE: 100 (connected) GENERAL.CONNECTION: virginmedia4709476 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/8 IP4.ADDRESS[1]: 192.168.0.3/24 IP4.GATEWAY:192.168.0.1 IP4.ROUTE[1]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000 IP4.DNS[1]: 194.168.4.100 IP4.DNS[2]: 194.168.8.100 IP6.ADDRESS[1]: fe80::521a:c5ff:fee8:2f09/64 IP6.GATEWAY: (...) wlp1s0Link encap:Ethernet HWaddr 50:1a:c5:e8:2f:09 inet6 addr: fe80::521a:c5ff:fee8:2f09/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:304 (304.0 B) TX bytes:680 (680.0 B) $ dmesg (...) [7.850180] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready [7.850263] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready [7.859773] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready [7.869408] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready (...) I'm happy to try to fix the bug myself, but I could need some help: I don't know how to change booting order or something like that. I could also temporarily insert some commands into /etc/init.d /network-manager printing some status information about the wifi, but I don't know how to get such status information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 21 09:35:14 2016 IfupdownConfig: # interfaces(5) file
[Desktop-packages] [Bug 1566222] Re: [xenial] USB camera MIC: no input or high pitch until pavucontrol is opened
** Package changed: skype (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1566222 Title: [xenial] USB camera MIC: no input or high pitch until pavucontrol is opened Status in pulseaudio package in Ubuntu: Confirmed Bug description: Logitech Webcam C270 connected to USB 2.0 port: no mic input or high pitch voice appears randomly during voice calls(skype test call for example). Seems? to be fixed by opening pavucontrol from Skype -> Settings -> Devices. lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 skype: 4.3.0.37-0ubuntu0.12.04.1 pulseaudio: 1:8.0-0ubuntu3 This also happens on ubuntu 15.10 with the same skype package version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1566222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
