Suspending Lubuntu 16.04.3 results in network manager stops working

[Mark]

Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the network manager stops working or better it behaves weird. I noticed 4 behaviors in different occasions:

1) Enable networking and enable wifi are toggled but the connection I used before suspending is not shown (others are).

2) Enable networking and enable wifi are toggled but no Wi-Fi connections are displayed.

3) The icon changes to loading but it gets stuck, sometimes it just stays like that until I restart the network manager or sometimes it unstucks and connects, but instead of showing the "internet bars" for Wi-Fi it shows the icon as when you connect to a wired connection.

3)The network manager menu is grey and you can't click anything (no connections are shown).

The only way I have is either to restart nm-applet or restart Lubuntu.

I have seen this behavior for maybe 3 days, therefore I am assuming one package was updated and the update messes up with the suspending system.

The Network Manager I have is 1.2.6-0ubuntu0.16.04.1 and Xfce Power Manager is 1.4.4-4ubuntu2.

Can someone investigate?
Has anyone else experienced this?
If more info are needed I will try to do my best :)

Update: seems it the error I mentioned in my last message was reported on XFCE: https://bugzilla.xfce.org/show_bug.cgi?id=12317 don't know if it is any useful.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1719731

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.

[Mark (mago90)]

The bug is Confirmed

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/

[Mark (mago90)]

Hello sorry for the late reply.

I am not familiar with playing around the upstream kernel, this is my only machine and I cannot break anything :/

I have another kernerl version: Linux 4.4.0-93-generic I tried and it has the same behavior.

Today I notice that Power Manager shows a GDBUS.Error, so maybe that's the problem?

I attached a screenshot where you can see the complete error:
https://s1.postimg.org/2p5omsk99b/Screenshot_from_2017-10-05_16-38-41.png

As you can see at the bottom the icon displayed is the one used for wired networks however I am connected to a wifi network.

Hope it helps.

[Mark (mago90)]

Also is there any chance that the error is linked to https://ubuntuforums.org/showthread.php?t=2371537 where I reported that I cannot connect to a specific wifi (I can on Windows 10 though) and a specific router?

[Mark (mago90)]

I managed to fix the bug in XFCE power manager (following a tutorial online, just a string to edit), however the issue still persists.

On the internet I found out that I am not the only one to report this issue:

https://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade it is from april 2016...

#1589401 is also what I experience (wifi connections disappear) https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401

No idea which packet is the problem but it still persists :/