NetworkManager forgets that »Enable Networking« had been asserted

Bug #690667 reported by Detlef Lechner
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fedora
Invalid
Undecided
Unassigned
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

[Lucid] NetworkManagerApplet 0.8 after restart forgets that »Enable Networking« had been asserted although it was asserted when shutting down. The same applies when hibernating and thawing.
I can correct that by NetworkManager Applet > right-click > Enable Networking and '~$ sudo dhclient eth0'.
I call this a regression.
I expect that NetworkManager Applet does not forget this setting.
This bug is almost identical to https://bugzilla.redhat.com/show_bug.cgi?id=644990

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager-gnome 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
Uname: Linux 2.6.32-26-generic i686
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Wed Dec 15 15:19:20 2010
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.26 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.178.1 dev eth0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RfKill:

SourcePackage: network-manager-applet
WpaSupplicantLog:

Revision history for this message
Detlef Lechner (detlef-lechner) wrote :
Thomas Hood (jdthood)
summary: - [Lucid] NetworkManagerApplet 0.8 after restart forgets that »Enable
- Networking« had been asserted.
+ NetworkManager forgets that »Enable Networking« had been asserted
affects: network-manager-applet (Ubuntu) → network-manager (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Thomas Hood (jdthood) wrote :

@Detlef: Are you still having this problem in Ubuntu 12.04?

Changed in network-manager (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

This bug was marked Incomplete some time ago and was supposed to autoclose after 90 days. I'm going to close it manually due to no activity (and likely the issue has gone away/been fixed).

Changed in network-manager (Ubuntu):
status: Incomplete → Invalid
Changed in fedora:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.