indicator doesn't always work properly after suspend

Bug #1060167 reported by Jamie Strandboge on 2012-10-02
70
This bug affects 15 people
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
High
Unassigned

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.

apport information

tags: added: apport-collected quantal running-unity
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

description: updated
summary: - indicator doesn't work properly after suspend
+ indicator doesn't always work properly after suspend
description: updated

Confirming. There's a good number of duplicates with the same kind of details too. I thought it had been made less worse with the latest bug fixes though.

At least, now I can test with a long suspend cycle tonight.

Changed in network-manager (Ubuntu):
status: New → Confirmed
importance: Undecided → High
affects: network-manager (Ubuntu) → network-manager-applet (Ubuntu)

I'd like to add, that submenus like further networks, VPN etc are also not populated. As a heavy VPN user, one of the first things to do after every suspend is to restart nm-applet by hand. It's one of the biggest annoyances in daily ubuntu usage for me.

James Troup (elmo) wrote :

Still seeing this with raring.

Justyn Butler (justyn) wrote :

I have seen this for a while and still experience it in 13.04.

Killing nm-applet and starting it again fixes the problem, at least until the next time.

Jamie Strandboge (jdstrand) wrote :

I wonder if this is a dupe of bug #1011073. I hope so, cause that has a fix. :)

Doug Gale (doug16k) wrote :

Michael, you can work around that for now by running killall nm-applet with a script in your sleep.d directory:

http://askubuntu.com/questions/92218/how-to-execute-a-command-after-resume-from-suspend#92235

The problem seems to be gone with 16.04 for me. I only have to restart the network manager daemon now and then.

I get the problem on two laptops (16.04 up to date), after a suspend/resume cycle, wifi network list disappears from nm-applet. If I kill and restart nm-applet, wifi network list is displayed again.
On a third laptop, I have to restart network-manager service daemon.

Elad Hen (eladhen2) wrote :

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: 1024x600@60.00hz
           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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers