[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I would not trust ecryptfs anymore. https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840 Use the time to migrate your data. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1511840] Re: cannot apport-bug from IPv6-only network
I no longer receive the "Network is unreachable" message from the command-line tool, so that part is fixed. I was unable to test the complete workflow of reporting a bug because login.launchpad.net does not have records therefore the browser window that was opened died in its tracks. I realize that's yet another infrastructure bug. Thanks for moving this forward. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1511840 Title: cannot apport-bug from IPv6-only network Status in apport package in Ubuntu: Fix Released Bug description: Attempting to report a bug using apport-bug from a machine without a legacy IP address fails: # apport-bug foopackage ... *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. *** Error: Network problem Cannot connect to crash database, please check your Internet connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1511840/+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 1707966] [NEW] Inconsistent sample name used for x11-bell
Public bug reported: A startup script is being patched to load module-x11-bell with a given sample name: debian/patches/0006-load-module-x11-bell.patch:+@PACTL_BINARY@ load- module module-x11-bell "display=$DISPLAY" "sample=bell.ogg" > /dev/null yet in the default example: src/daemon/default.pa.in:#load-sample-lazy x11-bell /usr/share/sounds/freedesktop/stereo/bell.oga As this is an example, no such sample gets loaded, but the patched script does not use either of the desired sample name or the matching file extension. I recommend updating the script to load the module using "sample=x11-bell" to be consistent with upstream and the fact that the sample name is not specific to a given format. This was discovered while trying to figure out how to set the bell sound on XFCE. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kjotte 1626 F pulseaudio CurrentDesktop: XFCE Date: Tue Aug 1 12:43:03 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2011-12-09 (2061 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2016-05-31 (427 days ago) dmi.bios.date: 10/12/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET73WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET73WW(1.43):bd10/12/2016:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1707966 Title: Inconsistent sample name used for x11-bell Status in pulseaudio package in Ubuntu: New Bug description: A startup script is being patched to load module-x11-bell with a given sample name: debian/patches/0006-load-module-x11-bell.patch:+@PACTL_BINARY@ load-module module-x11-bell "display=$DISPLAY" "sample=bell.ogg" > /dev/null yet in the default example: src/daemon/default.pa.in:#load-sample-lazy x11-bell /usr/share/sounds/freedesktop/stereo/bell.oga As this is an example, no such sample gets loaded, but the patched script does not use either of the desired sample name or the matching file extension. I recommend updating the script to load the module using "sample=x11-bell" to be consistent with upstream and the fact that the sample name is not specific to a given format. This was discovered while trying to figure out how to set the bell sound on XFCE. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kjotte 1626 F pulseaudio CurrentDesktop: XFCE Date: Tue Aug 1 12:43:03 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2011-12-09 (2061 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2016-05-31 (427 days ago) dmi.bios.date: 10/12/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET73WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET73WW(1.43):bd10/12/2016:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707966/+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 1610479] Re: interface-order needs definitions for systemd predictable names
Is there anything else you need from me to be able to merge this patch? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1610479 Title: interface-order needs definitions for systemd predictable names Status in resolvconf package in Ubuntu: Confirmed Bug description: Another release, another round of interface name changes. This time systemd has gotten into the fray to make things even more interesting. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ As such, IPv4 resolvers are now being preferred over IPv6 again on these new interface names. kjotte@flounder:~$ grep '' /run/resolvconf/interface/ens3.* /run/resolvconf/interface/ens3.dhclient:search nivex.lan. /run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30 /run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net. /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10 /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 5 19:53:25 2016 InstallationDate: Installed on 2016-08-04 (1 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+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 1547702] Re: iputils-ping does not support IPv6 in ping command
So it looks like this was merged into 16.10 (3:20150815-2ubuntu3 vs 3:20121221-4ubuntu1.1 per packages.ubuntu.com). Should this be closed out as Fix Released? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1547702 Title: iputils-ping does not support IPv6 in ping command Status in iputils package in Ubuntu: Confirmed Status in iputils package in Debian: Fix Released Bug description: The iputils package included in Ubuntu is from 2012. There have been several releases since then and should be updated. Specifically, the iputils-ping package needs to be updated to support the unified ping binary. Specific commit: https://github.com/iputils/iputils/commit/ebad35fee3de851b809c7b72ccc654a72b6af61d Last release: https://github.com/iputils/iputils/releases/tag/s20150815 Given 16.04 is a LTS, it would be extremely bad for Ubuntu to miss this updated. Competitively, Fedora 24 will be including it as well. https://fedoraproject.org//wiki/Changes/PingIpv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1547702/+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 1656054] Re: Unable to validate GoDaddy signed certs
Thank you for the swift and thorough reply. It is appreciated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1656054
Title:
Unable to validate GoDaddy signed certs
Status in ca-certificates package in Ubuntu:
Invalid
Bug description:
I am updating a script to use a new version of the US National Weather
Service API and am running into a certificate problem.
kjotte@daedalus:/tmp$ curl https://api-v1.weather.gov/
curl: (60) server certificate verification failed. CAfile:
/etc/ssl/certs/ca-certificates.crt CRLfile: none
...
I have run update-ca-certificates to ensure the master bundle is
current. This URL is accessible in Firefox with correct validation.
Workaround:
kjotte@daedalus:/tmp$ curl -sO
https://certs.godaddy.com/repository/gd_bundle-g2.crt
kjotte@daedalus:/tmp$ curl --cacert ./gd_bundle-g2.crt
https://api-v1.weather.gov/
{"status":"OK"}
Please update the system certificate store so I don't have to load the
GoDaddy cert bundle on every machine I'll be running my scripts on.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jan 12 12:43:45 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-12-09 (1861 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: ca-certificates
UpgradeStatus: Upgraded to xenial on 2016-05-31 (226 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1656054/+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 1656054] Re: Unable to validate GoDaddy signed certs
kjotte@daedalus:~$ openssl s_client -CApath /etc/ssl/certs -connect
api-v1.weather.gov:443
CONNECTED(0003)
depth=0 OU = Domain Control Validated, CN = nws.noaa.gov
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 OU = Domain Control Validated, CN = nws.noaa.gov
verify error:num=21:unable to verify the first certificate
verify return:1
---
Certificate chain
0 s:/OU=Domain Control Validated/CN=nws.noaa.gov
i:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com,
Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate
Authority - G2
---
Server certificate
...
subject=/OU=Domain Control Validated/CN=nws.noaa.gov
issuer=/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com,
Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate
Authority - G2
---
No client certificate CA names sent
---
SSL handshake has read 2604 bytes and written 647 bytes
---
Does the i: line in that output mean the server is sending that intermediate
cert or that it is expected? I want to make absolutely certain I've got this
right before I go telling the federal government they've messed up.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1656054
Title:
Unable to validate GoDaddy signed certs
Status in ca-certificates package in Ubuntu:
Invalid
Bug description:
I am updating a script to use a new version of the US National Weather
Service API and am running into a certificate problem.
kjotte@daedalus:/tmp$ curl https://api-v1.weather.gov/
curl: (60) server certificate verification failed. CAfile:
/etc/ssl/certs/ca-certificates.crt CRLfile: none
...
I have run update-ca-certificates to ensure the master bundle is
current. This URL is accessible in Firefox with correct validation.
Workaround:
kjotte@daedalus:/tmp$ curl -sO
https://certs.godaddy.com/repository/gd_bundle-g2.crt
kjotte@daedalus:/tmp$ curl --cacert ./gd_bundle-g2.crt
https://api-v1.weather.gov/
{"status":"OK"}
Please update the system certificate store so I don't have to load the
GoDaddy cert bundle on every machine I'll be running my scripts on.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jan 12 12:43:45 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-12-09 (1861 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: ca-certificates
UpgradeStatus: Upgraded to xenial on 2016-05-31 (226 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1656054/+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 1656054] [NEW] Unable to validate GoDaddy signed certs
Public bug reported:
I am updating a script to use a new version of the US National Weather
Service API and am running into a certificate problem.
kjotte@daedalus:/tmp$ curl https://api-v1.weather.gov/
curl: (60) server certificate verification failed. CAfile:
/etc/ssl/certs/ca-certificates.crt CRLfile: none
...
I have run update-ca-certificates to ensure the master bundle is
current. This URL is accessible in Firefox with correct validation.
Workaround:
kjotte@daedalus:/tmp$ curl -sO
https://certs.godaddy.com/repository/gd_bundle-g2.crt
kjotte@daedalus:/tmp$ curl --cacert ./gd_bundle-g2.crt
https://api-v1.weather.gov/
{"status":"OK"}
Please update the system certificate store so I don't have to load the
GoDaddy cert bundle on every machine I'll be running my scripts on.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jan 12 12:43:45 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-12-09 (1861 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: ca-certificates
UpgradeStatus: Upgraded to xenial on 2016-05-31 (226 days ago)
** Affects: ca-certificates (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1656054
Title:
Unable to validate GoDaddy signed certs
Status in ca-certificates package in Ubuntu:
New
Bug description:
I am updating a script to use a new version of the US National Weather
Service API and am running into a certificate problem.
kjotte@daedalus:/tmp$ curl https://api-v1.weather.gov/
curl: (60) server certificate verification failed. CAfile:
/etc/ssl/certs/ca-certificates.crt CRLfile: none
...
I have run update-ca-certificates to ensure the master bundle is
current. This URL is accessible in Firefox with correct validation.
Workaround:
kjotte@daedalus:/tmp$ curl -sO
https://certs.godaddy.com/repository/gd_bundle-g2.crt
kjotte@daedalus:/tmp$ curl --cacert ./gd_bundle-g2.crt
https://api-v1.weather.gov/
{"status":"OK"}
Please update the system certificate store so I don't have to load the
GoDaddy cert bundle on every machine I'll be running my scripts on.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jan 12 12:43:45 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-12-09 (1861 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: ca-certificates
UpgradeStatus: Upgraded to xenial on 2016-05-31 (226 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1656054/+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 1643063] Re: unable to ifup vlan based interface with systemd persistent naming
This may need to be filed against the vlan package as /etc/network/if-pre-up.d/vlan is owned by same. It was my understanding, however, that vconfig was deprecated in favor of 'ip link' as used in my workaround. -- 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/1643063 Title: unable to ifup vlan based interface with systemd persistent naming Status in ifupdown package in Ubuntu: New Bug description: root@atlantis:/etc# ifup enp2s0.121 Cannot find device "enp2s0.121" Failed to bring up enp2s0.121. Workaround: Add pre-up /sbin/ip link add link enp2s0 name enp2s0.121 type vlan id 121 to /etc/network/interfaces declaration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1643063/+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 1643063] [NEW] unable to ifup vlan based interface with systemd persistent naming
Public bug reported: root@atlantis:/etc# ifup enp2s0.121 Cannot find device "enp2s0.121" Failed to bring up enp2s0.121. Workaround: Add pre-up /sbin/ip link add link enp2s0 name enp2s0.121 type vlan id 121 to /etc/network/interfaces declaration. ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- 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/1643063 Title: unable to ifup vlan based interface with systemd persistent naming Status in ifupdown package in Ubuntu: New Bug description: root@atlantis:/etc# ifup enp2s0.121 Cannot find device "enp2s0.121" Failed to bring up enp2s0.121. Workaround: Add pre-up /sbin/ip link add link enp2s0 name enp2s0.121 type vlan id 121 to /etc/network/interfaces declaration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1643063/+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 1002454] Re: IPv4 DNS preferred over IPv6 ones
There was a response to the upstream bug indicating the method I used in my patch would be insufficient. I don't have the skill to whip it into shape to get it accepted, sadly. If someone who is a developer could look at the bug in the GNOME bugtracker and rework the patch a bit they will probably take it. -- 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/1002454 Title: IPv4 DNS preferred over IPv6 ones Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The Network Manager always prefers IPv4 DNS over IPv6 ones. The issue occurs both when DNSs are statically configured and when they're acquired via DHCPv4/DHCPv6. Network Manager puts IPv4 DNSs before IPv6 ones in the /var/run/nm- dns-dnsmasq.conf so Dnsmasq resolves names using IPv4 DNSs before using IPv6 ones. If I disable Dnsmasq, DNS servers are put in the wrong way in /etc/resolv.conf file. The system shoud prefer IPv6 DNSs in any case. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon May 21 21:05:59 2012 ExecutablePath: /usr/bin/nm-connection-editor IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.0.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.217 metric 1 192.168.36.0/24 dev vmnet1 proto kernel scope link src 192.168.36.1 192.168.70.0/24 dev vmnet8 proto kernel scope link src 192.168.70.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: RfKill: SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-05-02 (18 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH eth0-Static 0bcb2b9f-a2c0-46f9-a6b1-59f66e383264 802-3-ethernet1337627018 lun 21 mag 2012 21:03:38 CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1002454/+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 1610479] Re: interface-order needs definitions for systemd predictable names
I'm curious why this has been given such an abysmally low priority (wishlist) when a similar bug (#1094345) was fixed quickly a few years ago and a patch has been submitted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1610479 Title: interface-order needs definitions for systemd predictable names Status in resolvconf package in Ubuntu: Confirmed Bug description: Another release, another round of interface name changes. This time systemd has gotten into the fray to make things even more interesting. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ As such, IPv4 resolvers are now being preferred over IPv6 again on these new interface names. kjotte@flounder:~$ grep '' /run/resolvconf/interface/ens3.* /run/resolvconf/interface/ens3.dhclient:search nivex.lan. /run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30 /run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net. /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10 /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 5 19:53:25 2016 InstallationDate: Installed on 2016-08-04 (1 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+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 1610479] Re: interface-order needs definitions for systemd predictable names
Previous patch did not fully account for PCI bus description. New patch attached. ** Patch removed: "interface-order.patch" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+attachment/4727594/+files/interface-order.patch ** Patch added: "interface-order.patch" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+attachment/4727750/+files/interface-order.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1610479 Title: interface-order needs definitions for systemd predictable names Status in resolvconf package in Ubuntu: Confirmed Bug description: Another release, another round of interface name changes. This time systemd has gotten into the fray to make things even more interesting. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ As such, IPv4 resolvers are now being preferred over IPv6 again on these new interface names. kjotte@flounder:~$ grep '' /run/resolvconf/interface/ens3.* /run/resolvconf/interface/ens3.dhclient:search nivex.lan. /run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30 /run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net. /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10 /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 5 19:53:25 2016 InstallationDate: Installed on 2016-08-04 (1 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+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 1610479] Re: interface-order needs definitions for systemd predictable names
Pattern matching and I have never been fast friends, but this appears to work in my one little test case. ** Patch added: "interface-order.patch" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+attachment/4727594/+files/interface-order.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1610479 Title: interface-order needs definitions for systemd predictable names Status in resolvconf package in Ubuntu: Confirmed Bug description: Another release, another round of interface name changes. This time systemd has gotten into the fray to make things even more interesting. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ As such, IPv4 resolvers are now being preferred over IPv6 again on these new interface names. kjotte@flounder:~$ grep '' /run/resolvconf/interface/ens3.* /run/resolvconf/interface/ens3.dhclient:search nivex.lan. /run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30 /run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net. /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10 /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 5 19:53:25 2016 InstallationDate: Installed on 2016-08-04 (1 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+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 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address
** Bug watch added: Debian Bug tracker #834928 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834928 ** Also affects: dhcp via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834928 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot assign requested address Status in DHCP: Unknown Status in isc-dhcp package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 address via DHCPv6. The root cause is that dhclient is exiting with the following message: - Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. - The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04 version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10 version) allows me to obtain an address. NetworkManager is the one launching dhclient. The two invocations (one for IPv4 and one for IPv6) are: dhclient_start(): running: /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient6-eth0.pid -lf /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b- 563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient6-eth0.conf eth0 I do not see anything suspicious with the way both dhclients are invoked. Given that a downgrade allows me to obtain an IPv6 address I think this might be a bug in the ISC DHCP client rather than in NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1447715/+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 1610479] [NEW] interface-order needs definitions for systemd predictable names
Public bug reported: Another release, another round of interface name changes. This time systemd has gotten into the fray to make things even more interesting. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ As such, IPv4 resolvers are now being preferred over IPv6 again on these new interface names. kjotte@flounder:~$ grep '' /run/resolvconf/interface/ens3.* /run/resolvconf/interface/ens3.dhclient:search nivex.lan. /run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30 /run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net. /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10 /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 5 19:53:25 2016 InstallationDate: Installed on 2016-08-04 (1 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1610479 Title: interface-order needs definitions for systemd predictable names Status in resolvconf package in Ubuntu: New Bug description: Another release, another round of interface name changes. This time systemd has gotten into the fray to make things even more interesting. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ As such, IPv4 resolvers are now being preferred over IPv6 again on these new interface names. kjotte@flounder:~$ grep '' /run/resolvconf/interface/ens3.* /run/resolvconf/interface/ens3.dhclient:search nivex.lan. /run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30 /run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net. /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10 /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 5 19:53:25 2016 InstallationDate: Installed on 2016-08-04 (1 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+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 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address
This is still an issue in Ubuntu Server 16.04.1. I have the following in my /etc/network/interfaces file: # The primary network interface auto ens3 iface ens3 inet dhcp # This is an autoconfigured IPv6 interface iface ens3 inet6 auto dhcp 1 And on startup: Aug 5 15:55:23 flounder dhclient[2483]: Can't bind to dhcp address: Cannot assign requested address Can confirm the "gross ugly hack" in #7 works. I suggest involving the ifupdown and NetworkManager maintainers as well since their tools should probably be aware of the state of the link and can control when dhclient is invoked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot assign requested address Status in isc-dhcp package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 address via DHCPv6. The root cause is that dhclient is exiting with the following message: - Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. - The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04 version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10 version) allows me to obtain an address. NetworkManager is the one launching dhclient. The two invocations (one for IPv4 and one for IPv6) are: dhclient_start(): running: /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient6-eth0.pid -lf /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b- 563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient6-eth0.conf eth0 I do not see anything suspicious with the way both dhclients are invoked. Given that a downgrade allows me to obtain an IPv6 address I think this might be a bug in the ISC DHCP client rather than in NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1447715/+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 1511830] Re: apparmor denies VM startup when image is network mounted
Now this is bizarre. The first start of the VM after restarting libvirt- bin succeeds. Once I shut down the VM and try to start it again, I get the same DENIED message in syslog. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1511830 Title: apparmor denies VM startup when image is network mounted Status in apparmor package in Ubuntu: New Status in libvirt package in Ubuntu: New Bug description: If I attempt to start a VM with one of its disk images on a libvirt managed NFS mount, it fails: Oct 30 15:30:56 athens kernel: [545232.917662] audit: type=1400 audit(1446233456.718:81): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/libvirt/virt-aa-helper" pid=13760 comm="virt-aa- helper" laddr=fd60:e0:a0f4:121::8 lport=757 faddr=fd60:e0:a0f4:121::4 fport=2049 family="inet6" sock_type="stream" protocol=6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1511830/+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 1511830] Re: apparmor denies VM startup when image is network mounted
Ah ha! I was looking in the abstractions.d for the actual VM definitions. I hadn't thought to look up a level for the virt-aa-helper definition. Sure enough, adding "network inet6," just below the "network inet," and restarting the libvirt-bin service caused the VM to be able to start. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1511830 Title: apparmor denies VM startup when image is network mounted Status in apparmor package in Ubuntu: New Status in libvirt package in Ubuntu: New Bug description: If I attempt to start a VM with one of its disk images on a libvirt managed NFS mount, it fails: Oct 30 15:30:56 athens kernel: [545232.917662] audit: type=1400 audit(1446233456.718:81): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/libvirt/virt-aa-helper" pid=13760 comm="virt-aa- helper" laddr=fd60:e0:a0f4:121::8 lport=757 faddr=fd60:e0:a0f4:121::4 fport=2049 family="inet6" sock_type="stream" protocol=6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1511830/+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 1260855] Re: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity)
I'd forgotten I mentioned the apport issue in this report. It now has its own report: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1511840 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1260855 Title: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity) Status in apport package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Bug description: When installing on an IPv6 only network, the installer incorrectly reports that no Internet connectivity is available. Steps to reproduce: - Download desktop ISO. I used http://cdimage.ubuntu.com/xubuntu/daily-live/current/trusty-desktop-amd64.iso current at Fri Dec 13 15:00 EST - Boot ISO on a computer where only IPv6 connectivity is available - Choose Install Xubuntu - Choose language Results: - At "Preparing to install Xubuntu screen" it states For best results, please ensure that this computer: ✓ has at least 5.5GB available drive space ✕ is connected to the Internet Expected results: - A checkmark next to "is connected to the internet" The install is able to complete from the ISO. Once the installed machine is booted, updates are able to be applied indicating Internet connectivity is indeed available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1260855/+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 1511840] [NEW] cannot apport-bug from IPv6-only network
Public bug reported: Attempting to report a bug using apport-bug from a machine without a legacy IP address fails: # apport-bug foopackage ... *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. *** Error: Network problem Cannot connect to crash database, please check your Internet connection. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Package changed: libvirt (Ubuntu) => apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1511840 Title: cannot apport-bug from IPv6-only network Status in apport package in Ubuntu: New Bug description: Attempting to report a bug using apport-bug from a machine without a legacy IP address fails: # apport-bug foopackage ... *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. *** Error: Network problem Cannot connect to crash database, please check your Internet connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1511840/+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 1002454] Re: IPv4 DNS preferred over IPv6 ones
I've submitted a patch to the upstream bug tracker to get this resolved, but there has been no further activity. -- 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/1002454 Title: IPv4 DNS preferred over IPv6 ones Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The Network Manager always prefers IPv4 DNS over IPv6 ones. The issue occurs both when DNSs are statically configured and when they're acquired via DHCPv4/DHCPv6. Network Manager puts IPv4 DNSs before IPv6 ones in the /var/run/nm- dns-dnsmasq.conf so Dnsmasq resolves names using IPv4 DNSs before using IPv6 ones. If I disable Dnsmasq, DNS servers are put in the wrong way in /etc/resolv.conf file. The system shoud prefer IPv6 DNSs in any case. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon May 21 21:05:59 2012 ExecutablePath: /usr/bin/nm-connection-editor IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.0.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.217 metric 1 192.168.36.0/24 dev vmnet1 proto kernel scope link src 192.168.36.1 192.168.70.0/24 dev vmnet8 proto kernel scope link src 192.168.70.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: RfKill: SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-05-02 (18 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH eth0-Static 0bcb2b9f-a2c0-46f9-a6b1-59f66e383264 802-3-ethernet1337627018 lun 21 mag 2012 21:03:38 CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1002454/+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 1448690] [NEW] /sbin/dhclient-script has bashisms
Public bug reported: /sbin/dhclient-script calls /bin/sh, which is of course dash, but contains bash-specific functions: root@mystic:~# ifup br0 Internet Systems Consortium DHCP Client 4.3.1 Copyright 2004-2014 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/br0/00:1d:92:d7:ad:8a Sending on LPF/br0/00:1d:92:d7:ad:8a Sending on Socket/fallback DHCPREQUEST of 172.31.3.6 on br0 to 255.255.255.255 port 67 (xid=0x7488da46) DHCPACK of 172.31.3.6 from 172.31.3.4 RTNETLINK answers: File exists bound to 172.31.3.6 -- renewal in 38988 seconds. /sbin/dhclient-script: 55: /sbin/dhclient-script: shopt: not found /sbin/dhclient-script: 60: /sbin/dhclient-script: [[: not found /sbin/dhclient-script: 60: /sbin/dhclient-script: [[: not found /sbin/dhclient-script: 68: /sbin/dhclient-script: shopt: not found root@mystic:~# head -n1 /sbin/dhclient-script #!/bin/sh root@mystic:~# Shebang line needs to be /bin/bash, or the script needs to be rewritten. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: isc-dhcp-client 4.3.1-5ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Sun Apr 26 10:29:56 2015 EcryptfsInUse: Yes ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: Upgraded to vivid on 2015-04-24 (1 days ago) ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1448690 Title: /sbin/dhclient-script has bashisms Status in isc-dhcp package in Ubuntu: New Bug description: /sbin/dhclient-script calls /bin/sh, which is of course dash, but contains bash-specific functions: root@mystic:~# ifup br0 Internet Systems Consortium DHCP Client 4.3.1 Copyright 2004-2014 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/br0/00:1d:92:d7:ad:8a Sending on LPF/br0/00:1d:92:d7:ad:8a Sending on Socket/fallback DHCPREQUEST of 172.31.3.6 on br0 to 255.255.255.255 port 67 (xid=0x7488da46) DHCPACK of 172.31.3.6 from 172.31.3.4 RTNETLINK answers: File exists bound to 172.31.3.6 -- renewal in 38988 seconds. /sbin/dhclient-script: 55: /sbin/dhclient-script: shopt: not found /sbin/dhclient-script: 60: /sbin/dhclient-script: [[: not found /sbin/dhclient-script: 60: /sbin/dhclient-script: [[: not found /sbin/dhclient-script: 68: /sbin/dhclient-script: shopt: not found root@mystic:~# head -n1 /sbin/dhclient-script #!/bin/sh root@mystic:~# Shebang line needs to be /bin/bash, or the script needs to be rewritten. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: isc-dhcp-client 4.3.1-5ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Sun Apr 26 10:29:56 2015 EcryptfsInUse: Yes ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: Upgraded to vivid on 2015-04-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448690/+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 1002454] Re: IPv4 DNS preferred over IPv6 ones
** Bug watch added: GNOME Bug Tracker #734454 https://bugzilla.gnome.org/show_bug.cgi?id=734454 ** Also affects: network-manager via https://bugzilla.gnome.org/show_bug.cgi?id=734454 Importance: Unknown Status: Unknown -- 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/1002454 Title: IPv4 DNS preferred over IPv6 ones Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Bug description: The Network Manager always prefers IPv4 DNS over IPv6 ones. The issue occurs both when DNSs are statically configured and when they're acquired via DHCPv4/DHCPv6. Network Manager puts IPv4 DNSs before IPv6 ones in the /var/run/nm- dns-dnsmasq.conf so Dnsmasq resolves names using IPv4 DNSs before using IPv6 ones. If I disable Dnsmasq, DNS servers are put in the wrong way in /etc/resolv.conf file. The system shoud prefer IPv6 DNSs in any case. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon May 21 21:05:59 2012 ExecutablePath: /usr/bin/nm-connection-editor IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.0.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.217 metric 1 192.168.36.0/24 dev vmnet1 proto kernel scope link src 192.168.36.1 192.168.70.0/24 dev vmnet8 proto kernel scope link src 192.168.70.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: RfKill: SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-05-02 (18 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH eth0-Static 0bcb2b9f-a2c0-46f9-a6b1-59f66e383264 802-3-ethernet1337627018 lun 21 mag 2012 21:03:38 CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1002454/+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 1446681] Re: resolvconf v4/v6 order does not handle bridge interfaces correctly
Tested on a KVM host and one of its VMs. Appears to work correctly on br0 and eth0. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1446681 Title: resolvconf v4/v6 order does not handle bridge interfaces correctly Status in resolvconf package in Ubuntu: Confirmed Bug description: The interface-order that ships with 1.70 does not correctly detect bridge interfaces and therefore renders IPv4 resolvers before IPv6 when they are in use. I believe the automatic bug reporter has attached the interface-order I hurriedly patched in which detects bridges separately from eth interfaces. It might make sense to combine these as @(br|eth) as is done with the wifi. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: resolvconf 1.69ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Tue Apr 21 10:02:47 2015 InstallationDate: Installed on 2012-12-14 (857 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to trusty on 2014-08-18 (245 days ago) mtime.conffile..etc.resolvconf.interface.order: 2015-04-20T23:43:05.861928 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1446681/+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 1446681] [NEW] resolvconf v4/v6 order does not handle bridge interfaces correctly
Public bug reported: The interface-order that ships with 1.70 does not correctly detect bridge interfaces and therefore renders IPv4 resolvers before IPv6 when they are in use. I believe the automatic bug reporter has attached the interface-order I hurriedly patched in which detects bridges separately from eth interfaces. It might make sense to combine these as @(br|eth) as is done with the wifi. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: resolvconf 1.69ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Tue Apr 21 10:02:47 2015 InstallationDate: Installed on 2012-12-14 (857 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to trusty on 2014-08-18 (245 days ago) mtime.conffile..etc.resolvconf.interface.order: 2015-04-20T23:43:05.861928 ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1446681 Title: resolvconf v4/v6 order does not handle bridge interfaces correctly Status in resolvconf package in Ubuntu: New Bug description: The interface-order that ships with 1.70 does not correctly detect bridge interfaces and therefore renders IPv4 resolvers before IPv6 when they are in use. I believe the automatic bug reporter has attached the interface-order I hurriedly patched in which detects bridges separately from eth interfaces. It might make sense to combine these as @(br|eth) as is done with the wifi. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: resolvconf 1.69ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Tue Apr 21 10:02:47 2015 InstallationDate: Installed on 2012-12-14 (857 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to trusty on 2014-08-18 (245 days ago) mtime.conffile..etc.resolvconf.interface.order: 2015-04-20T23:43:05.861928 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1446681/+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 1094345] Re: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order
I just discovered another gotcha. The new interface-order in #17 doesn't handle bridge interfaces. I've added those above the eth* for the following new file: # interface-order(5) lo.inet6 lo.inet lo.@(dnsmasq|pdnsd) lo.!(pdns|pdns-recursor) lo tun* tap* hso* em+([0-9])?(_+([0-9]))* p+([0-9])p+([0-9])?(_+([0-9]))* br*([^.]).inet6 br*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) br*([^.]).inet br*([^.]).@(dhclient|dhcpcd|pump|udhcpc) br* eth*([^.]).inet6 eth*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) eth*([^.]).inet eth*([^.]).@(dhclient|dhcpcd|pump|udhcpc) eth* @(ath|wifi|wlan)*([^.]).inet6 @(ath|wifi|wlan)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)*([^.]).inet @(ath|wifi|wlan)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)* ppp* * It seems to work OK, but I haven't checked for any fun corner cases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1094345 Title: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order Status in resolvconf package in Ubuntu: Confirmed Bug description: I am using /etc/network/interfaces rather than NetworkManager on this machine. resolvconf is always writing the IPv4 nameservers and search domains before the IPv6. I would like the IPv6 resolver information to be given priority or a method to select the behavior. kjotte@pegasus:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet6 auto dhcp 1 iface eth0 inet dhcp kjotte@pegasus:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 172.31.3.4 nameserver 2001:470:8:64f::4 search nivex.lan home.nivex.net ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: resolvconf 1.67ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Fri Dec 28 15:33:41 2012 MarkForUpload: True PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to quantal on 2012-05-10 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1094345/+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 1260855] Re: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity)
apport-bug: Cannot connect to crash database, please check your Internet connection. ** Also affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1260855 Title: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity) Status in apport package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: When installing on an IPv6 only network, the installer incorrectly reports that no Internet connectivity is available. Steps to reproduce: - Download desktop ISO. I used http://cdimage.ubuntu.com/xubuntu/daily-live/current/trusty-desktop-amd64.iso current at Fri Dec 13 15:00 EST - Boot ISO on a computer where only IPv6 connectivity is available - Choose Install Xubuntu - Choose language Results: - At "Preparing to install Xubuntu screen" it states For best results, please ensure that this computer: ✓ has at least 5.5GB available drive space ✕ is connected to the Internet Expected results: - A checkmark next to "is connected to the internet" The install is able to complete from the ISO. Once the installed machine is booted, updates are able to be applied indicating Internet connectivity is indeed available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1260855/+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 1002454] Re: IPv4 DNS preferred over IPv6 ones
NetworkManager is still handing the information to resolvconf in the wrong order. root@daedalus:~# lsb_release -d Description:Ubuntu 14.04.1 LTS root@daedalus:~# cat /run/resolvconf/interface/NetworkManager domain home.nivex.net search nivex.lan. home.nivex.net home.nivex.net. nameserver 172.31.3.4 nameserver 2001:470:8:64f::4 nameserver 2606:a000:aa20:2200::4 ** Changed in: network-manager (Ubuntu) Status: Expired => Confirmed -- 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/1002454 Title: IPv4 DNS preferred over IPv6 ones Status in network-manager package in Ubuntu: Confirmed Bug description: The Network Manager always prefers IPv4 DNS over IPv6 ones. The issue occurs both when DNSs are statically configured and when they're acquired via DHCPv4/DHCPv6. Network Manager puts IPv4 DNSs before IPv6 ones in the /var/run/nm- dns-dnsmasq.conf so Dnsmasq resolves names using IPv4 DNSs before using IPv6 ones. If I disable Dnsmasq, DNS servers are put in the wrong way in /etc/resolv.conf file. The system shoud prefer IPv6 DNSs in any case. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon May 21 21:05:59 2012 ExecutablePath: /usr/bin/nm-connection-editor IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.0.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.217 metric 1 192.168.36.0/24 dev vmnet1 proto kernel scope link src 192.168.36.1 192.168.70.0/24 dev vmnet8 proto kernel scope link src 192.168.70.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: RfKill: SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-05-02 (18 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH eth0-Static 0bcb2b9f-a2c0-46f9-a6b1-59f66e383264 802-3-ethernet1337627018 lun 21 mag 2012 21:03:38 CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1002454/+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
