I'm testing Xubuntu 17.04. Sadly, I still get this bug on one of my
laptops. After resume from suspend the nm-applet doesn't show my Wi-Fi
access points, although I'm still connected. killing nm-applet and
rerunning it fixes it. How hard can it be to just patch this little
thing?
My system (inxi -Fz):
System: Host: NB305 Kernel: 4.9.0-15-generic x86_64 (64 bit)
Desktop: Xfce 4.12.3
Distro: Ubuntu Zesty Zapus (development branch)
Machine: Device: laptop System: TOSHIBA product: TOSHIBA NB305 v:
PLL3DU-002002
Mobo: TOSHIBA model: PPVAA v: 1.00
BIOS: TOSHIBA v: 1.00 date: 12/02/2010
Battery BAT1: charge: 20.6 Wh 99.5% condition: 20.7/45.0 Wh (46%)
CPU: Dual core Intel Atom N550 (-HT-MCP-) cache: 512 KB
clock speeds: max: 1500 MHz 1: 1500 MHz 2: 1000 MHz 3: 1000 MHz
4: 1000 MHz
Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics
Controller
Display Server: X.Org 1.18.4 drivers: intel (unloaded:
modesetting,fbdev,vesa)
Resolution: [email protected]
GLX Renderer: Mesa DRI Intel Pineview M
GLX Version: 1.4 Mesa 13.0.4
Audio: Card Intel NM10/ICH7 Family High Definition Audio Controller
driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.9.0-15-generic
Network: Card-1: Qualcomm Atheros AR9285 Wireless Network Adapter
(PCI-Express)
driver: ath9k
IF: wlp7s0 state: up mac: <filter>
Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet
controller
driver: r8169
IF: enp9s0 state: down mac: <filter>
Drives: HDD Total Size: 250.1GB (2.6% used)
ID-1: /dev/sda model: TOSHIBA_MK2555GS size: 250.1GB
Partition: ID-1: / size: 229G used: 6.0G (3%) fs: ext4 dev: /dev/sda1
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 63.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 195 Uptime: 13:14 Memory: 1146.3/1988.2MB
Client: Shell (bash) inxi: 2.3.8
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1060167
Title:
indicator doesn't always work properly after suspend
Status in network-manager-applet package in Ubuntu:
Confirmed
Bug description:
This is not a new bug but I finally decided to report it.
I have a wired and a wireless connection at home. I usually disconnect
the wireless via network-manager while at home. After suspend, both
connections come up. If I use the network-manager indicator to
disconnect, I am unable to-- I can navigate the menus in the indicator
but clicking on things does not work (eg, disconnect from my home
connection, Edit connections, etc). This seems to be related to
suspending for some period of time: ie, it seems to always happen
after suspending at night/resuming in the morning whereas booting the
computer, logging in, suspending, resuming and using the indicator
straight away tends to work fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1060167/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
