Hello, Trusty reached "End of Standard Support" a while ago and so I am
marking this as "Won't Fix". Thank you.
** Changed in: ifupdown (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
There doesn't seem to be any action needed against mailman, so I'm
marking that task Invalid and accepting an SRU task for Trusty.
** Changed in: mailman (Ubuntu)
Status: Confirmed => Invalid
** Also affects: ifupdown (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also aff
Hi!
I've tested your patch, and it's still using ifconfig in network-interface.conf
it should use ip instead.
what's in network-interface.conf:
ifconfig lo 127.0.0.1 up || true
what should be in network-interface.conf:
ip link set dev lo up || true
--
You received this bug notifi
I have backported the fix to trusty in my ppa.
Unfortunately I was not able to reproduce this issue (although my tests
are ongoing). With that being said I would really appreciate anyone that
is affected by this issue to give it a try and let me know whether the
backport fixed that for them.
The
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Feel free to retweet this
https://twitter.com/An0Theral/status/675127147082686464
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
To manage
Please port this fix to trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
To manage notifications about this bug go to:
https://bugs.la
yeah. but net-tools is deprecated, so this really should be fixed in all
releases. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
To man
Guys this fix really needs to be in trusty too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
To manage notifications about this bug go to
All right, just found a simple workaround for trusty. Just install the
"net-tools" package and lo will be brought up correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown
This bug also prevents the mounting of NFS shares on boot, because
rpcbind is unable to start without the lo interface.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mailman (Ubuntu)
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/1375821
Title:
if
Hello,
we are a hosting provider in Switzerland and are running some Ubuntu
14.04. instances. This bug hits some of our customers, as essentially
services on localhost are unavailable.
This pretty much renders *any* service useless that accesses another
service on the same box (i.e. breaks mailma
Will this be updated in trusty as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
To manage notifications about this bug go to:
https:
This bug was fixed in the package ifupdown - 0.7.48.1ubuntu5
---
ifupdown (0.7.48.1ubuntu5) utopic; urgency=medium
* Fix broken loopback handling due to incorrect patching of the Debian
source. (LP: #1375821)
-- Stephane GraberWed, 01 Oct 2014 11:43:43 -0400
** Changed in:
Fix uploaded to utopic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
To manage notifications about this bug go to:
https://bugs.launchpad
I found an upstream bugreport detailing the actual issue in ifupdown source on
debian's bugtracker here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757291
** Bug watch added: Debian Bug tracker #757291
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757291
--
You received this bug n
I forgot to include, other interfaces (eth*) are configured as expected
upon boot:
root@:~# ip addr show
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft
18 matches
Mail list logo
