Re: [Touch-packages] [Bug 1517135] [NEW] ifupdown segfaults
On Tue, Nov 17, 2015 at 10:30 PM, Rustom <rustompm...@gmail.com> wrote: > Public bug reported: > > 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-all-auto.service > ● ifup-wait-all-auto.service - Wait for all "auto" /etc/network/interfaces > to be up for network-online.target >Loaded: loaded (/lib/systemd/system/ifup-wait-all-auto.service; static; > vendor preset: enabled) >Active: active (exited) since Mon 2015-11-16 07:33:22 IST; 27s ago > Docs: man:interfaces(5) >man:ifup(8) > Process: 514 ExecStart=/bin/sh -ec for i in $(ifquery --list --exclude > lo --allow auto); do INTERFACES="$INTERFACES$i "; done; [ -n "$INTERFACES" > ] || exit 0; while ! ifquery --state $INTERFACES >/dev/null; do sleep 1; > done; for i in $INTERFACES; do while [ -e /run/network/ifup-$i.pid ]; do > sleep 0.2; done; done (code=exited, status=0/SUCCESS) > Main PID: 514 (code=exited, status=0/SUCCESS) >CGroup: /system.slice/ifup-wait-all-auto.service > > Nov 16 07:32:53 xxx systemd[1]: Starting Wait for all "auto" > /etc/network/interfaces to be up for network-online.target... > 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/interfaces to be up for network-online.target. > $ 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 > # interfaces(5) file used by ifup(8) and ifdown(8) > auto lo > iface lo inet loopback > > auto enp7s0 > iface enp7s0 inet dhcp > > [Just in case others look here] It looks that commenting out all of /etc/network/interfaces seems to remove this problem [Does it cause new ones?? No idea... Right now net is up (wired) Wireless is down but thats been so since wily upgrade, ie a couple of weeks] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1517135 Title: ifupdown segfaults Status in ifupdown package in Ubuntu: New 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-all-auto.service ● ifup-wait-all-auto.service - Wait for all "auto" /etc/network/interfaces to be up for network-online.target Loaded: loaded (/lib/systemd/system/ifup-wait-all-auto.service; static; vendor preset: enabled) Active: active (exited) since Mon 2015-11-16 07:33:22 IST; 27s ago Docs: man:interfaces(5) man:ifup(8) Process: 514 ExecStart=/bin/sh -ec for i in $(ifquery --list --exclude lo --allow auto); do INTERFACES="$INTERFACES$i "; done; [ -n "$INTERFACES" ] || exit 0; while ! ifquery --state $INTERFACES >/dev/null; do sleep 1; done; for i in $INTERFACES; do while [ -e /run/network/ifup-$i.pid ]; do sleep 0.2; done; done (code=exited, status=0/SUCCESS) Main PID: 514 (code=exited, status=0/SUCCESS) CGroup: /system.slice/ifup-wait-all-auto.service Nov 16 07:32:53 xxx systemd[1]: Starting Wait for all "auto" /etc/network/interfaces to be up for network-online.target... 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/interfaces to be up for network-online.target. $ 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 # 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 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 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 "Qu
[Touch-packages] [Bug 1517135] Re: ifupdown segfaults
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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1517135 Title: ifupdown segfaults Status in ifupdown package in Ubuntu: New 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-all-auto.service ● ifup-wait-all-auto.service - Wait for all "auto" /etc/network/interfaces to be up for network-online.target Loaded: loaded (/lib/systemd/system/ifup-wait-all-auto.service; static; vendor preset: enabled) Active: active (exited) since Mon 2015-11-16 07:33:22 IST; 27s ago Docs: man:interfaces(5) man:ifup(8) Process: 514 ExecStart=/bin/sh -ec for i in $(ifquery --list --exclude lo --allow auto); do INTERFACES="$INTERFACES$i "; done; [ -n "$INTERFACES" ] || exit 0; while ! ifquery --state $INTERFACES >/dev/null; do sleep 1; done; for i in $INTERFACES; do while [ -e /run/network/ifup-$i.pid ]; do sleep 0.2; done; done (code=exited, status=0/SUCCESS) Main PID: 514 (code=exited, status=0/SUCCESS) CGroup: /system.slice/ifup-wait-all-auto.service Nov 16 07:32:53 xxx systemd[1]: Starting Wait for all "auto" /etc/network/interfaces to be up for network-online.target... 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/interfaces to be up for network-online.target. $ 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 # 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 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1517135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1517135] [NEW] ifupdown segfaults
Public bug reported: 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-all-auto.service ● ifup-wait-all-auto.service - Wait for all "auto" /etc/network/interfaces to be up for network-online.target Loaded: loaded (/lib/systemd/system/ifup-wait-all-auto.service; static; vendor preset: enabled) Active: active (exited) since Mon 2015-11-16 07:33:22 IST; 27s ago Docs: man:interfaces(5) man:ifup(8) Process: 514 ExecStart=/bin/sh -ec for i in $(ifquery --list --exclude lo --allow auto); do INTERFACES="$INTERFACES$i "; done; [ -n "$INTERFACES" ] || exit 0; while ! ifquery --state $INTERFACES >/dev/null; do sleep 1; done; for i in $INTERFACES; do while [ -e /run/network/ifup-$i.pid ]; do sleep 0.2; done; done (code=exited, status=0/SUCCESS) Main PID: 514 (code=exited, status=0/SUCCESS) CGroup: /system.slice/ifup-wait-all-auto.service Nov 16 07:32:53 xxx systemd[1]: Starting Wait for all "auto" /etc/network/interfaces to be up for network-online.target... 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/interfaces to be up for network-online.target. $ 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 # 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 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 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) ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1517135 Title: ifupdown segfaults Status in ifupdown package in Ubuntu: New 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-all-auto.service ● ifup-wait-all-auto.service - Wait for all "auto" /etc/network/interfaces to be up for network-online.target Loaded: loaded (/lib/systemd/system/ifup-wait-all-auto.service; static; vendor preset: enabled) Active: active (exited) since Mon 2015-11-16 07:33:22 IST; 27s ago Docs: man:interfaces(5) man:ifup(8) Process: 514 ExecStart=/bin/sh -ec for i in $(ifquery --list --exclude lo --allow auto); do INTERFACES="$INTERFACES$i "; done; [ -n "$INTERFACES" ] || exit 0; while ! ifquery --state $INTERFACES >/dev/null; do sleep 1; done; for i in $INTERFACES; do while [ -e /run/network/ifup-$i.pid ]; do sleep 0.2; done; done (code=exited, status=0/SUCCESS) Main PID: 514 (code=exited, status=0/SUCCESS) CGroup: /system.slice/ifup-wait-all-auto.service Nov 16 07:32:53 xxx systemd[1]: Starting Wait for all "auto" /etc/network/interfaces to be up for network-online.target... 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/interfaces to be up for network-online.target. $ 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 # 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 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 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
[Touch-packages] [Bug 1439109] Re: Network interface not coming up due to missing /etc/rcS.d/*networking
Firstly note that this is more like bug #1432173. Adding this comment here since that is a duplicate of this one I get : $ systemctl status -l ifup-wait-all-auto.service ● ifup-wait-all-auto.service - Wait for all "auto" /etc/network/interfaces to be up for network-online.target Loaded: loaded (/lib/systemd/system/ifup-wait-all-auto.service; static; vendor preset: enabled) Active: active (exited) since Mon 2015-11-16 07:33:22 IST; 27s ago Docs: man:interfaces(5) man:ifup(8) Process: 514 ExecStart=/bin/sh -ecfor i in $(ifquery --list --exclude lo --allow auto); do INTERFACES="$INTERFACES$i "; done;[ -n "$INTERFACES" ] || exit 0;while ! ifquery --state $INTERFACES >/dev/null; do sleep 1; done; for i in $INTERFACES; do while [ -e /run/network/ifup-$i.pid ]; do sleep 0.2; done; done (code=exited, status=0/SUCCESS) Main PID: 514 (code=exited, status=0/SUCCESS) CGroup: /system.slice/ifup-wait-all-auto.service Nov 16 07:32:53 xxx systemd[1]: Starting Wait for all "auto" /etc/network/interfaces to be up for network-online.target... 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/interfaces to be up for network-online.target. $ 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 # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp7s0 iface enp7s0 inet dhcp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1439109 Title: Network interface not coming up due to missing /etc/rcS.d/*networking Status in ifupdown package in Ubuntu: Fix Released Bug description: This used to work fine; now when I start my container there's no network inside. Manually bringing the interface up (ifup eth0 or systemctl start ifup@eth0) works. What information would be useful for you? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-5ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Wed Apr 1 11:35:28 2015 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: System manufacturer System Product Name ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1439109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe
Hello I upgraded vivid to wily yesterday and my networking is broken Not sure but it looked like this bug? Machine with vivid upgraded to wily: network not working $ ip -d route unicast 117.195.32.1 dev ppp0 proto kernel scope link src 117.195.47.122 unicast 169.254.0.0/16 dev ppp0 proto boot scope link metric 1000 [/code] By contrast 14.10 booted from usb and pppoe by hand -- network working $ ip -d route unicast default dev ppp0 proto boot scope link unicast 117.195.32.1 dev ppp0 proto kernel scope link src 117.195.40.157 unicast 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 1 Some evident issues - The absence of default is an obvious problem - The large metric is another problem - eth0 has become ppp0 As suggested earlier in this thread I downloaded pppoe package and installed it by hand (since apt is down with not networking) But its not helped -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1446689 Title: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe Status in network-manager package in Ubuntu: Fix Released Status in network-manager package in Debian: New Bug description: networkmanager switched from using ppp to using pppoe binary for dsl/pppoe connections, I am using pppoe and I can't connect to the Internet unless I install "pppoe" package. From: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10=7955806a02db64b20079267743056d7d9d45af3b "for now, work around this by using the userland pppoe client rather than the kernel code" One way to fix it is to include pppoe Another way is to configure --with-pppoe=/usr/sbin/pppd. I think this is urgent as pppoe/dsl on all vivid machines will be broken out-of-the-box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436330] Re: Network Manager doesn't set metric for local networks any more, causing connection issues
I added a comment in bug 1446689 which should have been better here So copying it here: --- I upgraded vivid to wily yesterday and my networking is broken Not sure but it looked like this bug? Machine with vivid upgraded to wily: network not working $ ip -d route unicast 117.195.32.1 dev ppp0 proto kernel scope link src 117.195.47.122 unicast 169.254.0.0/16 dev ppp0 proto boot scope link metric 1000 [/code] By contrast 14.10 booted from usb and pppoe by hand -- network working $ ip -d route unicast default dev ppp0 proto boot scope link unicast 117.195.32.1 dev ppp0 proto kernel scope link src 117.195.40.157 unicast 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 1 Some evident issues - The absence of default is an obvious problem - The large metric is another problem - eth0 has become ppp0 As suggested earlier in this thread I downloaded pppoe package and installed it by hand (since apt is down with not networking) But its not helped -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1436330 Title: Network Manager doesn't set metric for local networks any more, causing connection issues Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Vivid: Fix Released Bug description: [Impact] NM changed its method of setting routes on systems, and no longer attaches a metric value specific to the type of device being used. These values were used to prioritize connections, so that for example, when connected to both wired and wireless at the same time, wired can be used in priority over wireless without incurring packet loss. Currently, when connected to both wired and wireless are connected to the same subnet, the user may notice connectivity issues since packets are sent in a round-robin fashion over all default routes on the same subnet with the same metric. [Test Case] 1- Connect to a wireless network. 2- Connect to the same network over Ethernet both connections should come up on the same subnet. 3- Make sure there is no packet loss, and that there are specific metric values for each default route, as displayed by 'ip route'. [Regression Potential] Since handling default routes properly involves correcting the behavior for all device types, VPN behavior may change to pick up the default routes in all cases, over a wired connection. It's also possible that a connection pick up the default route when it is not meant to. --- With Vivid, having two connections to the same network subnet is unstable due to missing metrics for local networks. Example: Being connected to 192.168.1.0/24 via both wired and wireless will cause connectivity issues as sent packets hop between the two interfaces. It used to be that this wasn't an issue. I would go between work and home and plug in and my machine would automatically connect to wireless and it would use the lower metric ethernet interface for all communications, while the wlan interface would remain connected but unused. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 25 09:17:27 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-25 (58 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1436330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
