** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after
Sure thing. But 2 more points that maake me believe it's user space bug:
1. nmcli dev shows correct information (I believe under the hood it uses the
same syscalls as nm-applet)
2. I have this bug on a wide range of kernels from 4.4 to 4.15 We completely
the same behaviour. On 2 laptops with
It can not prove if it is a linux kernel bug or not even when you can
recover it from the UI.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot
Here is how nm-applet looks after restart (killall nm-applet && nm-
applet &)
** Attachment added: "Here is how nm-applet looks after restart"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401/+attachment/5053390/+files/Screenshot%20from%202018-02-11%2019-50-55.png
--
I've filed separate bug
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
It's not seems as linux bug because there is how I'm fixing it:
killall nm-applet && nm-applet &
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
Yuriy, please file a separate bug. Run `ubuntu-bug linux`.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after
I still have this bug on Dell XPS13 9360 with ath10k and Lenovo T530 with
iwlwifi
Both with:
ii network-manager 1.2.6-0ubuntu0.16.04.2
amd64network management framework (daemon and
userspace tools)
ii network-manager-gnome
I am still having this issue on Lubuntu 16.04.3, could it be possibly
related to another bug I opened: #1719731?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719731
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
What's the output of `nmcli d` when the problem happens?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling
I'm posting this here merely because another bug page on launchpad says that
that thread,is actually a duplicate of this one, even though it seems it's not.
I'm on Peppermint, which is still ubuntu under the hood, all else works fine,
except from time to time, with no explanation, regardless of
https://packages.debian.org/stretch/network-manager has contained those
fixes.
Could someone help to test
https://launchpad.net/~happyaron/+archive/ubuntu/nm-oem/+packages if it
can fix this bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Using ath9k driver: no issues
My netbook running iwlwifi driver still has this bug. It's in Ubuntu,
because I'm running Debian Stretch just fine there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
Is this still an issue with 1.2.6-0ubuntu0.16.04.3 in 16.04? I see that
Ken applied the patch I identified in
https://bugzilla.gnome.org/show_bug.cgi?id=767317 to fix
https://bugs.launchpad.net/ubuntu/+source/network-manager-
applet/+bug/1641889, which references a different upstream bug.
--
You
I have encountered the same issue, I'm sure there is nothing related to the
network-manager. This package is working properly and I can connect to any wifi
as I with.
However i thing it's related with the wifi indicator:)
Generally this issue recovers after I relaunch the Xorg.
--
You
Does anyone encounter the same issue on Ubuntu 17.04?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling
I see something similar in 16.10.
Weird enough, issuing an
iwlist wlan0 scan
seems to be enough to get the available connections again
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I also had the issue on a fresh Ubuntu 16.04, the applet not working
properly after resuming from suspend.
But I may have something to help here. A few days ago, I didn't had the
issue on a previous install, so I tried the two changes I made on that
one suspend-related.
First, I enabled
** Changed in: network-manager
Status: Unknown => Confirmed
** Changed in: network-manager
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
When resuming from suspend and hitting this issue, the networkmanager
logs show:
NetworkManager[773]: [1488932351.8820] manager: wake requested
(sleeping: yes enabled: yes)
NetworkManager[773]: [1488932351.8821] manager: waking up...
NetworkManager[773]: [1488932351.8823] device
I have only seen this when resuming from suspend.
For the upstream developers, we need to add to
/etc/NetworkManager/NetworkManager.conf:
[logging]
level=TRACE
Then restart, and when the issue is observed, capture the networkmanager logs
with:
journalctl -u NetworkManager -b
and put into:
I have observed this issue on both Broadcom and Atheros (ath10k)
wireless cards, and even reproduced it on the current stable 4.9.13
kernel, thus it would appear to be a higher-level issue. Running 'sudo
iw dev wlan0 scan' works around it every time.
** Changed in: network-manager (Ubuntu)
After I gave up and shifted to a wired connection, I noticed that I'd get
disconnected periodically but then it would reconnect successfully. It
seems some drivers manage to reconnect and other drivers don't.
So there may be _two_ bugs:
1) A bug that results in occasional loss of connection.
2)
Network Manager is the culprit, not anyone's routers. This is evident by
the fact that earlier versions of Ubuntu didn't experience this issue,
this issue happens regardless of which router we're connecting to, it
happens regardless of which location we are at, and the underlying issue
is that
It definitely could be. Personally, I think many of the issues mentioned
above are completely unrelated to Network Manager. Those cases should be
excluded from a bug report. Therefore I suggest that everyone who's
having problems check their beacon interval settings.
--
You received this bug
The applet started functioning properly after 16.04.2. If the problem
was Intel drivers, it solved it. Intel Wireless 3160 + Ubuntu MATE with
kernel 4.8.0-39-generic. Confirm this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Yes, this bug is not related to beacon intervals on the router.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after
Why do that? This is a bug with Network Manager, not our routers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after
All of you who are affected by this bug, try the following: Change the
beacon interval on your router to the lowest value possible.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Any change after 16.04.2? New kernel 4.8...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
Status
Please try network-manager-1.2.6 from xenial-proposed, if you have
16.04. For me it seems to fix this bug. But when you will test don't
forget to turn off all self-made scripts to see if it really does the
job.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I too have this bug on a Lenovo W520 with Ubuntu 16.04 kernel 4.4.0-62-generic
The only solution that has worked is restarting the network-manager service,
however if I attach an USB WiFi adapter based on rtl8187, the icon becomes
normal and I can choose a network for that adapter. The Intel
I can't confirm. unfortunately this doesn't do the trick for me.
What's different now is that the WiFi is already conected on the login screen
with the arrow icon. As soon as I login, it's the WiFi icon. When I suspend and
return I have arrows again.
--
You received this bug notification
Can anybody confirm this:
In 'network connections', if the setting "All users may connect to this
network" are set for the used wi-fi connection, nm-applet will no longer
crash when returning from suspend?
Any idea why?
--
You received this bug notification because you are a member of Ubuntu
** Bug watch added: GNOME Bug Tracker #767317
https://bugzilla.gnome.org/show_bug.cgi?id=767317
** Changed in: network-manager
Importance: Undecided => Unknown
** Changed in: network-manager
Status: Confirmed => Unknown
** Changed in: network-manager
Remote watch: None => GNOME
iwlist didn't work on my system. Nothing did. I finally gave up and
bought another interface.
On Thu, Jan 19, 2017 at 2:02 PM, Jeremy LaCroix <1589...@bugs.launchpad.net>
wrote:
> Again, you shouldn't need to restart network manager or the applet. You
> can simply rescan your wireless networks
Again, you shouldn't need to restart network manager or the applet. You
can simply rescan your wireless networks manually.
sudo iwlist scan
The applet should be doing this as soon as the machine wakes up, but
it's clearly not.
--
You received this bug notification because you are a member of
I should add that after resume my WiFi connection is still working and I
can browse the Internet fine. The problem is the applet displays the
wrong icon and no APs are listed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
When my laptop was on Ubuntu I just needed the service to restart
network manager. When switching to Xubuntu that service no longer
works. Even after restarting network manager the icon is still showing
Ethernet and no WiFi networks are listed. This bug only happens after
very long suspends.
** Changed in: network-manager
Importance: Medium => Undecided
** Changed in: network-manager
Remote watch: GNOME Bug Tracker #767317 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Same thing. The list of wifis refreshes only after nm-applet is
restarted.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks
Same issue on arch.
As a workaround you can create this systemd unit :
[Unit]
Description=System resume actions
After=suspend.target
[Service]
Environment=XAUTHORITY=/home/user_name/.Xauthority
Environment=DISPLAY=:0.0
Type=simple
ExecStart=/usr/bin/bash -c "killall nm-applet && sudo -E -u
First of all, you just cost me a few hours trying to get my network
connection back after the instructions for reinstall of network-manager
upon failed WICD, themselves, failed.
Second, if the default network manager system that comes with distributions
has a bug, it's not "whining" to rather
@anders-frisk650
Well done! Now we're getting somewhere.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after
@fourdollars, I installed your ppa in #120 above. Unfortunately I could
not detect any significant change compared to the latest released
versions. Following are my notes from my tests. The test PC has a fresh
Ubuntu 16.04 install with all updates. The wifi interface name is wlp1s0
and there is no
network-manager 1.2.2-0ubuntu0.16.04.3 and network-manager-gnome
1.2.0-0ubuntu0.16.04.4 still had this bug.
Only nm-applet restart help
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Testing Linux Mint MATE 18.1 BETA and having this bug. It was also
present on Linux Mint MATE 18. Just installed WICD and it doesn't have
this problem and it shows the access point around me after resuming from
suspend.
--
You received this bug notification because you are a member of Ubuntu
@ghuisman:
I tried WICD for a few of weeks. My experiences were the same as yours.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi
Hi,
I made some proposed fix for this issue in ppa:fourdollars/lp1589401 for xenial.
Please help to check if it works or not.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
mm i am experiencing problems also since upgrading to 16.10. I m
oppening a new bug Bug #1641154. I have the feeling that the device
does connect to the network but the kernel crashes when establishing the
connection this is the dmesg output when coming back from suspend
wlan0: authenticate
@Peter S (peter-sevemark):
First of all I agree on your comment #114: We need to test suggested
scenarios so we can converge to a solution or approach to tackle the
issue.
So I have installed WICD (conform issue #109) and removed the default network
manager.
summary of my issue: in most cases
@Sander Jonkers (jonkers) I'm not really very skilled but just a regular
user that does whatever i can to get this bug fixed.
Can anybody help, and please join at bugzilla.
https://bugzilla.gnome.org/show_bug.cgi?id=767317
--
You received this bug notification because you are a member of Ubuntu
@Hansen ... I did that, did a reboot, did a suspend/resume (arrows
appeared), and the logging is 1997 lines long. Can you advice what to do
with that logging?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
On Bugzilla one ask's:
---
It would be useful to have also NM logs. Would you please set:
[logging]
level=TRACE
in /etc/NetworkManager/NetworkManager.conf, restart the NM service,
reproduce the issue and then attach the journal log ('journalctl -u
NetworkManager -b')? Thanks!
--
If people keep whining about bugs in network-manager, without even
trying WICD (or the like) for a couple of weeks, this thread is
meaningless!
I'm still not sure that the problems I experience are completely
unrelated to network-manager. I seem to have a more stable connection
with WICD, so far.
Shouldn't i close the bugzilla report already, it's seems dead anyway.
Will it change anything, making the bug unassigned?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I'm eager to hear other members of this thread sharing their experience
with WICD (see #109 for installation intructions). Especially those with
a Intel wifi chip. If the the same connectivity issues remain in WICD, I
assume we could abandon the idea that these issues are to be derived to
I spoke too soon still exists in Yakkety.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
Status
@peter-sevemark Yep, same exact problems with WICD means it's the
wireless driver/kernel. Probably why no one is looking at this bug
seriously.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I'm starting to doubt that network-manager is the root of all this mess.
Have any of you tried using WICD instead (an alternative network
manager)? I seem to have the same connectivity issues there. And just as
with network-manager, they appear at random.
Here's an instruction:
Could all you guys please click "This bug affects me" so we can get some
action on solving this on the new report.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
After performing some more tests:
The triggers for the network-manager showing the arrow icon and no WiFi
networks are:
- Suspend mode (suspend/wake up)
- Hardware wireless button (turn WiFi off/an)
- Wireless network in network-manager GUI (deactivate/activate)
- Network in network-manager GUI
Dear all,
I have discovered something that may not have been reported in here so far:
After a fresh boot, when you suspend the machine, there will be arrows after
waking up.
If you do "service network-manager restart" once, you'll get the WiFi icon
back. From now on you can suspend as many times
With my recent update to Yakkety I no longer seem to be experiencing
this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi
As requested by Mathieu Trudel-Lapierre (cyphermox) I have filed my own
bug report in bug #1636282
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
No, nothing i know of is happening to solve this bug.
The bug report on bugzilla seems to wait on this bug report and nobody are
working in it here.
I have tried to contact a couple of people to get some attention to it but to
no avail.
If anybody know of any way to draw attention to this bug
Is Ubuntu working on this bug? It's not the first release this problem
happens. I have the same problem with a RTL8723be.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
@Joakim: Ah, OK, I now understand. Thanks.
However: I have the beam symbol, but it's now grey (like: no signal), and no
Wifi networks visible. :-(
After a "sudo systemctl restart network-manager.service" the beam signal
shortly becomes an empty pizza slice, then the Up-Down-arrow, and greyed
Sander: You don't need to have to file wifi-resume.service already..
nano will create it for you.. Just read what I wrote on askubuntu and do
that ;) it will work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
FWIW2:
I only have Wifi. No fixed ethernet. Maybe that is part of the problem?
Maybe the indicator assumes the first ethernet is always fixed ethernet,
and puts that symbol on it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I have the same problem with a fresh install of Ubuntu 16.10 / yakkety
on my HP Stream 13.
The workaround "sudo systemctl restart network-manager.service" works
for me: it removes the up-down-arrow, and gives back the beam symbol
showing the available wifi networks.
I have no file
I'm using a Dell Lattitude E6230 with Intel wireless card (Centrino
Advanced-N 6205 [Taylor Peak]). On Ubuntu 16.04 this bug affected (wifi
icon changed to two arrows, network manager could not be controlled,
have to be relaunched). But since upgrading to Ubuntu 16.10 for the past
week I have not
I'm using a Toshiba laptop with a Qualcomm Atheros AR8152 network card
and the bug affects me too. It also happens if the connection is lost
abruptly or WiFi is turned off
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I'm running Ubuntu 14.04.5 for now. It's unaffected by this. The .5
release added the support I needed. None of the workarounds for 16.04
worked in this hardware.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Sorry, spoke a bit to soon. My workaround above doesn't actually work
when I do LightDM+Unity, only when I do text boot (i.e. when I've done
systemctl set-default multi-user.target (instead of graphical.target)),
and start i3 with startx.
(Actually, when running Unity, the script *does* execute
I'm seeing the same problem on a Thinkpad T450s with "Intel Corporation
Wireless 7265 (rev 59)" (iwlwifi) on Ubuntu 16.04.1, all packages up-to-
date as of time of writing:
Kernel 4.4.0-43-generic
network-manager 1.2.2-0ubuntu0.16.04.3
network-manager-gnome 1.2.0-0ubuntu0.16.04.4
This is a
Not stand it anymore this gnome network managers.
Buggy, Buggy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after
I've also upgraded to 16.10 and see the same issues. There's also other
networking issues on my laptops that wasn't present in 15.10. Seems that
Wi-Fi and networking was fundamentally broken in 16.04 and now carries
over to 16.10
--
You received this bug notification because you are a member of
Just made a fresh installation of Ubuntu 16.04 and then upgraded to
16.10 through APT. I'm running kernel 4.8 and see no improvement
whatsoever in 16.10.
This bug is not fixed in any way, shape or form.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Well for what it's worth the bug seems to be fixed in 16.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after
'sudo iw dev wlan0 scan' (or in my case wlp13s0 instead of wlan0)
doesn't work for me. Here's the output:
command failed: Device or resource busy (-16)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
I have been running a manual script ten times a day for half a year to live
with this bug.
The bug I reported upstream are either waiting for us here on launchpad or the
bug's not being taken serious. Are there anyone reading this that knows
anything about how we can get this fixed, I don't
Centrino Advanced-N 6205 here too. I have different issues from time to
time, I'd rather say I have every one described on this page. But they
happen without some strict manner, the only thing for sure is that after
every suspend I have to restart nm-applet to bring it back to normal
work.
--
I have an X1 Carbon Gen1 with Intel Centrino Advanced-N 6205 [Taylor Peak] (rev
96).
'sudo iw dev wlan0 scan' doesn't help. I usually have a blank wireless icon (no
bars) with no networks listed, occasionally the up-down arrow wired connector
icon. Need to go to System Settings > Network to see
I have Intel Wireless 3165 (rev 81)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
Status in
Running 'sudo iw dev wlan0 scan' does work around the issue for me. I
have this issue on two computers, they have the following wireless cards
from Intel:
Intel Wireless 7260 (rev bb)
Intel Wireless 7260 (rev 73)
Just to be clear, should I be creating a new bug for each of these two
cards? Would
If you have issues with wireless not coming up after suspend, please run
'sudo iw dev wlan0 scan', and see if the applet then changes (it may
take a few seconds) to wireless and displays the list of APs. It does
not seem to me like any other workarounds are likely to work for
everyone.
If you
I still have the same issue, even after enabling static IP.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after
Thanks for the input about 16.10, Christian. I was considering an
upgrade to get rid of the problem, but now I will think twice before
doing so.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Christian: Sounds like maybe it could be a problem with network-manager
+ lightdm, as gnome use GDM it makes sense there is no issue there.
In the meantime, you could always use this script:
http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
after-16-04-upgrade/761220#761220
I am having the same problem in Ubuntu 16.10 Beta 1. The main reason I
went for it so early was hoping these issues were resolved. They are
not. There's always problems when I come home after work and resume my
laptop. I'm either stuck on the now non existing work network or I do
not have any
Peter S: Just tried, same result.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
Status in
Have any of you tried using static IP adressess for your system?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after
The arrows are not gone. I just made a clean install and update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after
Are there any progress on this bug, i still have to runs scripts several
time a day to get the applet working.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
The arrows are gone for me too now (after reinstalling, I think), but
there are still connectivity issues. Either one has to wait a minute or
two for a wifi connection after bott up or put it in suspend mode (close
the lid) to establish a wifi connection.
--
You received this bug notification
Likewise, I've seen it before, but not for a while now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling
I found out, that after installing the latest updates and REBOOTED the
bug is gone. No more arrows, and connection establishes directly.
For me the bug can be closed as "soled"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Peter: Thanks for trying. I run the same kernel etc. etc. but it keeps
happening for me.
Well, for me, it's not a big deal, since I just use my script from here:
http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade/761220#761220
but for new users, it can be
It keeps working after reboot and suspend. I'm not sure exactly which
kernel version I used to run before re-installing, but this one is
called 4.4.0-34-generic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager
1 - 100 of 172 matches
Mail list logo
