It's still happening in 14.04 LTS (Trusty) on my Dell Inspiron mini 1012
laptop, usually after a fairly long use session. But it always starts
working again after either another suspend/resume cycle or restarting
Network Manager.
--
You received this bug notification because you are a member of
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: network-manager (Ubuntu Lucid)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I realised this bug after upgrading to saucy. In raring networking and
suspend worked well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/524454
Title:
Networking is disabled on boot (usually after
This bug still exitsts in lucid-current:
uname -a
Linux unicron 2.6.32-42-generic #95-Ubuntu SMP Wed Jul 25 15:56:09 UTC 2012
x86_64 GNU/Linux
lsb_release -r
Release:10.04
aptitude show network-manager |grep Version
Version: 0.8-0ubuntu3.3
This bug hit me when hibernating the machine
Did this ever make it into an SRU for lucid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/524454
Title:
Networking is disabled on boot (usually after suspend/hibernate)
To manage notifications
getting the ball rolling for lucid SRU (that's a pretty hefty patch at
26KB!)
** Patch added: debdiff for lucid
https://bugs.launchpad.net/ubuntu/lucid/+source/network-manager/+bug/524454/+attachment/2494956/+files/lp524454-lucid.debdiff
--
You received this bug notification because you are
resetting status and assignment for SRU process
** Changed in: network-manager (Ubuntu Lucid)
Status: Fix Committed = Confirmed
** Changed in: network-manager (Ubuntu Lucid)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
--
You received this bug notification because
Hey!
Bedankt voor je mail! Ik ben er even tussenuit geknepen naar een lekker
warm land! Ik beantwoord je mail na mijn vakantie (11 oktober).
Groetjes!
Ruben
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed that the package in Mathieu's PPA fixes the issue for me on
Lucid. I'm happy to verify a SRU.
(I have an office of machines affected by this, although they don't
correctly suspend/hibernate anyway, due to NFS-mounted /home)
--
You received this bug notification because you are a
I just had this problem on my Kubuntu 10.10
I tried to run with live cds: Ubuntu 10.10 and Helix 3.1. These live cds
also didn't detect my LAN card. Problem solved after I unplugged the
power bar, then I plugged it again, turned on the computer. The LAN card
finally detected.
--
You received
papukaija, no. What I wrote there is so that we could get the necessary
testing to figure out what is wrong. If a later version of the package
(such as the one in Maverick) works, then I know which patches to apply.
My PPA (linked above) contains a premade package for Lucid that contains
the
Isn't this bug fixed yet in 10.04? It's a very serious bug when you have
many computers that need to be connected to a wifi automatically, with
no user intervention. I might try the hard workaround of removing all
write permissions on that file, but I don't like that sort of dirty
hacks to make it
@Lars: Lucid users need to use a PPA, more information in comment 91.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/524454
Title:
Networking is disabled on boot (usually after suspend/hibernate)
I've had this problem too.
Here's a workaround: http://www.ubuntugeek.com/how-to-fix-network-
manager-disabled-problem-in-ubuntu-10-04-lucid.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/524454
[TEMPORARY SOLUTION for some cases]
Although in the associated Gnome bug report, this is reported to have
been committed to the 0.8.1 update for network-manager, people using the
stock variety of Ubuntu have the daunting task of putting up with an
Ubuntu system which shows Network Manager as
Adrien, after upgrading if the file is set to false, you would still
need to click Enable in nm-applet or edit the file, but normally you
should only have to do it once. Note that if you used Chris' workaround
with chattr then you may want to revert that as well.
--
Networking is disabled on
Updating to NetworkManager 0.8.1 (i.e. updating from Lucid to Maverick)
has not fix the bug on my computer. I had to manually change the config
files as described here. So even as a backport, it may not be enough.
--
Networking is disabled on boot (usually after suspend/hibernate)
@Adrien: Did you try rebooting before suspending/hibernating as network-
manager doesn't (I think) restart automatically on upgrade?
@Mathieu: Thank you for working on this bug.
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You
Chris, you probably shouldn't do this because it will likely cause you
further issues when disabling wireless or networking later.
I'm building packages now for testing, they will be available in
https://edge.launchpad.net/~mathieu-tl/+archive/nm as soon as they are
done building with the package
I've marked this Fix Committed since there are now two ways to get a fix
for this issue, as outlined above. It still means you need to go through
using PPAs for now. After some testing of the packages we could look
into whether this is too involved a fix to make it into a SRU or not, or
wether
** Changed in: network-manager (Ubuntu Lucid)
Status: Confirmed = In Progress
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Oops. I commented on a duplicate instead of this one. Sorry.
It's a bit drastic perhaps but you can fix this this problem permanently
by making your /var/lib/NetworkManager/NetworkManager.state file look
like so:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
And then
Thumbs up to the solution given by Nexos in comment #88 - I added the
the two PPA lines given in the link, ran update manager and installed
all updates, and since then the networking has stayed enabled between
restarts for the first time in a long time.
Running Xubuntu 10.04 and been experiencing
This bug was reported in February... and almost reaching October I just
summed to the 92 affected people being the 93rd.
I am using Kubuntu Lucid Lynx fully updated.
I changed both /var/lib/NetworkManager/NetworkManager.state and
/etc/NetworkManager/nm-system-settings.conf as described.
FWIW, I found a PPA to get newer versions of network-manager on Lucid:
cf. https://launchpad.net/~network-
manager/+archive/trunk?field.series_filter=lucid (NetworkManager daily
trunk builds for ubuntu):
It seems to work for me, but YMMV (you shouldn't probably do this if you
are not able to fix
Mathieu,
I don't reboot it before/during/after Suspend. When it goes to sleep
(Suspend) it's working, and when it wakes from Suspend it's disabled.
Just like that. :) There are no problems waking back up - everything
works fine, except networking. That's why I wanted to mention it here;
no one
I don't know if this is new info or not, but on mine I've noticed that
it only does this when coming back on after Suspend, but *only when
there's a USB connection plugged in*. USB Key, external harddrive,
camera - all of them will cause it. I want to say it's only when the
item is unplugged
Sheryl, this might be what causes your system to fail to suspend
properly (assuming it does and you then reboot the system completely,
which is how this bug is usually triggered). I don't think it has any
link in why NM starts disabled though.
--
Networking is disabled on boot (usually after
I don't really think Low is an appropriate priority level. I would rate it as
High since there's no obvious workaround (disabling/re-enabling networking via
the applet is simple enough, but does not work consistently).
So basically, for a standard user, the only remedy is closing any application
Nexos, I stuck with Ubuntu 9.10 for reasons such as this.
Like Microsoft, Ubuntu is introducing new features/bugs before they nail
down all the previous bugs. Ubuntu can say 'Fix Released' all they
want, but if it doesn't appear/install from Update Manger -- it isn't
fixed. Now that I can't
I haven't been using Suspend or Wake-on-LAN, and I am using a wired
connection.
Nevertheless, I found it helpful to remove Network Manager 8.0 and use WICD
instead.
I find it very frustrating bumping into such basic problems with new
releases (I'm thinking of various gnome-applet issues with
** Changed in: network-manager
Importance: Unknown = High
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Tags added: metabug
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks markofealing the solution is worked for me!
service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start
And sorry for my last comment, suspend not worked with 9.10 too...
Here is the official answer from Point Of View, regarding my PC
(Mobii
FYI people, might be helpful for some:
I've seem to have traced my problem to a (faulty?) wireless on-off switch on my
Dell D830. It seems to be very sensitive to the position. When I would switch
my wireless on/off with a hardware switch I would get 10 hw on-off signals in
/var/log.
What I
Same problem: Networking disabled (after hibernation) and the enable greyed out.
I'll try the solution today.
Anyway there is a lot bug around the new power management...
I dont have suspend to ram, and hibernation does not work correctly.
I dont get why Karmic just worked out of the box.
--
Possibly related issue with Ubuntu 10.4 ...
Using Network Manager or WICD - even with Wake-on-LAN disabled - wired NIC is
not powered off after shutdown request - unlike in Ubuntu 8.04 (and even
Windows Vista).
Workaround is to sudo ifconfig eth[n] down prior to sudo shutdown -h now.
On
I can confirm this bug on 64bit lucid with all updates up until now.
Luckily, erasing the NetworkManager.state file did fix the problem and
it hasn't occurred since.
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug
** Changed in: network-manager (Ubuntu Lucid)
Status: Confirmed = Fix Committed
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Right, thanks for that work, we'll just need to build an updated package
and propose an SRU, I'll see what can be done to that (so keeping myself
assigned for the issue in Lucid).
** Changed in: network-manager (Ubuntu Lucid)
Status: Fix Committed = Confirmed
** Changed in:
** Description changed:
Binary package hint: network-manager
My networking is disabled every time I boot. To correct, I must right-
click on Network Manager applet and choose Enable Networking, after
which my wireless networks become available and I can get online.
I'm using Lucid
Mathieu: I'm not sure but the patches are directly downloaded from the
upstream's git (see this bug's comments 59-61) and then uploaded to LP.
Therefore the file/directory names might need some adjustments in the
patches.
--
Networking is disabled on boot (usually after suspend/hibernate)
POSSIBLE WORKAROUND
I have this on an Asus EEE running Kubuntu.
It's annoying because I can't fix it from the GUI.
I put the attached text in a file called /etc/pm/sleep.d/90_netkick.sh and did
chmod +x on it so it will run automatically on wakeup.
This seems to have fixed it here.
**
The fact that this happens on a failed suspend/resume indicated it's not
NetworkManager's fault, but that the issue resides in the scripts run to
suspend networking on S3/S4 states.
I'm assigning myself for the tasks for both Lucid and Maverick, there
needs to be some work done to see if the
papukaija, do the patches you mentioned (which are the same as I found
but against the 0.8.1 tree), apply cleanly on top of 0.8-0ubuntu3?
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are
i think you can try that without reboot
service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification
This bug got to me since karmic...I'm on lucid and got bitten again...
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Also affects: network-manager (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu Maverick)
Importance: Low
Status: Confirmed
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
Started up laptop and network manager simply states Networking
disabled. Will not connect to any network.
Unknown cause
** Changed in: network-manager (Ubuntu Lucid)
Assignee: (unassigned) = Liam Farrell (liamfez)
--
Networking is disabled on boot (usually after suspend/hibernate)
Started up laptop and network manager simply states Networking
disabled. There is no option to enable networking and I am unable to
get it working again. Started yesterday 26/07/2010. Using HP Compaq
nx6110.
--
Networking is disabled on boot (usually after suspend/hibernate)
There is no option to enable networking - then it's not this bug.
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug is affecting 60 people which are probably all Lucid users.
** Description changed:
Binary package hint: network-manager
My networking is disabled every time I boot. To correct, I must right-
click on Network Manager applet and choose Enable Networking, after
which my wireless
The upstream has released NM 0.8.1
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Description changed:
Binary package hint: network-manager
My networking is disabled every time I boot. To correct, I must right-
click on Network Manager applet and choose Enable Networking, after
which my wireless networks become available and I can get online.
I'm using Lucid
** Changed in: network-manager (Debian)
Status: New = Fix Released
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
4.5 is even more annoying. There's no right click options.
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This is the first patch from the upstream.
** Patch added: First patch
http://launchpadlibrarian.net/51412174/ee3ece9dac985034c5c1f81a6769b40fd7856579.patch
** Tags added: patch
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You
Here's the second patch from the upstream to fix this bug. The urls to
these patches are:
1st:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/patch/?id=ee3ece9dac985034c5c1f81a6769b40fd7856579
2nd:
Just to add that both patches are needed to fix this bug (the second
option is to wait for a SRU with network-manager 0.8.1 ).
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of
@papukaija: The relevant commits are:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=NM_0_8_1id=ee3ece9dac985034c5c1f81a6769b40fd7856579
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=NM_0_8_1id=30374453b4b12953ed5a9b7bec4b81fe263ae9db
--
Networking is
I had the same problem in kubuntu lucid lynx, and it's persistent.
No matter what fix I try (rm'ing, editing the state file with it up or
down, rebooting, etc.), wireless stays off.
Wired works just fine.
Can't scan wifi networks.
Can't use wicd to connect.
Can't even dhclient wlan0 to do it.
Hi folks,
it looks like that a fix of this bug has already been released. I really want
to get rid of this issue so does anybody know when this fix will be committed
to Ubuntu or how bypass the Ubuntu update process and install directly the new
version of network-manager ?
--
Networking is
@Valentin: The upstream (Gnome) hasn't yet released network-manager
0.8.1. According to
http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.8/ the latest
release is 0.8.0.999. It seems that upstream has some delay with their
updates as the v.0.8.1 is shceduled for May 2010 (see
I only use wireless on an infrequent basis. I last used it about 1 month
ago. It worked then, but not any more. WirelessEnabled=false is in
/var/lib/NetworkManager/NetworkManager.state and despite changing the
file as root toWirelessEnabled=true , upon the next boot, it has
reverted back to
Hi electhor
You hit a different bug. Please search for an existing bug matching your
problem, or open a new one.
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs,
I have had this problem recently on two Dell laptops, both running Kubuntu
10.04.
In both cases, the computers locked up while suspending to RAM with a SD card
in. So it may be a different or related bug.
Oddly, in one of the laptops, the problem disappeared (networking came
back immediately)
I'm using kubuntu 10.04 on my son's laptop. This is the first and only real bug
I've found in kubuntu 10.04, congratulations on that. However, this is a very
annoying bug. Debian has upgraded it to important. I don't agree with the low
rating here.
For a user, this is a very annoying bug. Can
The SRU is Stable Release Update (a tested update). It isn't yet
available as the fixed network-manager (0.8.1) isn't yet released. You
can follow the release of network-manger at
http://live.gnome.org/NetworkManager/ReleaseProcess
--
Networking is disabled on boot (usually after
hi folks, got the same issue on an acer aspire one. on a regular boot
the networking is fine, but not after suspend. Well, suspend does not
really work right now. But this is another issue I will try to tackle
down...
--
Networking is disabled on boot (usually after suspend/hibernate)
I can confirm this problem, at least partially. I'll test some more.
I did a fresh install of Lucid on my new PC. First, networking worked
fine. Then I tried suspending, but resume did not work so I performed a
cold reboot. After that, networking did not come up.
The fix proposed, removing
I recently tried to suspend my system. There seems to be a problem with
unsuspending, so I hard-resetted my system. After the reboot the nm-
applet started even tough I never use it and therefore disabled in
AutoStart-Programs. In this state, all programs assumed offline-mode
(firefox, pidgin,
This happened to me yesterday, and it took until today to find the fix
in this bug. It ought to be first in the bugfix list, imo.47
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a
Updating the tracker and adding the debian's one to its own.
** Bug watch added: GNOME Bug Tracker #620806
https://bugzilla.gnome.org/show_bug.cgi?id=620806
** Changed in: network-manager
Status: New = Unknown
** Changed in: network-manager
Remote watch: Debian Bug tracker #566891 =
Why not release the fix (network-manager 0.8.1) throught SRU?
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: network-manager
Status: Unknown = Fix Released
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: network-manager (Debian)
Status: Unknown = New
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
None of solutions posted above helped in my case. Network Management is
still disabled.
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
According to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566891
this has been fixed upstream. I guess we just need a backport for
Lucid.
** Tags added: fixed-upstream
** Tags added: backport-needed
--
Networking is disabled on boot (usually after suspend/hibernate)
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Low
--
Networking is disabled on boot
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: Debian Bug tracker #566891
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566891
** Also affects: network-manager via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566891
Importance: Unknown
Status: Unknown
--
Networking is disabled on boot
Added the regression tag since this hasn't happened in karmic or older.
** Tags added: regression-release
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which
When enabled manually from nm-applet, the networking is enabled correctly:
** (nm-applet:1523): DEBUG: old state indicates that this was not a disconnect 0
** (nm-applet:1523): DEBUG: old state indicates that this was not a disconnect 1
** (nm-applet:1523): DEBUG: foo_client_state_changed_cb
**
Changed the bug's title as even the upstream report is named 'Network
Management disabled after suspend to ram '.
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: network-manager
Status: Unknown = New
--
Networking is disabled on boot (usually after suspend/hibernate)
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Same problem here with Kubuntu 10.04. The computer was in standby. It
didn't resume from it, instead black screen was shown. Then I forced
reboot and since then KNetworkManager showed Unmanaged/Network
Management disabled. After changing
/var/lib/NetworkManager/NetworkManager.state contents this
Happens to me too after I upgraded to Kubuntu Lucid. Whenever I have a problem
with standby, shutdown, or resume (about 1 in 4 times, alas), after I power-off
and reboot I have no network and KDE's knetworkmanager shows Network Manager
disabled. Every time I looked
Same problem for me: This fixed it for me. Thanks Jan Tarpila
ifupdown managed=false to true in
/etc/NetworkManager/nm-system-settings.conf
service network-manager start
Dell E4300.
--
Networking is disabled on boot
https://bugs.launchpad.net/bugs/524454
You received this bug notification
Same thing happened to me: suspend crashed for no apparent reason and
then had no network, just the grayed out message Network management
disabled. Following https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/524454/comments/35 solved the problem, but as
I just got the same issue, but it wasn't related to suspend or sleep, I just
hard-shutdowned it.
Only thing I made different related to network was to plug the laptop on cable
ethernet instead of using wireless... But it worked fine.
I hard shutdowned it by pure laziness as everything was
This ticket is starting to contain different bugs, let's focus on the first bug
reported by David Siegel:
Network manager is disabled on boot:
* when left clicking on it shows:Networking disabled
* when right clicking on it, Enable Networking is not ticked
* the file
My AMD64 Ubuntu 10.04 Lucid desktop system had exactely that problem.
The first time change of the NetworkingEnabled setting in the .state
file survived a couple of shutdowns and suspends, but then the problem
reappeared. I changed it a second time some days ago and it has been
working fine since
Same problem here on a Dell C640 running Kubuntu 10.04, had to do
following to fix:
service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start
Looks like QC on 10.04LTS has been very poor!
--
Networking is disabled on boot
I added my report on 5 May over at duplicate bug 71. Today I had the
problem again, however with these differences: 1) This time it occurred
after a successful sleep/reawaken (computer was running on battery and
auto-suspended to RAM). 2) NetworkingEnabled In NetworkManager.state was
still
Running Lucid Kubuntu here. Fully up to date and I can report that it
is still occurring for me as well. All I've come up with is that if I
attempt to hibernate or suspend to ram (both fail in Lucid both worked
in Karmic, this install is a clean install as I wanted to re-partition.
)
If I
I sometimes experience this bug whenever my system is suspended and
crashes when it tries to unsuspend.
--
Networking is disabled on boot
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 10.04
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
IpRoute:
192.168.5.0/24 dev wlan0 proto kernel scope link src 192.168.5.102
I had the very same problem described here after updating to 10.04.
lshw -C network was reporting disabled and all enabling option grayed out on
the networking applet.
NetworkManager.state was also set to false. Changing these did nothing.
However after setting:
ifupdown managed=false to true
Having the same problem here - just updated Dell Latitude and found no
networking.
Editing NetworkManager.state as above and rebooting gives wired networking but
wireless is always reset to false
--
Networking is disabled on boot
https://bugs.launchpad.net/bugs/524454
You received this bug
Wanted to report that after a clean install (formatting the drive etc..) it
runs just fine.
It therefore seems like it's a problem with the upgrade from karmic to lucid
that skips / keeps some files.
Good luck :)
--
Networking is disabled on boot
https://bugs.launchpad.net/bugs/524454
You
Mm, no, I'm affected and I did a clean install. It's only happened
about every third startup so far, though.
--
Networking is disabled on boot
https://bugs.launchpad.net/bugs/524454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
1 - 100 of 121 matches
Mail list logo
