Comment 7 for bug 1658016

Revision history for this message
GrzesiekC (grzesiekc) wrote :

FYI - these updates arrived today -

2017-02-23 09:56:29 status installed libnm-util2:amd64 1.2.6-0ubuntu0.16.04.1
2017-02-23 09:56:29 status installed libnm-glib-vpn1:amd64 1.2.6-0ubuntu0.16.04.1
2017-02-23 09:56:29 status installed libnm-glib4:amd64 1.2.6-0ubuntu0.16.04.1
2017-02-23 09:56:29 status installed libnm0:amd64 1.2.6-0ubuntu0.16.04.1
2017-02-23 09:56:40 status installed linux-image-4.8.0-39-generic:amd64 4.8.0-39.42~16.04.1
2017-02-23 09:56:50 status installed linux-image-extra-4.8.0-39-generic:amd64 4.8.0-39.42~16.04.1
2017-02-23 09:56:50 status installed linux-image-generic-hwe-16.04:amd64 4.8.0.39.10
2017-02-23 09:56:50 status installed linux-headers-4.8.0-39:all 4.8.0-39.42~16.04.1
2017-02-23 09:56:50 status installed linux-headers-4.8.0-39-generic:amd64 4.8.0-39.42~16.04.1
2017-02-23 09:56:50 status installed linux-headers-generic-hwe-16.04:amd64 4.8.0.39.10
2017-02-23 09:56:50 status installed linux-generic-hwe-16.04:amd64 4.8.0.39.10
2017-02-23 09:56:51 status installed linux-libc-dev:amd64 4.4.0-64.85
2017-02-23 09:56:51 status installed network-manager:amd64 1.2.6-0ubuntu0.16.04.1

I disabled my workaround "service" and I've suspended the laptop couple of times today.
It works properly now.