[Touch-packages] [Bug 2045494] Re: did not upgrade to 23.10

[Launchpad Bug Tracker]

[Expired for apt (Ubuntu) because there has been no activity for 60
days.]

** Changed in: apt (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  did not upgrade to 23.10

Status in apt package in Ubuntu:
  Expired

Bug description:
  root@localhost:/home/larsmartin# sudo apt update && sudo apt upgrade
  Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
  Hit:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
  Hit:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  1 package can be upgraded. Run 'apt list --upgradable' to see it.
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
exo-utils libopenexr25 libpostproc55 libavcodec58 libavutil56 libswscale5
xrdp libexo-2-0 libswresample3 libavformat58 libexo-common libavfilter7
  Learn more about Ubuntu Pro at https://ubuntu.com/pro
  The following packages have been kept back:
libayatana-appindicator3-1
  0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
  root@localhost:/home/larsmartin# sudo do-release-upgrade 
  Checking for a new Ubuntu release
  Please install all available updates for your release before upgra

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.11
  ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
  Uname: Linux 5.15.0-89-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Dec  3 09:21:14 2023
  InstallationDate: Installed on 2020-07-05 (1245 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-03-24 (618 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2045494/+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 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64

[Bug Watch Updater]

** Changed in: cpio (Debian)
   Status: Unknown => New

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

Title:
  autopkgtest unshare-qemuwrapper failing on amd64

Status in cpio package in Ubuntu:
  In Progress
Status in sbuild package in Ubuntu:
  New
Status in cpio source package in Noble:
  In Progress
Status in sbuild source package in Noble:
  New
Status in cpio package in Debian:
  New

Bug description:
  While watching Noble openssh migration, I saw this test failing and
  marking amd64 as regression.

  Log :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz

  Relevant part of the log:

  1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/
  1565s Setting up cpio (2.15+dfsg-1) ...
  1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist
  1565s dpkg: error processing package cpio (--configure):
  1565s  installed cpio package post-installation script subprocess returned 
error exit status 2

  It can be reproduced locally, too.

  The most recent test working is from 01/08/2024:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz

  The cpio version in the immediately log above is lower. The same
  (working) part is:

  2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/
  2188s Setting up cpio (2.14+dfsg-1) ...
  2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto 
mode

  cpio diff :
  https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+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 2050033] Re: gettext: msgfmt --java2 does not support Java 21

[Launchpad Bug Tracker]

This bug was fixed in the package gettext - 0.21-14ubuntu1

---
gettext (0.21-14ubuntu1) noble; urgency=medium

  * Update patches to support Java 21 (LP: #2050033):
- d/p/12-in-language-java-avoid-stack-overflow.patch: cherry-pick upstream
  patch to resolve Java 21 FTBFS.
- d/p/07-java-17-support.patch: add Java versions, set release level 8.

 -- Vladimir Petko   Mon, 22 Jan 2024
13:33:17 +1300

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

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

Title:
  gettext: msgfmt --java2 does not support Java 21

Status in gettext package in Ubuntu:
  Fix Released
Status in gettext package in Debian:
  New

Bug description:
  When building 'ssl-utils-clojure' package with Java 21 as default, the build
  fails with the following trace:
  --
  Applying task i18n to [make]
  Running 'make i18n'
  make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  --

  Running make in the build chroot produces the following error:
  ---
  msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
  locales/eo.po
  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
  make: *** [dev-resources/Makefile.i18n:94:
  resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
  ---

  It appears that gettext package does not support Java 21.

  Note: gettext 0.22.4 refactors Java support. This delta can be safely
  dropped after a new upstream release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64

[Miriam España Acebal]

Patch has been forwarded to Debian.

Added the Debian bug I created for tracking.

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

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

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

Title:
  autopkgtest unshare-qemuwrapper failing on amd64

Status in cpio package in Ubuntu:
  In Progress
Status in sbuild package in Ubuntu:
  New
Status in cpio source package in Noble:
  In Progress
Status in sbuild source package in Noble:
  New
Status in cpio package in Debian:
  Unknown

Bug description:
  While watching Noble openssh migration, I saw this test failing and
  marking amd64 as regression.

  Log :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz

  Relevant part of the log:

  1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/
  1565s Setting up cpio (2.15+dfsg-1) ...
  1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist
  1565s dpkg: error processing package cpio (--configure):
  1565s  installed cpio package post-installation script subprocess returned 
error exit status 2

  It can be reproduced locally, too.

  The most recent test working is from 01/08/2024:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz

  The cpio version in the immediately log above is lower. The same
  (working) part is:

  2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/
  2188s Setting up cpio (2.14+dfsg-1) ...
  2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto 
mode

  cpio diff :
  https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+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 2052328] [NEW] openssh-client encounters MAC algo issue with EL8

[Vip]

Public bug reported:

Ubuntu 22.04 system connecting to an Oracle Linux v8 host.  The
following error occurs regardless of the the MACs specified (or not) in
sshd_config:

Corrupted MAC on input.
ssh_dispatch_run_fatal: Connection to XX.XX.XX.XX port 22: message 
authentication code incorrect

Presumably, this may happen on any RHEL v8 variant. Note that connecting
to Enterprise Linux v7 work as well as other Ubuntu hosts. Downgrading
to previous version of openssh-client fixes issue.

apt install openssh-client=1:8.9p1-3

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

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

Title:
  openssh-client encounters MAC algo issue with EL8

Status in openssh package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 system connecting to an Oracle Linux v8 host.  The
  following error occurs regardless of the the MACs specified (or not)
  in sshd_config:

  Corrupted MAC on input.
  ssh_dispatch_run_fatal: Connection to XX.XX.XX.XX port 22: message 
authentication code incorrect

  Presumably, this may happen on any RHEL v8 variant. Note that
  connecting to Enterprise Linux v7 work as well as other Ubuntu hosts.
  Downgrading to previous version of openssh-client fixes issue.

  apt install openssh-client=1:8.9p1-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2052328/+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 2051540] Re: ufw ftbfs with Python 3.12 as default

[Bug Watch Updater]

** Changed in: ufw (Debian)
   Status: New => Fix Released

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

Title:
  ufw ftbfs with Python 3.12 as default

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

Bug description:
  ==
  ERROR: test_ufwcommand_parse 
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
  Test UFWCommand.parse()
  --
  Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in 
test_ufwcommand_parse
  self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
  ^
  AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did 
you mean: 'assertEqual'?

  ==
  ERROR: test_ufwcommand_rule_get_command 
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
  Test UFWCommand(Route)Rule.get_command()
  --
  Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in 
test_ufwcommand_rule_get_command
  self.assertEquals(len(errors), 0,
  ^
  AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did 
you mean: 'assertEqual'?

  --
  Ran 24 tests in 7.584s

  FAILED (errors=9)
  test_skeleton
  test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
  Test example dummy test ... ok

  --
  Ran 1 test in 0.000s

  OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2051540/+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 2052324] [NEW] Gnome not possible run from wsl

[Tero Nevalainen]

Public bug reported:

there is error xorg.conf (EE) no screens found(EE)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
Uname: Linux 5.15.133.1-microsoft-standard-WSL2 x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDmesg:
 Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
 ** (process:4174): WARNING **: 20:44:25.586: Unable to register authentication 
agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication 
agent already exists for the given subject
 Error registering local authentication agent: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent 
already exists for the given subject
Date: Fri Feb  2 20:44:11 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 
Lspci-vt:
 -+-[a214:00]---00.0  Red Hat, Inc. Virtio console
  \-[:00]-
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 480M
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: initrd=\initrd.img WSL_ROOT_INIT=1 panic=-1 nr_cpus=4 
bonding.max_bonds=0 dummy.numdummies=0 fb_tunnels=none console=hvc0 debug 
pty.legacy_count=0
ProcModules:
 
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
 Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with 
exit code 127: 
 ** (process:4187): WARNING **: 20:44:25.696: Unable to register authentication 
agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication 
agent already exists for the given subject
 Error registering local authentication agent: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent 
already exists for the given subject
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  Gnome not possible run from wsl

Status in xorg package in Ubuntu:
  New

Bug description:
  there is error xorg.conf (EE) no screens found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  Uname: Linux 5.15.133.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
   ** (process:4174): WARNING **: 20:44:25.586: Unable to register 
authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An 
authentication agent already exists for the given subject
   Error registering local authentication agent: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent 
already exists for the given subject
  Date: Fri Feb  2 20:44:11 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  Lspci-vt:
   -+-[a214:00]---00.0  Red Hat, Inc. Virtio console
\-[:00]-
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 480M
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: initrd=\initrd.img WSL_ROOT_INIT=1 panic=-1 nr_cpus=4 
bonding.max_bonds=0 dummy.numdummies=0 fb_tunnels=none console=hvc0 debug 
pty.legacy_count=0
  ProcModules:
   
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: 
   ** (process:4187): WARNING **: 20:44:25.696: Unable to register 
authentication agent: 

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

[John Johansen]

We have found that allowing the user namespace creation, and then
denying capabilities is in general handled much better by KDE. The the
case of the plasmashell and the browswer widget denying the creation of
the user namespace would cause a crash with a SIGTRAP backtrace, where
allowing the creation of the userns and then denying capabilities within
the user namespace would result in the browser widget falling back to a
sandbox that didn't use user namespaces, not ideal but better than a
crash. To make sure the widget was using the full sandbox we gave it a
profile (see QtWebEngineProcess in /etc/apparmor.d/plasmashell).

The apparmor package is adding a base set of profiles, including one for
the plasmashell and the unprivileged_userns profile.

We are willing to carry profiles in the apparmor package but are also
happy for other packages to carry them. Generally speaking, having the
profile carried in the package means its easier for the package
maintainer to update the profile, if that is something the package
maintainer is willing to do.

We are more than willing to take in profiles and patches to profiles, or
allow a maintainer to claim some profiles and move them out of the
apparmor package. What ever is best for the maintainer.

AppArmor does have a second set of profiles that are not installed by
default in the apparmor-profiles package. These profiles once installed
are not enabled by default but must be selectively enabled by the user.
If you are looking for a broader set of profiles as a base to start from
there is also the apparmor.d project
https://github.com/roddhjav/apparmor.d. They aren't tuned for ubuntu but
they can be a good starting point if a profile is needed.


Note: the current apparmor package doesn't allow you to specify the userns 
transition in policy. A new version of the apparmor package is coming that will 
allow it.

-- 
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 akregator package in Ubuntu:
  Confirmed
Status in angelfish package in Ubuntu:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Confirmed
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Confirmed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Confirmed
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kiwix package in Ubuntu:
  Confirmed
Status in konqueror package in Ubuntu:
  Confirmed
Status in kontact package in Ubuntu:
  Confirmed
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Confirmed
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in privacybrowser package in Ubuntu:
  Confirmed
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:
  Confirmed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Confirmed

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 denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: 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)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

[Krister Johansen]

Hi Matthew,
Thanks for the update. I'm glad this finally reproduced in your environment.  I 
don't have a great explanation for why it took so much longer there.  I did 
observe that it seemed more likely to occur in us-west-2 during the 9a-5p 
window in the local timezone. The timing may be subtly affected by overall EBS 
utilization.  Just a guess, though.

Thanks again,

-K

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

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  In Progress
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  In Progress
Status in e2fsprogs source package in Jammy:
  In Progress
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in e2fsprogs source package in Mantic:
  In Progress

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2040406] Re: Merge openssh from Debian unstable for noble

[Launchpad Bug Tracker]

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

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

  * Merge with Debian unstable (LP: #2040406). Remaining changes:
- debian/rules: modify dh_installsystemd invocations for
  socket-activated sshd.
- debian/openssh-server.postinst: handle migration of sshd_config
  options to systemd socket options on upgrade.
- debian/README.Debian: document systemd socket activation.
- debian/patches/socket-activation-documentation.patch: Document
  in sshd_config(5) that ListenAddress and Port no longer work.
- debian/openssh-server.templates: include debconf prompt
  explaining when migration cannot happen due to multiple
  ListenAddress values.
- debian/.gitignore: drop file.
- debian/openssh-server.postrm: remove systemd drop-ins for
  socket-activated sshd on purge.
- debian/openssh-server.ucf-md5sum: update for Ubuntu delta
- debian/openssh-server.tmpfile,debian/systemd/ssh.service: Move
  /run/sshd creation out of the systemd unit to a tmpfile config
  so that sshd can be run manually if necessary without having to
  create this directory by hand.
- debian/patches/systemd-socket-activation.patch: Fix sshd
  re-execution behavior when socket activation is used.
- debian/tests/systemd-socket-activation: Add autopkgtest
  for systemd socket activation functionality.
- d/p/test-set-UsePAM-no-on-some-tests.patch: set UsePAM=no
  for some tests.
  * Dropped changes, fixed upstream:
- d/p/fix-ftbfs-with-zlib13.patch: fix ftbfs when using zlib 1.3
  (LP #2049552)

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

  * Allow passing extra ssh-agent arguments via
"/usr/lib/openssh/agent-launch start", making it possible to override
things like identity lifetime using a systemd drop-in unit (closes:
#1059639).
  * Don't try to start rescue-ssh.target in postinst (LP: #2047082).

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

  * Improve detection of broken -fzero-call-used-regs=used (see
https://bugzilla.mindrot.org/show_bug.cgi?id=3645; fixes build on
ppc64/ppc64el).

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

  * Use single quotes in suggested ssh-keygen commands (closes: #1057835).
  * Debconf translations:
- Catalan (thanks, Pablo Huguet; closes: #1049995).
  * New upstream release (https://www.openssh.com/releasenotes.html#9.6p1):
- [CVE-2023-48795] ssh(1), sshd(8): implement protocol extensions to
  thwart the so-called "Terrapin attack" discovered by Fabian Bäumer,
  Marcus Brinkmann and Jörg Schwenk. This attack allows a MITM to effect
  a limited break of the integrity of the early encrypted SSH transport
  protocol by sending extra messages prior to the commencement of
  encryption, and deleting an equal number of consecutive messages
  immediately after encryption starts. A peer SSH client/server would
  not be able to detect that messages were deleted.
- [CVE-2023-51384] ssh-agent(1): when adding PKCS#11-hosted private keys
  while specifying destination constraints, if the PKCS#11 token
  returned multiple keys then only the first key had the constraints
  applied. Use of regular private keys, FIDO tokens and unconstrained
  keys are unaffected.
- [CVE-2023-51385] ssh(1): if an invalid user or hostname that contained
  shell metacharacters was passed to ssh(1), and a ProxyCommand,
  LocalCommand directive or "match exec" predicate referenced the user
  or hostname via %u, %h or similar expansion token, then an attacker
  who could supply arbitrary user/hostnames to ssh(1) could potentially
  perform command injection depending on what quoting was present in the
  user-supplied ssh_config(5) directive. OpenSSH 9.6 now bans most shell
  metacharacters from user and hostnames supplied via the command-line.
- ssh(1), sshd(8): the RFC4254 connection/channels protocol provides a
  TCP-like window mechanism that limits the amount of data that can be
  sent without acceptance from the peer. In cases where this limit was
  exceeded by a non-conforming peer SSH implementation, ssh(1)/sshd(8)
  previously discarded the extra data. From OpenSSH 9.6, ssh(1)/sshd(8)
  will now terminate the connection if a peer exceeds the window limit
  by more than a small grace factor. This change should have no effect
  of SSH implementations that follow the specification.
- ssh(1): add a %j token that expands to the configured ProxyJump
  hostname (or the empty string if this option is not being used) that
  can be used in a number of ssh_config(5) keywords.
- ssh(1): add ChannelTimeout support to the client, mirroring the same
  option in the server and allowing ssh(1) to terminate quiescent
  channels.
- ssh(1), sshd(8), ssh-add(1), ssh-keygen(1): add support for reading
  ED25519 private 

[Touch-packages] [Bug 2047082] Re: upgrading openssh-server always shows error: rescue-ssh.target is a disabled or a static unit not running, not starting it.

[Launchpad Bug Tracker]

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

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

  * Merge with Debian unstable (LP: #2040406). Remaining changes:
- debian/rules: modify dh_installsystemd invocations for
  socket-activated sshd.
- debian/openssh-server.postinst: handle migration of sshd_config
  options to systemd socket options on upgrade.
- debian/README.Debian: document systemd socket activation.
- debian/patches/socket-activation-documentation.patch: Document
  in sshd_config(5) that ListenAddress and Port no longer work.
- debian/openssh-server.templates: include debconf prompt
  explaining when migration cannot happen due to multiple
  ListenAddress values.
- debian/.gitignore: drop file.
- debian/openssh-server.postrm: remove systemd drop-ins for
  socket-activated sshd on purge.
- debian/openssh-server.ucf-md5sum: update for Ubuntu delta
- debian/openssh-server.tmpfile,debian/systemd/ssh.service: Move
  /run/sshd creation out of the systemd unit to a tmpfile config
  so that sshd can be run manually if necessary without having to
  create this directory by hand.
- debian/patches/systemd-socket-activation.patch: Fix sshd
  re-execution behavior when socket activation is used.
- debian/tests/systemd-socket-activation: Add autopkgtest
  for systemd socket activation functionality.
- d/p/test-set-UsePAM-no-on-some-tests.patch: set UsePAM=no
  for some tests.
  * Dropped changes, fixed upstream:
- d/p/fix-ftbfs-with-zlib13.patch: fix ftbfs when using zlib 1.3
  (LP #2049552)

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

  * Allow passing extra ssh-agent arguments via
"/usr/lib/openssh/agent-launch start", making it possible to override
things like identity lifetime using a systemd drop-in unit (closes:
#1059639).
  * Don't try to start rescue-ssh.target in postinst (LP: #2047082).

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

  * Improve detection of broken -fzero-call-used-regs=used (see
https://bugzilla.mindrot.org/show_bug.cgi?id=3645; fixes build on
ppc64/ppc64el).

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

  * Use single quotes in suggested ssh-keygen commands (closes: #1057835).
  * Debconf translations:
- Catalan (thanks, Pablo Huguet; closes: #1049995).
  * New upstream release (https://www.openssh.com/releasenotes.html#9.6p1):
- [CVE-2023-48795] ssh(1), sshd(8): implement protocol extensions to
  thwart the so-called "Terrapin attack" discovered by Fabian Bäumer,
  Marcus Brinkmann and Jörg Schwenk. This attack allows a MITM to effect
  a limited break of the integrity of the early encrypted SSH transport
  protocol by sending extra messages prior to the commencement of
  encryption, and deleting an equal number of consecutive messages
  immediately after encryption starts. A peer SSH client/server would
  not be able to detect that messages were deleted.
- [CVE-2023-51384] ssh-agent(1): when adding PKCS#11-hosted private keys
  while specifying destination constraints, if the PKCS#11 token
  returned multiple keys then only the first key had the constraints
  applied. Use of regular private keys, FIDO tokens and unconstrained
  keys are unaffected.
- [CVE-2023-51385] ssh(1): if an invalid user or hostname that contained
  shell metacharacters was passed to ssh(1), and a ProxyCommand,
  LocalCommand directive or "match exec" predicate referenced the user
  or hostname via %u, %h or similar expansion token, then an attacker
  who could supply arbitrary user/hostnames to ssh(1) could potentially
  perform command injection depending on what quoting was present in the
  user-supplied ssh_config(5) directive. OpenSSH 9.6 now bans most shell
  metacharacters from user and hostnames supplied via the command-line.
- ssh(1), sshd(8): the RFC4254 connection/channels protocol provides a
  TCP-like window mechanism that limits the amount of data that can be
  sent without acceptance from the peer. In cases where this limit was
  exceeded by a non-conforming peer SSH implementation, ssh(1)/sshd(8)
  previously discarded the extra data. From OpenSSH 9.6, ssh(1)/sshd(8)
  will now terminate the connection if a peer exceeds the window limit
  by more than a small grace factor. This change should have no effect
  of SSH implementations that follow the specification.
- ssh(1): add a %j token that expands to the configured ProxyJump
  hostname (or the empty string if this option is not being used) that
  can be used in a number of ssh_config(5) keywords.
- ssh(1): add ChannelTimeout support to the client, mirroring the same
  option in the server and allowing ssh(1) to terminate quiescent
  channels.
- ssh(1), sshd(8), ssh-add(1), ssh-keygen(1): add support for reading
  ED25519 private 

[Touch-packages] [Bug 2049552] Re: [noble] ftbfs with new zlib 1.3

[Launchpad Bug Tracker]

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

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

  * Merge with Debian unstable (LP: #2040406). Remaining changes:
- debian/rules: modify dh_installsystemd invocations for
  socket-activated sshd.
- debian/openssh-server.postinst: handle migration of sshd_config
  options to systemd socket options on upgrade.
- debian/README.Debian: document systemd socket activation.
- debian/patches/socket-activation-documentation.patch: Document
  in sshd_config(5) that ListenAddress and Port no longer work.
- debian/openssh-server.templates: include debconf prompt
  explaining when migration cannot happen due to multiple
  ListenAddress values.
- debian/.gitignore: drop file.
- debian/openssh-server.postrm: remove systemd drop-ins for
  socket-activated sshd on purge.
- debian/openssh-server.ucf-md5sum: update for Ubuntu delta
- debian/openssh-server.tmpfile,debian/systemd/ssh.service: Move
  /run/sshd creation out of the systemd unit to a tmpfile config
  so that sshd can be run manually if necessary without having to
  create this directory by hand.
- debian/patches/systemd-socket-activation.patch: Fix sshd
  re-execution behavior when socket activation is used.
- debian/tests/systemd-socket-activation: Add autopkgtest
  for systemd socket activation functionality.
- d/p/test-set-UsePAM-no-on-some-tests.patch: set UsePAM=no
  for some tests.
  * Dropped changes, fixed upstream:
- d/p/fix-ftbfs-with-zlib13.patch: fix ftbfs when using zlib 1.3
  (LP #2049552)

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

  * Allow passing extra ssh-agent arguments via
"/usr/lib/openssh/agent-launch start", making it possible to override
things like identity lifetime using a systemd drop-in unit (closes:
#1059639).
  * Don't try to start rescue-ssh.target in postinst (LP: #2047082).

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

  * Improve detection of broken -fzero-call-used-regs=used (see
https://bugzilla.mindrot.org/show_bug.cgi?id=3645; fixes build on
ppc64/ppc64el).

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

  * Use single quotes in suggested ssh-keygen commands (closes: #1057835).
  * Debconf translations:
- Catalan (thanks, Pablo Huguet; closes: #1049995).
  * New upstream release (https://www.openssh.com/releasenotes.html#9.6p1):
- [CVE-2023-48795] ssh(1), sshd(8): implement protocol extensions to
  thwart the so-called "Terrapin attack" discovered by Fabian Bäumer,
  Marcus Brinkmann and Jörg Schwenk. This attack allows a MITM to effect
  a limited break of the integrity of the early encrypted SSH transport
  protocol by sending extra messages prior to the commencement of
  encryption, and deleting an equal number of consecutive messages
  immediately after encryption starts. A peer SSH client/server would
  not be able to detect that messages were deleted.
- [CVE-2023-51384] ssh-agent(1): when adding PKCS#11-hosted private keys
  while specifying destination constraints, if the PKCS#11 token
  returned multiple keys then only the first key had the constraints
  applied. Use of regular private keys, FIDO tokens and unconstrained
  keys are unaffected.
- [CVE-2023-51385] ssh(1): if an invalid user or hostname that contained
  shell metacharacters was passed to ssh(1), and a ProxyCommand,
  LocalCommand directive or "match exec" predicate referenced the user
  or hostname via %u, %h or similar expansion token, then an attacker
  who could supply arbitrary user/hostnames to ssh(1) could potentially
  perform command injection depending on what quoting was present in the
  user-supplied ssh_config(5) directive. OpenSSH 9.6 now bans most shell
  metacharacters from user and hostnames supplied via the command-line.
- ssh(1), sshd(8): the RFC4254 connection/channels protocol provides a
  TCP-like window mechanism that limits the amount of data that can be
  sent without acceptance from the peer. In cases where this limit was
  exceeded by a non-conforming peer SSH implementation, ssh(1)/sshd(8)
  previously discarded the extra data. From OpenSSH 9.6, ssh(1)/sshd(8)
  will now terminate the connection if a peer exceeds the window limit
  by more than a small grace factor. This change should have no effect
  of SSH implementations that follow the specification.
- ssh(1): add a %j token that expands to the configured ProxyJump
  hostname (or the empty string if this option is not being used) that
  can be used in a number of ssh_config(5) keywords.
- ssh(1): add ChannelTimeout support to the client, mirroring the same
  option in the server and allowing ssh(1) to terminate quiescent
  channels.
- ssh(1), sshd(8), ssh-add(1), ssh-keygen(1): add support for reading
  ED25519 private 

[Touch-packages] [Bug 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64

[Miriam España Acebal]

** Merge proposal linked:
   
https://code.launchpad.net/~mirespace/ubuntu/+source/cpio/+git/cpio/+merge/459933

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

Title:
  autopkgtest unshare-qemuwrapper failing on amd64

Status in cpio package in Ubuntu:
  In Progress
Status in sbuild package in Ubuntu:
  New
Status in cpio source package in Noble:
  In Progress
Status in sbuild source package in Noble:
  New

Bug description:
  While watching Noble openssh migration, I saw this test failing and
  marking amd64 as regression.

  Log :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz

  Relevant part of the log:

  1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/
  1565s Setting up cpio (2.15+dfsg-1) ...
  1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist
  1565s dpkg: error processing package cpio (--configure):
  1565s  installed cpio package post-installation script subprocess returned 
error exit status 2

  It can be reproduced locally, too.

  The most recent test working is from 01/08/2024:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz

  The cpio version in the immediately log above is lower. The same
  (working) part is:

  2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/
  2188s Setting up cpio (2.14+dfsg-1) ...
  2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto 
mode

  cpio diff :
  https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+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 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64

[Miriam España Acebal]

** Description changed:

- While looking Noble openssh transition, I saw this test failing and
+ While looking Noble openssh migration, I saw this test failing and
  marking amd64 as regression.
  
  Log :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz
  
  Relevant part of the log:
  
  1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/
  1565s Setting up cpio (2.15+dfsg-1) ...
  1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist
  1565s dpkg: error processing package cpio (--configure):
  1565s  installed cpio package post-installation script subprocess returned 
error exit status 2
- 
  
  It can be reproduced locally, too.
  
  The most recent test working is from 01/08/2024:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz
  
  The cpio version in the immediately log above is lower. The same
  (working) part is:
  
  2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/
  2188s Setting up cpio (2.14+dfsg-1) ...
  2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto 
mode
  
  cpio diff :
  https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz

** Description changed:

- While looking Noble openssh migration, I saw this test failing and
+ While watching Noble openssh migration, I saw this test failing and
  marking amd64 as regression.
  
  Log :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz
  
  Relevant part of the log:
  
  1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/
  1565s Setting up cpio (2.15+dfsg-1) ...
  1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist
  1565s dpkg: error processing package cpio (--configure):
  1565s  installed cpio package post-installation script subprocess returned 
error exit status 2
  
  It can be reproduced locally, too.
  
  The most recent test working is from 01/08/2024:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz
  
  The cpio version in the immediately log above is lower. The same
  (working) part is:
  
  2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/
  2188s Setting up cpio (2.14+dfsg-1) ...
  2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto 
mode
  
  cpio diff :
  https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz

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

Title:
  autopkgtest unshare-qemuwrapper failing on amd64

Status in cpio package in Ubuntu:
  In Progress
Status in sbuild package in Ubuntu:
  New
Status in cpio source package in Noble:
  In Progress
Status in sbuild source package in Noble:
  New

Bug description:
  While watching Noble openssh migration, I saw this test failing and
  marking amd64 as regression.

  Log :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz

  Relevant part of the log:

  1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/
  1565s Setting up cpio (2.15+dfsg-1) ...
  1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist
  1565s dpkg: error processing package cpio (--configure):
  1565s  installed cpio package post-installation script subprocess returned 
error exit status 2

  It can be reproduced locally, too.

  The most recent test working is from 01/08/2024:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz

  The cpio version in the immediately log above is lower. The same
  (working) part is:

  2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/
  2188s Setting up cpio (2.14+dfsg-1) ...
  2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto 
mode

  cpio diff :
  https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

[Simon Déziel]

This was verified on Mantic with -proposed (1:5.0.1-0ubuntu8~23.10.1).
Here's how:

$ lxc launch ubuntu-daily:23.10 c2
Creating c2
Starting c2

$ lxc shell c2

root@c2:~# apt-get update
...
root@c2:~# apt-get install -Vy liblxc-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
...
   liblxc-common (1:5.0.1-0ubuntu7)
   liblxc1 (1:5.0.1-0ubuntu7)
...
   lxcfs (5.0.3-1)
..

root@c2:~# dpkg -l | grep liblxc-dev
ii  liblxc-dev  1:5.0.1-0ubuntu7
amd64Linux Containers userspace tools (development)
root@c2:~# grep LXC_DEVEL /usr/include/lxc/version.h
#define LXC_DEVEL 1


# enable -proposed

root@c2:~# apt-get update
...
root@c2:~# apt-get install -t mantic-proposed -Vy liblxc-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
   liblxc-common (1:5.0.1-0ubuntu8~23.10.1)
   liblxc1 (1:5.0.1-0ubuntu8~23.10.1)
The following packages will be upgraded:
   liblxc-common (1:5.0.1-0ubuntu7 => 1:5.0.1-0ubuntu8~23.10.1)
   liblxc-dev (1:5.0.1-0ubuntu7 => 1:5.0.1-0ubuntu8~23.10.1)
   liblxc1 (1:5.0.1-0ubuntu7 => 1:5.0.1-0ubuntu8~23.10.1)
3 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
Need to get 1804 kB of archives.
...

root@c2:~# grep LXC_DEVEL /usr/include/lxc/version.h
#define LXC_DEVEL 0

** Tags removed: verification-needed verification-needed-mantic
** Tags added: verification-done verification-done-mantic

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

Title:
  [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Jammy:
  Fix Committed
Status in lxc source package in Mantic:
  Fix Committed
Status in lxc source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2052307] Re: ALSA error: snd_pcm_open failed: Operation not supported.

[Cliff Carson]

Switching to VLC to play the same radio stream works as expected.

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

Title:
  ALSA error: snd_pcm_open failed: Operation not supported.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Getting the following error trying to play a radio stream in
  Audacious.

  ERROR ../src/libaudgui/util.cc:328 [audgui_simple_message]: ALSA
  error: snd_pcm_open failed: Operation not supported.

  This occurred after the daily update on 2/2/24.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:cliff  2336 F pipewire
   /dev/snd/controlC0:  cliff  2341 F wireplumber
   /dev/snd/controlC1:  cliff  2341 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  2 08:53:34 2024
  InstallationDate: Installed on 2023-12-02 (62 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2052307/+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 2051540] Re: ufw ftbfs with Python 3.12 as default

[Jamie Strandboge]

https://launchpad.net/ubuntu/+source/ufw/0.36.2-3/+build/27739360 built
fine. Closing.

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

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

Title:
  ufw ftbfs with Python 3.12 as default

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  Fix Released
Status in ufw package in Debian:
  New

Bug description:
  ==
  ERROR: test_ufwcommand_parse 
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
  Test UFWCommand.parse()
  --
  Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in 
test_ufwcommand_parse
  self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
  ^
  AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did 
you mean: 'assertEqual'?

  ==
  ERROR: test_ufwcommand_rule_get_command 
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
  Test UFWCommand(Route)Rule.get_command()
  --
  Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in 
test_ufwcommand_rule_get_command
  self.assertEquals(len(errors), 0,
  ^
  AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did 
you mean: 'assertEqual'?

  --
  Ran 24 tests in 7.584s

  FAILED (errors=9)
  test_skeleton
  test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
  Test example dummy test ... ok

  --
  Ran 1 test in 0.000s

  OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2051540/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Timo Aaltonen]

Hello Nafees, or anyone else affected,

Accepted python2.7 into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.18-13ubuntu1.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: python2.7 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  In Progress
Status in python2.7 source package in Jammy:
  Fix Committed
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.

  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.

  The fix modifies the portion of code in Lib/distutils/sysconfig.py
  which gets the cflags from the environments, and includes the dropped
  OPT flag from get_config_vars().

  [ Test Plan ]

  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set

  Test 1) No-change rebuilds

  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.

  Test 2) Functional test

  1. Create test container
  $ lxc launch ubuntu:jammy jammy-2002043
  $ lxc shell ubuntu:jammy jammy-2002043

  2. Install required packages
  For Jammy
  # apt update -y && apt install -y python2 python-pip
  For Focal
  # apt update -y && apt install -y python2 python-setuptools

  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

[Simon Déziel]

This was verified on Jammy with -proposed
(1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1). Here's how:

$ lxc launch ubuntu-daily:22.04 c1
Creating c1
Starting c1

root@c1:~# apt-get update
...
root@c1:~# apt-get install -Vy liblxc-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
   libfuse2 (2.9.9-5ubuntu3)
   liblxc-common (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1)
   liblxc1 (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1)
   lxcfs (5.0.0-0ubuntu2)
   uidmap (1:4.8.1-2ubuntu2.1)
The following NEW packages will be installed:
   libfuse2 (2.9.9-5ubuntu3)
   liblxc-common (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1)
   liblxc-dev (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1)
   liblxc1 (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1)
   lxcfs (5.0.0-0ubuntu2)
   uidmap (1:4.8.1-2ubuntu2.1)
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 1462 kB of archives.
...

root@c1:~# dpkg -l | grep liblxc-dev
ii  liblxc-dev  1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 
amd64Linux Containers userspace tools (development)
root@c1:~# grep LXC_DEVEL /usr/include/lxc/version.h
#define LXC_DEVEL 1


# enable -proposed

root@c1:~# apt-get update
...
root@c1:~# apt-get install -Vy liblxc-dev
...
The following packages will be upgraded:
   liblxc-common (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 => 
1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1)
   liblxc-dev (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 => 
1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1)
   liblxc1 (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 => 
1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1)
3 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.
Need to get 1268 kB of archives.
...

root@c1:~# grep LXC_DEVEL /usr/include/lxc/version.h
#define LXC_DEVEL 0

** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

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

Title:
  [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Jammy:
  Fix Committed
Status in lxc source package in Mantic:
  Fix Committed
Status in lxc source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2052307] [NEW] ALSA error: snd_pcm_open failed: Operation not supported.

[Cliff Carson]

Public bug reported:

Getting the following error trying to play a radio stream in Audacious.

ERROR ../src/libaudgui/util.cc:328 [audgui_simple_message]: ALSA error:
snd_pcm_open failed: Operation not supported.

This occurred after the daily update on 2/2/24.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:cliff  2336 F pipewire
 /dev/snd/controlC0:  cliff  2341 F wireplumber
 /dev/snd/controlC1:  cliff  2341 F wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  2 08:53:34 2024
InstallationDate: Installed on 2023-12-02 (62 days ago)
InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2018
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3503
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

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

Title:
  ALSA error: snd_pcm_open failed: Operation not supported.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Getting the following error trying to play a radio stream in
  Audacious.

  ERROR ../src/libaudgui/util.cc:328 [audgui_simple_message]: ALSA
  error: snd_pcm_open failed: Operation not supported.

  This occurred after the daily update on 2/2/24.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:cliff  2336 F pipewire
   /dev/snd/controlC0:  cliff  2341 F wireplumber
   /dev/snd/controlC1:  cliff  2341 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  2 08:53:34 2024
  InstallationDate: Installed on 2023-12-02 (62 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2052307/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Scarlett Gately Moore]

I have tested the above packages and created a profile for kontact
locally and kontact no longer crashes hooray. I am still sorting out
what I need to do here for the kde packages ( returning after a long
time gone ) Is there a package I need to add new profiles or is someone
else adding the new profiles? SO for my newbness.

-- 
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 akregator package in Ubuntu:
  Confirmed
Status in angelfish package in Ubuntu:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Confirmed
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Confirmed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Confirmed
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kiwix package in Ubuntu:
  Confirmed
Status in konqueror package in Ubuntu:
  Confirmed
Status in kontact package in Ubuntu:
  Confirmed
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Confirmed
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in privacybrowser package in Ubuntu:
  Confirmed
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:
  Confirmed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Confirmed

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 denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: 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)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64

[Miriam España Acebal]

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

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

Title:
  autopkgtest unshare-qemuwrapper failing on amd64

Status in cpio package in Ubuntu:
  In Progress
Status in sbuild package in Ubuntu:
  New
Status in cpio source package in Noble:
  In Progress
Status in sbuild source package in Noble:
  New

Bug description:
  While looking Noble openssh transition, I saw this test failing and
  marking amd64 as regression.

  Log :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz

  Relevant part of the log:

  1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/
  1565s Setting up cpio (2.15+dfsg-1) ...
  1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist
  1565s dpkg: error processing package cpio (--configure):
  1565s  installed cpio package post-installation script subprocess returned 
error exit status 2

  
  It can be reproduced locally, too.

  The most recent test working is from 01/08/2024:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz

  The cpio version in the immediately log above is lower. The same
  (working) part is:

  2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/
  2188s Setting up cpio (2.14+dfsg-1) ...
  2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto 
mode

  cpio diff :
  https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+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 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64

[Miriam España Acebal]

** Changed in: cpio (Ubuntu Noble)
 Assignee: (unassigned) => Miriam España Acebal (mirespace)

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

Title:
  autopkgtest unshare-qemuwrapper failing on amd64

Status in cpio package in Ubuntu:
  New
Status in sbuild package in Ubuntu:
  New
Status in cpio source package in Noble:
  New
Status in sbuild source package in Noble:
  New

Bug description:
  While looking Noble openssh transition, I saw this test failing and
  marking amd64 as regression.

  Log :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz

  Relevant part of the log:

  1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/
  1565s Setting up cpio (2.15+dfsg-1) ...
  1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist
  1565s dpkg: error processing package cpio (--configure):
  1565s  installed cpio package post-installation script subprocess returned 
error exit status 2

  
  It can be reproduced locally, too.

  The most recent test working is from 01/08/2024:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz

  The cpio version in the immediately log above is lower. The same
  (working) part is:

  2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/
  2188s Setting up cpio (2.14+dfsg-1) ...
  2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto 
mode

  cpio diff :
  https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+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 2052297] [NEW] Please add opt.keybase.keybase profile

[Julian Andres Klode]

Public bug reported:

Like the other Chrome binaries, Keybase also needs a profile:

abi ,

/opt/keybase/Keybase flags=(unconfined) {
allow userns create,
}


Keybase is heavily used for security and boot engineering for cross-vendor 
communication and broken without it

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

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

Title:
  Please add opt.keybase.keybase profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  Like the other Chrome binaries, Keybase also needs a profile:

  abi ,

  /opt/keybase/Keybase flags=(unconfined) {
  allow userns create,
  }

  
  Keybase is heavily used for security and boot engineering for cross-vendor 
communication and broken without it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052297/+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 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64

[Miriam España Acebal]

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

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

Title:
  autopkgtest unshare-qemuwrapper failing on amd64

Status in cpio package in Ubuntu:
  New
Status in sbuild package in Ubuntu:
  New
Status in cpio source package in Noble:
  New
Status in sbuild source package in Noble:
  New

Bug description:
  While looking Noble openssh transition, I saw this test failing and
  marking amd64 as regression.

  Log :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz

  Relevant part of the log:

  1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/
  1565s Setting up cpio (2.15+dfsg-1) ...
  1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist
  1565s dpkg: error processing package cpio (--configure):
  1565s  installed cpio package post-installation script subprocess returned 
error exit status 2

  
  It can be reproduced locally, too.

  The most recent test working is from 01/08/2024:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz

  The cpio version in the immediately log above is lower. The same
  (working) part is:

  2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/
  2188s Setting up cpio (2.14+dfsg-1) ...
  2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto 
mode

  cpio diff :
  https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

[Timo Aaltonen]

Hello Aleksandr, or anyone else affected,

Accepted lxc into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-jammy

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

Title:
  [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Jammy:
  Fix Committed
Status in lxc source package in Mantic:
  Fix Committed
Status in lxc source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2052137] Re: bonded link goes down on reconfigure

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

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

Title:
  bonded link goes down on reconfigure

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-networkd brings down member interfaces of a bond when they get
  reconfigured

  Jan 31 15:43:46 unique-slug systemd-networkd[2430]: pn1: Bringing link
  down

  This has a result that a server has complete downtime for a few
  seconds, this has also been reported upstream
  https://github.com/systemd/systemd/issues/31165.

  A pull request has been opened to fix this
  https://github.com/systemd/systemd/pull/31172

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/2052137/+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 2052137] Re: bonded link goes down on reconfigure

[Marlin Cremers]

** Attachment added: "gistfile2.txt"
   
https://bugs.launchpad.net/systemd/+bug/2052137/+attachment/5744298/+files/gistfile2.txt

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

Title:
  bonded link goes down on reconfigure

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-networkd brings down member interfaces of a bond when they get
  reconfigured

  Jan 31 15:43:46 unique-slug systemd-networkd[2430]: pn1: Bringing link
  down

  This has a result that a server has complete downtime for a few
  seconds, this has also been reported upstream
  https://github.com/systemd/systemd/issues/31165.

  A pull request has been opened to fix this
  https://github.com/systemd/systemd/pull/31172

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/2052137/+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 2052137] Re: bonded link goes down on reconfigure

[Marlin Cremers]

** Attachment added: "gistfile1.txt"
   
https://bugs.launchpad.net/systemd/+bug/2052137/+attachment/5744297/+files/gistfile1.txt

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

Title:
  bonded link goes down on reconfigure

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-networkd brings down member interfaces of a bond when they get
  reconfigured

  Jan 31 15:43:46 unique-slug systemd-networkd[2430]: pn1: Bringing link
  down

  This has a result that a server has complete downtime for a few
  seconds, this has also been reported upstream
  https://github.com/systemd/systemd/issues/31165.

  A pull request has been opened to fix this
  https://github.com/systemd/systemd/pull/31172

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/2052137/+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 2052138] [NEW] After screen turns off and you turn it back on, weird corruption

[George Salukvadze]

Public bug reported:

When the laptop main screen turns off due to inactivity and then you
turn it back on, there is a weird corruption.

Restart helps.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  2 10:14:53 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[17aa:3a58]
 Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev c4) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:3a58]
InstallationDate: Installed on 2024-01-12 (21 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash 
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN60WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.60
dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug corruption mantic ubuntu

** Attachment added: "20240202_101543.mp4"
   
https://bugs.launchpad.net/bugs/2052138/+attachment/5744272/+files/20240202_101543.mp4

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

Title:
  After screen turns off and you turn it back on, weird corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  When the laptop main screen turns off due to inactivity and then you
  turn it back on, there is a weird corruption.

  Restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

Patches sent (to multiple places per get_maintainer.pl):

https://lkml.org/lkml/2024/2/2/373
https://lkml.org/lkml/2024/2/2/375

-- 
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 linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug 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/linux/+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 2052137] [NEW] bonded link goes down on reconfigure

[Marlin Cremers]

Public bug reported:

systemd-networkd brings down member interfaces of a bond when they get
reconfigured

Jan 31 15:43:46 unique-slug systemd-networkd[2430]: pn1: Bringing link
down

This has a result that a server has complete downtime for a few seconds,
this has also been reported upstream
https://github.com/systemd/systemd/issues/31165.

A pull request has been opened to fix this
https://github.com/systemd/systemd/pull/31172

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: github.com/systemd/systemd/issues #31165
   https://github.com/systemd/systemd/issues/31165

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/31165
   Importance: Unknown
   Status: Unknown

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

Title:
  bonded link goes down on reconfigure

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-networkd brings down member interfaces of a bond when they get
  reconfigured

  Jan 31 15:43:46 unique-slug systemd-networkd[2430]: pn1: Bringing link
  down

  This has a result that a server has complete downtime for a few
  seconds, this has also been reported upstream
  https://github.com/systemd/systemd/issues/31165.

  A pull request has been opened to fix this
  https://github.com/systemd/systemd/pull/31172

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/2052137/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

[Aleksandr Mikhalitsyn]

Because, this is a production build of package. LXC_DEVEL is about type of 
build not about version.
For any package builds we should have LXC_DEVEL=0. The only case when 
LXC_DEVEL=1 is when you are doing local development of the LXC and building it 
for your self, or you building a package to install it on the CI VMs for 
testing purposes. Because whan LXC_DEVEL does it it effectively disables all 
the VERSION_AT_LEAST checks and make all of them to pass. Which is absolutely 
incorrect for any production builds.

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

Title:
  [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Fix Committed
Status in lxc source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

[Timo Aaltonen]

The jammy upstream version is at 5.0.0~git2209-g5a7b9ce67, which has
devel written all over it? Why should it drop LXC_DEVEL?

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

Title:
  [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Fix Committed
Status in lxc source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

[Timo Aaltonen]

Hello Aleksandr, or anyone else affected,

Accepted lxc into mantic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1:5.0.1-0ubuntu8~23.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-mantic

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

Title:
  [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Fix Committed
Status in lxc source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

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