[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Coeur Noir]

Ubuntu 24.04 installed today.

Firefox autonomous archive downloaded from
https://www.mozilla.org/fr/firefox/all/#product-desktop-release

And « ooops… » in any tab,

terminal says :

[Parent 5931, IPC I/O Parent] WARNING: process 6020 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6026 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6036 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6084 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6099 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6110 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6119 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6128 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6143 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6147 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6150 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265

…firefox as a snap looks to run fine but I have many bwrap processes that use 
100% cpu to the point of over-heating.
Is it related ?
See picture of monitor → https://i.ibb.co/BZCfNjJ/2404-bwrap.png

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Confirmed
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission 

[Touch-packages] [Bug 2059734] Re: Tar fails to extract archives that include folders with certain permissions on armhf

[Logan Bussell]

** Description changed:

  When running Ubuntu Noble in an arm32 Docker container, on certain hosts
  (Azure VM CI agents), tar fails to extract certain archives that include
  folders with specific permissions set.
  
  Here's a concise repro. The error occurs in when building the
  Dockerfile. I can only get this to work on Azure VMs, but can't find out
  why.
  
  ```Dockerfile
  FROM ubuntu.azurecr.io/ubuntu:noble
  
  # Create the problematic archive
  RUN mkdir /test \
- && chmod 775 /test \
- && cd /test \
- && mkdir 775 \
- && chmod 775 775 \
- && touch 775/test.txt \
- && chmod 644 775/test.txt \
- && tar -czvf /test.tar.gz .
+ && chmod 775 /test \
+ && cd /test \
+ && mkdir 775 \
+ && chmod 775 775 \
+ && touch 775/test.txt \
+ && chmod 644 775/test.txt \
+ && tar -czvf /test.tar.gz .
  
  # Extracting it gives an error
  RUN mkdir -p /test2 \
- && tar -tzvf /test.tar.gz \
- && tar -oxzf /test.tar.gz -C /test2
+ && tar -tzvf /test.tar.gz \
+ && tar -oxzf /test.tar.gz -C /test2
  ```
  
  What I expected to happen: The test.tar.gz archive should be
  successfully extracted to the /test2 directory.
  
  What happened instead: Tar throws the following error:
  ```
  tar: ./775: Cannot change mode to rwxrwxr-x: Operation not permitted
  tar: Exiting with failure status due to previous errors
  ```
  
  The Ubuntu container is running as root so there shouldn't be any
  permission errors.
  
  Since this is running in a container, I observed this happening on the 
following kernel:
- `Linux version 5.15.148.2-2.cm2 (root@CBL-Mariner) (gcc (GCC) 11.2.0, GNU ld 
(GNU Binutils) 2.37) #1 SMP Fri Feb 23 23:38:33 UTC 2024`.
+ `Linux version 5.15.148.2-2.cm2 (root@CBL-Mariner) (gcc (GCC) 11.2.0, GNU ld 
(GNU Binutils) 2.37) #1 SMP Fri Feb 23 23:38:33 UTC 2024`
+ As well as 
+ `Linux  6.5.0-1017-azure #17~22.04.1-Ubuntu SMP Sat Mar  9 10:04:07 
UTC 2024 aarch64 aarch64 aarch64 GNU/Linux`
  
  I was not able to reproduce it using Ubuntu 22.04 Jammy
  (ubuntu.azurecr.io/ubuntu:jammy), using the same kernel as above.
  
  Additionally I was not able to reproduce this on the kernel `Linux
  cb0507859b24 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11
  04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux`, which is running on
- my work machine, using Docker qemu emulation for the arm32 image (I do
- not have access to an arm32 native machine).
+ my work machine, using Docker qemu emulation for the arm32 image.
  
  Ubuntu version: Ubuntu Noble Numbat (development branch) 24.04 (from 
ubuntu.azurecr.io/ubuntu:noble)
  tar version: `1.35+dfsg-3`

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

Title:
  Tar fails to extract archives that include folders with certain
  permissions on armhf

Status in tar package in Ubuntu:
  New

Bug description:
  When running Ubuntu Noble in an arm32 Docker container, on certain
  hosts (Azure VM CI agents), tar fails to extract certain archives that
  include folders with specific permissions set.

  Here's a concise repro. The error occurs in when building the
  Dockerfile. I can only get this to work on Azure VMs, but can't find
  out why.

  ```Dockerfile
  FROM ubuntu.azurecr.io/ubuntu:noble

  # Create the problematic archive
  RUN mkdir /test \
  && chmod 775 /test \
  && cd /test \
  && mkdir 775 \
  && chmod 775 775 \
  && touch 775/test.txt \
  && chmod 644 775/test.txt \
  && tar -czvf /test.tar.gz .

  # Extracting it gives an error
  RUN mkdir -p /test2 \
  && tar -tzvf /test.tar.gz \
  && tar -oxzf /test.tar.gz -C /test2
  ```

  What I expected to happen: The test.tar.gz archive should be
  successfully extracted to the /test2 directory.

  What happened instead: Tar throws the following error:
  ```
  tar: ./775: Cannot change mode to rwxrwxr-x: Operation not permitted
  tar: Exiting with failure status due to previous errors
  ```

  The Ubuntu container is running as root so there shouldn't be any
  permission errors.

  Since this is running in a container, I observed this happening on the 
following kernel:
  `Linux version 5.15.148.2-2.cm2 (root@CBL-Mariner) (gcc (GCC) 11.2.0, GNU ld 
(GNU Binutils) 2.37) #1 SMP Fri Feb 23 23:38:33 UTC 2024`
  As well as 
  `Linux  6.5.0-1017-azure #17~22.04.1-Ubuntu SMP Sat Mar  9 10:04:07 
UTC 2024 aarch64 aarch64 aarch64 GNU/Linux`

  I was not able to reproduce it using Ubuntu 22.04 Jammy
  (ubuntu.azurecr.io/ubuntu:jammy), using the same kernel as above.

  Additionally I was not able to reproduce this on the kernel `Linux
  cb0507859b24 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11
  04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux`, which is running on
  my work machine, using Docker qemu emulation for the arm32 image.

  Ubuntu version: Ubuntu Noble Numbat (development branch) 

[Touch-packages] [Bug 2059281] Re: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

[Till Kamppeter]

I have uploaded c2esp 27-11ubuntu4 now.

In the code of c2esp I have found some logging statements which cast
pointer addresses to long int. Probably this works only on 64-bit and
not on 32-bit and so caused the crashes in the autopkgtest. I could not
test whether it is really the fix, I am simply giving it a try.

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

Title:
  libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in
  c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

Status in c2esp package in Ubuntu:
  In Progress
Status in cups package in Ubuntu:
  Fix Released

Bug description:
  libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in
  c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059281/+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 2046383] [NEW] lubuntu - minimal install ; no browser means `ubuntu-bug` is broken

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Lubuntu noble installed using minimal install option.

Side effect of no browser, will be if user discovers a bug, running
`ubuntu-bug` ends up with a terse xdg-open method error.

At the very least; this will need to be documented (ie. users will find
they do need a web browser to be installed for some features), or
another alternative utilized. This was reported on IRC days ago
(launchpad file delayed)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: lubuntu-default-settings 24.04.2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Tue Dec 12 18:24:51 2023
InstallationDate: Installed on 2023-12-11 (1 days ago)
InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210.2)
PackageArchitecture: all
SourcePackage: lubuntu-default-settings
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug noble
-- 
lubuntu - minimal install ; no browser means `ubuntu-bug` is broken
https://bugs.launchpad.net/bugs/2046383
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport in Ubuntu.

-- 
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 2059281] Re: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

[Till Kamppeter]

Problem seems to be rather the broken cups.pc file from Debian in the
cups package, which is fixed in 2.4.7-1.2ubuntu2, as after this cups
release the tests of said packages have passed.

** Package changed: libcupsfilters (Ubuntu) => cups (Ubuntu)

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

** Also affects: c2esp (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in
  c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

Status in c2esp package in Ubuntu:
  In Progress
Status in cups package in Ubuntu:
  Fix Released

Bug description:
  libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in
  c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059281/+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 2059734] [NEW] Tar fails to extract archives that include folders with certain permissions on armhf

[Logan Bussell]

Public bug reported:

When running Ubuntu Noble in an arm32 Docker container, on certain hosts
(Azure VM CI agents), tar fails to extract certain archives that include
folders with specific permissions set.

Here's a concise repro. The error occurs in when building the
Dockerfile. I can only get this to work on Azure VMs, but can't find out
why.

```Dockerfile
FROM ubuntu.azurecr.io/ubuntu:noble

# Create the problematic archive
RUN mkdir /test \
&& chmod 775 /test \
&& cd /test \
&& mkdir 775 \
&& chmod 775 775 \
&& touch 775/test.txt \
&& chmod 644 775/test.txt \
&& tar -czvf /test.tar.gz .

# Extracting it gives an error
RUN mkdir -p /test2 \
&& tar -tzvf /test.tar.gz \
&& tar -oxzf /test.tar.gz -C /test2
```

What I expected to happen: The test.tar.gz archive should be
successfully extracted to the /test2 directory.

What happened instead: Tar throws the following error:
```
tar: ./775: Cannot change mode to rwxrwxr-x: Operation not permitted
tar: Exiting with failure status due to previous errors
```

The Ubuntu container is running as root so there shouldn't be any
permission errors.

Since this is running in a container, I observed this happening on the 
following kernel:
`Linux version 5.15.148.2-2.cm2 (root@CBL-Mariner) (gcc (GCC) 11.2.0, GNU ld 
(GNU Binutils) 2.37) #1 SMP Fri Feb 23 23:38:33 UTC 2024`.

I was not able to reproduce it using Ubuntu 22.04 Jammy
(ubuntu.azurecr.io/ubuntu:jammy), using the same kernel as above.

Additionally I was not able to reproduce this on the kernel `Linux
cb0507859b24 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11
04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux`, which is running on
my work machine, using Docker qemu emulation for the arm32 image (I do
not have access to an arm32 native machine).

Ubuntu version: Ubuntu Noble Numbat (development branch) 24.04 (from 
ubuntu.azurecr.io/ubuntu:noble)
tar version: `1.35+dfsg-3`

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

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

Title:
  Tar fails to extract archives that include folders with certain
  permissions on armhf

Status in tar package in Ubuntu:
  New

Bug description:
  When running Ubuntu Noble in an arm32 Docker container, on certain
  hosts (Azure VM CI agents), tar fails to extract certain archives that
  include folders with specific permissions set.

  Here's a concise repro. The error occurs in when building the
  Dockerfile. I can only get this to work on Azure VMs, but can't find
  out why.

  ```Dockerfile
  FROM ubuntu.azurecr.io/ubuntu:noble

  # Create the problematic archive
  RUN mkdir /test \
  && chmod 775 /test \
  && cd /test \
  && mkdir 775 \
  && chmod 775 775 \
  && touch 775/test.txt \
  && chmod 644 775/test.txt \
  && tar -czvf /test.tar.gz .

  # Extracting it gives an error
  RUN mkdir -p /test2 \
  && tar -tzvf /test.tar.gz \
  && tar -oxzf /test.tar.gz -C /test2
  ```

  What I expected to happen: The test.tar.gz archive should be
  successfully extracted to the /test2 directory.

  What happened instead: Tar throws the following error:
  ```
  tar: ./775: Cannot change mode to rwxrwxr-x: Operation not permitted
  tar: Exiting with failure status due to previous errors
  ```

  The Ubuntu container is running as root so there shouldn't be any
  permission errors.

  Since this is running in a container, I observed this happening on the 
following kernel:
  `Linux version 5.15.148.2-2.cm2 (root@CBL-Mariner) (gcc (GCC) 11.2.0, GNU ld 
(GNU Binutils) 2.37) #1 SMP Fri Feb 23 23:38:33 UTC 2024`.

  I was not able to reproduce it using Ubuntu 22.04 Jammy
  (ubuntu.azurecr.io/ubuntu:jammy), using the same kernel as above.

  Additionally I was not able to reproduce this on the kernel `Linux
  cb0507859b24 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11
  04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux`, which is running on
  my work machine, using Docker qemu emulation for the arm32 image (I do
  not have access to an arm32 native machine).

  Ubuntu version: Ubuntu Noble Numbat (development branch) 24.04 (from 
ubuntu.azurecr.io/ubuntu:noble)
  tar version: `1.35+dfsg-3`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2059734/+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 2059281] [NEW] libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in
c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: Fix Released


** Tags: time-t
-- 
libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, 
cpdb-backend-cups, cpdb-libs, cups-browsed, libppd
https://bugs.launchpad.net/bugs/2059281
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

-- 
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 2059417] Re: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

[Shengjing Zhu]

It's reverted in Debian
https://tracker.debian.org/news/1515519/accepted-xz-
utils-561really545-1-source-into-unstable/

Though from the changelog I didn't see the reason.

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

Title:
  Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

Status in xz-utils package in Ubuntu:
  New

Bug description:
  Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

  Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1
  was recently released and uploaded to Debian as a bugfix only release.
  Notably, this fixes a bug that causes Valgrind to issue a warning on
  any application dynamically linked with liblzma. This includes a lot of
  important applications. This could break build scripts and test
  pipelines that expect specific output from Valgrind in order to pass.

  Additionally, this fixes a small typo for the man pages translations
  for Brazilian Portuguese, German, French, Korean, Romanian, and
  Ukrainian, and removes the need for patches applied for version
  5.6.0-0.2.

  The other bugfixes in this release have no impact on Ubuntu. They
  involve building with CMake or when building on a system without
  Landlock system calls defined (these are defined in Ubuntu).

  Changelog entries since current noble version 5.6.0-0.2:

  xz-utils (5.6.1-1) unstable; urgency=medium

    * Non-maintainer upload.
    * Import 5.6.1 (Closes: #1067708).
    * Takeover maintenance of the package.

   -- Sebastian Andrzej Siewior   Wed, 27 Mar
  2024 22:53:21 +0100

  
  Excerpt from the NEWS entry from upstream:

  5.6.1 (2024-03-09)

  * liblzma: Fixed two bugs relating to GNU indirect function (IFUNC)
with GCC. The more serious bug caused a program linked with
liblzma to crash on start up if the flag -fprofile-generate was
used to build liblzma. The second bug caused liblzma to falsely
report an invalid write to Valgrind when loading liblzma.

  * xz: Changed the messages for thread reduction due to memory
constraints to only appear under the highest verbosity level.

  * Build:

  - Fixed a build issue when the header file 
was present on the system but the Landlock system calls were
not defined in .

  - The CMake build now warns and disables NLS if both gettext
tools and pre-created .gmo files are missing. Previously,
this caused the CMake build to fail.

  * Minor improvements to man pages.

  * Minor improvements to tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2059417/+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 2037210] Re: unable to add PPA by its sources.list line

[Nick Rosbrook]

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => In Progress

** Tags removed: rls-nn-incoming

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

Title:
  unable to add PPA by its sources.list line

Status in Software Properties:
  Confirmed
Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 23.10 installed
  2. Run 

  ```
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 
E756285F30DB2B2BB35012E219BFCAF5168D33A9
  sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu 
jammy main"
  sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu 
jammy main"
  ```

  Expected results:

  * key added, two repositories are added to the relevant *.list files
  at /etc/apt/sources.list.d/

  Actual results:

  * relevant *.list files at /etc/apt/sources.list.d/ are not created,
  having errors instead

  ```
  $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu 
jammy main"
  Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main
  Components: 
  '
  Description:
  This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by 
stupid bug https://pad.lv/1922276 . So user will be able to select all terminal 
output with full scroll-back in MATE Terminal and other VTE-based terminals as 
it is expected.

  This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and
  Debian 12 (bookworm).

  As usual one can always remove this PPA and downgrade VTE packages by using 
`sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`.
  More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte
  Adding repository.
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.

  $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu 
jammy main"
  Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main
  Components: 
  '
  Description:
  This PPA provides patched libwnck3 package to fix  
https://github.com/mate-desktop/mate-panel/issues/1230 and 
https://pad.lv/1947420 .
  See details at 
https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 .

  This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm).

  As usual one can always remove this PPA and downgrade WNCK packages by using 
`sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`.
  More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck
  Adding repository.
  Found existing deb entry in 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.

  $ sudo apt-get update 
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-common 0.99.39
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback
  Date: Sun Sep 24 14:02:10 2023
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-09-24T13:25:34.901411

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-properties/+bug/2037210/+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 2053228] Re: software-properties-gtk does not start

[Roman]

For me app works fine now, don't see anything like @corradoventu does.
I've run a full-upgrade though (don't do this, I've broken my system a
bit, lol).

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

Title:
  software-properties-gtk does not start

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  On a new install with the new format sources.list software-properties-gtk 
does not start:
  corrado@corrado-n4-nn-0215:~$ software-properties-gtk
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file
  corrado@corrado-n4-nn-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:07:43 2024
  InstallationDate: Installed on 2024-02-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2049247] Re: Broken IPv4 support on IPv6-preferring networks (v255)

[Nick Rosbrook]

The referenced patch was included in v255.4, which has now landed in
noble.

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

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

Title:
  Broken IPv4 support on IPv6-preferring networks (v255)

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I noticed a bug in systemd version 255 which is currently available in
  noble-proposed (255.2-3ubuntu1).

  I have already reported to upstream at
  https://github.com/systemd/systemd/issues/30891 but there's no fix
  available yet as of today.

  I'm still reporting the bug here anyways because this bug can, under
  some conditions, result in the loss of IPv4 network connectivity in a
  completely standard Ubuntu 24.04 installation just by updating to
  systemd 255. I'm hoping that that's okay even though it's a bug caused
  by upstream not by Ubuntu; just because it could have a bad impact if
  this version ends up in 24.04 as it is.

  ---

  In systemd version 255, a feature has been added to "support" the
  IPv6-only DHCP option 108 defined in RFC8925. I'm putting "support" in
  quotation marks because one functionality that this RFC marks as a
  requirement is not implemented in systemd yet.

  To summarize: Option 108 can be sent by a DHCPv4 client to signal to
  the DHCPv4 server: "Hey, if (and only if) your network has proper IPv6
  support and a working NAT64 gateway, I don't really need my own IPv4
  address, I can handle it using 464XLAT and NAT64". The point of that
  option is to be able to run a Dual Stack network, where only clients
  that really need IPv4 (older Linux, Windows, etc.) will receive an
  IPv4 from DHCP, and clients that don't need IPv4 (Android, MacOS,
  Linux with systemd >=255, etc.) won't receive one from DHCP and
  instead set up a 464XLAT for outgoing IPv4 connectivity.

  This new code in systemd is enabled by default (the option
  "IPv6OnlyMode" defaults to "yes"). However, systemd does not actually
  have code to set up a 464XLAT yet (which violates the RFC).

  This means that systemd signals to the DHCPv4 server "Hey, I don't
  need IPv4, I'll just use 464XLAT and NAT64" but then it doesn't
  actually do that. Updating systemd on an Ubuntu 24.04 installation
  (where systemd-networkd is used) will result in the loss of the DHCP-
  assigned IPv4 address, breaking network connectivity for all IPv4-only
  applications.

  ---

  Information on how to reproduce this issue can be found in detail in
  the github bug report linked above, but to summarize:

  1. Have a Dual Stack network that announces a NAT64 through RAs or through 
DNS (or, ideally, both)
  2. Configure your DHCPv4 server to hand out option 108 ("v6-only-preferred")
  3. Connect an Ubuntu machine with systemd < 255.
  4. Notice that IPv4 connectivity is working fine.
  5. Update to systemd = 255.
  6. Notice that there's no IPv4 connectivity anymore and IPv4-only apps break.

  ---

  The proper fix for this issue to make systemd conform to the RFC would
  be to implement a 464XLAT. However that's not an easy task and most
  certainly not something that would end up as a hotfix / patch release.
  A good workaround for this bug would be, in my opinion, to change the
  default value for the "IPv6OnlyMode" to "no" when compiling systemd.

  That way, the RFC-violating code doesn't run by default, and if a user
  does set up a 464XLAT on their machine in some other way (outside of
  systemd) they can just change their config to include
  "IPv6OnlyMode=yes" and it'll be working as intended.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd 255.2-3ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Jan 13 07:05:42 2024
  InstallationDate: Installed on 2024-01-12 (0 days ago)
  InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64 
(20231011)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 001: Dev 002, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=b5e6aabf-881a-4589-85ae-688f41df0be7 ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to noble on 2024-01-12 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: 

[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start

[corrado venturini]

Now software-properties-gtk does not crash but page 'Ubuntu software' is
empty and page 'Other software' unclear. see screenshot

** Attachment added: "Screenshot from 2024-03-28 18-54-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+attachment/5760311/+files/Screenshot%20from%202024-03-28%2018-54-42.png

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

Title:
  software-properties-gtk does not start

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  On a new install with the new format sources.list software-properties-gtk 
does not start:
  corrado@corrado-n4-nn-0215:~$ software-properties-gtk
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file
  corrado@corrado-n4-nn-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:07:43 2024
  InstallationDate: Installed on 2024-02-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Roman]

Yeah, I guess making a full-upgrade instead of upgrade was a bad idea :)

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+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 2059367] Re: SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS

[Seth Arnold]

Hello Arunaav, I'm curious if you could double-check the testing
environment to make sure the user accounts are as you expected?

chmod 0600 /home/core/.ssh/authorized_keys
ssh -i .ssh/id_rsa onprem_shell@10.14.169.25
ssh -v user@10.14.169.25
debug1: identity file /root/.ssh/id_rsa type -1


There's usernames 'core', 'onprem_shell', 'user', and 'root' in play here, and 
I think it'd be extraordinarily easy to perhaps use sudo or another privilege 
changing tool in such a way that it is using the wrong private key or the wrong 
authorized_keys file, etc.

Thanks

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

Title:
  SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS

Status in openssh package in Ubuntu:
  New

Bug description:
  On a FIPS Enabled Ubuntu 22.04 kernel, we are seeing an issue with self-ssh.
  We created a key with the following steps:
  touch /home/core/.ssh/known_hosts
    ssh-keygen -q -t rsa -f /home/core/.ssh/id_rsa -N '' > /dev/null
    cp /home/core/.ssh/id_rsa.pub /home/core/.ssh/authorized_keys
    chmod 0600 /home/core/.ssh/id_rsa
    chmod 0600 /home/core/.ssh/authorized_keys

  When we try to do a self ssh with the key, the following happens:
  ssh -i .ssh/id_rsa onprem_shell@10.14.169.25
  Connection closed by 10.14.169.25 port 22

  FIPS status:
  cat /proc/sys/crypto/fips_enabled
  1

  PFB, the ssh dump:

  ssh -v user@10.14.169.25
  OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1, OpenSSL 3.0.2 15 Mar 2022
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug1: FIPS mode initialized
  debug1: Connecting to 10.14.169.25 [10.14.169.25] port 22.
  debug1: Connection established.
  debug1: identity file /root/.ssh/id_rsa type -1
  debug1: identity file /root/.ssh/id_rsa-cert type -1
  debug1: identity file /root/.ssh/id_ecdsa type -1
  debug1: identity file /root/.ssh/id_ecdsa-cert type -1
  debug1: identity file /root/.ssh/id_ecdsa_sk type -1
  debug1: identity file /root/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /root/.ssh/id_ed25519 type -1
  debug1: identity file /root/.ssh/id_ed25519-cert type -1
  debug1: identity file /root/.ssh/id_ed25519_sk type -1
  debug1: identity file /root/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /root/.ssh/id_xmss type -1
  debug1: identity file /root/.ssh/id_xmss-cert type -1
  debug1: identity file /root/.ssh/id_dsa type -1
  debug1: identity file /root/.ssh/id_dsa-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.9p1 
Ubuntu-3ubuntu0.6+Fips1
  debug1: compat_banner: match: OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1 pat 
OpenSSH* compat 0x0400
  debug1: Authenticating to 10.14.169.25:22 as 'user'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: ecdh-sha2-nistp256
  debug1: kex: host key algorithm: ssh-rsa
  debug1: kex: server->client cipher: aes128-cbc MAC: hmac-sha1 compression: 
none
  debug1: kex: client->server cipher: aes128-cbc MAC: hmac-sha1 compression: 
none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  Connection closed by 10.14.169.25 port 22

  hostname -i
  10.14.169.25

  Please note that SSH onto other hosts (both FIPS and non-FIPS) works.
  The only workaround that we have found has been removing the ssh-rsa
  entry from “HostKeyAlgorithms” in “etc/ssh/sshd_config” and restarting
  the SSH service. This issue has neither been encountered in the Ubuntu
  18.04 FIPS nor Ubuntu 20.04 FIPS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059367/+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 2059723] [NEW] Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3)

[Anders Kaseorg]

Public bug reported:

As part of the 64-bit time_t transition, libmagic1 was renamed to
libmagic1t64 in https://bugs.debian.org/1063113.  However, libmagic1
1:5.45-2 is still in the archive, despite being non-installable:


# apt-get install libmagic1
Reading package lists... Done
Building dependency tree... Done
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:
 libmagic1 : Depends: libmagic-mgc (= 1:5.45-2) but 1:5.45-3 is to be installed
E: Unable to correct problems, you have held broken packages.


Please delete libmagic1 from the archive, so that libmagic1t64 1:5.45-3 can 
take over this role (it’s already marked Provides: libmagic1 (= 1:5.45-3)).

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

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

Title:
  Please delete libmagic1 1:5.45-2 from the archive (in favor of
  libmagic1t64 1:5.45-3)

Status in file package in Ubuntu:
  New

Bug description:
  As part of the 64-bit time_t transition, libmagic1 was renamed to
  libmagic1t64 in https://bugs.debian.org/1063113.  However, libmagic1
  1:5.45-2 is still in the archive, despite being non-installable:

  
  # apt-get install libmagic1
  Reading package lists... Done
  Building dependency tree... Done
  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:
   libmagic1 : Depends: libmagic-mgc (= 1:5.45-2) but 1:5.45-3 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

  
  Please delete libmagic1 from the archive, so that libmagic1t64 1:5.45-3 can 
take over this role (it’s already marked Provides: libmagic1 (= 1:5.45-3)).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/2059723/+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 2051343] Re: unity: FTBFS in Noble

[Graham Inggs]

** Also affects: unity-lens-files (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-music (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-video (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-home (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-applications (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  unity: FTBFS in Noble

Status in unity package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in unity-lens-files package in Ubuntu:
  New
Status in unity-lens-music package in Ubuntu:
  New
Status in unity-lens-video package in Ubuntu:
  New
Status in unity-scope-home package in Ubuntu:
  New

Bug description:
  As seen in the test rebuild:
  
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-noble.html

  [  9%] Building CXX object tests/CMakeFiles/test-main-libs.dir/test_main.cpp.o
  cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/c++ -DUSE_X11 
-I/usr/src/googletest/googlemock/include 
-I/usr/src/googletest/googletest/include -I/usr/include/unity/unity 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/dee-1.0 
-I/usr/include/gio-unix-2.0 -I/usr/include/libappstream-glib 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/webp 
-I/usr/include/uuid -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo 
-I/usr/include/freetype2 -I/usr/include/pixman-1 
-I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi 
-I/usr/include/libindicator3-0.4 -I/usr/include/json-glib-1.0 
-I/usr/include/libbamf3 -I/usr/lib/x86_64-linux-gnu/libbamf3/include 
-I/usr/include/gnome-desktop-3.0 -I/usr/i
 nclude/gsettings-desktop-schemas -I/usr/include/libxml2 
-I/usr/include/unity-settings-daemon-1.0 
-I/usr/include/startup-notification-1.0 -I/usr/include/Nux-4.0 
-I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
-I/usr/include/unity-misc -I/usr/include/zeitgeist-2.0 
-I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
-I/usr/include/compiz -I/<>/obj-x86_64-linux-gnu/tests 
-I/<>/tests/. -I/<>/tests/.. 
-I/<>/tests/../services -I/<>/tests/../UnityCore 
-I/<>/tests/../plugins/unityshell/src 
-I/<>/obj-x86_64-linux-gnu 
-I/<>/plugins/unity-mt-grab-handles/src -I/<>/dash 
-I/<>/decorations -I/<>/launcher 
-I/<>/panel -I/<>/hud -I/<>/shortcuts 
-I/<>/shutdown -I/<>/unity-shared -g -O2 
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-
 map=/<>=. -fstack-protector-strong -fstack-clash-protection 
-Wformat -Werror=format-security -fcf-protection 
-fdebug-prefix-map=/<>=/usr/src/unity-7.7.0+23.04.20230222.2-0ubuntu2
 -Wdate-time -D_FORTIFY_SOURCE=3 -DGNOME_DESKTOP_USE_UNSTABLE_API -std=c++11 
-fno-permissive -Wall -Wcast-align -Wempty-body -Wformat-security -Winit-self 
-Warray-bounds -Wno-error=deprecated-declarations 
-Wno-error=unused-local-typedefs -Wno-sign-compare  -MD -MT 
tests/CMakeFiles/test-main-libs.dir/test_main.cpp.o -MF 
CMakeFiles/test-main-libs.dir/test_main.cpp.o.d -o 
CMakeFiles/test-main-libs.dir/test_main.cpp.o -c 
/<>/tests/test_main.cpp
  In file included from 
/usr/src/googletest/googletest/include/gtest/gtest-message.h:57,
   from 
/usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46,
   from /usr/src/googletest/googletest/include/gtest/gtest.h:64,
   from /<>/tests/test_main.cpp:1:
  /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:279:2: 
error: #error C++ versions less than C++14 are not supported.
279 | #error C++ versions less than C++14 are not supported.
|  ^
  make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/2051343/+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 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Danilo Egea Gondolfo]

Please refer to https://lists.ubuntu.com/archives/ubuntu-
devel/2024-March/042954.html for more information about the current
state of upgrades.

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+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 2058930] Re: Missing in i386 Packages index

[Skia]

Apparently this was linked to the extra `setup-commands` issue that made
us loose the `proposed` pocket, and got "fixed" by updating the database
with the `no-proposed` tag.

TL;DR: fixed, and we didn't loose any cowboy specific to that issue,
everything is fine.

** Changed in: libvpx (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Missing in i386 Packages index

Status in libvpx package in Ubuntu:
  Fix Released

Bug description:
  The new version of libvpx 1.14 seems not to be published to
  http://ftpmaster.internal on i386 only.

  This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having 
any effect on i386:
  https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+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 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Roman]

Temporary bypass:
wget 
http://mirrors.kernel.org/ubuntu/pool/main/n/network-manager/network-manager_1.45.90-1ubuntu1_amd64.deb
dpkg --force-all -i network-manager_1.45.90-1ubuntu1_amd64.deb

dpkg output on my system:
Preparing to unpack network-manager_1.45.90-1ubuntu1_amd64.deb ...
Unpacking network-manager (1.45.90-1ubuntu1) over (1.45.90-1ubuntu1) ...
dpkg: network-manager: dependency problems, but configuring anyway as you 
requested:
 network-manager depends on libnm0 (= 1.45.90-1ubuntu1); however:
  Version of libnm0:amd64 on system is 1.45.90-1ubuntu3.
Setting up network-manager (1.45.90-1ubuntu1) ...
...

After that everything works fine.

Did the same with network-manager-openvpn and network-manager-openvpn-
gnome to bring back VPN, also works.

Btw, after full-upgrade I have a ton (114) of "not gonna be installed"
packages in apt output because some libs are missing from repos, seems
something went wrong when uploading new packages.

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+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 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Roman]

Guess it uninstalls network-manager to install new version but new
version can't be installed because it depends on libnetplan1 which is
missing from repos.

https://packages.ubuntu.com/noble/network-manager currently shows
[depends on] libnetplan1 (>= 0.106)
Package not available 

You can't simply install previous version 1.45.90-1ubuntu1, which still
shows in `apt show network-manager`, because its dependency libnm0 of
the same version is already missing from repos.

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+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 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Doug Smythies]

After the extensive upgrades of today no network. As per this bug
report, network-manager seems to be gone. In my case this is a 24.04
Ubuntu Desktop QEMU/KVM VM running on my main Debian server host.

In my case the command was "sudo apt dist-upgrade"

** Attachment added: "dpkg listing"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+attachment/5760309/+files/dpkg-network-manager.png

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound

[aminesaka]

I did the modification :
[Unit]
Description=Sound Service

# We require pulseaudio.socket to be active before starting the daemon,
because
# while it is possible to use the service without the socket, it is not
clear
# why it would be desirable.
#
# A user installing pulseaudio and doing `systemctl --user start pulseaudio`
# will not get the socket started, which might be confusing and problematic
if
# the server is to be restarted later on, as the client autospawn feature
# might kick in. Also, a start of the socket unit will fail, adding to the
# confusion.
#
# After=pulseaudio.socket is not needed, as it is already implicit in the
# socket-service relationship, see systemd.socket(5).
Requires=pulseaudio.socket
ConditionUser=!root

[Service]
ExecStart=/usr/bin/pulseaudio - --daemonize=no
--log-target=file:/home/$USER/pulse.txt
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
Restart=on-failure
RestrictNamespaces=yes
SystemCallArchitectures=native
SystemCallFilter=@system-service
# Note that notify will only work if --daemonize=no
Type=notify
UMask=0077
Slice=session.slice

[Install]
Also=pulseaudio.socket
WantedBy=default.target

However, after rebooting the system, I couldn't locate the pulse.txt file
in my home directory (/home/$USER/) or by searching it, and have confirmed
that hidden files are visible.

On a positive note, I noticed that I can now choose the headphone
microphone from the input device list without the need to delete and
re-setup the headphone from the Bluetooth settings.
Thanks for the help.

On Thu, Mar 28, 2024 at 12:27 PM Hui Wang <2051...@bugs.launchpad.net>
wrote:

> The content in the pulseaudio.log (#9) is not helpful.
>
>
> Could you edit /usr/lib/systemd/user/pulseaudio.service:
> change the line "ExecStart=/usr/bin/pulseaudio --daemonize=no
> --log-target=journal" to "ExecStart=/usr/bin/pulseaudio -
> --daemonize=no --log-target=file:/home/$user/pulse.txt"
>
> reboot
>
> connect your bt headset and try to change profile from A2DP to HSP/HFP,
> then upload the pulse.txt.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2051570
>
> Title:
>   [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal]
>   Underruns, dropouts or crackling sound
>
> Status in alsa-driver package in Ubuntu:
>   New
>
> Bug description:
>   Since the last three weeks' updates, I have encountered several
>   challenges with the audio functionality on my system. Primarily, upon
>   starting my laptop, the audio often fails to work, displaying "Dummy
>   Output." To resolve this, I find myself needing to restart the laptop
>   two or three times before the audio becomes functional.
>
>   Even when the audio is working, I've noticed a recurring issue where,
>   after playing video or audio for approximately 2-3 minutes, the sound
>   starts crackling and buzzing. The intensity of these distortions
>   gradually increases, resembling the static interference on a radio
>   station with a weak signal. This issue persists even when using 3.5mm
>   headphones, requiring the use of a USB headset or Bluetooth headphones
>   to enjoy distortion-free audio.
>
>   Furthermore, I have observed that, regardless of the Ubuntu version
>   (ranging from 22.04 to 22.04.3), I face difficulties changing the
>   microphone output settings when an external audio peripheral, such as
>   a USB headset, 3.5mm headphones, or Bluetooth headphones, is
>   connected. The OS appears to exclusively utilize the microphone from
>   the connected peripheral, making it impossible to switch to the
>   laptop's built-in microphone.
>
>   For your reference, here are the specifications of my laptop and the
>   Ubuntu version I am currently using:
>
>   Laptop: Dell Vostro 3400
>   CPU: 11th Gen Intel i5-1135G7
>   GPU: Intel TigerLake-LP GT2 Iris Xe
>   Memory: 2490MiB / 19720MiB
>   Resolution: 1920x1080
>   OS: Ubuntu 22.04.3 LTS x86_64
>   Kernel: 6.5.0-14-generic
>   DE: GNOME 42.9
>   Shell: bash 5.1.16
>   Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42
>
>   **UPDATE 12/02/2024 Noticed that every time my laptop fan starts
> spinning the crackling sound appears, after fan stops the crackling sound
> disappear.
>   **UPDATE 19/03/2024 I did a software update to the linux kernel
> 6.5.0-26, now i get a dummy output in sound even if i restart the system
> many times, and if i use my Bluetooth headphone i can't use the mic,
> neither the mic of the laptop or of the headphone (there is no option is
> the settings to choose from) it's all blank.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu7
>   ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
>   Uname: Linux 6.5.0-15-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  galxy-a10   1437 

[Touch-packages] [Bug 2055825] Re: Upgrade from 20.04 to 22.04 failed with "Fatal: unexpected error from getentropy: Invalid argument"

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apt (Ubuntu)
   Status: New => 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/2055825

Title:
  Upgrade from 20.04 to 22.04 failed with "Fatal: unexpected error from
  getentropy: Invalid argument"

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Upgrade from 20.04 to 22.04 failed with "Fatal: unexpected error from
  getentropy: Invalid argument". We have fips-updates enabled thru
  Ubuntu pro subscription. Tried to upgrade from 18.04 to 22.04. Upgrade
  from 18.04 to 204 is successful but upgrade from 20.04 to 22.04
  failed. Apt or do-release-upgrade commands no longer working after the
  upgrade failed so we have to restore the host to the Ubuntu 20.04
  snapshots.

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

  Upgrade log:
  Processing triggers for libc-bin (2.35-0ubuntu3.6) ...
  Errors were encountered while processing:
   systemd
   ntfs-3g
   dbus
   libpam-systemd:amd64
   systemd-sysv
   libnss-systemd:amd64
   friendly-recovery
   samba-common-bin
   samba
   update-notifier-common
  Fatal: unexpected error from getentropy: Invalid argument
  fatal error in libgcrypt, file ../../src/misc.c, line 146, function 
_gcry_logv: internal error (fatal or bug)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055825/+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 2058930] Re: Missing in i386 Packages index

[Lukas Märdian]

** Tags removed: rls-nn-incoming

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

Title:
  Missing in i386 Packages index

Status in libvpx package in Ubuntu:
  Fix Released

Bug description:
  The new version of libvpx 1.14 seems not to be published to
  http://ftpmaster.internal on i386 only.

  This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having 
any effect on i386:
  https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+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 2037210] Re: unable to add PPA by its sources.list line

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/software-properties/+git/software-properties/+merge/463298

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

Title:
  unable to add PPA by its sources.list line

Status in Software Properties:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 23.10 installed
  2. Run 

  ```
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 
E756285F30DB2B2BB35012E219BFCAF5168D33A9
  sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu 
jammy main"
  sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu 
jammy main"
  ```

  Expected results:

  * key added, two repositories are added to the relevant *.list files
  at /etc/apt/sources.list.d/

  Actual results:

  * relevant *.list files at /etc/apt/sources.list.d/ are not created,
  having errors instead

  ```
  $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu 
jammy main"
  Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main
  Components: 
  '
  Description:
  This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by 
stupid bug https://pad.lv/1922276 . So user will be able to select all terminal 
output with full scroll-back in MATE Terminal and other VTE-based terminals as 
it is expected.

  This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and
  Debian 12 (bookworm).

  As usual one can always remove this PPA and downgrade VTE packages by using 
`sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`.
  More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte
  Adding repository.
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.

  $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu 
jammy main"
  Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main
  Components: 
  '
  Description:
  This PPA provides patched libwnck3 package to fix  
https://github.com/mate-desktop/mate-panel/issues/1230 and 
https://pad.lv/1947420 .
  See details at 
https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 .

  This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm).

  As usual one can always remove this PPA and downgrade WNCK packages by using 
`sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`.
  More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck
  Adding repository.
  Found existing deb entry in 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.

  $ sudo apt-get update 
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-common 0.99.39
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback
  Date: Sun Sep 24 14:02:10 2023
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-09-24T13:25:34.901411

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-properties/+bug/2037210/+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 1995790] Re: regression: ?garbage does not work correctly in install commands

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.4.12

---
apt (2.4.12) jammy; urgency=medium

  * Restore ?garbage by calling MarkAndSweep before parsing (LP: #1995790)
  * For phasing, check if current version is a security update, not just 
previous ones
(LP: #2051181)

 -- Julian Andres Klode   Tue, 13 Feb 2024 16:39:04
+0100

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

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

Title:
  regression: ?garbage does not work correctly in install commands

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Jammy:
  Fix Released
Status in apt source package in Lunar:
  Won't Fix
Status in apt source package in Mantic:
  Fix Released
Status in apt source package in Noble:
  Fix Released

Bug description:
  [Impact]
  The '?garbage' pattern doesn't work with install/remove commands which is 
confusing, and the fix for it is trivial.

  [Test plan]
  Successful autopkgtest. The comprehensive test suite run as an autopkgtest 
has been updated in test/integration/test-apt-get-autoremove to test for the 
correct behavior of '?garbage' with install and remove.

  [Where problems could occur]
  You can see we had to tweak the test suite in a bunch of places because it 
relies on exact debug output format and because we now call "markandsweep" 
there's additional mark flags in the debug output. It's unlikely that this is a 
problem for others.

  We have not seen regressions in noble in the past 2 weeks or noble-
  proposed since 2023-11-23 (it was stuck for other reasons there),
  hence other places the code change may affect have been thoroughly
  exercised in the builders and autopkgtest runners.

  [Original bug report]
  The awesome apt has a some wonderful tips on their EXAMPLES section (printed 
below). The choice of name to "garbage" might not have been the best but the 
function is extremely useful.

  $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d'
     apt remove ?garbage
     Remove all packages that are automatically installed and no longer 
needed -
     same as apt autoremove

     apt purge ?config-files
     Purge all packages that only have configuration files left

     apt list '~i !~M (~slibs|~sperl|~spython)'
     List all manually-installed packages in sections matching libs, 
perl, or
     python.

  Lets mark a package as automatically installed, and use the examples.

  $ sudo apt-mark auto shotwell
  shotwell set to automatically installed.

  $ sudo apt remove ?garbage
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    libraw20 shotwell shotwell-common
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt autoremove
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
    libraw20 shotwell shotwell-common
  0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
  After this operation, 9.806 kB disk space will be freed.
  Do you want to continue? [Y/n] N
  Abort.

  Apt-patterns works as it should everywhere else, as far as I can see,
  it works wonders with ie `apt list '~g|~c'` and many other
  applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04
  for years, so I feel this is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.8
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 10:57:52 2022
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995790/+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 2037509] Re: Gnome/Ubuntu desktop wayland

[Daniel van Vugt]

Thanks for the bug report. Please attach screenshots, photos or a video
of the problem so we can better understand the issue.

** Package changed: ubuntu-meta (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Gnome/Ubuntu desktop wayland

Status in Ubuntu:
  Incomplete

Bug description:
  Good day, I hasten to inform you about a problem that has not left
  your distribution for several releases in a row. When the Wayland
  secant is launched, some window elements for control are not active.
  In particular, the open new tab/settings expand/collapse buttons in
  browsers and ower applications do not work. Snap and Deb are equally
  susceptible to this problem. The solution is to login to X11 and
  immediately log out and log into Wayland again. In the current builds
  of the Minotaur, the problem appeared quite recently, with the release
  of the public beta; in the builds for developers, this problem did not
  occur. I will be very upset if this problem goes into release. Please
  correct it if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 11:14:33 2023
  InstallationDate: Installed on 2023-06-21 (98 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230620)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2037509/+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 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+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 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+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 2037210] Re: unable to add PPA by its sources.list line

[Nick Rosbrook]

** Tags added: rls-nn-incoming

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

Title:
  unable to add PPA by its sources.list line

Status in Software Properties:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 23.10 installed
  2. Run 

  ```
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 
E756285F30DB2B2BB35012E219BFCAF5168D33A9
  sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu 
jammy main"
  sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu 
jammy main"
  ```

  Expected results:

  * key added, two repositories are added to the relevant *.list files
  at /etc/apt/sources.list.d/

  Actual results:

  * relevant *.list files at /etc/apt/sources.list.d/ are not created,
  having errors instead

  ```
  $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu 
jammy main"
  Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main
  Components: 
  '
  Description:
  This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by 
stupid bug https://pad.lv/1922276 . So user will be able to select all terminal 
output with full scroll-back in MATE Terminal and other VTE-based terminals as 
it is expected.

  This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and
  Debian 12 (bookworm).

  As usual one can always remove this PPA and downgrade VTE packages by using 
`sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`.
  More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte
  Adding repository.
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.

  $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu 
jammy main"
  Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main
  Components: 
  '
  Description:
  This PPA provides patched libwnck3 package to fix  
https://github.com/mate-desktop/mate-panel/issues/1230 and 
https://pad.lv/1947420 .
  See details at 
https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 .

  This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm).

  As usual one can always remove this PPA and downgrade WNCK packages by using 
`sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`.
  More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck
  Adding repository.
  Found existing deb entry in 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.

  $ sudo apt-get update 
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-common 0.99.39
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback
  Date: Sun Sep 24 14:02:10 2023
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-09-24T13:25:34.901411

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-properties/+bug/2037210/+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 2051181] Re: apt cannot upgrade phased updates if the current security version is same as updates

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.4.12

---
apt (2.4.12) jammy; urgency=medium

  * Restore ?garbage by calling MarkAndSweep before parsing (LP: #1995790)
  * For phasing, check if current version is a security update, not just 
previous ones
(LP: #2051181)

 -- Julian Andres Klode   Tue, 13 Feb 2024 16:39:04
+0100

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

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

Title:
  apt cannot upgrade phased updates if the current security version is
  same as updates

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Jammy:
  Fix Released
Status in apt source package in Mantic:
  Fix Released
Status in apt source package in Noble:
  Fix Released

Bug description:
  [Impact]
  A package that has the same version in -security and -updates, with the 
latter having a Phased-Update-Percentage set is subject to phasing which is not 
expected by the security team.

  [Test plan]
  An automatic test case has been added to apt's comprehensive integration test 
suite that simulates the problem. Passing of the autopkgtests is a successful 
test.

  [Where problems could occur]
  The fix in question changes the behavior, some people may have relied on 
that, but also this should not have happened server side (normally security 
updates do not receive a value but the real one in this case went a different 
route).

  Otherwise the fix is fairly contained, it removes a single OtherVer++
  increment which made it go one version below the current version, so
  we do not expect any problems; setting aside the usual regression
  potential from bugs in the compiler and so on.

  [Original bug report]
  When I finished installation with Jammy 22.04.3, I noticed that 
nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt 
dist-upgrade`.

  Below is the log of apt upgrade:
  ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run

[2/1878]
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Entering ResolveByKeep 10%
    Dependencies are not satisfied for nvidia-driver-535:amd64 < 
535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib >
  Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on 
nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 
535.129.03-1)
    Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends
    Dependencies are not satisfied for 
linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii 
umH Ib >
  Keeping package linux-modules-nvidia-535-oem-22.04c:amd64
    Dependencies are not satisfied for 
linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii 
umH Ib >
  Package linux-modules-nvidia-535-oem-22.04c:amd64 
linux-modules-nvidia-535-oem-22.04c:amd64 Depends on 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 
6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27)
    Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN 
Ib >
  Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on 
linux-signatures-nvidia-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 
@ii umU > (= 6.1.0-1027.27)
    Keeping Package linux-signatures-nvidia-6.1.0-1027-oem:amd64 due to Depends
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on 
linux-objects-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 
6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27)
    Keeping Package linux-objects-nvidia-535-6.1.0-1027-oem:amd64 due to Depends

  https://pastebin.canonical.com/p/7frwTKZG6D/

To manage notifications about this bug go 

[Touch-packages] [Bug 2059651] [NEW] network-manager gets uninstalled on apt full-upgrade

[Daniel van Vugt]

Public bug reported:

network-manager gets uninstalled on apt full-upgrade

I've tried two Noble systems this evening and both got their network-
manager packages removed. So wifi is gone.

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

** Affects: ubuntu-meta (Ubuntu)
 Importance: High
 Status: New


** Tags: noble

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => High

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+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 2059550] [NEW] autopkgtest failures on 1:5.0.3-2ubuntu2 (Noble)

[Aleksandr Mikhalitsyn]

Public bug reported:

We can see autopkgtest failures on Noble:
https://autopkgtest.ubuntu.com/packages/lxc
1:5.0.3-2ubuntu2 from noble-proposed/universe

Details from log 
(https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz):
=
3266s Removing autopkgtest-satdep (0) ...
3269s autopkgtest [20:29:48]: test no-devel: [---
3269s + grep LXC_DEVEL /usr/include/lxc/version.h
3269s + grep 0
3269s #define LXC_DEVEL 0
3269s autopkgtest [20:29:48]: test no-devel: ---]
3269s autopkgtest [20:29:48]: test no-devel:  - - - - - - - - - - results - - - 
- - - - - - -
3269s no-devel PASS
3269s autopkgtest [20:29:48]:  summary
3269s exercise FAIL non-zero exit status 1
3269s unprivileged-containers FAIL non-zero exit status 1
3269s basics-create-destroy PASS (superficial)
3269s no-devel PASS
=


unprivileged-containers
=
1896s Unpacking the rootfs
1900s 
1900s ---
1900s You just created an Ubuntu mantic amd64 (20240326_07:42) container.
1900s 
1900s To enable SSH, run: apt install openssh-server
1900s No default root or user password are set by LXC.
1900s + systemd-run --scope --quiet --user --property=Delegate=yes lxc-start -n 
mycontainer
1900s Failed to connect to bus: No medium found

=

exercise
=
1113s FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
1113s ---
1113s Name:   c1
1113s State:  RUNNING
1113s PID:52927
1113s Link:   veth1001_HZ75
1113s  TX bytes:  0 bytes
1113s  RX bytes:  0 bytes
1113s  Total bytes:   0 bytes
1113s Name:   c1
1113s State:  RUNNING
1113s PID:52994
1113s Link:   veth1001_ujGT
1113s  TX bytes:  0 bytes
1113s  RX bytes:  0 bytes
1113s  Total bytes:   0 bytes
1113s lxc-copy: c1: ../src/lxc/utils.c: lxc_drop_groups: 1365 Operation not 
permitted - Failed to drop supplimentary groups
<...>
1113s info: Removing crontab ...
1113s info: Removing user `lxcunpriv' ...
1113s FAIL
1113s ---
1114s PASS: lxc-tests: /usr/bin/lxc-test-usernic
1114s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec
1114s PASS: lxc-tests: /usr/bin/lxc-test-utils
1114s 
1114s SUMMARY: pass=55, fail=1, ignored=0
1115s autopkgtest [19:53:54]: test exercise: ---]
1115s autopkgtest [19:53:54]: test exercise:  - - - - - - - - - - results - - - 
- - - - - - -
1115s exercise FAIL non-zero exit status 1
=


In the previous version we had no unprivileged-containers testsuite because it 
was inherited from Debian.

lxc-test-unpriv was a skipped test too because we had this piece of code:
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/exercise?h=applied/ubuntu/noble#n129
=
# Skip some tests due to cgroup v2 incompatibility
if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then

[ "$testbin" = "lxc-test-apparmor-mount" ] && \
ignore "$STRING" && continue

[ "$testbin" = "lxc-test-autostart" ] && \
ignore "$STRING" && continue

[ "$testbin" = "lxc-test-no-new-privs" ] && \
ignore "$STRING" && continue

[ "$testbin" = "lxc-test-unpriv" ] && \
ignore "$STRING" && continue

fi
=

Just compare:
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble
and
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble-devel

We want to fix all of this for sure, but it would be awesome to get an
updated and actual version of LXC in the upcoming Ubuntu Noble release
too. So, may be it makes sense to skip this tests for the sake of having
LXC updated.

What I found in Debian, is that autopkgtests are skipped too:
https://ci.debian.net/packages/l/lxc/unstable/amd64/

Taking this into account it (probably) reasonable to skip this tests too
for now.

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

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

Title:
  autopkgtest failures on 1:5.0.3-2ubuntu2 (Noble)

Status in lxc package in Ubuntu:
  New

Bug description:
  We can see autopkgtest failures on Noble:
  https://autopkgtest.ubuntu.com/packages/lxc
  1:5.0.3-2ubuntu2 from noble-proposed/universe

  Details from log 
(https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz):
  =
  3266s Removing autopkgtest-satdep (0) ...
  3269s autopkgtest [20:29:48]: test no-devel: [---
  3269s + grep LXC_DEVEL /usr/include/lxc/version.h
  3269s + grep 0
  3269s #define LXC_DEVEL 0
  3269s autopkgtest [20:29:48]: test no-devel: 

[Touch-packages] [Bug 2059412] Re: SyntaxWarning: invalid escape sequence '\.'

[Nathan Teodosio]

** Merge proposal linked:
   
https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/463288

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

Title:
  SyntaxWarning: invalid escape sequence '\.'

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Installing software-properties gives

  --->
  /usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197: 
SyntaxWarning: invalid escape sequence '\.'
    elif 
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
 uri) == None:
  <---

  Marked as "wishlist" importance because Python still passes that to
  re.match as '\.' instead of '.', so the behavior is correct, as can be
  confirmed with

  --->
  % python3 -c 'print("\.")'
  :1: SyntaxWarning: invalid escape sequence '\.'
  \.
  <---

  In a future Python version they will be eventually a SyntaxError[1].

  [1] https://docs.python.org/3/reference/lexical_analysis.html#escape-
  sequences

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059412/+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 2057773] Re: After the latest kernel update if you toggle wifi on and off the system crashes

[Fred]

** Summary changed:

- After the latest Kernal update if you toggle wifi on and off the system 
crashes
+ After the latest kernel update if you toggle wifi on and off the system 
crashes

** Description changed:

- I got a kernal update today and updated it.
+ I got a kernel update today and updated it.
  So after i updated it and toggled wifi on and off the system soft locked it 
is nonfunctional but the mouse still works.
  It even can't do a sudo reboot or reboot at all.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 13 15:23:23 2024
  InstallationDate: Installed on 2024-01-22 (51 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  IpRoute:
-  default via 192.168.0.1 dev wlp2s0 proto dhcp src 192.168.2.37 metric 600 
-  169.254.0.0/16 dev wlp2s0 scope link metric 1000 
-  192.168.0.0/22 dev wlp2s0 proto kernel scope link src 192.168.2.37 metric 600
+  default via 192.168.0.1 dev wlp2s0 proto dhcp src 192.168.2.37 metric 600
+  169.254.0.0/16 dev wlp2s0 scope link metric 1000
+  192.168.0.0/22 dev wlp2s0 proto kernel scope link src 192.168.2.37 metric 600
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
-  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
-  running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

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

Title:
  After the latest kernel update if you toggle wifi on and off the
  system crashes

Status in network-manager package in Ubuntu:
  New

Bug description:
  I got a kernel update today and updated it.
  So after i updated it and toggled wifi on and off the system soft locked it 
is nonfunctional but the mouse still works.
  It even can't do a sudo reboot or reboot at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 13 15:23:23 2024
  InstallationDate: Installed on 2024-01-22 (51 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp src 192.168.2.37 metric 600
   169.254.0.0/16 dev wlp2s0 scope link metric 1000
   192.168.0.0/22 dev wlp2s0 proto kernel scope link src 192.168.2.37 metric 600
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057773/+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 1586528] Re: Avahi-daemon withdraws address record

[Ashish upara]

Is this issue solved till now?
Also are these solutions applicable for Ubuntu 20.04.6 LTS or not.

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan

[Lukas Märdian]

https://github.com/canonical/netplan/pull/447

** Changed in: netplan
   Status: Triaged => Fix Committed

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

Title:
  NetworkManager connections with an explicit DoT (DNS over TLS) are not
  supported with Netplan

Status in Netplan:
  Fix Committed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From: https://discourse.ubuntu.com/t/blog-netplan-developer-
  diaries/35932/11

  Hi all,

  NetworkManager connections with an explicit DoT (DNS over TLS)
  configuration are not supported with Netplan, but NetworkManager does
  feed back the DoT DNS info with server address and Server Name
  Indication (SNI) in the form server_address#SNI, e.g.
  1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a
  result, subsequent Netplan config applications fail because DNS
  servers don’t have the expected dotted decimal (IPv4) or colon’ed hex
  (IPv6) form.

  ```
  nmcli> describe ipv4.dns

  === [dns] ===
  [NM property description]
  Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server 
name can be specified by appending "#example.com" to the IP address of the DNS 
server. This currently only has effect when using systemd-resolved.
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2055148/+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 2059417] Re: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

[Jia Tan]

** Description changed:

  Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main)
  
  Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1
  was recently released and uploaded to Debian as a bugfix only release.
  Notably, this fixes a bug that causes Valgrind to issue a warning on
  any application dynamically linked with liblzma. This includes a lot of
  important applications. This could break build scripts and test
  pipelines that expect specific output from Valgrind in order to pass.
  
  Additionally, this fixes a small typo for the man pages translations
  for Brazilian Portuguese, German, French, Korean, Romanian, and
  Ukrainian, and removes the need for patches applied for version
  5.6.0-0.2.
  
  The other bugfixes in this release have no impact on Ubuntu. They
  involve building with CMake or when building on a system without
  Landlock system calls defined (these are defined in Ubuntu).
  
  Changelog entries since current noble version 5.6.0-0.2:
  
  xz-utils (5.6.1-1) unstable; urgency=medium
  
-   * Non-maintainer upload.
-   * Import 5.6.1 (Closes: #1067708).
-   * Takeover maintenance of the package.
+   * Non-maintainer upload.
+   * Import 5.6.1 (Closes: #1067708).
+   * Takeover maintenance of the package.
  
-  -- Sebastian Andrzej Siewior   Wed, 27 Mar
+  -- Sebastian Andrzej Siewior   Wed, 27 Mar
  2024 22:53:21 +0100
+ 
+ 
+ Excerpt from the NEWS entry from upstream:
+ 
+ 5.6.1 (2024-03-09)
+ 
+ * liblzma: Fixed two bugs relating to GNU indirect function (IFUNC)
+   with GCC. The more serious bug caused a program linked with
+   liblzma to crash on start up if the flag -fprofile-generate was
+   used to build liblzma. The second bug caused liblzma to falsely
+   report an invalid write to Valgrind when loading liblzma.
+ 
+ * xz: Changed the messages for thread reduction due to memory
+   constraints to only appear under the highest verbosity level.
+ 
+ * Build:
+ 
+ - Fixed a build issue when the header file 
+   was present on the system but the Landlock system calls were
+   not defined in .
+ 
+ - The CMake build now warns and disables NLS if both gettext
+   tools and pre-created .gmo files are missing. Previously,
+   this caused the CMake build to fail.
+ 
+ * Minor improvements to man pages.
+ 
+ * Minor improvements to tests.

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

Title:
  Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

Status in xz-utils package in Ubuntu:
  New

Bug description:
  Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

  Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1
  was recently released and uploaded to Debian as a bugfix only release.
  Notably, this fixes a bug that causes Valgrind to issue a warning on
  any application dynamically linked with liblzma. This includes a lot of
  important applications. This could break build scripts and test
  pipelines that expect specific output from Valgrind in order to pass.

  Additionally, this fixes a small typo for the man pages translations
  for Brazilian Portuguese, German, French, Korean, Romanian, and
  Ukrainian, and removes the need for patches applied for version
  5.6.0-0.2.

  The other bugfixes in this release have no impact on Ubuntu. They
  involve building with CMake or when building on a system without
  Landlock system calls defined (these are defined in Ubuntu).

  Changelog entries since current noble version 5.6.0-0.2:

  xz-utils (5.6.1-1) unstable; urgency=medium

    * Non-maintainer upload.
    * Import 5.6.1 (Closes: #1067708).
    * Takeover maintenance of the package.

   -- Sebastian Andrzej Siewior   Wed, 27 Mar
  2024 22:53:21 +0100

  
  Excerpt from the NEWS entry from upstream:

  5.6.1 (2024-03-09)

  * liblzma: Fixed two bugs relating to GNU indirect function (IFUNC)
with GCC. The more serious bug caused a program linked with
liblzma to crash on start up if the flag -fprofile-generate was
used to build liblzma. The second bug caused liblzma to falsely
report an invalid write to Valgrind when loading liblzma.

  * xz: Changed the messages for thread reduction due to memory
constraints to only appear under the highest verbosity level.

  * Build:

  - Fixed a build issue when the header file 
was present on the system but the Landlock system calls were
not defined in .

  - The CMake build now warns and disables NLS if both gettext
tools and pre-created .gmo files are missing. Previously,
this caused the CMake build to fail.

  * Minor improvements to man pages.

  * Minor improvements to tests.

To manage notifications about this bug go to:

[Touch-packages] [Bug 2059417] [NEW] Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

[Jia Tan]

Public bug reported:

Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1
was recently released and uploaded to Debian as a bugfix only release.
Notably, this fixes a bug that causes Valgrind to issue a warning on
any application dynamically linked with liblzma. This includes a lot of
important applications. This could break build scripts and test
pipelines that expect specific output from Valgrind in order to pass.

Additionally, this fixes a small typo for the man pages translations
for Brazilian Portuguese, German, French, Korean, Romanian, and
Ukrainian, and removes the need for patches applied for version
5.6.0-0.2.

The other bugfixes in this release have no impact on Ubuntu. They
involve building with CMake or when building on a system without
Landlock system calls defined (these are defined in Ubuntu).

Changelog entries since current noble version 5.6.0-0.2:

xz-utils (5.6.1-1) unstable; urgency=medium

  * Non-maintainer upload.
  * Import 5.6.1 (Closes: #1067708).
  * Takeover maintenance of the package.

 -- Sebastian Andrzej Siewior   Wed, 27 Mar
2024 22:53:21 +0100


Excerpt from the NEWS entry from upstream:

5.6.1 (2024-03-09)

* liblzma: Fixed two bugs relating to GNU indirect function (IFUNC)
  with GCC. The more serious bug caused a program linked with
  liblzma to crash on start up if the flag -fprofile-generate was
  used to build liblzma. The second bug caused liblzma to falsely
  report an invalid write to Valgrind when loading liblzma.

* xz: Changed the messages for thread reduction due to memory
  constraints to only appear under the highest verbosity level.

* Build:

- Fixed a build issue when the header file 
  was present on the system but the Landlock system calls were
  not defined in .

- The CMake build now warns and disables NLS if both gettext
  tools and pre-created .gmo files are missing. Previously,
  this caused the CMake build to fail.

* Minor improvements to man pages.

* Minor improvements to tests.

** Affects: xz-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

Status in xz-utils package in Ubuntu:
  New

Bug description:
  Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

  Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1
  was recently released and uploaded to Debian as a bugfix only release.
  Notably, this fixes a bug that causes Valgrind to issue a warning on
  any application dynamically linked with liblzma. This includes a lot of
  important applications. This could break build scripts and test
  pipelines that expect specific output from Valgrind in order to pass.

  Additionally, this fixes a small typo for the man pages translations
  for Brazilian Portuguese, German, French, Korean, Romanian, and
  Ukrainian, and removes the need for patches applied for version
  5.6.0-0.2.

  The other bugfixes in this release have no impact on Ubuntu. They
  involve building with CMake or when building on a system without
  Landlock system calls defined (these are defined in Ubuntu).

  Changelog entries since current noble version 5.6.0-0.2:

  xz-utils (5.6.1-1) unstable; urgency=medium

    * Non-maintainer upload.
    * Import 5.6.1 (Closes: #1067708).
    * Takeover maintenance of the package.

   -- Sebastian Andrzej Siewior   Wed, 27 Mar
  2024 22:53:21 +0100

  
  Excerpt from the NEWS entry from upstream:

  5.6.1 (2024-03-09)

  * liblzma: Fixed two bugs relating to GNU indirect function (IFUNC)
with GCC. The more serious bug caused a program linked with
liblzma to crash on start up if the flag -fprofile-generate was
used to build liblzma. The second bug caused liblzma to falsely
report an invalid write to Valgrind when loading liblzma.

  * xz: Changed the messages for thread reduction due to memory
constraints to only appear under the highest verbosity level.

  * Build:

  - Fixed a build issue when the header file 
was present on the system but the Landlock system calls were
not defined in .

  - The CMake build now warns and disables NLS if both gettext
tools and pre-created .gmo files are missing. Previously,
this caused the CMake build to fail.

  * Minor improvements to man pages.

  * Minor improvements to tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2059417/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : 

[Touch-packages] [Bug 2059418] [NEW] Bluetooth earbuds not being 'set up' on new machine

[Bill Gradwohl]

Public bug reported:

The problem concerns earbuds 0B:20:24:A3:E7:56 T60 that worked perfectly
under completely patched Ubuntu 22.04 on my old machine but now refuse
to be setup on a new box running completely patched Ubuntu 22.04 . Other
old bluetooth gadgets attached without issue.

The end result at the very bottom of this page indicates ‘requestor
exited before bonding was completed’ .


root@bill:~# bluetoothctl --version
bluetoothctl: 5.64
root@bill:~# hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: BC:C7:46:9D:25:98 ACL MTU: 1021:8 SCO MTU: 255:12
UP RUNNING PSCAN
RX bytes:11627 acl:0 sco:0 events:466 errors:0
TX bytes:78563 acl:0 sco:0 commands:422 errors:0
Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: PERIPHERAL ACCEPT
Name: 'bill'
Class: 0x7c0104
Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony
Device Class: Computer, Desktop workstation
HCI Version: (0xc) Revision: 0x40d
LMP Version: (0xc) Subversion: 0x7225
Manufacturer: Realtek Semiconductor Corporation (93)


root@bill:~# bluetoothctl
Agent registered
[CHG] Controller BC:C7:46:9D:25:98 Pairable: yes
[bluetooth]# show
Controller BC:C7:46:9D:25:98 (public)
Name: bill
Alias: bill
Class: 0x007c0104
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x00b4
Pairable: yes
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb)
UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: Vendor specific (5005--1000-8000-0002ee01)
UUID: Headset (1108--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb)
UUID: Audio Sink (110b--1000-8000-00805f9b34fb)
UUID: Device Information (180a--1000-8000-00805f9b34fb)
UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb)
UUID: Audio Source (110a--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (1106--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0540
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x0a (10)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
[bluetooth]# devices
Device 74:45:CE:BA:24:65 WH-CH710N


At this point I started the earbuds (T60) having a problem getting set up.


[CHG] Controller BC:C7:46:9D:25:98 Discoverable: yes
[CHG] Controller BC:C7:46:9D:25:98 Discovering: yes
[NEW] Device 34:95:04:4B:07:3C 34-95-04-4B-07-3C
[CHG] Device 34:95:04:4B:07:3C RSSI: -86
[NEW] Device 0B:20:24:A3:E7:56 T60
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -54
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -54
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -54
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -54
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -52
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -58
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -56
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -56
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -58
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -58
[CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -60
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -60
[CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -58
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -64
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -60
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -60
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -60
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -60
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -60
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -72
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -72
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -72
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -72
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -72
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -48
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -48
[CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -48
[CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -50
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -50
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -80
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -72
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -72
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -72
[CHG] Device 0B:20:24:A3:E7:56 RSSI: -46
[bluetooth]# info 0B:20:24:A3:E7:56
Device 0B:20:24:A3:E7:56 (public)
Name: T60
Alias: T60
Class: 0x00240404
Icon: audio-headset
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
ManufacturerData Key: 0x7262

[Touch-packages] [Bug 2059367] Re: SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS

[João Gomes]

Hi Arunaav, thank you for your report.
How did you install the FIPS packages?
Can you also provide the server log with debug enabled?

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

Title:
  SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS

Status in openssh package in Ubuntu:
  New

Bug description:
  On a FIPS Enabled Ubuntu 22.04 kernel, we are seeing an issue with self-ssh.
  We created a key with the following steps:
  touch /home/core/.ssh/known_hosts
    ssh-keygen -q -t rsa -f /home/core/.ssh/id_rsa -N '' > /dev/null
    cp /home/core/.ssh/id_rsa.pub /home/core/.ssh/authorized_keys
    chmod 0600 /home/core/.ssh/id_rsa
    chmod 0600 /home/core/.ssh/authorized_keys

  When we try to do a self ssh with the key, the following happens:
  ssh -i .ssh/id_rsa onprem_shell@10.14.169.25
  Connection closed by 10.14.169.25 port 22

  FIPS status:
  cat /proc/sys/crypto/fips_enabled
  1

  PFB, the ssh dump:

  ssh -v user@10.14.169.25
  OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1, OpenSSL 3.0.2 15 Mar 2022
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug1: FIPS mode initialized
  debug1: Connecting to 10.14.169.25 [10.14.169.25] port 22.
  debug1: Connection established.
  debug1: identity file /root/.ssh/id_rsa type -1
  debug1: identity file /root/.ssh/id_rsa-cert type -1
  debug1: identity file /root/.ssh/id_ecdsa type -1
  debug1: identity file /root/.ssh/id_ecdsa-cert type -1
  debug1: identity file /root/.ssh/id_ecdsa_sk type -1
  debug1: identity file /root/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /root/.ssh/id_ed25519 type -1
  debug1: identity file /root/.ssh/id_ed25519-cert type -1
  debug1: identity file /root/.ssh/id_ed25519_sk type -1
  debug1: identity file /root/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /root/.ssh/id_xmss type -1
  debug1: identity file /root/.ssh/id_xmss-cert type -1
  debug1: identity file /root/.ssh/id_dsa type -1
  debug1: identity file /root/.ssh/id_dsa-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.9p1 
Ubuntu-3ubuntu0.6+Fips1
  debug1: compat_banner: match: OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1 pat 
OpenSSH* compat 0x0400
  debug1: Authenticating to 10.14.169.25:22 as 'user'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: ecdh-sha2-nistp256
  debug1: kex: host key algorithm: ssh-rsa
  debug1: kex: server->client cipher: aes128-cbc MAC: hmac-sha1 compression: 
none
  debug1: kex: client->server cipher: aes128-cbc MAC: hmac-sha1 compression: 
none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  Connection closed by 10.14.169.25 port 22

  hostname -i
  10.14.169.25

  Please note that SSH onto other hosts (both FIPS and non-FIPS) works.
  The only workaround that we have found has been removing the ssh-rsa
  entry from “HostKeyAlgorithms” in “etc/ssh/sshd_config” and restarting
  the SSH service. This issue has neither been encountered in the Ubuntu
  18.04 FIPS nor Ubuntu 20.04 FIPS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059367/+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 2059412] Re: SyntaxWarning: invalid escape sequence '\.'

[Nathan Teodosio]

** Description changed:

  Installing software-properties gives
  
  --->
  /usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197: 
SyntaxWarning: invalid escape sequence '\.'
    elif 
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
 uri) == None:
  <---
  
  Marked as "wishlist" importance because Python still passes that to
  re.match as '\.' instead of '.', so the behavior is correct, as can be
  confirmed with
  
  --->
  % python3 -c 'print("\.")'
  :1: SyntaxWarning: invalid escape sequence '\.'
  \.
  <---
+ 
+ In a future Python version they will be eventually a SyntaxError[1].
+ 
+ [1] https://docs.python.org/3/reference/lexical_analysis.html#escape-
+ sequences

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

Title:
  SyntaxWarning: invalid escape sequence '\.'

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Installing software-properties gives

  --->
  /usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197: 
SyntaxWarning: invalid escape sequence '\.'
    elif 
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
 uri) == None:
  <---

  Marked as "wishlist" importance because Python still passes that to
  re.match as '\.' instead of '.', so the behavior is correct, as can be
  confirmed with

  --->
  % python3 -c 'print("\.")'
  :1: SyntaxWarning: invalid escape sequence '\.'
  \.
  <---

  In a future Python version they will be eventually a SyntaxError[1].

  [1] https://docs.python.org/3/reference/lexical_analysis.html#escape-
  sequences

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059412/+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 2057671] Re: Rename the ubuntu-advantage-tools package

[Calvin Mwadime Makokha]

** Merge proposal linked:
   
https://code.launchpad.net/~calvinmwadime/software-properties/+git/software-properties/+merge/463282

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

Title:
  Rename the ubuntu-advantage-tools package

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Noble:
  Triaged

Bug description:
  From ubuntu-advantage-tools v31, it has been renamed to ubuntu-pro-
  client. The current package is now a transitional package pointing to
  ubuntu-pro-client. software-properties depends on ubuntu-advantage-
  tool thus we should rename the dependency to ubuntu-pro-client to
  avoid having the transitional package as a dependency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2057671/+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 2059412] [NEW] SyntaxWarning: invalid escape sequence '\.'

[Nathan Teodosio]

Public bug reported:

Installing software-properties gives

--->
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197: 
SyntaxWarning: invalid escape sequence '\.'
  elif 
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
 uri) == None:
<---

Marked as "wishlist" importance because Python still passes that to
re.match as '\.' instead of '.', so the behavior is correct, as can be
confirmed with

--->
% python3 -c 'print("\.")'
:1: SyntaxWarning: invalid escape sequence '\.'
\.
<---

** Affects: software-properties (Ubuntu)
 Importance: Wishlist
 Assignee: Nathan Teodosio (nteodosio)
 Status: Triaged

** Description changed:

  Installing software-properties gives
  
  --->
  /usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197: 
SyntaxWarning: invalid escape sequence '\.'
-   elif 
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
 uri) == None:
+   elif 
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
 uri) == None:
  <---
+ 
+ Marked as "wishlist" importance because Python still passes that to
+ re.match as '\.' instead of '.', so the behavior is correct, as can be
+ confirmed with
+ 
+ --->
+ % python3 -c 'print("\.")'
+ :1: SyntaxWarning: invalid escape sequence '\.'
+ \.
+ <---

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

Title:
  SyntaxWarning: invalid escape sequence '\.'

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Installing software-properties gives

  --->
  /usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197: 
SyntaxWarning: invalid escape sequence '\.'
    elif 
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
 uri) == None:
  <---

  Marked as "wishlist" importance because Python still passes that to
  re.match as '\.' instead of '.', so the behavior is correct, as can be
  confirmed with

  --->
  % python3 -c 'print("\.")'
  :1: SyntaxWarning: invalid escape sequence '\.'
  \.
  <---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059412/+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 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound

[Hui Wang]

The content in the pulseaudio.log (#9) is not helpful.


Could you edit /usr/lib/systemd/user/pulseaudio.service:
change the line "ExecStart=/usr/bin/pulseaudio --daemonize=no 
--log-target=journal" to "ExecStart=/usr/bin/pulseaudio - --daemonize=no 
--log-target=file:/home/$user/pulse.txt"

reboot

connect your bt headset and try to change profile from A2DP to HSP/HFP,
then upload the pulse.txt.

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

Title:
  [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal]
  Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since the last three weeks' updates, I have encountered several
  challenges with the audio functionality on my system. Primarily, upon
  starting my laptop, the audio often fails to work, displaying "Dummy
  Output." To resolve this, I find myself needing to restart the laptop
  two or three times before the audio becomes functional.

  Even when the audio is working, I've noticed a recurring issue where,
  after playing video or audio for approximately 2-3 minutes, the sound
  starts crackling and buzzing. The intensity of these distortions
  gradually increases, resembling the static interference on a radio
  station with a weak signal. This issue persists even when using 3.5mm
  headphones, requiring the use of a USB headset or Bluetooth headphones
  to enjoy distortion-free audio.

  Furthermore, I have observed that, regardless of the Ubuntu version
  (ranging from 22.04 to 22.04.3), I face difficulties changing the
  microphone output settings when an external audio peripheral, such as
  a USB headset, 3.5mm headphones, or Bluetooth headphones, is
  connected. The OS appears to exclusively utilize the microphone from
  the connected peripheral, making it impossible to switch to the
  laptop's built-in microphone.

  For your reference, here are the specifications of my laptop and the
  Ubuntu version I am currently using:

  Laptop: Dell Vostro 3400
  CPU: 11th Gen Intel i5-1135G7
  GPU: Intel TigerLake-LP GT2 Iris Xe
  Memory: 2490MiB / 19720MiB
  Resolution: 1920x1080
  OS: Ubuntu 22.04.3 LTS x86_64
  Kernel: 6.5.0-14-generic
  DE: GNOME 42.9
  Shell: bash 5.1.16
  Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42

  **UPDATE 12/02/2024 Noticed that every time my laptop fan starts spinning the 
crackling sound appears, after fan stops the crackling sound disappear.
  **UPDATE 19/03/2024 I did a software update to the linux kernel 6.5.0-26, now 
i get a dummy output in sound even if i restart the system many times, and if i 
use my Bluetooth headphone i can't use the mic, neither the mic of the laptop 
or of the headphone (there is no option is the settings to choose from) it's 
all blank.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galxy-a10   1437 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 17:50:44 2024
  InstallationDate: Installed on 2024-01-16 (13 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: جانفي 29 17:49:49 galxya10-VR 
whoopsie-upload-all[712]: INFO:root:/var/crash/_usr_bin_pulseaudio.1000.crash 
already marked for upload, skipping
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.27.1
  dmi.board.name: 0GGCMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3400
  dmi.product.sku: 0A23
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-01-28T08:52:28.427855

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570/+subscriptions


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

[Touch-packages] [Bug 2045250] Re: pam_lastlog doesn't handle localtime_r related errors properly

[Frank Heimes]

Included in pam | 1.5.3-5ubuntu3.

** Changed in: pam (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  pam_lastlog doesn't handle localtime_r related errors properly

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in pam package in Ubuntu:
  Fix Released
Status in pam package in Fedora:
  Fix Released

Bug description:
  The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to 
noble) are affected by
  https://bugzilla.redhat.com/show_bug.cgi?id=2012871

  Customers report a command going through PAM crashing for a given user.
  A potential follow on issue can be that no ssh remote connections to an 
affected server are possible anymore, esp. painful with headless systems (was 
reported on a different distro).

  This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
  with tm = localtime_r(...) that can be NULL and needs to be handled.

  There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
  314-  ll_time = last_login.ll_time;
  315:  if ((tm = localtime_r (_time, _buf)) != NULL) {
  316-  strftime (the_time, sizeof (the_time),
  317-  /* TRANSLATORS: "strftime options for date of last 
login" */
  --
  574-
  575-  lf_time = utuser.ut_tv.tv_sec;
  576:  tm = localtime_r (_time, _buf);
  577-  strftime (the_time, sizeof (the_time),
  578-  /* TRANSLATORS: "strftime options for date of last login" */

  Case 1 (line 315) is properly handled, but not case 2 (line 576).

  The second case got fixed by:
  
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c

  This fix should be included in Ubuntu (and Debian).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2045250/+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 1991545] Re: Domain groups not accepted as 'AdminIdentities'

[James Paton-Smith]

After revisiting this, I found the issue was on my side.

Our LDAP wasn't returning the members list for groups when queried so polkit 
wasn't able to authorise those users.
I fixed this in our sssd.conf using the 'ignore_group_members = false' option.

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

Title:
  Domain groups not accepted as  'AdminIdentities'

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  Domain groups cannot be configured as 'AdminIdentities' under
  /etc/polkit-1/localauthority.conf.d

  EXAMPLE CONFIG

  # /etc/polkit-1/localauthority.conf.d/90-test.conf
  [Configuration]
  AdminIdentities=unix-group:sysapp

  
  With the above config, 'sysapp' is a group in LDAP. SSSD is configured on the 
machine to allow domain users to log in.
  Sudo rules have been configured for the 'sysapp' group and work correctly.

  However, any action that creates a polkit/GUI prompt for
  authentication does not allow users in the 'sysapp' group to
  authenticate. Instead, it only accepts auth from the root user.

  
  If I change the config to use a local group, instead of a domain group, 
everything works as expected.
  Similarly if I specify a domain USER instead of a domain group, everything 
works as expected.

  The problem seems to only be with domain/LDAP groups.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: policykit-1 0.105-33
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct  3 15:20:36 2022
  InstallationDate: Installed on 2022-07-15 (80 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1991545/+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 2053228] Re: software-properties-gtk does not start

[Danilo Alculete]

For me it still not working, or it takes a while to be added to the
updates?

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

Title:
  software-properties-gtk does not start

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  On a new install with the new format sources.list software-properties-gtk 
does not start:
  corrado@corrado-n4-nn-0215:~$ software-properties-gtk
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file
  corrado@corrado-n4-nn-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:07:43 2024
  InstallationDate: Installed on 2024-02-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
    quiet splash loglevel=3 fastboot

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2045096] Re: Error in network definition: Invalid MAC address 'random'

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 1.0-1

---
netplan.io (1.0-1) unstable; urgency=medium

  * New upstream release 1.0:
- state/status: add support for identifying bridge/bond/vrf members !420
- Netplan status --diff !440
- Netplan state diff !386
- allow COMMON_LINK_HANDLERS for VRFs (LP: #2031421, Closes: #1049432) !401
- netplan: add support for WPA3-Enterprise (LP: #2029876) !402
- wifi: support WPA2 and WPA3 Personal simultaneously !404
- auth: add support for LEAP and EAP-PWD (LP: #2038811) !415
- wifi: allow to have a psk and an eap password simultaneously !416
- Migrate CriticalConnection to KeepConfiguration (LP: #1896799) !424
- apply: bring "lo" back up if it's managed by NM (LP: # 2034595) !408
- Post 0.107 cleanup & dropping API/ABI compat !400
- ABI: Refactoring for libnetplan.so.1 !434
- Add additional bridge port settings !410
- SR-IOV improvements (VF-LAG support) !439
Documentation:
- Add spelling checking to the CI !417
- doc: libnetplan API reference, using Doxygen and Sphinx.breathe !423
- doc: Update 'Netplan everywhere' for 23.10 !418
- added mii-monitor-interval !411
- Adopt Docs Starter Pack !429
- Fix howto docs !430
- docs: add a topic about security !433
- Document and restructure libnetplan's public API symbols !438
- Lang. & formatting fixes in API docs. !441
- Update examples.md !442
Bug fixes:
- GitHub CI fixes !405
- util: don't return a placeholder netdef in the iterator !406
- tunnels/validation: do not error out if "local" is not defined !407
- cli/sriov: remove unused code !435
- wireguard: ignore empty endpoints (LP: #2038811) !414
- parse: improve the parsing of access-points (LP: #1809994) !413
- tests: Add autopkgtest for LP: #1959570 !419
- Fix permissions on folder '/run/NetworkManager/' !422
- parse-nm/wg: append the correct prefix to IPv6 (LP: #2046158) !428
- disable StartLimitBurst in the ovs-cleanup service (LP: #2047827) !431
- ctests: stop including C files in the test files !432
- workflow/coverity: install missing dependencies !436
- state_diff: fix filtering of host scoped routes !426
- sriov: don't generate duplicate entries in the rebind.service file !437
- check if ovsdb-server.service is active before displaying warning !421
- parser: accept the special MAC address options (LP: #2045096) !427
- CI: fix NetworkManager autopkgtest not using deb822 !443
- tests: Be less strict about systemctl daemon-reload (LP: #2048388)
- Netplan status --diff refactoring !444
  * d/netplan-generator.install: Fix PLACEHOLDER location
  * d/netplan-generator.lintian-overrides: Clean up unused override
  * d/source/options: Ignore .envrc (direnv)
  * d/control: pkg-config -> pkgconf
  * d/rules: Make use of -Dpython.bytecompile=-1
  * d/control: Update short description
  * d/control,d/libnetplan1.symbols: Prepare for libnetplan1 SOVER bump
  * d/control: Add iproute2 build-dep (for running tests)
  * d/rules: Drop removal of legacy symlink (integrated in meson)
  * d/t/control: execute netplan diff test cases
  * d/patches: Drop patches, applied upstream
  * d/t/control: Mark new 'diff' autopkgtest as flaky

 -- Lukas Märdian   Thu, 29 Feb 2024 11:51:50 +0100

** Changed in: netplan.io (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Error in network definition: Invalid MAC address 'random'

Status in Netplan:
  Fix Committed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  New

Bug description:
  netplan dose not understand the 'random' key word in 'Cloned MAC address' set 
by networkmanager.
  ```
  /etc/netplan/90-NM-X.yaml:9:19: Error in network definition: Invalid MAC 
address 'random', must be XX:XX:XX:XX:XX:XX or 
XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
macaddress: "random"
^
  ```

  netplan Version 0.107-5ubuntu2
  network-manager Version 1.44.2-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2045096/+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 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 1.0-1

---
netplan.io (1.0-1) unstable; urgency=medium

  * New upstream release 1.0:
- state/status: add support for identifying bridge/bond/vrf members !420
- Netplan status --diff !440
- Netplan state diff !386
- allow COMMON_LINK_HANDLERS for VRFs (LP: #2031421, Closes: #1049432) !401
- netplan: add support for WPA3-Enterprise (LP: #2029876) !402
- wifi: support WPA2 and WPA3 Personal simultaneously !404
- auth: add support for LEAP and EAP-PWD (LP: #2038811) !415
- wifi: allow to have a psk and an eap password simultaneously !416
- Migrate CriticalConnection to KeepConfiguration (LP: #1896799) !424
- apply: bring "lo" back up if it's managed by NM (LP: # 2034595) !408
- Post 0.107 cleanup & dropping API/ABI compat !400
- ABI: Refactoring for libnetplan.so.1 !434
- Add additional bridge port settings !410
- SR-IOV improvements (VF-LAG support) !439
Documentation:
- Add spelling checking to the CI !417
- doc: libnetplan API reference, using Doxygen and Sphinx.breathe !423
- doc: Update 'Netplan everywhere' for 23.10 !418
- added mii-monitor-interval !411
- Adopt Docs Starter Pack !429
- Fix howto docs !430
- docs: add a topic about security !433
- Document and restructure libnetplan's public API symbols !438
- Lang. & formatting fixes in API docs. !441
- Update examples.md !442
Bug fixes:
- GitHub CI fixes !405
- util: don't return a placeholder netdef in the iterator !406
- tunnels/validation: do not error out if "local" is not defined !407
- cli/sriov: remove unused code !435
- wireguard: ignore empty endpoints (LP: #2038811) !414
- parse: improve the parsing of access-points (LP: #1809994) !413
- tests: Add autopkgtest for LP: #1959570 !419
- Fix permissions on folder '/run/NetworkManager/' !422
- parse-nm/wg: append the correct prefix to IPv6 (LP: #2046158) !428
- disable StartLimitBurst in the ovs-cleanup service (LP: #2047827) !431
- ctests: stop including C files in the test files !432
- workflow/coverity: install missing dependencies !436
- state_diff: fix filtering of host scoped routes !426
- sriov: don't generate duplicate entries in the rebind.service file !437
- check if ovsdb-server.service is active before displaying warning !421
- parser: accept the special MAC address options (LP: #2045096) !427
- CI: fix NetworkManager autopkgtest not using deb822 !443
- tests: Be less strict about systemctl daemon-reload (LP: #2048388)
- Netplan status --diff refactoring !444
  * d/netplan-generator.install: Fix PLACEHOLDER location
  * d/netplan-generator.lintian-overrides: Clean up unused override
  * d/source/options: Ignore .envrc (direnv)
  * d/control: pkg-config -> pkgconf
  * d/rules: Make use of -Dpython.bytecompile=-1
  * d/control: Update short description
  * d/control,d/libnetplan1.symbols: Prepare for libnetplan1 SOVER bump
  * d/control: Add iproute2 build-dep (for running tests)
  * d/rules: Drop removal of legacy symlink (integrated in meson)
  * d/t/control: execute netplan diff test cases
  * d/patches: Drop patches, applied upstream
  * d/t/control: Mark new 'diff' autopkgtest as flaky

 -- Lukas Märdian   Thu, 29 Feb 2024 11:51:50 +0100

** Changed in: netplan.io (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Test suite often fails with "systemd units changed without reload" on
  s390x

Status in Netplan:
  Invalid
Status in netplan.io package in Ubuntu:
  Fix Released
Status in wpa package in Ubuntu:
  New

Bug description:
  The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
  often fails with

  AssertionError: systemd units changed without reload

  Looking at the history of autopkgtest runs, it looks like that the
  error does not always occur during execution of a specific test. I've
  seen occurrences of this error during the following test-cases:

  test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
  test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
  test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL

  Example [1]:

  781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
  781s --
  781s Traceback (most recent call last):
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line 
189, in test_dhcp6
  781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in 
generate_and_settle
  781s self.fail('systemd units changed without reload')
  781s AssertionError: systemd units changed 

[Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

[Launchpad Bug Tracker]

This bug was fixed in the package privoxy - 3.0.34-3ubuntu1

---
privoxy (3.0.34-3ubuntu1) noble; urgency=medium

  * debian/apparmor/usr.sbin.privoxy: attempt on fixing the denial on
containers (LP: #2058866).

 -- Łukasz 'sil2100' Zemczak   Tue, 26 Mar
2024 17:16:43 +0100

** Changed in: privoxy (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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2058866

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  Invalid
Status in cups-browsed package in Ubuntu:
  Fix Released
Status in privoxy package in Ubuntu:
  Fix Released

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2052930] Re: liblocale-gettext-perl autopkgtests fail against glibc 2.39

[Launchpad Bug Tracker]

This bug was fixed in the package liblocale-gettext-perl - 1.07-6ubuntu4

---
liblocale-gettext-perl (1.07-6ubuntu4) noble; urgency=medium

  * No-change rebuild against perlapi-5.38.2t64

 -- Steve Langasek   Fri, 22 Mar 2024
19:37:42 +

** Changed in: liblocale-gettext-perl (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  liblocale-gettext-perl autopkgtests fail against glibc 2.39

Status in glibc package in Ubuntu:
  Invalid
Status in liblocale-gettext-perl package in Ubuntu:
  Fix Released

Bug description:
  The autopkgtests for liblocale-gettext-perl fail against glibc 2.39
  with the following errors:

  autopkgtest [15:27:03]: test autodep8-perl-build-deps: 
[---
  243s t/bind.t ... 
  243s 1..1
  243s # Running under perl version 5.036000 for linux
  243s # Current time local: Wed Feb  7 15:27:02 2024
  243s # Current time GMT:   Wed Feb  7 15:27:02 2024
  243s # Using Test.pm version 1.31
  243s ok 1
  243s ok
  243s t/frconvert.t .. 
  243s 1..1
  243s # Running under perl version 5.036000 for linux
  243s # Current time local: Wed Feb  7 15:27:02 2024
  243s # Current time GMT:   Wed Feb  7 15:27:02 2024
  243s # Using Test.pm version 1.31
  243s not ok 1
  243s # Failed test 1 in t/frconvert.t at line 22
  243s #  t/frconvert.t line 22 is: ok(0);
  243s Failed 1/1 subtests 
  243s t/jaconvert.t .. 
  243s 1..1
  243s # Running under perl version 5.036000 for linux
  243s # Current time local: Wed Feb  7 15:27:03 2024
  243s # Current time GMT:   Wed Feb  7 15:27:03 2024
  243s # Using Test.pm version 1.31
  243s test
  243s not ok 1
  243s # Failed test 1 in t/jaconvert.t at line 23
  243s #  t/jaconvert.t line 23 is: ok(0);
  243s Failed 1/1 subtests 
  243s t/raw.t  
  243s 1..1
  243s # Running under perl version 5.036000 for linux
  243s # Current time local: Wed Feb  7 15:27:03 2024
  243s # Current time GMT:   Wed Feb  7 15:27:03 2024
  243s # Using Test.pm version 1.31
  243s not ok 1
  243s # Failed test 1 in t/raw.t at line 14
  243s #  t/raw.t line 14 is:   ok(0);
  243s Failed 1/1 subtests 
  243s t/use.t  
  243s 1..1
  243s # Running under perl version 5.036000 for linux
  243s # Current time local: Wed Feb  7 15:27:03 2024
  243s # Current time GMT:   Wed Feb  7 15:27:03 2024
  243s # Using Test.pm version 1.31
  243s ok 1
  243s ok
  243s 
  243s Test Summary Report
  243s ---
  243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1)
  243s   Failed test:  1
  243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1)
  243s   Failed test:  1
  243s t/raw.t  (Wstat: 0 Tests: 1 Failed: 1)
  243s   Failed test:  1
  243s Files=5, Tests=5,  1 wallclock secs ( 0.03 usr  0.01 sys +  0.09 cusr  
0.07 csys =  0.20 CPU)
  243s Result: FAIL

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

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:9.6p1-3ubuntu11

---
openssh (1:9.6p1-3ubuntu11) noble; urgency=medium

  * d/t/ssh-gssapi: make the test a bit more rebust (LP: #2058276):
- deal with return codes
- match a more specific success expression from the logs
- add klist output in the case of failure

 -- Andreas Hasenack   Mon, 18 Mar 2024 10:25:15
-0300

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

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

Status in openssh package in Ubuntu:
  Fix Released
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:
  Fix Released

Bug description:
  [ Impact ]

  The gssapi-keyex authentication mechanism has been inadvertently
  broken in openssh. It comes from a distro patch[1], and while the
  patch still applied, it was no longer correct.

  Without the fix, sshd will fail to start if gssapi-keyex is listed in
  the AuthenticationMethods of the server, and if not, sshd will still
  start, but gssapi-keyex will not be available.

  
  [ Test Plan ]

  This update adds a new autopkgtest to the package, which tests both
  gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
  and gssapi-keyex, which, before this update, does not work.

  The test plan is to run the new ssh-gssapi autopkgtest and verify it
  succeeds.

  
  [ Where problems could occur ]

  ssh is a critical piece of infrastructure, and problems with it could
  have catastrophic consequences. The service itself has a test command
  before it starts up to verify the syntax of the config file, but that
  test is not applied on shutdown, so a restart with an invalid config
  file could still leave sshd dead.

  The patch adds a change to an authentication structure, but that
  change is already present in the upstream code, and we are just
  updating it in the new gssapi-keyex code (introduced by the distro[1]
  patch, already present). Therefore, mistakes here should manifest
  themselves just in the gssapi-keyex code, which wasn't working anyway.
  Effectively, though, we are enabling a new authentication mechanism in
  sshd, one that was not supposed to have been removed, but was broken
  by mistake.

  
  [ Other Info ]

  The fact no-one noticed this problem for more than two years could be
  telling that there are not many users of this authentication mechanism
  out there. The same applies to debian: it has also been broken for a
  while there. Maybe we should drop it for future ubuntu releases, since
  upstream refuses to take it in.

  [ Original 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 1970069] Re: Annoying boot messages interfering with splash screen

[Launchpad Bug Tracker]

This bug was fixed in the package plymouth - 24.004.60-1ubuntu6

---
plymouth (24.004.60-1ubuntu6) noble; urgency=medium

  * Cherry-pick upstream fixes for consistent default scale selection
that matches what Mutter chooses on the login screen (LP: #2054769)
  * plymouth.hook: Stop automatically re-installing DRM kernel modules in
initrd. initramfs-tools already does this for us in hooks/framebuffer and
should be the authority for which drivers to include.
  * Install a /usr/share/initramfs-tools/conf-hooks.d/plymouth with
FRAMEBUFFER=y to make it clear to initramfs-tools that we always want
framebuffer support when Plymouth is installed. (LP: #1970069)

 -- Daniel van Vugt   Thu, 21 Mar 2024
14:46:56 +0100

** Changed in: plymouth (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
    quiet splash loglevel=3 fastboot

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2055806] Re: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:9.6p1-3ubuntu11

---
openssh (1:9.6p1-3ubuntu11) noble; urgency=medium

  * d/t/ssh-gssapi: make the test a bit more rebust (LP: #2058276):
- deal with return codes
- match a more specific success expression from the logs
- add klist output in the case of failure

 -- Andreas Hasenack   Mon, 18 Mar 2024 10:25:15
-0300

** Changed in: openssh (Ubuntu)
   Status: Fix Committed => 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/2055806

Title:
  sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing
  privilege separation directory: /run/sshd

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

Bug description:
  Symptom: ssh.service is not running and not accepting new SSH
  connections and returns socket closed error upon attempted connection.
  ssh.service shows a failed with error message "Missing privilege
  separation directory: /run/sshd".

  The following line is needed in the SystemD Unit configuration of the
  ssh.service file for the openssh-server package to fix what appears to
  be a race condition when ssh.service is sometimes started before
  systemd-tmpfiles-setup.service is finished processing the file in
  /usr/lib/tmpfiles.d/openssh.server.conf that is required to create the
  /run/sshd directory that is required by ssh.service to start property.

  There might be more depth or an alternative reason to why /run/sshd/
  still didn't exist after using ```systemctl reset-failed
  ssh.service```.  So more investigation is needed by someone with more
  background in systemd-tmpfiles-setup.service and openssh-server
  package after it when to socket activation.

  = Error Messages =

  ```
  $journalctl -u ssh.service -b-1

  Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure 
Shell server...
  Mar 02 21:30:56 server sshd[1271]: Missing privilege separation directory: 
/run/sshd
  Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, 
code=exited, status=255/EXCEPTION
  Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD 
Secure Shell server.
  Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 1.
  Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell 
server.
  Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure 
Shell server...
  Mar 02 21:30:56 server sshd[1369]: Missing privilege separation directory: 
/run/sshd
  Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, 
code=exited, status=255/EXCEPTION
  Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD 
Secure Shell server.
  Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 2.
  Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell 
server.
  Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure 
Shell server...
  Mar 02 21:30:56 server sshd[1454]: Missing privilege separation directory: 
/run/sshd
  Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, 
code=exited, status=255/EXCEPTION
  Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD 
Secure Shell server.
  Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 3.
  Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell 
server.
  Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure 
Shell server...
  Mar 02 21:30:57 server sshd[1465]: Missing privilege separation directory: 
/run/sshd
  Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, 
code=exited, status=255/EXCEPTION
  Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD 
Secure Shell server.
  Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 4.
  Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell 
server.
  Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure 
Shell server...
  Mar 02 21:30:57 server sshd[1475]: Missing privilege separation directory: 
/run/sshd
  Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, 
code=exited, status=255/EXCEPTION
  Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service 

[Touch-packages] [Bug 2055193] Re: [FFe] APT 24.04 crypto policy update

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.7.14

---
apt (2.7.14) unstable; urgency=medium

  [ Steve Langasek ]
  * Support building without gnutls
  * Add an artificial Conflicts: against libnettle8
to force upgrades in launchpad buildd chroots

  [ David Kalnischkies ]
  * Handle EINTR in the static FileFd::Write overload
  * Remove non-existent Debug::BuildDeps from apt.conf(5)
  * Parse unsupported != relation in dependencies

  [ Frans Spiesschaert ]
  * Dutch program translation update (Closes: #1065513)
  * Dutch manpages translation update (Closes: #1065517)

  [ Wesley Schwengle ]
  * Update documentation for apt-get upgrade with pkg arg (Closes: #1065831)
  * Update documentation for apt upgrade with pkg arg (Closes: #1065831)
  * Include Dutch translation for apt/apt-get upgrade documenation update
  * Update Graphviz URL to https://graphviz.org/
  * Update VCG tool URI to new location
  * s#http://bugs.debian.org/src/#https://bugs.debian.org/src#

  [ Julian Andres Klode ]
  * pkgTagFile::Jump: Use lookback buffer to rejump to current position
(Closes: #1067440)
  * debrecords: Do not reparse if given same location (Closes: #1067440)
  * Revert "debrecords: Do not reparse if given same location"

 -- Julian Andres Klode   Fri, 22 Mar 2024 11:11:44
+0100

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

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

Title:
  [FFe] APT 24.04 crypto policy update

Status in apt package in Ubuntu:
  Fix Released
Status in gnupg2 package in Ubuntu:
  Fix Released

Bug description:
  I don't know if this will land before the feature freeze but I'm
  filing this in any case:

  Our goal for 24.04 is to reject 1024-bit RSA repository signing keys.
  Work is ongoing in Launchpad to allow dual-signing PPAs and then
  resign all PPAs with a 4096-bit key.

  This needs the following changes:

  1) The gnupg upstream commit for https://dev.gnupg.org/T6946 needs to be 
backported. This is applying fine and in the package already, but the test 
suite fails with issues that look weirdly unrelated.
  2) APT needs to learn to pass the argument if supported
  3) APT needs to learn to interpret the output
  4) APT possibly may have to learn to issue warnings instead of errors for 
weak keys and pass the URL to the gpgv method to allow 1024-bit RSA keys over 
TLS connections, in case there are unforeseen issues with the PPA migration.

  Signing key policy: We would like to adopt a signing key policy of

  rsa>2048,ed25519,ed448

  As a result we would like to reject

  - RSA keys below 2048 bits
  - DSA keys
  - Unsafe ECC keys:
    - NIST P-{256,384,521}
    - Brainpool P-{256,384,512}
    - secp256k1

  Notes:
  - DSA keys are not possible to use anymore due to the deprecation of SHA1 
that happened years ago
  - NIST and Brainpool and secp256k1 are not very popular, 
https://safecurves.cr.yp.to/ lists all of them as unsafe. It is believed they 
have backdoors. Some FIPS customers may prefer them over Ed25519 and Ed448 as 
they have been approved longer, so it's possible fips support packages could 
reenable them by setting the correct apt.conf setting in a snippet.

  
  Timing wrt feature freeze and launchpad changes:

  Launchpad changes won't be landing before feature freeze and it will
  take some more weeks to resign the repositories, hence we need to do
  uploads after FF to enable the error by default even if we ship the
  functionality before it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055193/+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 2057710] Re: Accountsservice FTBFS on noble

[Launchpad Bug Tracker]

This bug was fixed in the package accountsservice - 23.13.9-2ubuntu4

---
accountsservice (23.13.9-2ubuntu4) noble; urgency=medium

  * debian/patches/0001-tests-s-assertEquals-assertEqual.patch:
Add patch to fix FTBFS with unittest from Python 3.12.
(LP: #2057710)

 -- David Mohammed   Tue, 12 Mar 2024 21:51:36
+

** Changed in: accountsservice (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Accountsservice FTBFS on noble

Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
   package version 23.13.9-2ubuntu FTBFS on all architectures.

  This is because of an invalid test

  This has been resolved upstream - see the attached debdiff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2057710/+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 2058053] Re: Change sudo compile options from --with-all-insults to --with-pc-insults

[Launchpad Bug Tracker]

This bug was fixed in the package sudo - 1.9.15p5-3ubuntu3

---
sudo (1.9.15p5-3ubuntu3) noble; urgency=medium

  * Disable an offensive insult (LP: #2058053)
- d/p/disable_offensive_insult.patch: properly disable an offensive
  insult that was fogotten when the configure options were refactored
  in plugins/sudoers/ins_csops.h.

 -- Marc Deslauriers   Mon, 18 Mar 2024
07:53:26 -0400

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

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

Title:
  Change sudo compile options from --with-all-insults to --with-pc-
  insults

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Focal:
  Confirmed
Status in sudo source package in Jammy:
  Confirmed
Status in sudo source package in Mantic:
  Confirmed
Status in sudo source package in Noble:
  Fix Released

Bug description:
  Tame as they might be, I'd like to continue using "Defaults insults" without 
any risk of upsetting anyone (and without having to maintain our own package 
version.)
  Would the safe insults version at compile time "--with-pc-insults" be a 
sensible default for all?

  Current as of Jammy, but looks like it's still the default compile option 
across the board
  Version: 1.9.9-1ubuntu2

  Current behaviour  : Enabling includes the "not PC" insults 
  Expected behaviour : Insults would default to "PC"

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/2058053/+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 2058276] Re: Improve ssh-gssapi DEP8 test

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:9.6p1-3ubuntu11

---
openssh (1:9.6p1-3ubuntu11) noble; urgency=medium

  * d/t/ssh-gssapi: make the test a bit more rebust (LP: #2058276):
- deal with return codes
- match a more specific success expression from the logs
- add klist output in the case of failure

 -- Andreas Hasenack   Mon, 18 Mar 2024 10:25:15
-0300

** Changed in: openssh (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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2058276

Title:
  Improve ssh-gssapi DEP8 test

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  The DEP8 test introduced in
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146 could
  still show s PASS even when the login didn't work. This is because
  it's relying on `set -e` to work inside functions, but that's not the
  case.

  For example, here I forced a failure by using an invalid user (I added "x" to 
the username):
  ```
  ## ssh'ing into localhost using gssapi-keyex auth
  testuser229...@sshd-gssapi.example.fake: Permission denied (gssapi-keyex).

  ## checking that we got a service ticket for ssh (host/)
  03/18/24 12:16:55  03/18/24 22:16:55  host/sshd-gssapi.example.fake@
Ticket server: host/sshd-gssapi.example.f...@example.fake

  ## Checking ssh logs to confirm gssapi-keyex auth was used
  Mar 18 12:16:55 sshd-gssapi.example.fake sshd[22994]: Failed gssapi-keyex for 
invalid user testuser22924x from 127.0.0.1 port 39550 ssh2: 
testuser22...@example.fake
  ## PASS test_gssapi_keyex_login

  ```

  Furthermore, the --grep option used in journalctl is not specific
  enough, as can also be seen above. It's just looking for the
  authentication method name, not whether is succeeded or not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2058276/+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 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 24.0.3-1ubuntu3

---
mesa (24.0.3-1ubuntu3) noble; urgency=medium

  * Unwind remaining bootstrap changes.

 -- Steve Langasek   Fri, 22 Mar 2024
18:31:49 +

** Changed in: mesa (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [radeon] gnome-shell and Xorg both crash with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa package in Debian:
  Fix Released

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2054851/+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 2057704] Re: jackd2 FTBFS due to waflib incompatible with Python 3.12

[Launchpad Bug Tracker]

This bug was fixed in the package jackd2 - 1.9.21~dfsg-3ubuntu1

---
jackd2 (1.9.21~dfsg-3ubuntu1) noble; urgency=medium

  * d/p/1002-Update-to-waf-2.0.26.patch: apply an upstream patch to fix
Python 3.12 compatibility issues with the waf build system.
(LP: #2057704).

 -- Zixing Liu   Tue, 12 Mar 2024 14:45:25
-0600

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

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

Title:
  jackd2 FTBFS due to waflib incompatible with Python 3.12

Status in jackd2 package in Ubuntu:
  Fix Released

Bug description:
  jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF
  build system inside.

  The upstream has already fixed the issue in a recent commit, we need
  to introduce this as a patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2057704/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

This bug was fixed in the package policykit-1 - 124-1ubuntu1

---
policykit-1 (124-1ubuntu1) noble; urgency=medium

  * polkitd.postinst: call systemd-sysusers with SYSTEMD_NSS_DYNAMIC_BYPASS=1
This works around an upgrade bug in systemd where nss-systemd cannot
establish a varlink connection with io.systemd.DynamicUser, hence causing
the polkitd user/group creation to fail. (LP: #2054716)

 -- Nick Rosbrook   Wed, 13 Mar 2024 14:15:18 -0400

** Changed in: policykit-1 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 
libzstd1 locales systemd systemd-dev systemd-oomd
systemd-resolved systemd-sysv systemd-timesyncd udev
  Suggested packages:
glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
libqrencode4 libtss2-rc0
  Recommended packages:
libnss-nis libnss-nisplus
  The following NEW packages will be installed:
libduktape207 libsystemd-shared systemd-dev systemd-resolved
  The following packages will be upgraded:
gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
  26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
  Need to get 34.9 MB of archives.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: polkitd 124-1
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Feb 22 08:46:48 2024
  ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-11-02 (112 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: policykit-1
  Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess 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/policykit-1/+bug/2054716/+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 2019026] Re: systemd /tmp cleaning is suboptimal

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 255.4-1ubuntu5

---
systemd (255.4-1ubuntu5) noble; urgency=medium

  * No-change rebuild against libcurl4t64

 -- Steve Langasek   Sat, 16 Mar 2024
07:04:30 +

** Changed in: systemd (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  systemd /tmp cleaning is suboptimal

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Noble:
  Fix Released

Bug description:
  Historically on Debian and Ubuntu, before systemd, the default
  handling of /tmp was to periodically, and at boot, remove all
  files/directories older than 30 days; and leave other contents alone.

  With the move to systemd, the "default" (really, hard-coded in
  /usr/lib/tmpfiles.d/tmp.conf) is to not clean /tmp periodically, but
  at boot to remove all contents.

  This is suboptimal for two reasons.

  By cleaning /tmp *only* at boot, if a system makes heavy use of /tmp
  and has lots of inodes under it, possibly due to failures of some
  process to clean up after itself, at boot the system will be
  unavailable for an unnecessarily long time while these files are
  removed.

  By cleaning *all* files under /tmp, this makes a reboot an Event where
  in-progress files may be unnecessarily lost.

  While the FHS does not *guarantee* that files under /tmp will persist
  across boot (because /tmp may be a tmpfs), it also does not *require*
  that /tmp be cleared on boot.

 Although data stored in /tmp may be deleted in a site-specific
 manner, it is recommended that files and directories located in
 /tmp be deleted whenever the system is booted.

 FHS added this recommendation on the basis of historical
 precedent and common practice, but did not make it a
 requirement because system administration is not within the
 scope of this standard.

  I therefore believe the correct value for /usr/lib/tmpfiles.d/tmp.conf
  to restore past behavior is 'd /tmp 1777 root root 30d'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2019026/+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 2055180] Re: coreutils 9.4-3ubuntu1 FTBFS

[Launchpad Bug Tracker]

This bug was fixed in the package coreutils - 9.4-3ubuntu3

---
coreutils (9.4-3ubuntu3) noble; urgency=medium

  * No-change rebuild against libssl3t64.

 -- Steve Langasek   Mon, 04 Mar 2024
04:54:09 +

** Changed in: coreutils (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  coreutils 9.4-3ubuntu1 FTBFS

Status in coreutils package in Ubuntu:
  Fix Released

Bug description:
  The recent upload FTBFS due to a build-time test failure[1]:

  
  FAIL: tests/cp/cp-i
  ===

  --- err4  2024-02-26 18:03:34.566066156 +
  +++ err_skip  2024-02-26 18:03:34.554065852 +
  @@ -1 +1 @@
  -cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
  +cp: not replacing 'd'
  FAIL tests/cp/cp-i.sh (exit status: 1)

  This appears related to a new Debian patch that we pulled in with the
  merge.

  [1] https://launchpadlibrarian.net/716215295/buildlog_ubuntu-noble-
  amd64.coreutils_9.4-3ubuntu1_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2055180/+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 2055200] Re: tests-in-lxd is broken with latest autopkgtest version

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 255.4-1ubuntu5

---
systemd (255.4-1ubuntu5) noble; urgency=medium

  * No-change rebuild against libcurl4t64

 -- Steve Langasek   Sat, 16 Mar 2024
07:04:30 +

** Changed in: systemd (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  tests-in-lxd is broken with latest autopkgtest version

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Mantic:
  Won't Fix

Bug description:
  With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks
  because it can't patch `autopkgtest-build-lxd` anymore.

  Please find a debdiff attached to fix that issue.

  [1]:
  https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+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 2055193] Re: [FFe] APT 24.04 crypto policy update

[Launchpad Bug Tracker]

This bug was fixed in the package gnupg2 - 2.4.4-2ubuntu15

---
gnupg2 (2.4.4-2ubuntu15) noble; urgency=medium

  * Also drop build dependency on libcurl4-gnutls-dev.

 -- Matthias Klose   Thu, 07 Mar 2024 10:32:56 +0100

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

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

Title:
  [FFe] APT 24.04 crypto policy update

Status in apt package in Ubuntu:
  Fix Committed
Status in gnupg2 package in Ubuntu:
  Fix Released

Bug description:
  I don't know if this will land before the feature freeze but I'm
  filing this in any case:

  Our goal for 24.04 is to reject 1024-bit RSA repository signing keys.
  Work is ongoing in Launchpad to allow dual-signing PPAs and then
  resign all PPAs with a 4096-bit key.

  This needs the following changes:

  1) The gnupg upstream commit for https://dev.gnupg.org/T6946 needs to be 
backported. This is applying fine and in the package already, but the test 
suite fails with issues that look weirdly unrelated.
  2) APT needs to learn to pass the argument if supported
  3) APT needs to learn to interpret the output
  4) APT possibly may have to learn to issue warnings instead of errors for 
weak keys and pass the URL to the gpgv method to allow 1024-bit RSA keys over 
TLS connections, in case there are unforeseen issues with the PPA migration.

  Signing key policy: We would like to adopt a signing key policy of

  rsa>2048,ed25519,ed448

  As a result we would like to reject

  - RSA keys below 2048 bits
  - DSA keys
  - Unsafe ECC keys:
    - NIST P-{256,384,521}
    - Brainpool P-{256,384,512}
    - secp256k1

  Notes:
  - DSA keys are not possible to use anymore due to the deprecation of SHA1 
that happened years ago
  - NIST and Brainpool and secp256k1 are not very popular, 
https://safecurves.cr.yp.to/ lists all of them as unsafe. It is believed they 
have backdoors. Some FIPS customers may prefer them over Ed25519 and Ed448 as 
they have been approved longer, so it's possible fips support packages could 
reenable them by setting the correct apt.conf setting in a snippet.

  
  Timing wrt feature freeze and launchpad changes:

  Launchpad changes won't be landing before feature freeze and it will
  take some more weeks to resign the repositories, hence we need to do
  uploads after FF to enable the error by default even if we ship the
  functionality before it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055193/+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 2056593] Re: [FFE] FIPS compatibility patches

[Launchpad Bug Tracker]

This bug was fixed in the package openssl - 3.0.13-0ubuntu2

---
openssl (3.0.13-0ubuntu2) noble; urgency=medium

  [ Tobias Heider ]
  * Add fips-mode detection and adjust defaults when running in fips mode
(LP: #2056593):
- d/p/fips/crypto-Add-kernel-FIPS-mode-detection.patch:
  Detect if kernel fips mode is enabled
- d/p/fips/crypto-Automatically-use-the-FIPS-provider-when-the-kerne.patch:
  Load FIPS provider if running in FIPS mode
- d/p/fips/apps-speed-Omit-unavailable-algorithms-in-FIPS-mode.patch:
  Limit openssl-speed to FIPS compliant algorithms when running in FIPS mode
- d/p/fips/apps-pass-propquery-arg-to-the-libctx-DRBG-fetches.patch
  Make sure DRBG respects query properties
- d/p/fips/test-Ensure-encoding-runs-with-the-correct-context-during.patch:
  Make sure encoding runs with correct library context and provider

  [ Adrien Nader ]
  * Re-enable intel/0002-AES-GCM-enabled-with-AVX512-vAES-and-vPCLMULQDQ.patch
(LP: #2030784)
Thanks Bun K Tan and Dan Zimmerman
  * Disable LTO with which the codebase is generally incompatible (LP: #2058017)

 -- Adrien Nader   Fri, 15 Mar 2024 09:46:33
+0100

** Changed in: openssl (Ubuntu)
   Status: Fix Committed => 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/2056593

Title:
  [FFE] FIPS compatibility patches

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  We have an open MR with a handful of FIPS compatibilty changes we wore hoping
  to get into 24.04. The main purpose of the changes is to detect whether the
  kernel is running in FIPS mode and adjust the behavior of the library
  accordingly by loading the correct provider backend and using defaults that
  are FIPS compliant (no md5, DES etc) instead trying to use non-compliant code
  paths and crashing.

  The proposed patches were taken from the OpenSSL version shipped in the FIPS
  archive at esm.ubuntu.com for 22.04. Having them in the regular archive will
  reduce the maintenance work significantly. None of the changes should have any
  impact on running OpenSSL in regular (non-fips) mode.

  Below is a detailed list of the changes:

  - d/p/fips/crypto-Add-kernel-FIPS-mode-detection.patch:
    This adds a new internal API to determine whether the kernel has been booted
    in FIPS mode. This can be overridden with the OPENSSL_FORCE_FIPS_MODE
    environment variable. OPENSSL_FIPS_MODE_SWITCH_PATH can be used to specify 
an
    alternative path for the fips_enabled file and is used in tests.
    The FIPS_MODULE switch can be used to enable build of the the FIPS provider
    module specific parts which are not needed in the OpenSSL library itself.

  - d/p/fips/crypto-Automatically-use-the-FIPS-provider-when-the-kerne.patch:
    This automatically configures all library contexts to use the FIPS provider 
when
    the kernel is booted in FIPS mode by:
    - Setting "fips=yes" as the default property for algorithm fetches
    - Loading and activating the FIPS provider as the fallback provider.

    If applications load providers via a configuration either because the 
default
    configuration is modified or they override the default configuration, this
    disables loading of the fallback providers. In this case, the configuration
    must load the FIPS provider when FIPS mode is enabled, else algorithm 
fetches
    will fail

    Applications can choose to use non-FIPS approved algorithms by specifying 
the
    "-fips" or "fips=no" property for algorithm fetches and loading the default
    provider.

  - d/p/fips/apps-speed-Omit-unavailable-algorithms-in-FIPS-mode.patch:
    Omit unavailable algorithms in FIPS mode

  - d/p/fips/apps-pass-propquery-arg-to-the-libctx-DRBG-fetches.patch
    The -propquery argument might be used to define a preference for which 
provider
    an algorithm is fetched from. Set the query properties for the library 
context
    DRBG fetches as well so that they are fetched with the same properties.

  - d/p/fips/test-Ensure-encoding-runs-with-the-correct-context-during.patch:
    This test uses 2 library contexts - one context for creating initial test 
keys,
    and then another context (or the default context) for running tests. There 
is an
    issue that during the encoding tests, the OSSL_ENCODER_CTX is created from 
the
    created EVP_PKEYs, which are associated with the library context used to 
create
    the keys. This means that encoding tests run with the wrong library context,
    which always uses the default provider.

  These changes are now included in a larger MR with other changes in
  the same package version:
  
https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+merge/462486

  The now-superseded MR is at
  
https://code.launchpad.net/~tobhe/ubuntu/+source/openssl/+git/openssl/+merge/460953

  Since 

[Touch-packages] [Bug 2058017] Re: openssl is not LTO-safe

[Launchpad Bug Tracker]

This bug was fixed in the package openssl - 3.0.13-0ubuntu2

---
openssl (3.0.13-0ubuntu2) noble; urgency=medium

  [ Tobias Heider ]
  * Add fips-mode detection and adjust defaults when running in fips mode
(LP: #2056593):
- d/p/fips/crypto-Add-kernel-FIPS-mode-detection.patch:
  Detect if kernel fips mode is enabled
- d/p/fips/crypto-Automatically-use-the-FIPS-provider-when-the-kerne.patch:
  Load FIPS provider if running in FIPS mode
- d/p/fips/apps-speed-Omit-unavailable-algorithms-in-FIPS-mode.patch:
  Limit openssl-speed to FIPS compliant algorithms when running in FIPS mode
- d/p/fips/apps-pass-propquery-arg-to-the-libctx-DRBG-fetches.patch
  Make sure DRBG respects query properties
- d/p/fips/test-Ensure-encoding-runs-with-the-correct-context-during.patch:
  Make sure encoding runs with correct library context and provider

  [ Adrien Nader ]
  * Re-enable intel/0002-AES-GCM-enabled-with-AVX512-vAES-and-vPCLMULQDQ.patch
(LP: #2030784)
Thanks Bun K Tan and Dan Zimmerman
  * Disable LTO with which the codebase is generally incompatible (LP: #2058017)

 -- Adrien Nader   Fri, 15 Mar 2024 09:46:33
+0100

** Changed in: openssl (Ubuntu)
   Status: Fix Committed => 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/2058017

Title:
  openssl is not LTO-safe

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  tl;dr: since it's too much work to make openssl LTO-safe, upstream
  doesn't see it as a goal and doesn't test it, and there are probably
  no performance gains to LTO for this package.

  Openssl is an old project and the codebase wasn't written with
  aliasing rules in mind. There are several reports of issues related to
  LTO. The openssl technical commitee says "currently we're not going to
  fix all the strict aliasing and other LTO problems" and "Fixes raised
  in pull requests will be considered."; in other words: if you find a
  violation, we'll merge your fixes but we're not going to dedicate time
  to fixing them ourselves.

  We don't have specific reports on launchpad at the moment but there
  has been at least one issue experienced by the FIPS: the compiler
  decided a 0-filled array could be removed and proceeded to do so. In
  addition to that, compilers are only pushing this further and further.
  Issues are impossible to predict and even security updates could
  trigger issues.

  Gentoo prevents usage of LTO for openssl and has some links related to this 
at 
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/openssl/openssl-3.2.1-r1.ebuild#n131
 :
  - https://github.com/llvm/llvm-project/issues/55255
  - https://github.com/openssl/openssl/issues/12247
  - https://github.com/openssl/openssl/issues/18225
  - https://github.com/openssl/openssl/issues/18663
  - https://github.com/openssl/openssl/issues/18663#issuecomment-1181478057

  Gentoo also prevents usage of -fstrict-aliasing and always set -fno-
  strict-aliasing. I don't plan to do the same at least at the moment
  and for Noble since I don't have time to investigate more changes.

  Performance shouldn't be impacted much if at all:
  - crypto algorithms are implemented in ASM (funnily, using C implementations 
can trigger issues because these got miscompiled)
  - the rest of the openssl codebase probably doesn't benefit from LTO because 
source files match codepaths quite well
  - at the moment, openssl performance for servers is bad due to 
algorithmic/architectural issues, not micro-optimizations and these wouldn't be 
noticed
  - if LTO-compliance was doable and thought to be useful by upstream, they 
would have certainly pushed that forward, especially in the wake of openssl 
3.0's performance issues.

  Code size increases by a few percents except for libcrypto which gets
  17% larger. The corresponding .deb file increases by 2.6% only.

  I ran "openssl speed" with a long benchmark time in order to get good
  results (there is a variation of several percents with the default
  times). I then scripted a diff which output is shown below; "."
  means the difference is within 2% which is the vast majority. Also
  note that some important ciphers are not present due to how openssl
  speed works; small aes-*-cbc are negatively impacted, up to -10% but
  that would -50% if you compared between "software" and "hardware"
  implementations, the results would be reversed at anything but the
  smallest data sizes, and the fact that you want to use hardware
  implementations as much as possible means that you also want to avoid
  places where LTO could have an effect.

  type  16  bytes   64 bytes  256  
bytes   1024   bytes  8192  bytes  16384  bytes
  md5   .   .   .  .  ..
  sha1  .   .   

[Touch-packages] [Bug 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1

[Launchpad Bug Tracker]

This bug was fixed in the package cups - 2.4.7-1.2ubuntu2

---
cups (2.4.7-1.2ubuntu2) noble; urgency=low

  * Remove Debian's own (broken) cups.pc file, CUPS has it upstreanm from
2.4.6 on (LP: #2059157).

 -- Till Kamppeter   Tue, 26 Mar 2024 23:17:19
+0100

** Changed in: cups (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  proposed-migration for cups 2.4.7-1.2ubuntu1

Status in c2esp package in Ubuntu:
  New
Status in cups package in Ubuntu:
  Fix Released

Bug description:
  multiple cups-related packages are having test failures on armhf after time_t 
transition.
  https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf
  https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9

  I am suspecting a common cups-based issue.

  cups-browsed already has a separate bug open at
  https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

[DanielBodart]

I thought it was worth mentioning that sound does work via the headphone
jack on Ubuntu 23.10 and that when using the speaker, audio levels are
still detected in system settings. This makes me think all codecs etc
are working but that it's a simple toggle somewhere to get the speaker
to work rather than it requiring driver updates etc.

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2026885] Re: nano is not available on i386

[Steve Langasek]

packages are provided on i386 only if they are required for binary
compatibility.

** Changed in: nano (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 nano in Ubuntu.
https://bugs.launchpad.net/bugs/2026885

Title:
  nano is not available on i386

Status in nano package in Ubuntu:
  Won't Fix

Bug description:
  There is no i386 Nano package in Jammy. I used Nano all the time
  including in chroots, which is where this reared its ugly head.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/2026885/+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 2058242] Re: Demote isc-dhcp to universe

[Steve Langasek]

anyway, this doesn't need an ubuntu-archive bug, it just needs the
dependency removed.

** Package changed: isc-dhcp (Ubuntu) => avahi (Ubuntu)

** Changed in: avahi (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Demote isc-dhcp to universe

Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Following the replacement of dhclient by dhcpcd as new DHCP client
  tool, it is now time to demote isc-dhcp-client. After demoting isc-
  dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted.

  ```
  $ reverse-depends -c main,restricted isc-dhcp-client
  $ reverse-depends -c main,restricted -b isc-dhcp-client
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2058242/+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 2058242] Re: Demote isc-dhcp to universe

[Steve Langasek]

avahi-autoipd still depends on it. But I was sure I uploaded avahi to
drop it?

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

Title:
  Demote isc-dhcp to universe

Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Following the replacement of dhclient by dhcpcd as new DHCP client
  tool, it is now time to demote isc-dhcp-client. After demoting isc-
  dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted.

  ```
  $ reverse-depends -c main,restricted isc-dhcp-client
  $ reverse-depends -c main,restricted -b isc-dhcp-client
  ```

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