[Touch-packages] [Bug 2025116] Re: apt-key saves key in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)

[Jeffrey Walton]

> 1 million people wasting 15 minutes each 250,000 man hours.
> 3 days or 1 month is much cheaper than 250,000 hours.

Oh, man... According to the apt-key(8) man pages:

   Use of apt-key is deprecated, except for the use of apt-key del in
   maintainer scripts to remove existing keys from the main keyring. If
   such usage of apt-key is desired the additional installation of the GNU
   Privacy Guard suite (packaged in gnupg) is required.

I can't believe Ubuntu deprecated apt-key for that dumpster fire gpg2.
The estimate was completely wrong. Users are going to waste _a lot_ more
time than 15 minutes on that awful tool.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2025116

Title:
  apt-key saves key in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Hi Everyone,

  I want to install Firefox from Mozilla PPA. I added issued apt-key
  (from apt package) to fetch the signing key, and then enabled the PPA
  in /etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list. The apt-
  key command used was:

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
  9BDB3D89CE49EC21

  Then, upon apt-get update:

  # sudo apt-get update
  Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
  ...
  Reading package lists... Done
  W: 
https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/jammy/InRelease: 
Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the 
DEPRECATION section in apt-key(8) for details.

  -

  In the old days, we were supposed to put keys at
  /etc/apt/trusted.gpg.d. If I am parsing things correctly nowadays... a
  new method is supposed to be used: adding [signed-by=] to the
  sources.list line and putting the key in /usr/share/keyrings or
  /etc/apt/keyrings [1].

  [1] https://lists.debian.org/debian-user/2023/06/msg00722.html

  -

  A related bug appears to be
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
  upgrader/+bug/1995825. The 1995825 appears to trigger after an
  upgrade. For me, this is a fresh install. There was no upgrade.

  -

  This is Ubuntu 22.04 LTS, x86_64, fully patched.

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ dpkg -S /usr/bin/apt-key
  apt: /usr/bin/apt-key

  $ apt-cache show apt
  Package: apt
  Architecture: amd64
  Version: 2.4.9
  Priority: important
  Section: admin
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: APT Development Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 4156
  Provides: apt-transport-https (= 2.4.9)
  Depends: adduser, gpgv | gpgv2 | gpgv1, libapt-pkg6.0 (>= 2.4.9), 
ubuntu-keyring, libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libgnutls30 (>= 
3.7.0), libseccomp2 (>= 2.4.2), libstdc++6 (>= 11), libsystemd0
  Recommends: ca-certificates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2025116/+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 2025116] Re: apt-key saves key in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)

[Jeffrey Walton]

Thanks Julian.

> Also read the warning message apt-key gives you:
> 
> Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead 
> (see apt-key(8))

I think the wrong course of action was taken. Deprecated is not
withdrawn. As long as apt-key is provided, it is expected to perform
properly. Once apt-key goes away, then all bets are off.

I also think its a bad idea to [eventually] remove apt-key. The tool is
ubiquitous and it is cited across the web. Searching for "apt-key"
returns over 1 million hits. It would be wise to keep the tool since it
is so well known and used.

I think it would be better to fix apt-key since so many people are
familiar with it and depend on it. And it is economical to fix it. The
cost of fixing apt-key is less expensive than 1 million people working
around the missing tool and learning to use a new tool. One person
fixing apt-key may take 3 days or 1 month. 1 million people wasting 15
minutes each 250,000 man hours. 3 days or 1 month is much cheaper than
250,000 hours.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2025116

Title:
  apt-key saves key in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Hi Everyone,

  I want to install Firefox from Mozilla PPA. I added issued apt-key
  (from apt package) to fetch the signing key, and then enabled the PPA
  in /etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list. The apt-
  key command used was:

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
  9BDB3D89CE49EC21

  Then, upon apt-get update:

  # sudo apt-get update
  Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
  ...
  Reading package lists... Done
  W: 
https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/jammy/InRelease: 
Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the 
DEPRECATION section in apt-key(8) for details.

  -

  In the old days, we were supposed to put keys at
  /etc/apt/trusted.gpg.d. If I am parsing things correctly nowadays... a
  new method is supposed to be used: adding [signed-by=] to the
  sources.list line and putting the key in /usr/share/keyrings or
  /etc/apt/keyrings [1].

  [1] https://lists.debian.org/debian-user/2023/06/msg00722.html

  -

  A related bug appears to be
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
  upgrader/+bug/1995825. The 1995825 appears to trigger after an
  upgrade. For me, this is a fresh install. There was no upgrade.

  -

  This is Ubuntu 22.04 LTS, x86_64, fully patched.

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ dpkg -S /usr/bin/apt-key
  apt: /usr/bin/apt-key

  $ apt-cache show apt
  Package: apt
  Architecture: amd64
  Version: 2.4.9
  Priority: important
  Section: admin
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: APT Development Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 4156
  Provides: apt-transport-https (= 2.4.9)
  Depends: adduser, gpgv | gpgv2 | gpgv1, libapt-pkg6.0 (>= 2.4.9), 
ubuntu-keyring, libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libgnutls30 (>= 
3.7.0), libseccomp2 (>= 2.4.2), libstdc++6 (>= 11), libsystemd0
  Recommends: ca-certificates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2025116/+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 2025116] [NEW] apt-key saves key in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)

[Jeffrey Walton]

Public bug reported:

Hi Everyone,

I want to install Firefox from Mozilla PPA. I added issued apt-key (from
apt package) to fetch the signing key, and then enabled the PPA in
/etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list. The apt-key
command used was:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
9BDB3D89CE49EC21

Then, upon apt-get update:

# sudo apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
...
Reading package lists... Done
W: 
https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/jammy/InRelease: 
Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the 
DEPRECATION section in apt-key(8) for details.

-

In the old days, we were supposed to put keys at /etc/apt/trusted.gpg.d.
If I am parsing things correctly nowadays... a new method is supposed to
be used: adding [signed-by=] to the sources.list line and putting
the key in /usr/share/keyrings or /etc/apt/keyrings [1].

[1] https://lists.debian.org/debian-user/2023/06/msg00722.html

-

A related bug appears to be
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1995825. The 1995825 appears to trigger after an upgrade.
For me, this is a fresh install. There was no upgrade.

-

This is Ubuntu 22.04 LTS, x86_64, fully patched.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename:   jammy

-

$ dpkg -S /usr/bin/apt-key
apt: /usr/bin/apt-key

$ apt-cache show apt
Package: apt
Architecture: amd64
Version: 2.4.9
Priority: important
Section: admin
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: APT Development Team 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 4156
Provides: apt-transport-https (= 2.4.9)
Depends: adduser, gpgv | gpgv2 | gpgv1, libapt-pkg6.0 (>= 2.4.9), 
ubuntu-keyring, libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libgnutls30 (>= 
3.7.0), libseccomp2 (>= 2.4.2), libstdc++6 (>= 11), libsystemd0
Recommends: ca-certificates

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2025116

Title:
  apt-key saves key in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)

Status in apt package in Ubuntu:
  New

Bug description:
  Hi Everyone,

  I want to install Firefox from Mozilla PPA. I added issued apt-key
  (from apt package) to fetch the signing key, and then enabled the PPA
  in /etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list. The apt-
  key command used was:

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
  9BDB3D89CE49EC21

  Then, upon apt-get update:

  # sudo apt-get update
  Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
  ...
  Reading package lists... Done
  W: 
https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/jammy/InRelease: 
Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the 
DEPRECATION section in apt-key(8) for details.

  -

  In the old days, we were supposed to put keys at
  /etc/apt/trusted.gpg.d. If I am parsing things correctly nowadays... a
  new method is supposed to be used: adding [signed-by=] to the
  sources.list line and putting the key in /usr/share/keyrings or
  /etc/apt/keyrings [1].

  [1] https://lists.debian.org/debian-user/2023/06/msg00722.html

  -

  A related bug appears to be
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
  upgrader/+bug/1995825. The 1995825 appears to trigger after an
  upgrade. For me, this is a fresh install. There was no upgrade.

  -

  This is Ubuntu 22.04 LTS, x86_64, fully patched.

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ dpkg -S /usr/bin/apt-key
  apt: /usr/bin/apt-key

  $ apt-cache show apt
  Package: apt
  Architecture: amd64
  Version: 2.4.9
  Priority: important
  Section: admin
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: APT Development Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 4156
  Provides: apt-transport-https (= 2.4.9)
  Depends: adduser, gpgv | gpgv2 | gpgv1, libapt-pkg6.0 (>= 2.4.9), 
ubuntu-keyring, libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libgnutls30 (>= 
3.7.0), libseccomp2 (>= 2.4.2), libstdc++6 (>= 11), libsystemd0
  Recommends: ca-certificates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2025116/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post 

[Touch-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )

[Jeffrey Walton]

Thorsten, a quick question...

The first part of my book build script has this:

echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."

Why did the book pass validation when using emdash entity reference? It
seems like that should have failed.

An example of the build script can be found at
https://github.com/noloader/POWER8-crypto/tree/master/docbook. make-
book.sh builds the book, and it includes the snippet.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814

Title:
  xmllint does not recognize emdash ()

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to 
build a PDF. One of the steps I use in my build script is to validate and 
format the XML using xmllint from libxml2-utils
  2.9.13+dfsg-1ubuntu0.3:

  echo "Validating book..."
  if ! xmllint --xinclude --noout --postvalid book.xml
  then
  echo "Validation failed. Exiting."
  exit 1
  fi
  echo "Complete."

  echo "Formatting source code..."
  for file in *.xml
  do
  if xmllint --format "${file}" --output "${file}.format"
  then
  mv "${file}.format" "${file}"
  fi
  done
  echo "Complete."

  When I added an emdash () the book failed to format:

  Validating book...
  Complete.
  Formatting source code...
  ch02.xml:58: parser error : Entity 'mdash' not defined
   injections are remediated using several methods. And two output devices 


 ^
  ch02.xml:58: parser error : Entity 'mdash' not defined
   methods. And two output devices  the printer and plaintext email 


 ^
  Complete.

  The text is:

  ... And two output devices  the printer and plaintext
  email  do not require...

  It seems like emdash should be recognized.

  -

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ xmllint --version
  xmllint: using libxml version 20913
 compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

  $ command -v xmllint
  /usr/bin/xmllint

  $ dpkg -S /usr/bin/xmllint
  libxml2-utils: /usr/bin/xmllint

  $ apt-cache show libxml2-utils
  Package: libxml2-utils
  Architecture: amd64
  Version: 2.9.13+dfsg-1ubuntu0.3
  Multi-Arch: foreign
  Priority: optional
  Section: text
  Source: libxml2
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian XML/SGML Group 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 202
  Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
  Filename: 
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
  Size: 40192
  MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
  SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
  SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
  SHA512: 
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
  Homepage: http://xmlsoft.org
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+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

Re: [Touch-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )

[Jeffrey Walton]

On Thu, May 25, 2023 at 5:35 PM Thorsten Glaser
<2020...@bugs.launchpad.net> wrote:
>
> I doubt this is a bug: nowhere do you pass the validator a DTD, and
> entities are defined in the DTD.
>
> It’s best practice nowadays to not use entities but just write the UTF-8
> characters directly.
>
> An em dash surrounded by hair spaces is: “ — ” (for your copy/paste
> convenience)

I think you are right - this is not a bug. I took a quick peek at RFC
3470, and I don't see where HTML entity references are optional.

Sorry about that. I got some bad info off the internet (surprise,
surprise). It said to use the character entity reference for emdash
due to portability problems when using the character itself.

Jeff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814

Title:
  xmllint does not recognize emdash ()

Status in libxml2 package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to 
build a PDF. One of the steps I use in my build script is to validate and 
format the XML using xmllint from libxml2-utils
  2.9.13+dfsg-1ubuntu0.3:

  echo "Validating book..."
  if ! xmllint --xinclude --noout --postvalid book.xml
  then
  echo "Validation failed. Exiting."
  exit 1
  fi
  echo "Complete."

  echo "Formatting source code..."
  for file in *.xml
  do
  if xmllint --format "${file}" --output "${file}.format"
  then
  mv "${file}.format" "${file}"
  fi
  done
  echo "Complete."

  When I added an emdash () the book failed to format:

  Validating book...
  Complete.
  Formatting source code...
  ch02.xml:58: parser error : Entity 'mdash' not defined
   injections are remediated using several methods. And two output devices 


 ^
  ch02.xml:58: parser error : Entity 'mdash' not defined
   methods. And two output devices  the printer and plaintext email 


 ^
  Complete.

  The text is:

  ... And two output devices  the printer and plaintext
  email  do not require...

  It seems like emdash should be recognized.

  -

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ xmllint --version
  xmllint: using libxml version 20913
 compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

  $ command -v xmllint
  /usr/bin/xmllint

  $ dpkg -S /usr/bin/xmllint
  libxml2-utils: /usr/bin/xmllint

  $ apt-cache show libxml2-utils
  Package: libxml2-utils
  Architecture: amd64
  Version: 2.9.13+dfsg-1ubuntu0.3
  Multi-Arch: foreign
  Priority: optional
  Section: text
  Source: libxml2
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian XML/SGML Group 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 202
  Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
  Filename: 
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
  Size: 40192
  MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
  SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
  SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
  SHA512: 
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
  Homepage: http://xmlsoft.org
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+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 2020814] [NEW] xmllint does not recognize emdash ( )

[Jeffrey Walton]

Public bug reported:

I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to build 
a PDF. One of the steps I use in my build script is to validate and format the 
XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:

echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."

echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."

When I added an emdash () the book failed to format:

Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
 injections are remediated using several methods. And two output devices 


   ^
ch02.xml:58: parser error : Entity 'mdash' not defined
 methods. And two output devices  the printer and plaintext email 


   ^
Complete.

The text is:

... And two output devices  the printer and plaintext
email  do not require...

It seems like emdash should be recognized.

-

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename:   jammy

-

$ xmllint --version
xmllint: using libxml version 20913
   compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

$ command -v xmllint
/usr/bin/xmllint

$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint

$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian XML/SGML Group 

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename: pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512: 
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...

** Affects: libxml2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814

Title:
  xmllint does not recognize emdash ()

Status in libxml2 package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to 
build a PDF. One of the steps I use in my build script is to validate and 
format the XML using xmllint from libxml2-utils
  2.9.13+dfsg-1ubuntu0.3:

  echo "Validating book..."
  if ! xmllint --xinclude --noout --postvalid book.xml
  then
  echo "Validation failed. Exiting."
  exit 1
  fi
  echo "Complete."

  echo "Formatting source code..."
  for file in *.xml
  do
  if xmllint --format "${file}" --output "${file}.format"
  then
  mv "${file}.format" "${file}"
  fi
  done
  echo "Complete."

  When I added an emdash () the book failed to format:

  Validating book...
  Complete.
  Formatting source code...
  ch02.xml:58: parser error : Entity 'mdash' not defined
   injections are remediated using several methods. And two output devices 


 ^
  ch02.xml:58: parser error : Entity 'mdash' not defined
   methods. And two output devices  the printer and plaintext email 


 ^
  Complete.

  The text is:

  ... And two output devices  the printer and plaintext
  email  do not require...

  It seems like emdash should be recognized.

  -

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ xmllint --version
  xmllint: using libxml version 20913
 compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

  $ command -v 

[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say nothing

[Jeffrey Walton]

Yes, please fix.

>From a security standpoint, we can't tell the "good" held backs (Phased
Updates) from the "bad" held backs (problem with package). So we assume
its a package problem, go in with a hammer, and use Aptitude's safe-
upgrade to force the updates. Now we've subverted/undermined the Phased
Updates when there was no problem.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1988819

Title:
  When apt keeps back packages due to phased updates, it should say
  nothing

Status in apt package in Ubuntu:
  Triaged

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+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 1990624] Re: Removing old kernel-core leaves modules.builtin.alias.bin under /lib/modules

[Jeffrey Walton]

Thanks Nick.

Would you happen to know which component the issue should be assigned
to? (I picked Systemd because of the Red Hat bug).

And I should have provided this in the report. Sorry about that:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.5 LTS
Release:20.04
Codename:   focal

-- 
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/1990624

Title:
  Removing old kernel-core leaves modules.builtin.alias.bin under
  /lib/modules

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Triaged

Bug description:
  After I remove old kernels, I see there are artifacts left over in
  /lib/modules. Below, I should have only two folders - one for the
  latest 5.4 kernel, and one for the latest 5.15 kernel.

  $ ls /lib/modules
  5.15.0-41-generic  5.15.0-46-generic  5.4.0-126-generic
  5.15.0-43-generic  5.15.0-48-generic

  $ ls /lib/modules/5.15.0-41-generic/
  misc   modules.builtin.alias.bin  modules.dep.bin  modules.symbols
  modules.alias  modules.builtin.binmodules.devname  
modules.symbols.bin
  modules.alias.bin  modules.depmodules.softdep

  This appears to be a rehash of Red Hat Issue 2016630 - Removing old
  kernel-core leaves modules.builtin.alias.bin under /lib/modules,
  https://bugzilla.redhat.com/show_bug.cgi?id=2016630 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990624/+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 1990624] Re: Removing old kernel-core leaves modules.builtin.alias.bin under /lib/modules

[Jeffrey Walton]

> Are you invoking kernel-install to remove kernels? Or what action did
you perform exactly?

Good question, Nick.

I am not using kernel-install. Instead, I use a command like:

   # For the case of 5.15.0-41-generic kernel
   $ sudo apt-get remove --purge '*5.15.0-41*'

In fact, I ran the command manually when I noticed the accumulation of
old kernel parts in /lib/modules. Apt said there was nothing to do.

I knew about the 2016630 bug from Red Hat because I first experienced
the issue on Fedora 35. Now I am seeing it on Ubuntu, too.

--

Here is the actual script I am running. It looks at the current kernel,
and makes a list of all kernels. It removes the current kernel from the
list of all kernels, and then removes all the old kernels.

# Get a list mostly removed kernels. The kernel and package have been
# removed, but the configuration files and directory remains.
old_kernels=($(dpkg -l | grep linux-image | grep '^rc' | tr -s " " | \
cut -f 2 -d ' ' | sort | uniq))

if [ "${#old_kernels[@]}" -ne 0 ]; then
apt-get remove -y --purge "${old_kernels[@]}" 1>/dev/null
fi

# Get the current kernel
current_kernel=$(uname -r)
version_only=$(get_version ${current_kernel})

echo "Current kernel:"
echo "  ${current_kernel} (${version_only})"

# Get a list of installed kernels. The `grep -v` removes the
# current kernel from the list, which should be the latest kernel.
old_kernels=($(dpkg -l | grep linux-image | grep '^ii' | tr -s " " | \
cut -f 2 -d ' ' | sort -V | uniq | grep -v "${current_kernel}"))

temp_list=()
for k in "${old_kernels[@]}"
do
# Skip the metapackage linux-image-generic
if [[ "${k}" == linux-image-generic* ]]; then
continue
fi
temp_list+=("${k}")
done

# Swap-in the new list
old_kernels=("${temp_list[@]}")

if [ "${#old_kernels[@]}" -eq 0 ]; then
echo "No old kernels found"
exit 0
fi

echo "Old kernels to remove:"
for k in "${old_kernels[@]}"
do
version_only=$(get_version ${k})
echo "  ${k} (${version_only})"
done

for k in "${old_kernels[@]}"
do
version_only=$(get_version ${k})
if ! apt-get remove -y --purge "*${version_only}*"; then
echo "Failed to remove ${k}"
some_error=1
fi

done

apt-get install -y --reinstall linux-image-generic linux-headers-
generic

Fedora is a lot easier to remove old kernels. On Fedora I use:

old_kernels=($(dnf repoquery --installonly --latest-limit=-1 -q))
if [ "${#old_kernels[@]}" -eq 0 ]; then
echo "No old kernels found"
exit 0
fi

if ! dnf -y remove "${old_kernels[@]}"; then
echo "Failed to remove old kernels"
exit 1
fi

-- 
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/1990624

Title:
  Removing old kernel-core leaves modules.builtin.alias.bin under
  /lib/modules

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After I remove old kernels, I see there are artifacts left over in
  /lib/modules. Below, I should have only two folders - one for the
  latest 5.4 kernel, and one for the latest 5.15 kernel.

  $ ls /lib/modules
  5.15.0-41-generic  5.15.0-46-generic  5.4.0-126-generic
  5.15.0-43-generic  5.15.0-48-generic

  $ ls /lib/modules/5.15.0-41-generic/
  misc   modules.builtin.alias.bin  modules.dep.bin  modules.symbols
  modules.alias  modules.builtin.binmodules.devname  
modules.symbols.bin
  modules.alias.bin  modules.depmodules.softdep

  This appears to be a rehash of Red Hat Issue 2016630 - Removing old
  kernel-core leaves modules.builtin.alias.bin under /lib/modules,
  https://bugzilla.redhat.com/show_bug.cgi?id=2016630 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990624/+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 1990624] [NEW] Removing old kernel-core leaves modules.builtin.alias.bin under /lib/modules

[Jeffrey Walton]

Public bug reported:

After I remove old kernels, I see there are artifacts left over in
/lib/modules. Below, I should have only two folders - one for the latest
5.4 kernel, and one for the latest 5.15 kernel.

$ ls /lib/modules
5.15.0-41-generic  5.15.0-46-generic  5.4.0-126-generic
5.15.0-43-generic  5.15.0-48-generic

$ ls /lib/modules/5.15.0-41-generic/
misc   modules.builtin.alias.bin  modules.dep.bin  modules.symbols
modules.alias  modules.builtin.binmodules.devname  
modules.symbols.bin
modules.alias.bin  modules.depmodules.softdep

This appears to be a rehash of Red Hat Issue 2016630 - Removing old
kernel-core leaves modules.builtin.alias.bin under /lib/modules,
https://bugzilla.redhat.com/show_bug.cgi?id=2016630 .

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1990624

Title:
  Removing old kernel-core leaves modules.builtin.alias.bin under
  /lib/modules

Status in systemd package in Ubuntu:
  New

Bug description:
  After I remove old kernels, I see there are artifacts left over in
  /lib/modules. Below, I should have only two folders - one for the
  latest 5.4 kernel, and one for the latest 5.15 kernel.

  $ ls /lib/modules
  5.15.0-41-generic  5.15.0-46-generic  5.4.0-126-generic
  5.15.0-43-generic  5.15.0-48-generic

  $ ls /lib/modules/5.15.0-41-generic/
  misc   modules.builtin.alias.bin  modules.dep.bin  modules.symbols
  modules.alias  modules.builtin.binmodules.devname  
modules.symbols.bin
  modules.alias.bin  modules.depmodules.softdep

  This appears to be a rehash of Red Hat Issue 2016630 - Removing old
  kernel-core leaves modules.builtin.alias.bin under /lib/modules,
  https://bugzilla.redhat.com/show_bug.cgi?id=2016630 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990624/+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 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection

[Jeffrey Walton]

Sebastien, do you know how I can mark my ethernet connection as the
default one? The ethernet connection I want to set as default is the
wired ethernet, which is enp4s0 in the dumps shown above.

I cannot find a setting in the Settings program to set a default
connection. I also cannot find a discussion of it in the docs.[1,2] The
docs only say the program usually picks the right one:[1]

In most cases the wired network connection will simply work
without any changes to the default Kubuntu configuration.
Wired network connections are selected as default when they
are available.

(And it is not picking a wired connection as stated in the docs. It is
picking a Wifi connection via the Android phone).

[1] https://userbase.kde.org/Kubuntu/Basic/en#Networking
[2] https://userbase.kde.org/NetworkManagement

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 

[Touch-packages] [Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection

[Jeffrey Walton]

> Sebastien Bacher wrote:
>
> yes, the current details are about a working system but we want to work on 
> the bug

Thanks again Sebastien.

I rebooted the machine with the phone tethered and it used USB0 as the
network adapter. I then ran 'apport-collect 1975549'.

Here is the current nmcli when running the command in its current state
(boot with phone tethered):

$ nmcli
usb0: connected to Ethernet
"Google Nexus 4/5/7/10"
ethernet (rndis_host), 82:1F:DF:52:0B:39, hw, mtu 1500
ip4 default
inet4 192.168.11.182/24
route4 0.0.0.0/0
route4 192.168.11.0/24
route4 169.254.0.0/16
inet6 fe80::801f:dfff:fe52:b39/64
route6 fe80::/64

enp4s0: disconnected
"Qualcomm Atheros Killer E2400"
1 connection available
ethernet (alx), D8:9E:F3:92:24:60, hw, mtu 1500

wlp3s0: disconnected
"Qualcomm Atheros QCA9377"
wifi (ath10k_pci), 90:32:4B:76:E0:B9, hw, mtu 1500

p2p-dev-wlp3s0: disconnected
"p2p-dev-wlp3s0"
wifi-p2p, hw

lo: unmanaged
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
servers: 192.168.11.111
interface: usb0

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage
details.

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID 

[Touch-packages] [Bug 1975549] WifiSyslog.txt

[Jeffrey Walton]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592936/+files/WifiSyslog.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link metric 1000 
  

[Touch-packages] [Bug 1975549] nmcli-dev.txt

[Jeffrey Walton]

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592937/+files/nmcli-dev.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link metric 1000 
   

[Touch-packages] [Bug 1975549] RfKill.txt

[Jeffrey Walton]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1975549/+attachment/5592935/+files/RfKill.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link metric 1000 
   

[Touch-packages] [Bug 1975549] NetworkManager.conf.txt

[Jeffrey Walton]

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592931/+files/NetworkManager.conf.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope 

[Touch-packages] [Bug 1975549] NetDevice.wlp3s0.txt

[Jeffrey Walton]

apport information

** Attachment added: "NetDevice.wlp3s0.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592930/+files/NetDevice.wlp3s0.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link 

[Touch-packages] [Bug 1975549] ProcEnviron.txt

[Jeffrey Walton]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592934/+files/ProcEnviron.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link metric 1000 

[Touch-packages] [Bug 1975549] NetDevice.usb0.txt

[Jeffrey Walton]

apport information

** Attachment added: "NetDevice.usb0.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592929/+files/NetDevice.usb0.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link metric 

[Touch-packages] [Bug 1975549] PciNetwork.txt

[Jeffrey Walton]

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592932/+files/PciNetwork.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link metric 1000 
  

[Touch-packages] [Bug 1975549] ProcCpuinfoMinimal.txt

[Jeffrey Walton]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592933/+files/ProcCpuinfoMinimal.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope 

[Touch-packages] [Bug 1975549] NetDevice.enp4s0.txt

[Jeffrey Walton]

apport information

** Attachment added: "NetDevice.enp4s0.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592927/+files/NetDevice.enp4s0.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link 

[Touch-packages] [Bug 1975549] NetDevice.lo.txt

[Jeffrey Walton]

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592928/+files/NetDevice.lo.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link metric 

[Touch-packages] [Bug 1975549] Dependencies.txt

[Jeffrey Walton]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592924/+files/Dependencies.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link metric 

[Touch-packages] [Bug 1975549] IpAddr.txt

[Jeffrey Walton]

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1975549/+attachment/5592925/+files/IpAddr.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link metric 1000 
   

[Touch-packages] [Bug 1975549] IwConfig.txt

[Jeffrey Walton]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592926/+files/IwConfig.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (108 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 192.168.11.111 dev usb0 proto dhcp metric 100 
   169.254.0.0/16 dev usb0 scope link metric 1000 
   

[Touch-packages] [Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection

[Jeffrey Walton]

apport information

** Description changed:

  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.
  
  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.
  
  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It literally
  calls the connection "ethernet", as if it was using the network adapter.
  This is new behavior over the last week or two.
  
  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called "ethernet"
  instead of something more meaningful like "USB" or "Android" or "wired
  hotspot".
  
  The third item ("ethernet" name when using Android phone) was misleading
  enough to waste a lot of time troubleshooting the issue. I thought I had
  an odd firewall issue or a mDNS issue.
  
  The reason I was having so many troubles, like printing and ssh, is the
  Android phone uses Wifi and it is on a different VLAN and subnet to keep
  traffic segregated from my trusted internal network.
  
  -
  
  It looks like I am running network-manager via systemd:
  
  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2022-02-05 (108 days ago)
+ InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
+ IpRoute:
+  default via 192.168.11.111 dev usb0 proto dhcp metric 100 
+  169.254.0.0/16 dev usb0 scope link metric 1000 
+  192.168.11.0/24 dev usb0 proto kernel scope link src 192.168.11.182 metric 
100
+ Package: network-manager 1.22.10-1ubuntu2.3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
+ Tags:  focal
+ Uname: Linux 5.13.0-44-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ nmcli-con:
+  

[Touch-packages] [Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection

[Jeffrey Walton]

> It's a bit weird, https://launchpadlibrarian.net/602981658/nmcli-dev.txt
> shows no connection associated to the usb device nor IP for it

Thanks again Sebastien.

This may be because I booted the machine with the phone unplugged.

I can run apport again with the phone plugged in (and then reboot) to
duplicate the issue.

Would you like me to run apport again after booting with the phone
plugged in?

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions


-- 
Mailing list: 

[Touch-packages] [Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection

[Jeffrey Walton]

> Thank you for your bug report, could you do
> 
> $ apport-collect 1975549
> 
> on the machine at the time you are having the issue?

Thanks Sebastien.

This caught my eye (from the apport generated files):

   Android phone:

   * ID_NET_LINK_FILE=/usr/lib/systemd/network/73-usb-net-by-mac.link

   NIC adapter:

   * ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link

I can envision a situation where 73 is given higher precedence than 99.

What I don't know is, why things changed recently (assuming they were
the same way in the past).

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage 

[Touch-packages] [Bug 1975549] WifiSyslog.txt

[Jeffrey Walton]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592647/+files/WifiSyslog.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] nmcli-dev.txt

[Jeffrey Walton]

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592648/+files/nmcli-dev.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] NetDevice.usb0.txt

[Jeffrey Walton]

apport information

** Attachment added: "NetDevice.usb0.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592640/+files/NetDevice.usb0.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] NetDevice.wlp3s0.txt

[Jeffrey Walton]

apport information

** Attachment added: "NetDevice.wlp3s0.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592641/+files/NetDevice.wlp3s0.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] ProcCpuinfoMinimal.txt

[Jeffrey Walton]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592644/+files/ProcCpuinfoMinimal.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] RfKill.txt

[Jeffrey Walton]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1975549/+attachment/5592646/+files/RfKill.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] PciNetwork.txt

[Jeffrey Walton]

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592643/+files/PciNetwork.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] ProcEnviron.txt

[Jeffrey Walton]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592645/+files/ProcEnviron.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] NetworkManager.conf.txt

[Jeffrey Walton]

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592642/+files/NetworkManager.conf.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] IpAddr.txt

[Jeffrey Walton]

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1975549/+attachment/5592636/+files/IpAddr.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] IwConfig.txt

[Jeffrey Walton]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592637/+files/IwConfig.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] NetDevice.lo.txt

[Jeffrey Walton]

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592639/+files/NetDevice.lo.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] NetDevice.enp4s0.txt

[Jeffrey Walton]

apport information

** Attachment added: "NetDevice.enp4s0.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592638/+files/NetDevice.enp4s0.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] Dependencies.txt

[Jeffrey Walton]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1975549/+attachment/5592635/+files/Dependencies.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection

[Jeffrey Walton]

apport information

** Tags added: apport-collected focal

** Description changed:

  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.
  
  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.
  
  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It literally
  calls the connection "ethernet", as if it was using the network adapter.
  This is new behavior over the last week or two.
  
  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called "ethernet"
  instead of something more meaningful like "USB" or "Android" or "wired
  hotspot".
  
  The third item ("ethernet" name when using Android phone) was misleading
  enough to waste a lot of time troubleshooting the issue. I thought I had
  an odd firewall issue or a mDNS issue.
  
  The reason I was having so many troubles, like printing and ssh, is the
  Android phone uses Wifi and it is on a different VLAN and subnet to keep
  traffic segregated from my trusted internal network.
  
  -
  
  It looks like I am running network-manager via systemd:
  
  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2022-02-05 (107 days ago)
+ InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
+ IpRoute:
+  default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
+  169.254.0.0/16 dev enp4s0 scope link metric 1000 
+  172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
+ Package: network-manager 1.22.10-1ubuntu2.3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
+ Tags:  focal
+ Uname: Linux 5.13.0-44-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ nmcli-con:
+  NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

+  Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connections/Ethernet.nmconnection
+ nmcli-nm:
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1975549/+attachment/5592634/+files/CRDA.txt

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android 

[Touch-packages] [Bug 1975549] [NEW] NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection

[Jeffrey Walton]

Public bug reported:

I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.

I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.

I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It literally
calls the connection "ethernet", as if it was using the network adapter.
This is new behavior over the last week or two.

This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called "ethernet"
instead of something more meaningful like "USB" or "Android" or "wired
hotspot".

The third item ("ethernet" name when using Android phone) was misleading
enough to waste a lot of time troubleshooting the issue. I thought I had
an odd firewall issue or a mDNS issue.

The reason I was having so many troubles, like printing and ssh, is the
Android phone uses Wifi and it is on a different VLAN and subnet to keep
traffic segregated from my trusted internal network.

-

It looks like I am running network-manager via systemd:

# service systemd-networkd status
● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
 Active: inactive (dead)
   Docs: man:systemd-networkd.service(8)
# service network-manager  status
● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
 Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
   Docs: man:NetworkManager(8)
   Main PID: 928 (NetworkManager)
  Tasks: 3 (limit: 76693)
 Memory: 12.0M
 CGroup: /system.slice/NetworkManager.service
 └─928 /usr/sbin/NetworkManager --no-daemon
  ...

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...

To manage notifications about this bug go to:

[Touch-packages] [Bug 1922212] Re: SSHD does not honor configuration files

[Jeffrey Walton]

Something is really sideways here:

# sshd -T | grep -i -E 'password|pam|authentication|publickey'
usepam yes
hostbasedauthentication no
pubkeyauthentication yes
kerberosauthentication no
gssapiauthentication no
passwordauthentication yes
kbdinteractiveauthentication yes
challengeresponseauthentication yes
permitemptypasswords no
authenticationmethods any

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1922212

Title:
  SSHD does not honor configuration files

Status in openssh package in Ubuntu:
  New

Bug description:
  I'm working on Ubuntu 20, x86_64, fully patched.

 # lsb_release -a
 Distributor ID:Ubuntu
 Description:   Ubuntu 20.04.2 LTS
 ...

  We are seeing reports of failed password-based logins using root:

 jounralctl -xe
 ...
 Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 
49.88.112.77 port 36206 ssh2
 Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 
49.88.112.77 port 36206 ssh2
 ...

  There are three attempts every second or two (literally):

 # journalctl -xe | grep -i -c 'Failed password for root'
 324

  Our OpenSSH server is configured with both no-password based logins
  and no-root logins.

 # ls /etc/ssh/sshd_config.d/
 10_pubkey_auth.conf  20_disable_root_login.conf

 # cat /etc/ssh/sshd_config.d/10_pubkey_auth.conf 
 # Disable passwords
 PasswordAuthentication no
 ChallengeResponseAuthentication no
 UsePAM no
 # Enable public key
 PubkeyAuthentication yes

 # cat /etc/ssh/sshd_config.d/20_disable_root_login.conf 
 PermitRootLogin no

  The config files are included last in our /etc/ssh/sshd_config file:

 # tail -n 3 /etc/ssh/sshd_config

 # For some reason OpenSSH does not include additional conf files by 
default.
 Include /etc/ssh/sshd_config.d/*.conf

  I dislike modifying /etc/ssh/sshd_config since it will be overwritten
  by the distro. With that said, I modified it without success.

  It really annoys me that we can't secure this service. Something looks
  very broken here.

  -

  # apt-cache show openssh-server
  Package: openssh-server
  Architecture: amd64
  Version: 1:8.2p1-4ubuntu0.2
  Multi-Arch: foreign
  Priority: optional
  Section: net
  Source: openssh
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian OpenSSH Maintainers 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212/+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 1922212] Re: SSHD does not honor configuration files

[Jeffrey Walton]

Also see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109846. It is
an old bug report (from 2001), but it says this is what we need:

   PasswordAuthentication no
   ChallengeResponseAuthentication no
   UsePAM no

** Bug watch added: Debian Bug tracker #109846
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109846

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1922212

Title:
  SSHD does not honor configuration files

Status in openssh package in Ubuntu:
  New

Bug description:
  I'm working on Ubuntu 20, x86_64, fully patched.

 # lsb_release -a
 Distributor ID:Ubuntu
 Description:   Ubuntu 20.04.2 LTS
 ...

  We are seeing reports of failed password-based logins using root:

 jounralctl -xe
 ...
 Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 
49.88.112.77 port 36206 ssh2
 Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 
49.88.112.77 port 36206 ssh2
 ...

  There are three attempts every second or two (literally):

 # journalctl -xe | grep -i -c 'Failed password for root'
 324

  Our OpenSSH server is configured with both no-password based logins
  and no-root logins.

 # ls /etc/ssh/sshd_config.d/
 10_pubkey_auth.conf  20_disable_root_login.conf

 # cat /etc/ssh/sshd_config.d/10_pubkey_auth.conf 
 # Disable passwords
 PasswordAuthentication no
 ChallengeResponseAuthentication no
 UsePAM no
 # Enable public key
 PubkeyAuthentication yes

 # cat /etc/ssh/sshd_config.d/20_disable_root_login.conf 
 PermitRootLogin no

  The config files are included last in our /etc/ssh/sshd_config file:

 # tail -n 3 /etc/ssh/sshd_config

 # For some reason OpenSSH does not include additional conf files by 
default.
 Include /etc/ssh/sshd_config.d/*.conf

  I dislike modifying /etc/ssh/sshd_config since it will be overwritten
  by the distro. With that said, I modified it without success.

  It really annoys me that we can't secure this service. Something looks
  very broken here.

  -

  # apt-cache show openssh-server
  Package: openssh-server
  Architecture: amd64
  Version: 1:8.2p1-4ubuntu0.2
  Multi-Arch: foreign
  Priority: optional
  Section: net
  Source: openssh
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian OpenSSH Maintainers 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212/+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 1922212] Re: SSHD does not honor configuration files

[Jeffrey Walton]

This gets worse. Adding the following to the tail of
/etc/ssh/sshd_config does not configure the service properly.

   PasswordAuthentication no
   ChallengeResponseAuthentication no
   UsePAM no
   PubkeyAuthentication yes
   PermitRootLogin no

The login attempts are still allowed:

Apr 01 09:31:10 localhost sshd[239597]: pam_unix(sshd:auth): authentication 
failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.77  user=root
Apr 01 09:31:13 localhost sshd[239597]: Failed password for root from 
49.88.112.77 port 50368 ssh2
Apr 01 09:31:16 localhost sshd[239597]: Failed password for root from 
49.88.112.77 port 50368 ssh2
Apr 01 09:31:19 localhost sshd[239597]: Failed password for root from 
49.88.112.77 port 50368 ssh2
Apr 01 09:31:20 localhost sshd[239597]: Received disconnect from 49.88.112.77 
port 50368:11:  [preauth]
Apr 01 09:31:20 localhost sshd[239597]: Disconnected from authenticating user 
root 49.88.112.77 port 50368 [preauth]
Apr 01 09:31:20 localhost sshd[239597]: PAM 2 more authentication failures; 
logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.77  user=root

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1922212

Title:
  SSHD does not honor configuration files

Status in openssh package in Ubuntu:
  New

Bug description:
  I'm working on Ubuntu 20, x86_64, fully patched.

 # lsb_release -a
 Distributor ID:Ubuntu
 Description:   Ubuntu 20.04.2 LTS
 ...

  We are seeing reports of failed password-based logins using root:

 jounralctl -xe
 ...
 Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 
49.88.112.77 port 36206 ssh2
 Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 
49.88.112.77 port 36206 ssh2
 ...

  There are three attempts every second or two (literally):

 # journalctl -xe | grep -i -c 'Failed password for root'
 324

  Our OpenSSH server is configured with both no-password based logins
  and no-root logins.

 # ls /etc/ssh/sshd_config.d/
 10_pubkey_auth.conf  20_disable_root_login.conf

 # cat /etc/ssh/sshd_config.d/10_pubkey_auth.conf 
 # Disable passwords
 PasswordAuthentication no
 ChallengeResponseAuthentication no
 UsePAM no
 # Enable public key
 PubkeyAuthentication yes

 # cat /etc/ssh/sshd_config.d/20_disable_root_login.conf 
 PermitRootLogin no

  The config files are included last in our /etc/ssh/sshd_config file:

 # tail -n 3 /etc/ssh/sshd_config

 # For some reason OpenSSH does not include additional conf files by 
default.
 Include /etc/ssh/sshd_config.d/*.conf

  I dislike modifying /etc/ssh/sshd_config since it will be overwritten
  by the distro. With that said, I modified it without success.

  It really annoys me that we can't secure this service. Something looks
  very broken here.

  -

  # apt-cache show openssh-server
  Package: openssh-server
  Architecture: amd64
  Version: 1:8.2p1-4ubuntu0.2
  Multi-Arch: foreign
  Priority: optional
  Section: net
  Source: openssh
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian OpenSSH Maintainers 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212/+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 1922212] [NEW] SSHD does not honor configuration files

[Jeffrey Walton]

Public bug reported:

I'm working on Ubuntu 20, x86_64, fully patched.

   # lsb_release -a
   Distributor ID:  Ubuntu
   Description: Ubuntu 20.04.2 LTS
   ...

We are seeing reports of failed password-based logins using root:

   jounralctl -xe
   ...
   Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 
49.88.112.77 port 36206 ssh2
   Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 
49.88.112.77 port 36206 ssh2
   ...

There are three attempts every second or two (literally):

   # journalctl -xe | grep -i -c 'Failed password for root'
   324

Our OpenSSH server is configured with both no-password based logins and
no-root logins.

   # ls /etc/ssh/sshd_config.d/
   10_pubkey_auth.conf  20_disable_root_login.conf

   # cat /etc/ssh/sshd_config.d/10_pubkey_auth.conf 
   # Disable passwords
   PasswordAuthentication no
   ChallengeResponseAuthentication no
   UsePAM no
   # Enable public key
   PubkeyAuthentication yes

   # cat /etc/ssh/sshd_config.d/20_disable_root_login.conf 
   PermitRootLogin no

The config files are included last in our /etc/ssh/sshd_config file:

   # tail -n 3 /etc/ssh/sshd_config

   # For some reason OpenSSH does not include additional conf files by default.
   Include /etc/ssh/sshd_config.d/*.conf

I dislike modifying /etc/ssh/sshd_config since it will be overwritten by
the distro. With that said, I modified it without success.

It really annoys me that we can't secure this service. Something looks
very broken here.

-

# apt-cache show openssh-server
Package: openssh-server
Architecture: amd64
Version: 1:8.2p1-4ubuntu0.2
Multi-Arch: foreign
Priority: optional
Section: net
Source: openssh
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian OpenSSH Maintainers 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1922212

Title:
  SSHD does not honor configuration files

Status in openssh package in Ubuntu:
  New

Bug description:
  I'm working on Ubuntu 20, x86_64, fully patched.

 # lsb_release -a
 Distributor ID:Ubuntu
 Description:   Ubuntu 20.04.2 LTS
 ...

  We are seeing reports of failed password-based logins using root:

 jounralctl -xe
 ...
 Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 
49.88.112.77 port 36206 ssh2
 Apr 01 09:08:21 localhost sshd[239302]: Failed password for root from 
49.88.112.77 port 36206 ssh2
 ...

  There are three attempts every second or two (literally):

 # journalctl -xe | grep -i -c 'Failed password for root'
 324

  Our OpenSSH server is configured with both no-password based logins
  and no-root logins.

 # ls /etc/ssh/sshd_config.d/
 10_pubkey_auth.conf  20_disable_root_login.conf

 # cat /etc/ssh/sshd_config.d/10_pubkey_auth.conf 
 # Disable passwords
 PasswordAuthentication no
 ChallengeResponseAuthentication no
 UsePAM no
 # Enable public key
 PubkeyAuthentication yes

 # cat /etc/ssh/sshd_config.d/20_disable_root_login.conf 
 PermitRootLogin no

  The config files are included last in our /etc/ssh/sshd_config file:

 # tail -n 3 /etc/ssh/sshd_config

 # For some reason OpenSSH does not include additional conf files by 
default.
 Include /etc/ssh/sshd_config.d/*.conf

  I dislike modifying /etc/ssh/sshd_config since it will be overwritten
  by the distro. With that said, I modified it without success.

  It really annoys me that we can't secure this service. Something looks
  very broken here.

  -

  # apt-cache show openssh-server
  Package: openssh-server
  Architecture: amd64
  Version: 1:8.2p1-4ubuntu0.2
  Multi-Arch: foreign
  Priority: optional
  Section: net
  Source: openssh
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian OpenSSH Maintainers 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212/+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 1910567] [NEW] Wget cannot download from ftp.gnu.org using Let's Encrypt R3 CA certificate

[Jeffrey Walton]

Public bug reported:

I'm working on Ubuntu 18.05, x86_64, fully patched. The system has been
through both apt-get upgrade and dist-upgrade. The system provides Wget
1.19.4

The program below fails to download from ftp.gnu.org using Let's Encrypt
R3 CA certificate. Let's Encrypt R3 is the issuer for ftp.gnu.org. It is
about the best trust anchor you can choose (sans pinning the host's
public key).

If I use Daniel Stenberg's cacert.pem
(https://curl.haxx.se/docs/caextract.html), then the download succeeds.
I'm not a fan of using the CA Zoo when I know the Issuing CA in advance.
There's no reason to trust every PKI in the world.

If I use a newer version of Wget built with an OpenSSL backend, then the
download succeeds. For example, Wget 1.20.3 and Wget 1.21 with an
OpenSSL backend work fine.

-

$ ./wget-test.sh
Failed to download Ncurses

# Hmm... Add --debug to Wget command
$ ./wget-test.sh
Setting --quiet (quiet) to 1
Setting --quiet (quiet) to 1
Setting --output-document (outputdocument) to ncurses-6.1.tar.gz
Setting --output-document (outputdocument) to ncurses-6.1.tar.gz
Setting --ca-certificate (cacertificate) to lets-encrypt-roots.pem
Setting --ca-certificate (cacertificate) to lets-encrypt-roots.pem
DEBUG output created by Wget 1.19.4 on linux-gnu.

Reading HSTS entries from /home/jwalton/.wget-hsts
URI encoding = ‘UTF-8’
Caching ftp.gnu.org => 209.51.188.20 2001:470:142:3::b
Created socket 4.
Releasing 0x5590bdacd590 (new refcount 1).
Initiating SSL handshake.
Handshake successful; connected socket 4 to SSL handle 0x5590bdad1fd0
certificate:
  subject: CN=ftp.gnu.org
  issuer:  CN=R3,O=Let's Encrypt,C=US
Closed 4/SSL 0x5590bdad1fd0

Failed to download Ncurses

$ cat ./wget-test.sh
#!/usr/bin/env bash

{
# This is the new "Let's Encrypt Authority R3"
# https://letsencrypt.org/certificates/
echo "-BEGIN CERTIFICATE-
MIIFFjCCAv6gAwIBAgIRAJErCErPDBinU/bWLiWnX1owDQYJKoZIhvcNAQELBQAw
TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh
cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwHhcNMjAwOTA0MDAwMDAw
WhcNMjUwOTE1MTYwMDAwWjAyMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNTGV0J3Mg
RW5jcnlwdDELMAkGA1UEAxMCUjMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC7AhUozPaglNMPEuyNVZLD+ILxmaZ6QoinXSaqtSu5xUyxr45r+XXIo9cP
R5QUVTVXjJ6oojkZ9YI8QqlObvU7wy7bjcCwXPNZOOftz2nwWgsbvsCUJCWH+jdx
sxPnHKzhm+/b5DtFUkWWqcFTzjTIUu61ru2P3mBw4qVUq7ZtDpelQDRrK9O8Zutm
NHz6a4uPVymZ+DAXXbpyb/uBxa3Shlg9F8fnCbvxK/eG3MHacV3URuPMrSXBiLxg
Z3Vms/EY96Jc5lP/Ooi2R6X/ExjqmAl3P51T+c8B5fWmcBcUr2Ok/5mzk53cU6cG
/kiFHaFpriV1uxPMUgP17VGhi9sVAgMBAAGjggEIMIIBBDAOBgNVHQ8BAf8EBAMC
AYYwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMBMBIGA1UdEwEB/wQIMAYB
Af8CAQAwHQYDVR0OBBYEFBQusxe3WFbLrlAJQOYfr52LFMLGMB8GA1UdIwQYMBaA
FHm0WeZ7tuXkAXOACIjIGlj26ZtuMDIGCCsGAQUFBwEBBCYwJDAiBggrBgEFBQcw
AoYWaHR0cDovL3gxLmkubGVuY3Iub3JnLzAnBgNVHR8EIDAeMBygGqAYhhZodHRw
Oi8veDEuYy5sZW5jci5vcmcvMCIGA1UdIAQbMBkwCAYGZ4EMAQIBMA0GCysGAQQB
gt8TAQEBMA0GCSqGSIb3DQEBCwUAA4ICAQCFyk5HPqP3hUSFvNVneLKYY611TR6W
PTNlclQtgaDqw+34IL9fzLdwALduO/ZelN7kIJ+m74uyA+eitRY8kc607TkC53wl
ikfmZW4/RvTZ8M6UK+5UzhK8jCdLuMGYL6KvzXGRSgi3yLgjewQtCPkIVz6D2QQz
CkcheAmCJ8MqyJu5zlzyZMjAvnnAT45tRAxekrsu94sQ4egdRCnbWSDtY7kh+BIm
lJNXoB1lBMEKIq4QDUOXoRgffuDghje1WrG9ML+Hbisq/yFOGwXD9RiX8F6sw6W4
avAuvDszue5L3sz85K+EC4Y/wFVDNvZo4TYXao6Z0f+lQKc0t8DQYzk1OXVu8rp2
yJMC6alLbBfODALZvYH7n7do1AZls4I9d1P4jnkDrQoxB3UqQ9hVl3LEKQ73xF1O
yK5GhDDX8oVfGKF5u+decIsH4YaTw7mP3GFxJSqv3+0lUFJoi5Lc5da149p90Ids
hCExroL1+7mryIkXPeFM5TgO9r0rvZaBFOvV2z0gp35Z0+L4WPlbuEjN/lxPFin+
HlUjr8gRsI3qfJOQFy/9rKIJR0Y/8Omwt/8oTWgy1mdeHmmjk7j1nYsvC9JSQ6Zv
MldlTTKB3zhThV1+XWYp6rjd5JW1zbVWEkLNxE7GJThEUG3szgBVGP7pSWTUTsqX
nLRbwHOoq7hHwg==
-END CERTIFICATE-"

# This is the original "Let's Encrypt Authority X3"
# https://letsencrypt.org/certificates/
echo "-BEGIN CERTIFICATE-
MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/
MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT
DkRTVCBSb290IENBIFgzMB4XDTE2MDMxNzE2NDA0NloXDTIxMDMxNzE2NDA0Nlow
SjELMAkGA1UEBhMCVVMxFjAUBgNVBAoTDUxldCdzIEVuY3J5cHQxIzAhBgNVBAMT
GkxldCdzIEVuY3J5cHQgQXV0aG9yaXR5IFgzMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEAnNMM8FrlLke3cl03g7NoYzDq1zUmGSXhvb418XCSL7e4S0EF
q6meNQhY7LEqxGiHC6PjdeTm86dicbp5gWAf15Gan/PQeGdxyGkOlZHP/uaZ6WA8
SMx+yk13EiSdRxta67nsHjcAHJyse6cF6s5K671B5TaYucv9bTyWaN8jKkKQDIZ0
Z8h/pZq4UmEUEz9l6YKHy9v6Dlb2honzhT+Xhq+w3Brvaw2VFn3EK6BlspkENnWA
a6xK8xuQSXgvopZPKiAlKQTGdMDQMc2PMTiVFrqoM7hD8bEfwzB/onkxEz0tNvjj
/PIzark5McWvxI0NHWQWM6r6hCm21AvA2H3DkwIDAQABo4IBfTCCAXkwEgYDVR0T
AQH/BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwfwYIKwYBBQUHAQEEczBxMDIG
CCsGAQUFBzABhiZodHRwOi8vaXNyZy50cnVzdGlkLm9jc3AuaWRlbnRydXN0LmNv
bTA7BggrBgEFBQcwAoYvaHR0cDovL2FwcHMuaWRlbnRydXN0LmNvbS9yb290cy9k
c3Ryb290Y2F4My5wN2MwHwYDVR0jBBgwFoAUxKexpHsscfrb4UuQdf/EFWCFiRAw
VAYDVR0gBE0wSzAIBgZngQwBAgEwPwYLKwYBBAGC3xMBAQEwMDAuBggrBgEFBQcC
ARYiaHR0cDovL2Nwcy5yb290LXgxLmxldHNlbmNyeXB0Lm9yZzA8BgNVHR8ENTAz
MDGgL6AthitodHRwOi8vY3JsLmlkZW50cnVzdC5jb20vRFNUUk9PVENBWDNDUkwu

[Touch-packages] [Bug 1881859] Re: RaspberryPi and "openssl:Error: 'rehash' is an invalid command"

[Jeffrey Walton]

I think I incorrectly filed this against OpenSSL. I think it should be
the ca-certificates  package.

** Package changed: openssl (Ubuntu) => ca-certificates (Ubuntu)

** Description changed:

  Hi Everyone,
  
  I ran dist-upgrade today on my RPI-3. It resulted in:
  
  ```
  Calculating upgrade... Done
  The following packages will be upgraded:
-   armbian-bionic-desktop armbian-config armbian-firmware ca-certificates
-   chromium-browser chromium-chromedriver chromium-codecs-ffmpeg-extra
-   python3-software-properties software-properties-common
+   armbian-bionic-desktop armbian-config armbian-firmware ca-certificates
+   chromium-browser chromium-chromedriver chromium-codecs-ffmpeg-extra
+   python3-software-properties software-properties-common
  9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  ```
  
  And:
  
  ```
  ...
  Setting up chromium-codecs-ffmpeg-extra (83.0.4103.61-0ubuntu0.18.04.1) ...
  Setting up python3-software-properties (0.96.24.32.13) ...
  Setting up ca-certificates (20190110~18.04.1) ...
  Updating certificates in /etc/ssl/certs...
  openssl:Error: 'rehash' is an invalid command.
  
  Standard commands
  asn1parse caciphers   cms
  crl   crl2pkcs7 dgst  dh
  dhparam   dsa   dsaparam  ec
  ...
  
  127 added, 8 removed; done.
  Setting up software-properties-common (0.96.24.32.13) ...
  Setting up chromium-browser (83.0.4103.61-0ubuntu0.18.04.1) ...
  ```
  
  Operating System:
  
  ```
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  ```
  
  
  And finally:
  
  ```
+ $ apt-cache show ca-certificates
+ Package: ca-certificates
+ Architecture: all
+ Version: 20190110~18.04.1
+ Multi-Arch: foreign
+ Priority: important
+ Section: misc
+ Origin: Ubuntu
+ Maintainer: Ubuntu Developers 
+ Original-Maintainer: Michael Shuler 
+ Bugs: https://bugs.launchpad.net/ubuntu/+filebug
+ Installed-Size: 382
+ Depends: openssl (>= 1.1.0), debconf (>= 0.5) | debconf-2.0
+ Breaks: ca-certificates-java (<< 20121112+nmu1)
+ Enhances: openssl
+ Filename: pool/main/c/ca-certificates/ca-certificates_20190110~18.04.1_all.deb
+ Size: 145500
+ MD5sum: f0c73db6f5e857f13af04aaa736f87f0
+ SHA1: 8a3d4583491b426691a986ef11b1c805c2d4cf54
+ SHA256: fcfa84619207690491a3f9ab898de3fb2d46eeb7a73d525b91d05e7655815f5b
+ Description: Common CA certificates
+ Description-md5: e867d2a359bea1800b5bff209fc65bd1
+ Task: minimal
+ Supported: 5y
+ 
+ Package: ca-certificates
+ Architecture: all
+ Version: 20180409
+ Multi-Arch: foreign
+ Priority: important
+ Section: misc
+ Origin: Ubuntu
+ Maintainer: Ubuntu Developers 
+ Original-Maintainer: Michael Shuler 
+ Bugs: https://bugs.launchpad.net/ubuntu/+filebug
+ Installed-Size: 392
+ Depends: openssl (>= 1.1.0), debconf (>= 0.5) | debconf-2.0
+ Breaks: ca-certificates-java (<< 20121112+nmu1)
+ Enhances: openssl
+ Filename: pool/main/c/ca-certificates/ca-certificates_20180409_all.deb
+ Size: 150932
+ MD5sum: eae40792673dcb994af86284d0a01f36
+ SHA1: 8ac5ac1506810b0483f0b80b0652071348459fc4
+ SHA256: 195ffe05ae7d060146f890b1db225f5e8c3a8c505ffbea1fba30a520a1cd58d8
+ Description: Common CA certificates
+ Description-md5: e867d2a359bea1800b5bff209fc65bd1
+ Task: minimal
+ Supported: 5y
+ 
+ 
  $ apt-cache show openssl
  Package: openssl
  Architecture: armhf
  Version: 1.1.1-1ubuntu2.1~18.04.6
  Multi-Arch: foreign
  Priority: important
  Section: utils
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian OpenSSL Team 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 986
  Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.1)
  Suggests: ca-certificates
  Filename: pool/main/o/openssl/openssl_1.1.1-1ubuntu2.1~18.04.6_armhf.deb
  Size: 589160
  MD5sum: 37a31fce651134a5b057c9f6f356aaf2
  SHA1: 476816221f03bae71ecd760e1e4e6d155f85e7c1
  SHA256: 2787b66aba181e230f36ce49600b3a7d9dea7695aa332da0496a5e1a62281d39
  Homepage: https://www.openssl.org/
  Description: Secure Sockets Layer toolkit - cryptographic utility
  Description-md5: 9b6de2bb6e1d9016aeb0f00bcf6617bd
  Task: minimal
  Supported: 5y
  
  Package: openssl
  Architecture: armhf
  Version: 1.1.0g-2ubuntu4
  Multi-Arch: foreign
  Priority: important
  Section: utils
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian OpenSSL Team 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 883
  Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.0)
  Suggests: ca-certificates
  Filename: pool/main/o/openssl/openssl_1.1.0g-2ubuntu4_armhf.deb
  Size: 509616
  MD5sum: 0645cdd015e63ab37fcebf6b5c81b823
  SHA1: 89852170f97d4dc2e6a0e83b045318fd05342634
  SHA256: 57adec97bf6dec47c6079ea8b94598e853334e99c88c5e86afa838cbc57fcd32
  Homepage: https://www.openssl.org/
  Description: Secure Sockets Layer 

[Touch-packages] [Bug 1881859] [NEW] RaspberryPi and "openssl:Error: 'rehash' is an invalid command"

[Jeffrey Walton]

Public bug reported:

Hi Everyone,

I ran dist-upgrade today on my RPI-3. It resulted in:

```
Calculating upgrade... Done
The following packages will be upgraded:
  armbian-bionic-desktop armbian-config armbian-firmware ca-certificates
  chromium-browser chromium-chromedriver chromium-codecs-ffmpeg-extra
  python3-software-properties software-properties-common
9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
```

And:

```
...
Setting up chromium-codecs-ffmpeg-extra (83.0.4103.61-0ubuntu0.18.04.1) ...
Setting up python3-software-properties (0.96.24.32.13) ...
Setting up ca-certificates (20190110~18.04.1) ...
Updating certificates in /etc/ssl/certs...
openssl:Error: 'rehash' is an invalid command.

Standard commands
asn1parse caciphers   cms
crl   crl2pkcs7 dgst  dh
dhparam   dsa   dsaparam  ec
...

127 added, 8 removed; done.
Setting up software-properties-common (0.96.24.32.13) ...
Setting up chromium-browser (83.0.4103.61-0ubuntu0.18.04.1) ...
```

Operating System:

```
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename:   bionic
```


And finally:

```
$ apt-cache show openssl
Package: openssl
Architecture: armhf
Version: 1.1.1-1ubuntu2.1~18.04.6
Multi-Arch: foreign
Priority: important
Section: utils
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian OpenSSL Team 

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 986
Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.1)
Suggests: ca-certificates
Filename: pool/main/o/openssl/openssl_1.1.1-1ubuntu2.1~18.04.6_armhf.deb
Size: 589160
MD5sum: 37a31fce651134a5b057c9f6f356aaf2
SHA1: 476816221f03bae71ecd760e1e4e6d155f85e7c1
SHA256: 2787b66aba181e230f36ce49600b3a7d9dea7695aa332da0496a5e1a62281d39
Homepage: https://www.openssl.org/
Description: Secure Sockets Layer toolkit - cryptographic utility
Description-md5: 9b6de2bb6e1d9016aeb0f00bcf6617bd
Task: minimal
Supported: 5y

Package: openssl
Architecture: armhf
Version: 1.1.0g-2ubuntu4
Multi-Arch: foreign
Priority: important
Section: utils
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian OpenSSL Team 

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 883
Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.0)
Suggests: ca-certificates
Filename: pool/main/o/openssl/openssl_1.1.0g-2ubuntu4_armhf.deb
Size: 509616
MD5sum: 0645cdd015e63ab37fcebf6b5c81b823
SHA1: 89852170f97d4dc2e6a0e83b045318fd05342634
SHA256: 57adec97bf6dec47c6079ea8b94598e853334e99c88c5e86afa838cbc57fcd32
Homepage: https://www.openssl.org/
Description: Secure Sockets Layer toolkit - cryptographic utility
Description-md5: 9b6de2bb6e1d9016aeb0f00bcf6617bd
Task: minimal
Supported: 5y
```

** Affects: openssl (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1881859

Title:
  RaspberryPi and "openssl:Error: 'rehash' is an invalid command"

Status in openssl package in Ubuntu:
  New

Bug description:
  Hi Everyone,

  I ran dist-upgrade today on my RPI-3. It resulted in:

  ```
  Calculating upgrade... Done
  The following packages will be upgraded:
armbian-bionic-desktop armbian-config armbian-firmware ca-certificates
chromium-browser chromium-chromedriver chromium-codecs-ffmpeg-extra
python3-software-properties software-properties-common
  9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  ```

  And:

  ```
  ...
  Setting up chromium-codecs-ffmpeg-extra (83.0.4103.61-0ubuntu0.18.04.1) ...
  Setting up python3-software-properties (0.96.24.32.13) ...
  Setting up ca-certificates (20190110~18.04.1) ...
  Updating certificates in /etc/ssl/certs...
  openssl:Error: 'rehash' is an invalid command.

  Standard commands
  asn1parse caciphers   cms
  crl   crl2pkcs7 dgst  dh
  dhparam   dsa   dsaparam  ec
  ...

  127 added, 8 removed; done.
  Setting up software-properties-common (0.96.24.32.13) ...
  Setting up chromium-browser (83.0.4103.61-0ubuntu0.18.04.1) ...
  ```

  Operating System:

  ```
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  ```
  

  And finally:

  ```
  $ apt-cache show openssl
  Package: openssl
  Architecture: armhf
  Version: 1.1.1-1ubuntu2.1~18.04.6
  Multi-Arch: foreign
  Priority: important
  Section: utils
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian OpenSSL Team 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 986
  Depends: libc6 

[Touch-packages] [Bug 1880450] [NEW] Unmet package dependency "xserver-xorg-core (>= 2:1.17.2-2)"

[Jeffrey Walton]

Public bug reported:

I'm using Ubuntu 18.04 x86_64 (fully patched) on a Dell XPS 8930
(https://www.amazon.com/gp/product/B078N85NCR). I recently performed a
dist-upgrade to 5.3.0-53-generic. After the upgrade I lost X in non-
recovery mode. In recovery mode I get a GUI at 800x600. 800x600 leaves a
lot to be desired with a 32" monitor.

I reinstalled the kernel components with no joy. Secure Boot is Off.
Reboots did not help. The kernel components were:

* linux-headers-5.3.0-53-generic
* linux-image-5.3.0-53-generic
* linux-modules-5.3.0-53-generic
* linux-modules-extra-5.3.0-53-generic
* linux-tools-5.3.0-53-generic

I tried the Nvidia drivers 435 and 440 with no joy. Reboots did not
help.

I then removed the Nvidia drivers, and I tried the default Xorg server,
but it errors with the following. Reboots did not help.

# apt-get install xserver-xorg-video-nouveau nouveau-firmware
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xserver-xorg-video-nouveau : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
E: Unable to correct problems, you have held broken packages.

I'm not sure which package is the problem here. I generically filed the
report against Xorg, but I suspect there's a better choice of package.
(There is no xserver-xorg-core package available to select).

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  I'm using Ubuntu 18.04 x86_64 (fully patched) on a Dell XPS 8930
  (https://www.amazon.com/gp/product/B078N85NCR). I recently performed a
  dist-upgrade to 5.3.0-53-generic. After the upgrade I lost X in non-
  recovery mode. In recovery mode I get a GUI at 480x320 or 640x480 (if I
  am estimating it correctly).
  
- I reinstalled the kernel components with no joy. I tried the Nvisia
+ I reinstalled the kernel components with no joy. I tried the Nvidia
  drivers 435 and 440 with no joy. I tried the default Xorg server, but it
  errors with:
  
  # apt-get install --reinstall xserver-xorg-video-nouveau nouveau-firmware
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
-  xserver-xorg-video-nouveau : Depends: xorg-video-abi-23
-   Depends: xserver-xorg-core (>= 2:1.18.99.901)
+  xserver-xorg-video-nouveau : Depends: xorg-video-abi-23
+   Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.
+ 
+ I'm not sure which package is the problem here. I generically filled it
+ against Xorg, but I suspect there's a better choice of package.

** Description changed:

  I'm using Ubuntu 18.04 x86_64 (fully patched) on a Dell XPS 8930
  (https://www.amazon.com/gp/product/B078N85NCR). I recently performed a
  dist-upgrade to 5.3.0-53-generic. After the upgrade I lost X in non-
  recovery mode. In recovery mode I get a GUI at 480x320 or 640x480 (if I
  am estimating it correctly).
  
  I reinstalled the kernel components with no joy. I tried the Nvidia
- drivers 435 and 440 with no joy. I tried the default Xorg server, but it
- errors with:
+ drivers 435 and 440 with no joy. Reboots did not help.
+ 
+ I then removed the Nvidia drivers, and I tried the default Xorg server,
+ but it errors with the following. Reboots did not help.
  
  # apt-get install --reinstall xserver-xorg-video-nouveau nouveau-firmware
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   xserver-xorg-video-nouveau : Depends: xorg-video-abi-23
    Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.
  
  I'm not sure which package is the problem here. I generically filled it
  against Xorg, but I suspect there's a better choice of package.

** 

[Touch-packages] [Bug 1853618] [NEW] Sphix cannot find data files

[Jeffrey Walton]

Public bug reported:

I'm working on Ubuntu 18.04 x86_64 (fully patched). According to CMU
tutorial on PocketSphinx
(https://cmusphinx.github.io/wiki/tutorialpocketsphinx/), we can test
PocketSphinx with:

pocketsphinx_continuous -inmic yes

When I attempt to run pocketsphinx_continuous on Ubuntu 18.04, the
program eventually exits:

INFO: feat.c(715): Initializing feature stream to type: '1s_c_d_dd', ceplen=13, 
CMN='batch', VARNORM='no', AGC='none'
ERROR: "acmod.c", line 80: Acoustic model definition is not specified either 
with -mdef option or with -hmm

However, the same programs runs fine on Fedora 31:

INFO: feat.c(713): Initializing feature stream to type: '1s_c_d_dd', ceplen=13, 
CMN='batch', VARNORM='no', AGC='none'
INFO: acmod.c(161): Using subvector specification 0-12/13-25/26-38
...

INFO: continuous.c(252): Ready

I think the Ubuntu configuration can be improved. I'm not sure what the
config differences are between Fedora and Ubuntu, but Ubuntu seems to
lack some directory structure (present on Fedora):

$ ls /usr/share/pocketsphinx/model/en-us/
ls: cannot access '/usr/share/pocketsphinx/model/en-us/': No such file or 
directory

$ ls /usr/share/pocketsphinx/model/en-us/en-us/feat.params
ls: cannot access '/usr/share/pocketsphinx/model/en-us/en-us/feat.params': No 
such file or directory

$ ls /usr/share/pocketsphinx/model/en-us/cmudict-en-us.dict
ls: cannot access '/usr/share/pocketsphinx/model/en-us/cmudict-en-us.dict': No 
such file or directory

==

I believe all of the relevant packages are installed on Ubuntu:

pocketsphinx libsphinxbase-dev libpocketsphinx-dev sphinx-voxforge-
hmm-en sphinx-voxforge-lm-en

==

Ubuntu 18.04 startup:

$ pocketsphinx_continuous -inmic yes
Current configuration:
[NAME]  [DEFLT] [VALUE]
-agcnonenone
-agcthresh  2.0 2.00e+00
-allphone   
-allphone_cino  no
-alpha  0.979.70e-01
-ascale 20.02.00e+01
-aw 1   1
-backtrace  no  no
-beam   1e-48   1.00e-48
-bestpath   yes yes
-bestpathlw 9.5 9.50e+00
-ceplen 13  13
-cmncurrent current
-cmninit8.0 8.0
-compallsen no  no
-debug  0
-dict   
-dictcase   no  no
-dither no  no
-doublebw   no  no
-ds 1   1
-fdict  
-feat   1s_c_d_dd   1s_c_d_dd
-featparams 
-fillprob   1e-81.00e-08
-frate  100 100
-fsg
-fsgusealtpron  yes yes
-fsgusefiller   yes yes
-fwdflatyes yes
-fwdflatbeam1e-64   1.00e-64
-fwdflatefwid   4   4
-fwdflatlw  8.5 8.50e+00
-fwdflatsfwin   25  25
-fwdflatwbeam   7e-29   7.00e-29
-fwdtreeyes yes
-hmm
-input_endian   little  little
-jsgf   
-keyphrase  
-kws
-kws_delay  10  10
-kws_plp1e-11.00e-01
-kws_threshold  1   1.00e+00
-latsize50005000
-lda
-ldadim 0   0
-lifter 0   0
-lm 
-lmctl  
-lmname 
-logbase1.0001  1.000100e+00
-logfn  
-logspecno  no
-lowerf 133.4   1.33e+02
-lpbeam 1e-40   1.00e-40
-lponlybeam 7e-29   7.00e-29
-lw 6.5 6.50e+00
-maxhmmpf   3   3
-maxwpf -1  -1
-mdef   
-mean   
-mfclogdir  
-min_endfr  0   0
-mixw   
-mixwfloor  0.001   1.00e-07
-mllr   
-mmap   yes yes
-ncep

[Touch-packages] [Bug 1741698] Re: DNS break after Artful/17.10 upgrade

[Jeffrey Walton]

The following does not help per https://askubuntu.com/questions/966870
/dns-not-working-after-upgrade-17-04-to-17-10

$ sudo rm /etc/resolv.conf
$ sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf
$ sudo systemctl restart resolvconf

-- 
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/1741698

Title:
  DNS break after Artful/17.10 upgrade

Status in systemd package in Ubuntu:
  New

Bug description:
  I was running Zesty/17.04. I upgraded to Artful/17.10 over SSH using
  upgrade-manager. Priot to upgrade everything worked fine using DHCP.
  After reboot name resolution broke. I understand Systemd is now the
  resolver.

  A lot of people are suffering https://askubuntu.com/questions/966870
  /dns-not-working-after-upgrade-17-04-to-17-10 . It looks like a mix of
  Network Manager problems and Systemd problems.

  This looks like a similar report, but comment 20 says to file a new
  bug. https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840
  .

  Something is missing in the upgrade scripts. I don't know what, but it
  would be nice if it was fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741698/+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 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

[Jeffrey Walton]

Ping...

-- 
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/1725840

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+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 1741698] Re: DNS break after Artful/17.10 upgrade

[Jeffrey Walton]

Running 'dpkg-reconfigure resolvconf' per comment 9 at
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840 did
not help.

-- 
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/1741698

Title:
  DNS break after Artful/17.10 upgrade

Status in systemd package in Ubuntu:
  New

Bug description:
  I was running Zesty/17.04. I upgraded to Artful/17.10 over SSH using
  upgrade-manager. Priot to upgrade everything worked fine using DHCP.
  After reboot name resolution broke. I understand Systemd is now the
  resolver.

  A lot of people are suffering https://askubuntu.com/questions/966870
  /dns-not-working-after-upgrade-17-04-to-17-10 . It looks like a mix of
  Network Manager problems and Systemd problems.

  This looks like a similar report, but comment 20 says to file a new
  bug. https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840
  .

  Something is missing in the upgrade scripts. I don't know what, but it
  would be nice if it was fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741698/+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 1741698] [NEW] DNS break after Artful/17.10 upgrade

[Jeffrey Walton]

Public bug reported:

I was running Zesty/17.04. I upgraded to Artful/17.10 over SSH using
upgrade-manager. Priot to upgrade everything worked fine using DHCP.
After reboot name resolution broke. I understand Systemd is now the
resolver.

A lot of people are suffering https://askubuntu.com/questions/966870
/dns-not-working-after-upgrade-17-04-to-17-10 . It looks like a mix of
Network Manager problems and Systemd problems.

This looks like a similar report, but comment 20 says to file a new bug.
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840 .

Something is missing in the upgrade scripts. I don't know what, but it
would be nice if it was fixed.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1741698

Title:
  DNS break after Artful/17.10 upgrade

Status in systemd package in Ubuntu:
  New

Bug description:
  I was running Zesty/17.04. I upgraded to Artful/17.10 over SSH using
  upgrade-manager. Priot to upgrade everything worked fine using DHCP.
  After reboot name resolution broke. I understand Systemd is now the
  resolver.

  A lot of people are suffering https://askubuntu.com/questions/966870
  /dns-not-working-after-upgrade-17-04-to-17-10 . It looks like a mix of
  Network Manager problems and Systemd problems.

  This looks like a similar report, but comment 20 says to file a new
  bug. https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840
  .

  Something is missing in the upgrade scripts. I don't know what, but it
  would be nice if it was fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741698/+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 1698704] Re: NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/zesty

[Jeffrey Walton]

According to https://askubuntu.com/questions/493460/how-to-install-add-
apt-repository-using-the-terminal, 'add-apt-repository' may be part of
python-software-properties.

However, searching for add-apt-repository results in no hits. I'm not
sure what package it truly belongs to:

goldmont$ apt-cache search add-apt-repository
goldmont$

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1698704

Title:
  NoDistroTemplateException: Error: could not find a distribution
  template for Ubuntu/zesty

Status in apt package in Ubuntu:
  New

Bug description:
  I'm trying to get GCC 7 on a machine to test C++17 and std::byte.
  According to https://askubuntu.com/questions/859256/how-to-install-
  gcc-7-or-clang-4-0:

  $ sudo add-apt-repository ppa:ubuntu-toolchain-r/test
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 95, in 
  sp = SoftwareProperties(options=options)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
114, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
607, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 89, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/zesty

  **

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04
  Codename:   zesty

  $ uname -a
  Linux goldmont 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1698704/+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 1698704] [NEW] NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/zesty

[Jeffrey Walton]

Public bug reported:

I'm trying to get GCC 7 on a machine to test C++17 and std::byte.
According to https://askubuntu.com/questions/859256/how-to-install-gcc-7
-or-clang-4-0:

$ sudo add-apt-repository ppa:ubuntu-toolchain-r/test
Traceback (most recent call last):
  File "/usr/bin/add-apt-repository", line 95, in 
sp = SoftwareProperties(options=options)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
114, in __init__
self.reload_sourceslist()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
607, in reload_sourceslist
self.distro.get_sources(self.sourceslist)
  File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 89, in 
get_sources
(self.id, self.codename))
aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/zesty

**

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04
Codename:   zesty

$ uname -a
Linux goldmont 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1698704

Title:
  NoDistroTemplateException: Error: could not find a distribution
  template for Ubuntu/zesty

Status in apt package in Ubuntu:
  New

Bug description:
  I'm trying to get GCC 7 on a machine to test C++17 and std::byte.
  According to https://askubuntu.com/questions/859256/how-to-install-
  gcc-7-or-clang-4-0:

  $ sudo add-apt-repository ppa:ubuntu-toolchain-r/test
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 95, in 
  sp = SoftwareProperties(options=options)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
114, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
607, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 89, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/zesty

  **

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04
  Codename:   zesty

  $ uname -a
  Linux goldmont 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1698704/+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 1670096] Re: objdump fails to disassemble rdrand

[Jeffrey Walton]

The disassembly of rdrand looks ok in 2.26.1-1ubuntu1~16.04.3.

Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1670096

Title:
  objdump fails to disassemble rdrand

Status in binutils package in Ubuntu:
  New

Bug description:
  `objdump --disassemble` is not producing expected output for the
  rdrand instruction. The same test using rdseed appears to be ok.

  $ cat test.S
  globalNASM_RDRAND
  section   .text
  align 16

  NASM_RDRAND:
  rdrand rax
  jnc NASM_RDRAND
  ret

  $ nasm -f elf64 test.S -o test.o

  $ objdump --disassemble test.o

  test.o: file format elf64-x86-64

  Disassembly of section .text:

   :
 0:   48 0f 07sysretq
 3:   f0 73 falock jae 0 
 6:   c3  retq

  

  $ objdump -v
  GNU objdump (GNU Binutils for Ubuntu) 2.26.1
  Copyright (C) 2015 Free Software Foundation, Inc.

  $ uname -a
  Linux qotom 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  

  $ apt-cache show binutils
  Package: binutils
  Priority: optional
  Section: devel
  Installed-Size: 13328
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Matthias Klose 
  Architecture: amd64
  Version: 2.26.1-1ubuntu1~16.04.3
  Replaces: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
  Provides: binutils-gold, elf-binutils
  Depends: libc6 (>= 2.14), zlib1g (>= 1:1.2.0)
  Suggests: binutils-doc (>= 2.26.1-1ubuntu1~16.04.3)
  Conflicts: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3), 
elf-binutils, gas, modutils (<< 2.4.19-1)
  Breaks: binutils-mingw-w64-i686 (<< 2.23.52.20130612-1+3), 
binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
  Filename: pool/main/b/binutils/binutils_2.26.1-1ubuntu1~16.04.3_amd64.deb
  Size: 2310310
  MD5sum: 04b00c4b3ba1d86afbb679b63476d05a
  SHA1: d15740302cd64dea8d4d853aa660b0bba3bb9105
  SHA256: 1db714433416a0d9bd49f1174e85b55f65597fe337116267ad5ad16fc7f3e2dd
  Description-en: GNU assembler, linker and binary utilities
   The programs in this package are used to assemble, link and manipulate
   binary and object files.  They may be used in conjunction with a compiler
   and various libraries to build programs.
  Description-md5: fde49b4cfeaad346a6e094f973da28d7
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Build-Essential: yes
  Origin: Ubuntu
  Supported: 5y
  Task: ubuntu-desktop, ubuntu-usb, kubuntu-desktop, kubuntu-full, 
edubuntu-desktop, edubuntu-usb, xubuntu-core, xubuntu-desktop, 
mythbuntu-frontend, mythbuntu-desktop, mythbuntu-backend-slave, 
mythbuntu-backend-master, mythbuntu-backend-master, lubuntu-live, 
ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntu-gnome-desktop, 
ubuntu-touch, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, 
ubuntu-mate-cloudtop

  Package: binutils
  Priority: optional
  Section: devel
  Installed-Size: 13332
  Maintainer: Ubuntu Core developers 
  Original-Maintainer: Matthias Klose 
  Architecture: amd64
  Version: 2.26-8ubuntu2
  Replaces: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
  Provides: binutils-gold, elf-binutils
  Depends: libc6 (>= 2.14), zlib1g (>= 1:1.2.0)
  Suggests: binutils-doc (>= 2.26-8ubuntu2)
  Conflicts: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3), 
elf-binutils, gas, modutils (<< 2.4.19-1)
  Breaks: binutils-mingw-w64-i686 (<< 2.23.52.20130612-1+3), 
binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
  Filename: pool/main/b/binutils/binutils_2.26-8ubuntu2_amd64.deb
  Size: 2302996
  MD5sum: 94899981678c27e438f85e554746deff
  SHA1: 3197b042645a7ee607391f873a4f7012d888bf3c
  SHA256: 053b01a92bdb39329c199e85a621910a9d81ad4ec9d65d9e7e59ff4ab2709d55
  Description-en: GNU assembler, linker and binary utilities
   The programs in this package are used to assemble, link and manipulate
   binary and object files.  They may be used in conjunction with a compiler
   and various libraries to build programs.
  Description-md5: fde49b4cfeaad346a6e094f973da28d7
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Build-Essential: yes
  Origin: Ubuntu
  Supported: 5y
  Task: 

[Touch-packages] [Bug 1670096] [NEW] objdump fails to disassemble rdrand

[Jeffrey Walton]

Public bug reported:

`objdump --disassemble` is not producing expected output for the rdrand
instruction. The same test using rdseed appears to be ok.

$ cat test.S
globalNASM_RDRAND
section   .text
align 16

NASM_RDRAND:
rdrand rax
jnc NASM_RDRAND
ret

$ nasm -f elf64 test.S -o test.o

$ objdump --disassemble test.o

test.o: file format elf64-x86-64

Disassembly of section .text:

 :
   0:   48 0f 07sysretq
   3:   f0 73 falock jae 0 
   6:   c3  retq



$ objdump -v
GNU objdump (GNU Binutils for Ubuntu) 2.26.1
Copyright (C) 2015 Free Software Foundation, Inc.

$ uname -a
Linux qotom 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:   xenial



$ apt-cache show binutils
Package: binutils
Priority: optional
Section: devel
Installed-Size: 13328
Maintainer: Ubuntu Developers 
Original-Maintainer: Matthias Klose 
Architecture: amd64
Version: 2.26.1-1ubuntu1~16.04.3
Replaces: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
Provides: binutils-gold, elf-binutils
Depends: libc6 (>= 2.14), zlib1g (>= 1:1.2.0)
Suggests: binutils-doc (>= 2.26.1-1ubuntu1~16.04.3)
Conflicts: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3), 
elf-binutils, gas, modutils (<< 2.4.19-1)
Breaks: binutils-mingw-w64-i686 (<< 2.23.52.20130612-1+3), 
binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
Filename: pool/main/b/binutils/binutils_2.26.1-1ubuntu1~16.04.3_amd64.deb
Size: 2310310
MD5sum: 04b00c4b3ba1d86afbb679b63476d05a
SHA1: d15740302cd64dea8d4d853aa660b0bba3bb9105
SHA256: 1db714433416a0d9bd49f1174e85b55f65597fe337116267ad5ad16fc7f3e2dd
Description-en: GNU assembler, linker and binary utilities
 The programs in this package are used to assemble, link and manipulate
 binary and object files.  They may be used in conjunction with a compiler
 and various libraries to build programs.
Description-md5: fde49b4cfeaad346a6e094f973da28d7
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Build-Essential: yes
Origin: Ubuntu
Supported: 5y
Task: ubuntu-desktop, ubuntu-usb, kubuntu-desktop, kubuntu-full, 
edubuntu-desktop, edubuntu-usb, xubuntu-core, xubuntu-desktop, 
mythbuntu-frontend, mythbuntu-desktop, mythbuntu-backend-slave, 
mythbuntu-backend-master, mythbuntu-backend-master, lubuntu-live, 
ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntu-gnome-desktop, 
ubuntu-touch, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, 
ubuntu-mate-cloudtop

Package: binutils
Priority: optional
Section: devel
Installed-Size: 13332
Maintainer: Ubuntu Core developers 
Original-Maintainer: Matthias Klose 
Architecture: amd64
Version: 2.26-8ubuntu2
Replaces: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
Provides: binutils-gold, elf-binutils
Depends: libc6 (>= 2.14), zlib1g (>= 1:1.2.0)
Suggests: binutils-doc (>= 2.26-8ubuntu2)
Conflicts: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3), 
elf-binutils, gas, modutils (<< 2.4.19-1)
Breaks: binutils-mingw-w64-i686 (<< 2.23.52.20130612-1+3), 
binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
Filename: pool/main/b/binutils/binutils_2.26-8ubuntu2_amd64.deb
Size: 2302996
MD5sum: 94899981678c27e438f85e554746deff
SHA1: 3197b042645a7ee607391f873a4f7012d888bf3c
SHA256: 053b01a92bdb39329c199e85a621910a9d81ad4ec9d65d9e7e59ff4ab2709d55
Description-en: GNU assembler, linker and binary utilities
 The programs in this package are used to assemble, link and manipulate
 binary and object files.  They may be used in conjunction with a compiler
 and various libraries to build programs.
Description-md5: fde49b4cfeaad346a6e094f973da28d7
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Build-Essential: yes
Origin: Ubuntu
Supported: 5y
Task: ubuntu-desktop, ubuntu-usb, kubuntu-desktop, kubuntu-full, 
edubuntu-desktop, edubuntu-usb, xubuntu-core, xubuntu-desktop, 
mythbuntu-frontend, mythbuntu-desktop, mythbuntu-backend-slave, 
mythbuntu-backend-master, mythbuntu-backend-master, lubuntu-live, 
ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntu-gnome-desktop, 
ubuntu-touch, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, 
ubuntu-mate-cloudtop

** Affects: binutils (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug 

[Touch-packages] [Bug 1616729] Re: Clang 3.5 only advertises SSE2

[Jeffrey Walton]

This appears to be a Ubuntu issue. On a Debian 8 system with Clang 3.5
installed, I get the following, which seems to indicate Debian has
remediated the issue:

$ clang++ -march=native -dM -E - https://bugs.launchpad.net/bugs/1616729

Title:
  Clang 3.5 only advertises SSE2

Status in llvm-toolchain-3.4 package in Ubuntu:
  New

Bug description:
  I'm working on a 5th generation Core i5 (see /proc/cpuinfo below). The
  CPU offers SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, RDRAND, RDSEED,
  etc.

  After installing Clang 3.5, the compiler claims SSE2 is all that is
  available:

  $ clang++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE_MATH__ 1

  $ g++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __AES__ 1
  #define __AVX__ 1
  #define __AVX2__ 1
  #define __BMI__ 1
  #define __BMI2__ 1
  #define __core_avx2 1
  #define __core_avx2__ 1
  #define __RDRND__ 1
  #define __RDSEED__ 1
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE3__ 1
  #define __SSE4_1__ 1
  #define __SSE4_2__ 1
  #define __SSE_MATH__ 1
  #define __SSSE3__ 1

  

  This is nearly the same report as "Clang 3.4 only advertises SSE2",
  http://bugs.launchpad.net/ubuntu/+source/llvm-
  toolchain-3.4/+bug/1616723.

  A separate report was provided in case they get worked separately.

  

  $ cat /proc/cpuinfo
  processor : 0
  vendor_id : GenuineIntel
  cpu family : 6
  model : 61
  model name : Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
  stepping : 4
  microcode : 0x16
  cpu MHz : 800.058
  cache size : 3072 KB
  physical id : 0
  siblings : 4
  core id : 0
  cpu cores : 2
  apicid : 0
  initial apicid : 0
  fpu : yes
  fpu_exception : yes
  cpuid level : 20
  wp : yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp 
lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 
fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer 
aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm 
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep 
bmi2 erms invpcid rtm rdseed adx smap xsaveopt
  ...

  

  $ uname -a
  Linux qotom 3.19.0-66-generic #74~14.04.1-Ubuntu SMP Tue Jul 19 19:56:11 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 14.04.5 LTS
  Release: 14.04
  Codename: trusty

  $ clang -v
  Ubuntu clang version 3.5.0-4ubuntu2~trusty2 (tags/RELEASE_350/final) (based 
on LLVM 3.5.0)

  $ dpkg -l clang-3.5
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  clang-3.5  1:3.5-4ubunt amd64C, C++ and Objective-C compiler (

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1616729/+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 1616729] Re: Clang 3.5 only advertises SSE2

[Jeffrey Walton]

> This appears to be a Ubuntu issue. On a Debian 8 system with Clang 3.5
installed, I get the following, which seems to indicate Debian has
remediated the issue...

Regarding Comment 1, the host CPU has the following features. The Clang
defines were consistent with the flags:

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts mmx fxsr sse sse2 ss syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq ssse3 cx16 pcid sse4_1
sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm ida arat epb
xsaveopt pln pts dtherm

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in
Ubuntu.
https://bugs.launchpad.net/bugs/1616729

Title:
  Clang 3.5 only advertises SSE2

Status in llvm-toolchain-3.4 package in Ubuntu:
  New

Bug description:
  I'm working on a 5th generation Core i5 (see /proc/cpuinfo below). The
  CPU offers SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, RDRAND, RDSEED,
  etc.

  After installing Clang 3.5, the compiler claims SSE2 is all that is
  available:

  $ clang++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE_MATH__ 1

  $ g++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __AES__ 1
  #define __AVX__ 1
  #define __AVX2__ 1
  #define __BMI__ 1
  #define __BMI2__ 1
  #define __core_avx2 1
  #define __core_avx2__ 1
  #define __RDRND__ 1
  #define __RDSEED__ 1
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE3__ 1
  #define __SSE4_1__ 1
  #define __SSE4_2__ 1
  #define __SSE_MATH__ 1
  #define __SSSE3__ 1

  

  This is nearly the same report as "Clang 3.4 only advertises SSE2",
  http://bugs.launchpad.net/ubuntu/+source/llvm-
  toolchain-3.4/+bug/1616723.

  A separate report was provided in case they get worked separately.

  

  $ cat /proc/cpuinfo
  processor : 0
  vendor_id : GenuineIntel
  cpu family : 6
  model : 61
  model name : Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
  stepping : 4
  microcode : 0x16
  cpu MHz : 800.058
  cache size : 3072 KB
  physical id : 0
  siblings : 4
  core id : 0
  cpu cores : 2
  apicid : 0
  initial apicid : 0
  fpu : yes
  fpu_exception : yes
  cpuid level : 20
  wp : yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp 
lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 
fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer 
aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm 
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep 
bmi2 erms invpcid rtm rdseed adx smap xsaveopt
  ...

  

  $ uname -a
  Linux qotom 3.19.0-66-generic #74~14.04.1-Ubuntu SMP Tue Jul 19 19:56:11 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 14.04.5 LTS
  Release: 14.04
  Codename: trusty

  $ clang -v
  Ubuntu clang version 3.5.0-4ubuntu2~trusty2 (tags/RELEASE_350/final) (based 
on LLVM 3.5.0)

  $ dpkg -l clang-3.5
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  clang-3.5  1:3.5-4ubunt amd64C, C++ and Objective-C compiler (

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1616729/+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 1616731] [NEW] Clang 3.6 only advertises SSE2

[Jeffrey Walton]

Public bug reported:

I'm working on a 5th generation Core i5 (see /proc/cpuinfo below). The
CPU offers SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, RDRAND, RDSEED, etc.

After installing Clang 3.6, the compiler claims SSE2 is all that is
available:

$ clang++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
#define __SSE__ 1
#define __SSE2__ 1
#define __SSE2_MATH__ 1
#define __SSE_MATH__ 1

$ g++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
#define __AES__ 1
#define __AVX__ 1
#define __AVX2__ 1
#define __BMI__ 1
#define __BMI2__ 1
#define __core_avx2 1
#define __core_avx2__ 1
#define __RDRND__ 1
#define __RDSEED__ 1
#define __SSE__ 1
#define __SSE2__ 1
#define __SSE2_MATH__ 1
#define __SSE3__ 1
#define __SSE4_1__ 1
#define __SSE4_2__ 1
#define __SSE_MATH__ 1
#define __SSSE3__ 1



This is nearly the same report as "Clang 3.4 only advertises SSE2",
http://bugs.launchpad.net/ubuntu/+source/llvm-
toolchain-3.4/+bug/1616723; and "Clang 3.5 only advertises SSE2",
https://bugs.launchpad.net/ubuntu/+source/llvm-
toolchain-3.4/+bug/1616729.

A separate report was provided in case they get worked separately.



$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 61
model name : Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
stepping : 4
microcode : 0x16
cpu MHz : 800.058
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 20
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 
fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer 
aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm 
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep 
bmi2 erms invpcid rtm rdseed adx smap xsaveopt
...



$ uname -a
Linux qotom 3.19.0-66-generic #74~14.04.1-Ubuntu SMP Tue Jul 19 19:56:11 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty

$ clang -v
Ubuntu clang version 3.6.0-2ubuntu1~trusty1 (tags/RELEASE_360/final) (based on 
LLVM 3.6.0)
Target: x86_64-pc-linux-gnu
Thread model: posix

$ dpkg -l clang-3.6
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  clang-3.6  1:3.6-2ubunt amd64C, C++ and Objective-C compiler (

** Affects: llvm-toolchain-3.4 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in
Ubuntu.
https://bugs.launchpad.net/bugs/1616731

Title:
  Clang 3.6 only advertises SSE2

Status in llvm-toolchain-3.4 package in Ubuntu:
  New

Bug description:
  I'm working on a 5th generation Core i5 (see /proc/cpuinfo below). The
  CPU offers SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, RDRAND, RDSEED,
  etc.

  After installing Clang 3.6, the compiler claims SSE2 is all that is
  available:

  $ clang++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE_MATH__ 1

  $ g++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __AES__ 1
  #define __AVX__ 1
  #define __AVX2__ 1
  #define __BMI__ 1
  #define __BMI2__ 1
  #define __core_avx2 1
  #define __core_avx2__ 1
  #define __RDRND__ 1
  #define __RDSEED__ 1
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE3__ 1
  #define __SSE4_1__ 1
  #define __SSE4_2__ 1
  #define __SSE_MATH__ 1
  #define __SSSE3__ 1

  

  This is nearly the same report as "Clang 3.4 only advertises SSE2",
  http://bugs.launchpad.net/ubuntu/+source/llvm-
  toolchain-3.4/+bug/1616723; and "Clang 3.5 only advertises SSE2",
  https://bugs.launchpad.net/ubuntu/+source/llvm-
  toolchain-3.4/+bug/1616729.

  A separate report was provided in case they get worked separately.

  

  $ cat /proc/cpuinfo
  processor : 0
  vendor_id : GenuineIntel
  cpu family : 6
  model : 61
  model name : Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
  stepping : 4
  microcode : 0x16

[Touch-packages] [Bug 1616729] [NEW] Clang 3.5 only advertises SSE2

[Jeffrey Walton]

Public bug reported:

I'm working on a 5th generation Core i5 (see /proc/cpuinfo below). The
CPU offers SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, RDRAND, RDSEED, etc.

After installing Clang 3.5, the compiler claims SSE2 is all that is
available:

$ clang++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
#define __SSE__ 1
#define __SSE2__ 1
#define __SSE2_MATH__ 1
#define __SSE_MATH__ 1

$ g++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
#define __AES__ 1
#define __AVX__ 1
#define __AVX2__ 1
#define __BMI__ 1
#define __BMI2__ 1
#define __core_avx2 1
#define __core_avx2__ 1
#define __RDRND__ 1
#define __RDSEED__ 1
#define __SSE__ 1
#define __SSE2__ 1
#define __SSE2_MATH__ 1
#define __SSE3__ 1
#define __SSE4_1__ 1
#define __SSE4_2__ 1
#define __SSE_MATH__ 1
#define __SSSE3__ 1



This is nearly the same report as "Clang 3.4 only advertises SSE2",
http://bugs.launchpad.net/ubuntu/+source/llvm-
toolchain-3.4/+bug/1616723.

A separate report was provided in case they get worked separately.



$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 61
model name : Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
stepping : 4
microcode : 0x16
cpu MHz : 800.058
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 20
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 
fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer 
aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm 
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep 
bmi2 erms invpcid rtm rdseed adx smap xsaveopt
...



$ uname -a
Linux qotom 3.19.0-66-generic #74~14.04.1-Ubuntu SMP Tue Jul 19 19:56:11 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty

$ clang -v
Ubuntu clang version 3.5.0-4ubuntu2~trusty2 (tags/RELEASE_350/final) (based on 
LLVM 3.5.0)

$ dpkg -l clang-3.5
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  clang-3.5  1:3.5-4ubunt amd64C, C++ and Objective-C compiler (

** Affects: llvm-toolchain-3.4 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in
Ubuntu.
https://bugs.launchpad.net/bugs/1616729

Title:
  Clang 3.5 only advertises SSE2

Status in llvm-toolchain-3.4 package in Ubuntu:
  New

Bug description:
  I'm working on a 5th generation Core i5 (see /proc/cpuinfo below). The
  CPU offers SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, RDRAND, RDSEED,
  etc.

  After installing Clang 3.5, the compiler claims SSE2 is all that is
  available:

  $ clang++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE_MATH__ 1

  $ g++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __AES__ 1
  #define __AVX__ 1
  #define __AVX2__ 1
  #define __BMI__ 1
  #define __BMI2__ 1
  #define __core_avx2 1
  #define __core_avx2__ 1
  #define __RDRND__ 1
  #define __RDSEED__ 1
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE3__ 1
  #define __SSE4_1__ 1
  #define __SSE4_2__ 1
  #define __SSE_MATH__ 1
  #define __SSSE3__ 1

  

  This is nearly the same report as "Clang 3.4 only advertises SSE2",
  http://bugs.launchpad.net/ubuntu/+source/llvm-
  toolchain-3.4/+bug/1616723.

  A separate report was provided in case they get worked separately.

  

  $ cat /proc/cpuinfo
  processor : 0
  vendor_id : GenuineIntel
  cpu family : 6
  model : 61
  model name : Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
  stepping : 4
  microcode : 0x16
  cpu MHz : 800.058
  cache size : 3072 KB
  physical id : 0
  siblings : 4
  core id : 0
  cpu cores : 2
  apicid : 0
  initial apicid : 0
  fpu : yes
  fpu_exception : yes
  cpuid level : 20
  wp : yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 

[Touch-packages] [Bug 1616723] Re: Clang 3.4 only advertises SSE2

[Jeffrey Walton]

I think this is related from LLVM: "Issue 20213 - clang-cl doesn't
support SSSE3", http://llvm.org/bugs/show_bug.cgi?id=20213. I can't find
a Debian report at the moment.

I was always aware there was some trouble due to working with OS X. I
was not aware it was this bad. I did not realize there was no Lauchpad
reports or remediations in place.

** Bug watch added: LLVM #20213
   https://llvm.org/bugs/show_bug.cgi?id=20213

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in
Ubuntu.
https://bugs.launchpad.net/bugs/1616723

Title:
  Clang 3.4 only advertises SSE2

Status in llvm-toolchain-3.4 package in Ubuntu:
  New

Bug description:
  I'm working on a 5th generation Core i5 (see /proc/cpuinfo below). The
  CPU offers SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, RDRAND, RDSEED,
  etc.

  Ubuntu provides Clang 3.4. On this machine, the compiler claims SSE2
  is all that is available:

  $ clang++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE_MATH__ 1

  $ g++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __AES__ 1
  #define __AVX__ 1
  #define __AVX2__ 1
  #define __BMI__ 1
  #define __BMI2__ 1
  #define __core_avx2 1
  #define __core_avx2__ 1
  #define __RDRND__ 1
  #define __RDSEED__ 1
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE3__ 1
  #define __SSE4_1__ 1
  #define __SSE4_2__ 1
  #define __SSE_MATH__ 1
  #define __SSSE3__ 1

  

  Clang's configuration is causing self tests to fail. The self tests
  verify configuration and code generation
  (http://github.com/weidai11/cryptopp/blob/master/cryptest.sh#L1013):

  $ CXX=clang++ ./cryptest.sh

  IS_LINUX: 1
  IS_X64: 1
  ...

  
  Testing: X86 AES-NI code generation

  clang++ -DNDEBUG -g2 -O2  -fPIC -march=native -pipe -c rijndael.cpp
  ERROR: failed to generate aesenc instruction
  ERROR: failed to generate aesenclast instruction
  ERROR: failed to generate aesdec instruction
  ERROR: failed to generate aesdeclast instruction
  ERROR: failed to generate aesimc instruction
  ERROR: failed to generate aeskeygenassist instruction

  
  Testing: X86 carryless multiply code generation

  clang++ -DNDEBUG -g2 -O2  -fPIC -march=native -pipe -c gcm.cpp
  ERROR: failed to generate pclmullqh instruction
  ERROR: failed to generate pclmullql instruction

  
  Testing: X86 RDRAND and RDSEED code generation

  clang++ -DNDEBUG -g2 -O2  -fPIC -march=native -pipe -c rdrand.cpp
  Verified rdrand and rdseed machine instructions

  
  Testing: X86 CRC32 code generation

  clang++ -DNDEBUG -g2 -O2  -fPIC -march=native -pipe -c crc.cpp
  ERROR: failed to generate crc32l instruction
  ERROR: failed to generate crc32b instruction

  

  $ cat /proc/cpuinfo
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 61
  model name: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
  stepping  : 4
  microcode : 0x16
  cpu MHz   : 800.058
  cache size: 3072 KB
  physical id   : 0
  siblings  : 4
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 20
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat 
epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust 
bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt
  ...

  

  $ uname -a
  Linux qotom 3.19.0-66-generic #74~14.04.1-Ubuntu SMP Tue Jul 19 19:56:11 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release  -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  Codename: trusty

  $ dpkg -l clang-3.4
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  clang-3.4  1:3.4-1ubunt amd64C, C++ and 

[Touch-packages] [Bug 1616723] [NEW] Clang 3.4 only advertises SSE2

[Jeffrey Walton]

Public bug reported:

I'm working on a 5th generation Core i5 (see /proc/cpuinfo below). The
CPU offers SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, RDRAND, RDSEED, etc.

Ubuntu provides Clang 3.4. On this machine, the compiler claims SSE2 is
all that is available:

$ clang++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
#define __SSE__ 1
#define __SSE2__ 1
#define __SSE2_MATH__ 1
#define __SSE_MATH__ 1

$ g++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
#define __AES__ 1
#define __AVX__ 1
#define __AVX2__ 1
#define __BMI__ 1
#define __BMI2__ 1
#define __core_avx2 1
#define __core_avx2__ 1
#define __RDRND__ 1
#define __RDSEED__ 1
#define __SSE__ 1
#define __SSE2__ 1
#define __SSE2_MATH__ 1
#define __SSE3__ 1
#define __SSE4_1__ 1
#define __SSE4_2__ 1
#define __SSE_MATH__ 1
#define __SSSE3__ 1



Clang's configuration is causing self tests to fail. The self tests
verify configuration and code generation
(http://github.com/weidai11/cryptopp/blob/master/cryptest.sh#L1013):

$ CXX=clang++ ./cryptest.sh

IS_LINUX: 1
IS_X64: 1
...


Testing: X86 AES-NI code generation

clang++ -DNDEBUG -g2 -O2  -fPIC -march=native -pipe -c rijndael.cpp
ERROR: failed to generate aesenc instruction
ERROR: failed to generate aesenclast instruction
ERROR: failed to generate aesdec instruction
ERROR: failed to generate aesdeclast instruction
ERROR: failed to generate aesimc instruction
ERROR: failed to generate aeskeygenassist instruction


Testing: X86 carryless multiply code generation

clang++ -DNDEBUG -g2 -O2  -fPIC -march=native -pipe -c gcm.cpp
ERROR: failed to generate pclmullqh instruction
ERROR: failed to generate pclmullql instruction


Testing: X86 RDRAND and RDSEED code generation

clang++ -DNDEBUG -g2 -O2  -fPIC -march=native -pipe -c rdrand.cpp
Verified rdrand and rdseed machine instructions


Testing: X86 CRC32 code generation

clang++ -DNDEBUG -g2 -O2  -fPIC -march=native -pipe -c crc.cpp
ERROR: failed to generate crc32l instruction
ERROR: failed to generate crc32b instruction



$ cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 61
model name  : Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
stepping: 4
microcode   : 0x16
cpu MHz : 800.058
cache size  : 3072 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 20
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat 
epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust 
bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt
...



$ uname -a
Linux qotom 3.19.0-66-generic #74~14.04.1-Ubuntu SMP Tue Jul 19 19:56:11 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release  -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename:   trusty

$ dpkg -l clang-3.4
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  clang-3.4  1:3.4-1ubunt amd64C, C++ and Objective-C compiler (

** Affects: llvm-toolchain-3.4 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in
Ubuntu.
https://bugs.launchpad.net/bugs/1616723

Title:
  Clang 3.4 only advertises SSE2

Status in llvm-toolchain-3.4 package in Ubuntu:
  New

Bug description:
  I'm working on a 5th generation Core i5 (see /proc/cpuinfo below). The
  CPU offers SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, RDRAND, RDSEED,
  etc.

  Ubuntu provides Clang 3.4. On this machine, the compiler claims SSE2
  is all that is available:

  $ clang++ -march=native -dM -E - < /dev/null | egrep -i 
'(sse|aes|rdrnd|rdseed|avx|bmi)' | sort
  #define __SSE__ 1
  #define __SSE2__ 1
  #define __SSE2_MATH__ 1
  #define __SSE_MATH__ 1

  $ g++ -march=native -dM -E - < 

[Touch-packages] [Bug 1472558] [NEW] GDB Crash during debugging session due to libstdcxx.v6.printers import register_libstdcxx_printers

[Jeffrey Walton]

Public bug reported:

While attempting to debug a simple C++, program, GDB crashes. The
program is below:

$ gdb
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
...
(gdb) file ./cryptopp-test.exe 
Reading symbols from ./cryptopp-test.exe...done.
(gdb) r
Starting program: /home/user/cryptopp-test.exe 
Traceback (most recent call last):
  File 
/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py, 
line 63, in module
from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named 'libstdcxx'

Program received signal SIGSEGV, Segmentation fault.
Segmentation fault

**

This appears to be a Debian bug from February, 2013:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701935.

**

I'm on Ubuntu 14.04, x86_64 fully patched. I'm using Gnome-Fallback
desktop (it seems many think everything is a tablet now. I'd like to get
a hold of the drugs the folks at Microsoft, Fedora, Ubuntu (etc) are
using for recreational purposes, too).

$ uname -a
Linux ubuntu 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release 
No LSB modules are available.

**

The program below is going to provide (or not provide) heuristic
evidence of a bias in the Random Number Generator. The crash occurs with
different symbol levels (-g) and optimizations (-O).

// g++ -DDEBUG=1 -g3 -Og -Wall -Wextra -Wno-unused-parameter \
//-I/usr/local/include/cryptopp cryptopp-test.cpp \
///usr/local/lib/libcryptopp.a -o cryptopp-test.exe

static const word32 MIN_VAL = 0, MAX_VAL = 2;
static const word32 RANGE = MAX_VAL - MIN_VAL + 1;
static const unsigned int ITERATIONS = 10;

int main(int argc, char* argv[])
{
try {

RandomNumberGenerator rng;
vectorunsigned intbuckets;
buckets.resize(RANGE);

for(unsigned int i = 0; i  ITERATIONS; i++)
buckets[rng.GenerateWord32(MIN_VAL, MAX_VAL)]++;

for(unsigned int j = 0; j  RANGE; j++)
cout  j  :   buckets[j]  endl;
}
catch(CryptoPP::Exception ex)
{
cerr  ex.what()  endl;
}

return 0;
}

** Affects: gdb (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1472558

Title:
  GDB Crash during debugging session due to libstdcxx.v6.printers import
  register_libstdcxx_printers

Status in gdb package in Ubuntu:
  New

Bug description:
  While attempting to debug a simple C++, program, GDB crashes. The
  program is below:

  $ gdb
  GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
  ...
  (gdb) file ./cryptopp-test.exe 
  Reading symbols from ./cryptopp-test.exe...done.
  (gdb) r
  Starting program: /home/user/cryptopp-test.exe 
  Traceback (most recent call last):
File 
/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py, 
line 63, in module
  from libstdcxx.v6.printers import register_libstdcxx_printers
  ImportError: No module named 'libstdcxx'

  Program received signal SIGSEGV, Segmentation fault.
  Segmentation fault

  **

  This appears to be a Debian bug from February, 2013:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701935.

  **

  I'm on Ubuntu 14.04, x86_64 fully patched. I'm using Gnome-Fallback
  desktop (it seems many think everything is a tablet now. I'd like to
  get a hold of the drugs the folks at Microsoft, Fedora, Ubuntu (etc)
  are using for recreational purposes, too).

  $ uname -a
  Linux ubuntu 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release 
  No LSB modules are available.

  **

  The program below is going to provide (or not provide) heuristic
  evidence of a bias in the Random Number Generator. The crash occurs
  with different symbol levels (-g) and optimizations (-O).

  // g++ -DDEBUG=1 -g3 -Og -Wall -Wextra -Wno-unused-parameter \
  //-I/usr/local/include/cryptopp cryptopp-test.cpp \
  ///usr/local/lib/libcryptopp.a -o cryptopp-test.exe

  static const word32 MIN_VAL = 0, MAX_VAL = 2;
  static const word32 RANGE = MAX_VAL - MIN_VAL + 1;
  static const unsigned int ITERATIONS = 10;

  int main(int argc, char* argv[])
  {
  try {

  RandomNumberGenerator rng;
  vectorunsigned intbuckets;
  buckets.resize(RANGE);

  for(unsigned int i = 0; i  ITERATIONS; i++)
  buckets[rng.GenerateWord32(MIN_VAL, MAX_VAL)]++;

  for(unsigned int j = 0; j  RANGE; j++)
  cout  j  :   buckets[j]  endl;
  }
  catch(CryptoPP::Exception ex)
  {
  cerr  ex.what()  endl;
  }

  return 0;
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1472558/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1256576] Re: Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not support TLS 1.2

[Jeffrey Walton]

This can now be closed due to USN-2606-1
(http://www.ubuntu.com/usn/usn-2606-1/).

Good work. I'm glad to see TLS 1.2 is now available to LTS.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1256576

Title:
  Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not
  support TLS 1.2

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  The long term support version of Ubuntu 12.04 provides OpenSSL 1.0.0.
  A wireshark trace shows the version of OpenSSL used by Ubuntu does not
  support TLS 1.2. According to the change logs, TLS 1.2 support was
  added 14 March 2012. The change log can be found at
  http://www.openssl.org/news/changelog.html, and the TLS additions can
  be found under the heading Changes between 1.0.0h and 1.0.1.

  $ ldd /usr/lib/x86_64-linux-gnu/libssl.so
  linux-vdso.so.1 =  (0x7fffd9d84000)
  libcrypto.so.1.0.0 = /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
  (0x7f1e0691e000)
  libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f1e0655e000)
  libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1e06359000)
  libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f1e06142000)
  /lib64/ld-linux-x86-64.so.2 (0x7f1e06f6d000)

  ***

  OpenSSL 1.0.1 is compatible with 1.0.0. From the OpenSSL FAQ
  (http://www.openssl.org/support/faq.html):

  8. How does the versioning scheme work?

  After the release of OpenSSL 1.0.0 the versioning scheme changed.
  Letter releases (e.g. 1.0.1a) can only contain bug and security fixes
  and no new features. Minor releases change the last number (e.g.
  1.0.2) and can contain new features that retain binary compatibility.
  Changes to the middle number are considered major releases and neither
  source nor binary compatibility is guaranteed.

  **

  By the way, its nearly impossible to file a bug report through the
  launch pad. The maze that's been created is impossible to navigate,
  and its worse than one of those phone menu systems. I had to look up
  the URL to file at http://www.cryptopp.com/wiki/Talk:Linux. Great job
  to the designers of the system. Its probably the same idiots who
  thought a tablet manager was a great idea on the desktop..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1256576/+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 1440450] [NEW] GDB does not honor `set output-base 16`

[Jeffrey Walton]

Public bug reported:

From below, GDB does not appear to honor `set output-base 16`.

In case there's any ambiguity, I want to see output like
9D53491512D5A24D58A6D71D14A371... or 9D 53 49 15 12 D5 A2 4D 58 A6 D7 1D
14 A3 71 And I don't want to see
\023\066\236\255\370ř\376\206\215...

**

$ gdb
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
...
(gdb) file cryptopp-test.exe 
Reading symbols from cryptopp-test.exe...done.
(gdb) set output-radix 16
Output radix now set to decimal 16, hex 10, octal 20.
(gdb) show output-radix
Default output radix for printing of values is 16.
(gdb) r
Starting program: /home/user/cryptopp-test.exe 
...

Program received signal SIGSEGV, Segmentation fault.
CryptoPP::AESNI_Dec_Block(long long __vector, long long __vector const*, 
unsigned int) (block=..., subkeys=subkeys@entry=0x7fffdc60, 
rounds=rounds@entry=0x7fff) at rijndael.cpp:1040
1040block = _mm_aesdec_si128(block, subkeys[i+1]);
(gdb) where
#0  CryptoPP::AESNI_Dec_Block(long long __vector, long long __vector const*, 
unsigned int) (block=..., subkeys=subkeys@entry=0x7fffdc60, 
rounds=rounds@entry=0x7fff) at rijndael.cpp:1040
#1  0x0046dff2 in CryptoPP::AESNI_AdvancedProcessBlocksvoid (*)(long 
long __vector, long long __vector const*, unsigned int), void (*)(long long 
__vector, long long __vector, long long __vector, long long __vector, long 
long __vector const*, unsigned int)(void (*)(long long __vector, long long 
__vector const*, unsigned int), void (*)(long long __vector, long long 
__vector, long long __vector, long long __vector, long long __vector const*, 
unsigned int), long long __vector const*, unsigned int, unsigned char const*, 
unsigned char const*, unsigned char*, unsigned long, unsigned int) (
func1=func1@entry=0x46dad4 CryptoPP::AESNI_Dec_Block(long long __vector, 
long long __vector const*, unsigned int), 
func4=func4@entry=0x46db3c CryptoPP::AESNI_Dec_4_Blocks(long long 
__vector, long long __vector, long long __vector, long long __vector, long 
long __vector const*, unsigned int), subkeys=optimized out, 
rounds=optimized out, 
inBlocks=0x6ff908 
\023\066\236\255\370ř\376\206\215\324\332fEQ\342\310\337;\017/\020\335\036\005U\240\060
 , incomplete sequence \361, ...
...

** Affects: gdb (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1440450

Title:
  GDB does not honor `set output-base 16`

Status in gdb package in Ubuntu:
  New

Bug description:
  From below, GDB does not appear to honor `set output-base 16`.

  In case there's any ambiguity, I want to see output like
  9D53491512D5A24D58A6D71D14A371... or 9D 53 49 15 12 D5 A2 4D 58 A6 D7
  1D 14 A3 71 And I don't want to see
  \023\066\236\255\370ř\376\206\215...

  **

  $ gdb
  GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
  Copyright (C) 2014 Free Software Foundation, Inc.
  ...
  (gdb) file cryptopp-test.exe 
  Reading symbols from cryptopp-test.exe...done.
  (gdb) set output-radix 16
  Output radix now set to decimal 16, hex 10, octal 20.
  (gdb) show output-radix
  Default output radix for printing of values is 16.
  (gdb) r
  Starting program: /home/user/cryptopp-test.exe 
  ...

  Program received signal SIGSEGV, Segmentation fault.
  CryptoPP::AESNI_Dec_Block(long long __vector, long long __vector const*, 
unsigned int) (block=..., subkeys=subkeys@entry=0x7fffdc60, 
  rounds=rounds@entry=0x7fff) at rijndael.cpp:1040
  1040block = _mm_aesdec_si128(block, subkeys[i+1]);
  (gdb) where
  #0  CryptoPP::AESNI_Dec_Block(long long __vector, long long __vector const*, 
unsigned int) (block=..., subkeys=subkeys@entry=0x7fffdc60, 
  rounds=rounds@entry=0x7fff) at rijndael.cpp:1040
  #1  0x0046dff2 in CryptoPP::AESNI_AdvancedProcessBlocksvoid (*)(long 
long __vector, long long __vector const*, unsigned int), void (*)(long long 
__vector, long long __vector, long long __vector, long long __vector, long 
long __vector const*, unsigned int)(void (*)(long long __vector, long long 
__vector const*, unsigned int), void (*)(long long __vector, long long 
__vector, long long __vector, long long __vector, long long __vector const*, 
unsigned int), long long __vector const*, unsigned int, unsigned char const*, 
unsigned char const*, unsigned char*, unsigned long, unsigned int) (
  func1=func1@entry=0x46dad4 CryptoPP::AESNI_Dec_Block(long long 
__vector, long long __vector const*, unsigned int), 
  func4=func4@entry=0x46db3c CryptoPP::AESNI_Dec_4_Blocks(long long 
__vector, long long __vector, long long __vector, long long __vector, long 
long __vector const*, unsigned int), subkeys=optimized out, 
rounds=optimized out, 
  inBlocks=0x6ff908 

[Touch-packages] [Bug 1256576] Re: Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not support TLS 1.2

[Jeffrey Walton]

Closing due to USN-2367-1: OpenSSL update,
http://www.ubuntu.com/usn/usn-2367-1/.

** Changed in: openssl (Ubuntu)
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1256576

Title:
  Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not
  support TLS 1.2

Status in “openssl” package in Ubuntu:
  Fix Released

Bug description:
  The long term support version of Ubuntu 12.04 provides OpenSSL 1.0.0.
  A wireshark trace shows the version of OpenSSL used by Ubuntu does not
  support TLS 1.2. According to the change logs, TLS 1.2 support was
  added 14 March 2012. The change log can be found at
  http://www.openssl.org/news/changelog.html, and the TLS additions can
  be found under the heading Changes between 1.0.0h and 1.0.1.

  $ ldd /usr/lib/x86_64-linux-gnu/libssl.so
  linux-vdso.so.1 =  (0x7fffd9d84000)
  libcrypto.so.1.0.0 = /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
  (0x7f1e0691e000)
  libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f1e0655e000)
  libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1e06359000)
  libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f1e06142000)
  /lib64/ld-linux-x86-64.so.2 (0x7f1e06f6d000)

  ***

  OpenSSL 1.0.1 is compatible with 1.0.0. From the OpenSSL FAQ
  (http://www.openssl.org/support/faq.html):

  8. How does the versioning scheme work?

  After the release of OpenSSL 1.0.0 the versioning scheme changed.
  Letter releases (e.g. 1.0.1a) can only contain bug and security fixes
  and no new features. Minor releases change the last number (e.g.
  1.0.2) and can contain new features that retain binary compatibility.
  Changes to the middle number are considered major releases and neither
  source nor binary compatibility is guaranteed.

  **

  By the way, its nearly impossible to file a bug report through the
  launch pad. The maze that's been created is impossible to navigate,
  and its worse than one of those phone menu systems. I had to look up
  the URL to file at http://www.cryptopp.com/wiki/Talk:Linux. Great job
  to the designers of the system. Its probably the same idiots who
  thought a tablet manager was a great idea on the desktop..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1256576/+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 1370553] Re: Please add package alias for autoreconf

[Jeffrey Walton]

Does this god damn database of packages even work? I search for a
package, I get a package name, and then select it. When I try to save
it, I get There is 1 error in the data you entered. Please fix it and
try again.


** Package changed: ubuntu = apt (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1370553

Title:
  Please add package alias for autoreconf

Status in “apt” package in Ubuntu:
  New

Bug description:
  While trying to configure QEMU, I received the error:

  (cd .../qemu-2.1.1/pixman; autoreconf -v --install)
  /bin/sh: 1: autoreconf: not found
  make: *** [.../qemu-2.1.1/pixman/configure] Error 127

  I thought it would be easy to solve:

  sudo apt-get install autoreconf
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package autoreconf

  Fortunately, I came across others who had the same problem. The
  problem seems to be with the package name. There's nothing intuitive
  about dh-autoreconf.

  Please create an alias for dh-autoreconf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1370553/+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