As per the attached screenshots, after returning/resuming from suspend state to active state, i find that WiFi option behavior on top bar changes , as i can disconnect from WiFi but cannot join any other Access Points.
Please advise.
---
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: immu 2236 F.... pulseaudio
/dev/snd/controlC1: immu 2236 F.... pulseaudio
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=d847e58d-c6ed-4676-85e4-99daf40bc620
InstallationDate: Installed on 2017-03-19 (15 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Alienware Alienware 14
Package: linux (not installed)
ProcFB:
0 nouveaufb
1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=ed7ad53d-0e58-4f28-bdee-74cdce0c320d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.8.0-45-generic N/A
linux-backports-modules-4.8.0-45-generic N/A
linux-firmware 1.161.1
Tags: yakkety
Uname: Linux 4.8.0-45-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 04/23/2014
dmi.bios.vendor: Alienware
dmi.bios.version: A09
dmi.board.name: 07MJ2Y
dmi.board.vendor: Alienware
dmi.board.version: A01
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A09
dmi.modalias: dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
dmi.product.name: Alienware 14
dmi.product.version: A09
dmi.sys.vendor: Alienware
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1679743
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.