On Tue, Jan 29, 2013 at 04:12:43PM +0100, Michael Biebl wrote: > > Hi, > > On 08.03.2011 07:54, Alex Dănilă wrote: > > Among the 81 upgrades from yesterday I can see: > > [UPGRADE] firmware-iwlwifi 0.28 -> 0.29 > > [UPGRADE] firmware-linux 0.28 -> 0.29 > > [UPGRADE] firmware-linux-nonfree 0.28 -> 0.29 > > [UPGRADE] libnm-glib-vpn1 0.8.2-5 -> 0.8.2-6 > > [UPGRADE] libnm-glib2 0.8.2-5 -> 0.8.2-6 > > [UPGRADE] libnm-util1 0.8.2-5 -> 0.8.2-6 > > [UPGRADE] network-manager 0.8.2-5 -> 0.8.2-6 > > > > No network-manager-gnome or anything related to the gui side of NM was > > in the upgrade. Restarting nm-applet doesn't fix this (and didn't fix it > > in other cases. > > Is this problem still reproducible? In that case, please update to the > latest versions from sid and send me a new NM debug log. > > Thanks > Michael
(metoo ;-) It seems to have just resurfaced for me with the upgrade network-manager:amd64 0.9.8.0-5 -> 0.9.8.8-5 Now, on two different machines, suspending leads to network-manager saying that "Networking disabled" and entirely unable to be reenabled via the applet in the tray. The method in #566891: or run service network-manager stop rm /var/lib/NetworkManager/NetworkManager.state service network-manager start worked perfectly. Downgrading back to 0.9.8.0-5 also worked: suspending with that version allows the system to be suspended without problem. Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org