ifupdown segfaults
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Note that I added this as comment on bug #1439109
It is actually more similar to #1432173 which is a duplicate of above
I get :
$ systemctl status -l ifup-wait-
● ifup-wait-
Loaded: loaded (/lib/systemd/
Active: active (exited) since Mon 2015-11-16 07:33:22 IST; 27s ago
Docs: man:interfaces(5)
Process: 514 ExecStart=/bin/sh -ec for i in $(ifquery --list --exclude lo --allow auto); do INTERFACES=
Main PID: 514 (code=exited, status=0/SUCCESS)
CGroup: /system.
Nov 16 07:32:53 xxx systemd[1]: Starting Wait for all "auto" /etc/network/
Nov 16 07:32:54 xxx sh[514]: Segmentation fault
Nov 16 07:33:22 xxx systemd[1]: Started Wait for all "auto" /etc/network/
$ sudo vi /etc/resolv.conf
I tried what looked like solutions offered here:
1.
$ sudo update-rc.d networking remove
$ sudo update-rc.d networking defaults
[I am assuming that r.cd is a misspelling of rc.d]
No change
2. Reinstalled ifupdown
I believe I used to see two segfaults. Now I see one
Ubuntu wily
ifupdown 0.7.54ubuntu1
systemd 225-1ubuntu9
$ cat /etc/network/
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto enp7s0
iface enp7s0 inet dhcp
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ifupdown 0.7.54ubuntu1
ProcVersionSign
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov 17 22:26:04 2015
InstallationDate: Installed on 2012-12-22 (1060 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: ifupdown
UpgradeStatus: No upgrade log present (probably fresh install)
Would just like to point out that
UpgradeStatus: No upgrade log present (probably fresh install)
is wrong.
One line above is
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
which is right -- thats when this machine was installed
And in my view this is clearly an upgrade problem because with 15.10 booted from live USB there is no such issue