The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: ifupdown (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've recently created a VM running ubuntu server 12.04. I've configured
the networking with a static IP. For some reason the networking says
networking stop/waiting. I then manually input the IP with the netmask
as well at the default gateway and then issue a sudo
/etc/init.d/networking restart
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663352
I still seem to be affected by this for Precise.
** Also affects: ifupdown (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: ifupdown (Ubuntu Precise)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I realize this has been closed, however the fix never made it into
Precise LTS release. Are there plans to backport the fix to the LTS
release and is there some time estimate on that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package ifupdown - 0.7ubuntu1
---
ifupdown (0.7ubuntu1) quantal-proposed; urgency=low
* Resynchronise with Debian experimental. Remaining changes:
(LP: #298488, LP: #663352)
- ifupdown.nw: Use 100 as default route metric unless an explicit metric
** Changed in: ifupdown (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) = Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I had the same bug, but my work around was the following:
Manually take down your listening interfaces.
My interface was eth0 (yours might be wlan0, br0, or something else. ifconfig
usually lists only listening interface).
sudo ifconfig interface name down -- for me this would be written sudo
This is a very bag bug.
It still persists and the last update was made 4 months ago.
Be great to have someone assigned to fix this bug and an update about
workarounds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug also affects us on a Ubuntu 11.04 (64 bit) cluster
Here are some examples:
root@alamba:/client_filesystems/shared/home/install# service networking stop
stop: Unknown instance:
root@alamba:/client_filesystems/shared/home/install# service networking restart
restart: Unknown instance:
On Sat, Feb 12, 2011 at 5:34 PM, Steve Langasek
steve.langa...@canonical.com wrote:
Reassigning to the ifupdown package. This should be supported by
running 'service networking restart', but doesn't because
/etc/init/networking.conf doesn't contain a stop command.
Just for the archive, the
Reassigning to the ifupdown package. This should be supported by
running 'service networking restart', but doesn't because
/etc/init/networking.conf doesn't contain a stop command.
** Package changed: upstart (Ubuntu) = ifupdown (Ubuntu)
** Changed in: ifupdown (Ubuntu)
Status: Triaged =
Bug 644175 is related to this issue also. It seems that if network-
manager package is purged, wicd can not be used with wireless.
--
No way to stop/start networking without network management
https://bugs.launchpad.net/bugs/663352
You received this bug notification because you are a member of
Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!
** Changed in: upstart (Ubuntu)
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
** This bug is no longer a duplicate of bug 207869
automated removal of duplicate songs would be great
--
No way to stop/start networking without network management
https://bugs.launchpad.net/bugs/663352
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I meant, without network-manager
--
No way to stop/start networking without network management
https://bugs.launchpad.net/bugs/663352
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 207869 ***
https://bugs.launchpad.net/bugs/207869
** Package changed: gnome-nettool (Ubuntu) = ubuntu
--
No way to stop/start networking without network management
https://bugs.launchpad.net/bugs/663352
You received this bug notification because you are a
*** This bug is a duplicate of bug 207869 ***
https://bugs.launchpad.net/bugs/207869
** This bug has been marked a duplicate of bug 207869
automated removal of duplicate songs would be great
* You can subscribe to bug 207869 by following this link:
*** This bug is a duplicate of bug 207869 ***
https://bugs.launchpad.net/bugs/207869
Are you sure?
bug #207869, is all about removal of duplicate songs, and package
rhythmbox; whereas this is ubuntu networking? Seems entirely different
things to me.
What's your justification concluding this
20 matches
Mail list logo
