[Touch-packages] [Bug 1932542] Re: Add support for zstd

[Chris Halse Rogers]

Hello Dimitri, or anyone else affected,

Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.13 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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. 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: initramfs-tools (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  Add support for zstd

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * initramfs-tools in impish has changed default initrd compression to
  zstd. To allow compressing and uncompressing such initrds on Focal LTS
  release we should backport zstd support in the mkinitramfs &
  unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs
  tool to unpack and inspect impish initrds on a focal host.

   * Cherrypicking the feature from 0.138 release, which is also present
  in Hirsute and Impish.

  [Test Plan]

   * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img

   * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd-
  unpacked

   * For bionic also repeat the same with lz4.

  [Where problems could occur]

   * This adds support for zstd compressed initrd in both mkinitramfs
  and unmkinitramfs. However our GA kernels do not support zstd
  compressed initrds. And depends on zstd package is not added either.
  Meaning one still has to install zstd to gain the unpack support.
  Changing initramfs.conf to zstd may result in unbootable instance when
  used with GA kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932542/+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 1608804] Re: u1db-qt fails to build on yakkety due to licensecheck moved to different package

[Adolfo Jayme]

** Changed in: u1db-qt (Ubuntu)
   Status: New => Won't Fix

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

Title:
  u1db-qt fails to build on yakkety due to licensecheck moved to
  different package

Status in u1db-qt package in Ubuntu:
  Won't Fix

Bug description:
  licensecheck is now in its own package licensecheck instead of
  devscripts. Therefore u1db-qt fails to build on yakkety:
  https://launchpadlibrarian.net/276195878/buildlog_ubuntu-yakkety-amd64
  .u1db-
  
qt_0.1.5+15.10.20150826.1-0ubuntu2~~testrebuild1~~testrebuild1~1_BUILDING.txt.gz

  However I'm not sure how to resolve the issue in a tri-landing
  compatible way.

  It will only be issue once u1db-qt is wanted to be upgraded, currently
  the binaries are there and working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u1db-qt/+bug/1608804/+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 1925320] Re: Backport packages for 20.04.3 HWE stack

[Launchpad Bug Tracker]

This bug was fixed in the package llvm-toolchain-12 -
1:12.0.0-3ubuntu1~20.04.3

---
llvm-toolchain-12 (1:12.0.0-3ubuntu1~20.04.3) focal; urgency=medium

  * control, rules: Fix build on riscv64, force gcc version to 10.
(LP: #1925320)

 -- Timo Aaltonen   Wed, 23 Jun 2021 10:43:21 +0300

** Changed in: llvm-toolchain-12 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-12 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1923845] Re: Please compress packages with zstd by default

[Launchpad Bug Tracker]

This bug was fixed in the package reprepro - 5.3.0-1.3~ubuntu21.04

---
reprepro (5.3.0-1.3~ubuntu21.04) hirsute; urgency=medium

  * Backport Zstd compressed debs support to hirsute. LP: #1933363

reprepro (5.3.0-1.3) experimental; urgency=medium

  * Non-maintainer upload.
  * Add support for Zstd compressed debs. (LP: #1923845)

 -- Dimitri John Ledkov   Wed, 23 Jun 2021
17:01:44 +0100

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed

[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default

[Launchpad Bug Tracker]

This bug was fixed in the package reprepro - 5.3.0-1.3~ubuntu20.10

---
reprepro (5.3.0-1.3~ubuntu20.10) groovy; urgency=medium

  * Backport Zstd compressed debs support to hirsute. LP: #1933363

reprepro (5.3.0-1.3) experimental; urgency=medium

  * Non-maintainer upload.
  * Add support for Zstd compressed debs. (LP: #1923845)

reprepro (5.3.0-1.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Flush stdout and stderr before execv of an end hook (Closes: #982423)

 -- Dimitri John Ledkov   Wed, 23 Jun 2021
17:01:44 +0100

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

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packag

[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default

[Launchpad Bug Tracker]

This bug was fixed in the package reprepro - 5.3.0-1.3~ubuntu20.04

---
reprepro (5.3.0-1.3~ubuntu20.04) focal; urgency=medium

  * Backport Zstd compressed debs support to hirsute. LP: #1933363

reprepro (5.3.0-1.3) experimental; urgency=medium

  * Non-maintainer upload.
  * Add support for Zstd compressed debs. (LP: #1923845)

reprepro (5.3.0-1.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Flush stdout and stderr before execv of an end hook (Closes: #982423)

 -- Dimitri John Ledkov   Wed, 23 Jun 2021
17:01:44 +0100

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

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

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/arc

[Touch-packages] [Bug 1923845] Update Released

[Chris Halse Rogers]

The verification of the Stable Release Update for reprepro has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not af

[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

[Andy Chi]

Hi @mic159,
Can you also help to append sos report, BIOS version, `rfkill list` and `lspci 
-nnvv` in the new bug?
Thanks.

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in
  kernels 5.11 (approximately) onward. Devices are not refreshed in the
  list anymore.

  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

[Hui Wang]

@Thibaut,

Doesn't matter, Alex already. provided the log.

Please run below commands and test speaker. If those commands don't
work, I will contact realtek (I guess the spk amplifier is an i2s one,
need special initialization).


sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x10
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0f20
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1b
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0e4b
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x33
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8c00
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x35
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8d6a
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x36
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x5737
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x37
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xfe16
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x38
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x7981
//please test if speaker works.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x45
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xd089
//please test if speaker works.

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
  Symptom_Jack: Grey Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.release: 1.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Guinness_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF515-51T
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+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 1933842] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Failed during do-release-upgrade from 18.04 to 20.04.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 4.15.0-147.151-generic 4.15.18
  Uname: Linux 4.15.0-147-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jun 28 06:44:12 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-11-02 (2064 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-06-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1933842/+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 1934837] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[George J Kreger]

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

Public bug reported:

I did an upgrade on a Dell Latitude E6410 from 18.04 to 20.04. It failed
to install the package initramfs-tools.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.6
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jul  6 20:23:27 2021
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2015-12-24 (2022 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2021-07-07 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I did an upgrade on a Dell Latitude E6410 from 18.04 to 20.04. It
  failed to install the package initramfs-tools.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jul  6 20:23:27 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-12-24 (2022 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1934837/+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 1934837] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1933842, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1933842
   package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed 
initramfs-tools package post-installation script subprocess returned error exit 
status 1

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I did an upgrade on a Dell Latitude E6410 from 18.04 to 20.04. It
  failed to install the package initramfs-tools.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jul  6 20:23:27 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-12-24 (2022 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1934837/+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 1934757] Re: [Dell OptiPlex 9010] Pulseaudio does not recognize integrated audio device

[Daniel van Vugt]

> EDIT: oh, it works again. I'll keep track of this issue. Maybe I
should have started pulseaudio by systemd?

Does that mean there is a bug still?

** Summary changed:

- Pulseaudio does not recognize integrated audio device
+ [Dell OptiPlex 9010] Pulseaudio does not recognize integrated audio device

** Changed in: pulseaudio (Ubuntu)
   Status: New => Incomplete

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

Title:
  [Dell OptiPlex 9010] Pulseaudio does not recognize integrated audio
  device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-
  stereo" in "~/.config/pulse/default.pa". It caused pulseaudio to fail
  with this version. I removed the line and run pulseaudio.

  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)

  EDIT: oh, it works again. I'll keep track of this issue. Maybe I
  should have started pulseaudio by systemd?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934757/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

[Daniel van Vugt]

Thanks for letting us know. Please open a new bug about that by running:

  ubuntu-bug bluez

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in
  kernels 5.11 (approximately) onward. Devices are not refreshed in the
  list anymore.

  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1934005] Re: abstractions/X: Possible regression of X session functionality by removing 'w' from /tmp/.X11-unix/* line?

[Thomas Ward]

I did some testing with the adjusted X abstractions, and porting the
torbrowser-launcher apparmor rules back as part of testing.  With the X
abstractions added, and the adjusted X abstractions working, all looks
good there.

The other component of the SRU is a tests fix, that will only show in
the autopkgtests.

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

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

Title:
  abstractions/X: Possible regression of X session functionality by
  removing 'w' from /tmp/.X11-unix/* line?

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Hirsute:
  Fix Committed
Status in apparmor source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Any application that requires access to X11 sockets for the Display may want 
to include abstractions/X in the AppArmor rules, which usually will include 
rules that we would want for access to the Display socket for X.

  However, an upstream regression was made by changes to the
  abstractions/X to remove the 'w' and leave it read only.  This doesn't
  work - X11 needs readwrite on the sockets for it to properly interact
  with X11.

  This is a fundamental regression that has been fixed upstream.

  
  [Test Plan]

  Any application that needs X11 integration with apparmor rules should
  `#include `

  This is the problem with https://bugs.launchpad.net/ubuntu/+source
  /torbrowser-launcher/+bug/1933886 - while the fix for that would be to
  add `#include ` in the ruleset, it will not function
  with the existing abstractions.  This is our test case in Impish:

   - add `#include ` into 
`/etc/apparmor.d/torbrowser.Browser.firefox` and the apparmor rule.
   - `sudo systemctl restart apparmor.service`
   - Attempt to run torbrowser with torbrowser-launcher, which should now 
properly work with the revisions.  Without, torbrowser-launcher 'starts' Tor 
Browser but then it just segfaults and stops running.

  We don't have a full test case for Hirsute at this time.

  
  [Where problems could occur]

  Based on my understanding of X11 and the upstream AppArmor bugs on
  this (refer to comments), there is no breakage introduced by this, in
  fact the breakage was already introduced upstream, so this simply
  fixes and removes the breakage when an apparmor rule includes these X
  abstractions and need to write to the socket but can't.

  Therefore, I don't believe there are any 'problems' that can occur
  with this change.

  
  [Original Description]

  In Focal, abstractions/X has the following section in it:

    # the unix socket to use to connect to the display
    /tmp/.X11-unix/* rw,
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.X11-unix/X[0-9]*"),
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.ICE-unix/[0-9]*"),

  However, in Impish, this seems to have changed:

    # the unix socket to use to connect to the display
    /tmp/.X11-unix/* r,
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.X11-unix/X[0-9]*"),
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.ICE-unix/[0-9]*"),

  This in turn breaks torbrowser-launcher's Firefox from launching, even
  if we include the X abstractions, because the display sockets in
  /tmp/.X11-unix/* (X0 for Display :0 for example) are not read/write.

  This looks like a MAJOR regression by removing the permissions.  Or
  has Impish apparmor not been updated for any Ubuntu specific changes?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apparmor 3.0.0-0ubuntu8
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Tue Jun 29 14:39:00 2021
  InstallationDate: Installed on 2021-06-29 (0 days ago)
  InstallationMedia: Lubuntu 21.10 "Impish Indri" - Alpha amd64 (20210628)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.11.0-20-generic 
root=UUID=d042602b-0900-4b2e-acb1-f67436e9805f ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1934005/+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 1934826] [NEW] [LOW] software-properties should use Breeze theme on Kubuntu

[Omer I.S.]

Public bug reported:

software-properties should use Breeze (or any theme in use for Plasma desktop) 
theme on Kubuntu.
Currently, software-properties uses Fusion theme instead of Breeze.

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

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

Title:
  [LOW] software-properties should use Breeze theme on Kubuntu

Status in software-properties package in Ubuntu:
  New

Bug description:
  software-properties should use Breeze (or any theme in use for Plasma 
desktop) theme on Kubuntu.
  Currently, software-properties uses Fusion theme instead of Breeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934826/+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 1934825] [NEW] [FEATURE REQUEST] RTL interface for software-properties-qt

[Omer I.S.]

Public bug reported:

Please add RTL interface for software-properties-qt. This will improve
its usability for users from the middle east.

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

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

Title:
  [FEATURE REQUEST] RTL interface for software-properties-qt

Status in software-properties package in Ubuntu:
  New

Bug description:
  Please add RTL interface for software-properties-qt. This will improve
  its usability for users from the middle east.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934825/+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 1932331] Re: ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

[Brian Murray]

Hello Paolo, or anyone else affected,

Accepted apparmor into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/3.0.0-0ubuntu7.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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: apparmor (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Hirsute:
  Fix Committed

Bug description:
  It only affects arm64:

  ...
   06/15 13:09:11 ERROR| utils:0153| [stderr] running i18n

   06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed. Test
   'i18n (194) OPEN (octal) "/tmp/sdtest.411763-18905-et6mgO/file_Š_post"
   RW' was expected to 'pass'. Reason for failure 'FAIL: open 
/tmp/sdtest.411763-18905-et6mgO/file_Š_post failed - Permission denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed.
  Test 'i18n (195) OPEN (octal)
  "/tmp/sdtest.411763-18905-et6mgO/file_Ê_post" RW' was expected to
  'pass'. Reason for failure 'FAIL: open
  /tmp/sdtest.411763-18905-et6mgO/file_Ê_post failed - Permission
  denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed.
  Test 'i18n (196) OPEN (octal)
  "/tmp/sdtest.411763-18905-et6mgO/file_ÄŠ_post" RW' was expected to
  'pass'. Reason for failure 'FAIL: open
  /tmp/sdtest.411763-18905-et6mgO/file_ÄŠ_post failed - Permission
  denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed. Test 'i18n 
(197) OPEN (octal) "/tmp/sdtest.411763-18905-et6mgO/file_ÅŠ_post" RW' was 
expected to 'pass'. Reason for failure 'FAIL: open 
/tmp/sdtest.411763-18905-et6mgO/file_ÅŠ_post failed - Permission denied'
  ...

  
  Full log without LP manging the formatting: 
http://paste.ubuntu.com/p/3PHcCWb9Jw/plain/

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1932331/+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 1934005] Re: abstractions/X: Possible regression of X session functionality by removing 'w' from /tmp/.X11-unix/* line?

[Brian Murray]

Hello Thomas, or anyone else affected,

Accepted apparmor into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/3.0.0-0ubuntu7.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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: apparmor (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  abstractions/X: Possible regression of X session functionality by
  removing 'w' from /tmp/.X11-unix/* line?

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Hirsute:
  Fix Committed
Status in apparmor source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Any application that requires access to X11 sockets for the Display may want 
to include abstractions/X in the AppArmor rules, which usually will include 
rules that we would want for access to the Display socket for X.

  However, an upstream regression was made by changes to the
  abstractions/X to remove the 'w' and leave it read only.  This doesn't
  work - X11 needs readwrite on the sockets for it to properly interact
  with X11.

  This is a fundamental regression that has been fixed upstream.

  
  [Test Plan]

  Any application that needs X11 integration with apparmor rules should
  `#include `

  This is the problem with https://bugs.launchpad.net/ubuntu/+source
  /torbrowser-launcher/+bug/1933886 - while the fix for that would be to
  add `#include ` in the ruleset, it will not function
  with the existing abstractions.  This is our test case in Impish:

   - add `#include ` into 
`/etc/apparmor.d/torbrowser.Browser.firefox` and the apparmor rule.
   - `sudo systemctl restart apparmor.service`
   - Attempt to run torbrowser with torbrowser-launcher, which should now 
properly work with the revisions.  Without, torbrowser-launcher 'starts' Tor 
Browser but then it just segfaults and stops running.

  We don't have a full test case for Hirsute at this time.

  
  [Where problems could occur]

  Based on my understanding of X11 and the upstream AppArmor bugs on
  this (refer to comments), there is no breakage introduced by this, in
  fact the breakage was already introduced upstream, so this simply
  fixes and removes the breakage when an apparmor rule includes these X
  abstractions and need to write to the socket but can't.

  Therefore, I don't believe there are any 'problems' that can occur
  with this change.

  
  [Original Description]

  In Focal, abstractions/X has the following section in it:

    # the unix socket to use to connect to the display
    /tmp/.X11-unix/* rw,
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.X11-unix/X[0-9]*"),
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.ICE-unix/[0-9]*"),

  However, in Impish, this seems to have changed:

    # the unix socket to use to connect to the display
    /tmp/.X11-unix/* r,
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.X11-unix/X[0-9]*"),
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.ICE-unix/[0-9]*"),

  This in turn breaks torbrowser-launcher's Firefox from launching, even
  if we include the X abstractions, because the display sockets in
  /tmp/.X11-unix/* (X0 for Display :0 for example) are not read/write.

  This looks like a MAJOR regression by removing the permissions.  Or
  has Impish apparmor not been updated for any Ubuntu specific changes?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apparmor 3.0.0-0ubuntu8
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  Casp

[Touch-packages] [Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)

[Guilherme G. Piccoli]

** Summary changed:

- lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic
+ lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels 
(device_add_remove_test)

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

Title:
  lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
  (device_add_remove_test)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Bionic:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz

  The failing test seems to be:

  FAIL: lxc-tests: lxc-test-device-add-remove (0s)
  ---
  Adding /dev/network_latency to the container (device_add_remove_test) 
failed...
  ---

  This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note
  that this testcase is successful on Focal with the same kernel
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1886790/+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 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4

[Guilherme G. Piccoli]

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

** This bug has been marked a duplicate of bug 1886790
   lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic

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

Title:
  lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  Issue found on with 5.4.0-1016.16~18.04.1-oracle on both
  VM.Standard2.1 and VM.Standard2.16

  Test failed with:
   FAIL: lxc-tests: lxc-test-device-add-remove (1s)
   ---
   Adding /dev/network_latency to the container (device_add_remove_test) 
failed...

  This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on
  VM.Standard2.16 but passed on VM.Standard2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+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 1923880] Update Released

[Brian Murray]

The verification of the Stable Release Update for libdrm has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  libdrm 2.4.105: Add support for Intel Jasper Lake, Alder Lake

Status in libdrm package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Committed
Status in libdrm source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  There is a new minor release available, which adds support for i915
  Jasper Lake (JSL) and Alder Lake S (ADL-S), among other things.

  With this added, JSL can boot hirsute with the native driver.

  [Test case]

  Boot on JSL/ADL hardware, check that the native drm/dri driver is used
  (mesa support is already included).

  [What could go wrong]

  The worst case would be that the native driver would not be used
  anymore with this version, but there's no chance for that.

  Two regressing commits were reverted for impish, and we'll include
  those too.

  --

  git shortlog since 2.4.104:

  6b4e956d299c6ff Bump version to 2.4.105
  1d13cc1032bf66f amdgpu: add function of INFO ioctl for querying video caps
  50c98335c7b4013 amdgpu: sync up amdgpu_drm.h with latest from kernel
  b362850689d1b00 xf86drmMode: set FB_MODIFIERS flag when modifiers are supplied
  a5a400c9581c3b9 tests/amdgpu: fix bo eviction test issue
  af871ec1a6f017b drm/tests/amdgpu: fix Metadata test failed issue
  6d821612d9a4bc4 xf86drmMode: introduce drmModeGetPropertyType
  f5abbc303361980 test/amdgpu: remove static varible in Syncobj test
  cd3681976c3bbef intel: Keep libdrm working without pread/pwrite ioctls
  52f05d3d896480e meson: use library() instead of shared_library().
  7d6a1759900ffde xf86drm: fix null pointer deref in drmGetBufInfo
  2e67fef5f6c5870 intel: Add support for JSL
  a9bb32cfe1ee87f xf86drm: cap number of reported devices by drmGetDevice(2)
  06844b6eaefb03c Revert "xf86drm: cap number of reported devices by 
drmGetDevice(2)"
  632f59fcbfc790a xf86drm: warn about GEM handle reference counting
  523b3658aa8efa7 xf86drmMode: add drmIsKMS
  1225171bd55f65d amdgpu_drm: sync up with the latest amdgpu_drm.h based on 
drm-next (https://cgit.freedesktop.org/drm/drm)
  3b6cfb20fb3b7dd intel: add INTEL_ADLS_IDS to the pciids list
  9086ff9dafa87f9 intel: sync i915_pciids.h with kernel
  869ef0e4b22b8ba amdgpu: update marketing names
  a43cac24db2876b Avoid some compiler errors for 
tests/util/pattern.c62b9a3eee9bdaaf
  8cb12a2528d795c xf86drm: cap number of reported devices by drmGetDevice(2)
  19f0a9cb878da5b tests/amdgpu/vcn: clean abundant codes
  2315bcddd643b4b tests/amdgpu: add vcn test support for dimgrey_cavefish
  10377d661a31c7a tests/amdgpu: add vcn test support for navy_flounder
  5f85a6d98baba1d tests/util: Add mxsfb-drm driver
  62b9a3eee9bdaaf meson: Also search for rst2man.py
  10dd3eb6d5ab6c1 Use dep_rt in amdgpu/meson.build

  diffstat:
   amdgpu/amdgpu-symbols.txt|1
   amdgpu/amdgpu.h  |   17 +++
   amdgpu/amdgpu_gpu_info.c |   15 ++
   amdgpu/meson.build   |4 -
   core-symbols.txt |1
   data/amdgpu.ids  |6 ++
   etnaviv/meson.build  |2
   exynos/meson.build   |2
   freedreno/meson.build|2
   include/drm/amdgpu_drm.h |   51 +++---
   intel/i915_pciids.h  |  177 
+++--
   intel/intel_bufmgr_gem.c |   96 -
   intel/intel_chipset.c|2
   intel/meson.build|2
   libkms/meson.build   |2
   meson.build  |6 +-
   nouveau/meson.build  |2
   omap/meson.build |2
   radeon/meson.build   |2
   tegra/meson.build|2
   tests/amdgpu/amdgpu_test.c   |6 --
   tests/amdgpu/basic_tests.c   |   13 +++--
   tests/amdgpu/bo_tests.c  |4 -
   tests/amdgpu/syncobj_tests.c |2
   tests/amdgpu/vcn_tests.c |6 +-
   tests/util/kms.c |1
   tests/util/pattern.c |5 --
   xf86drm.c|   11 
   xf86drm.h|   18 +++
   xf86drmMode.c|   14 +-
   xf86drmMode.h|   12 +
   31 files changed, 365 insertions(+), 121 deletions(-)

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

[Touch-packages] [Bug 1923880] Re: libdrm 2.4.105: Add support for Intel Jasper Lake, Alder Lake

[Launchpad Bug Tracker]

This bug was fixed in the package libdrm - 2.4.105-3~21.04.1

---
libdrm (2.4.105-3~21.04.1) hirsute; urgency=medium

  * Backport to hirsute. (LP: #1923880)

 -- Timo Aaltonen   Wed, 19 May 2021 11:15:08 +0300

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

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

Title:
  libdrm 2.4.105: Add support for Intel Jasper Lake, Alder Lake

Status in libdrm package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Committed
Status in libdrm source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  There is a new minor release available, which adds support for i915
  Jasper Lake (JSL) and Alder Lake S (ADL-S), among other things.

  With this added, JSL can boot hirsute with the native driver.

  [Test case]

  Boot on JSL/ADL hardware, check that the native drm/dri driver is used
  (mesa support is already included).

  [What could go wrong]

  The worst case would be that the native driver would not be used
  anymore with this version, but there's no chance for that.

  Two regressing commits were reverted for impish, and we'll include
  those too.

  --

  git shortlog since 2.4.104:

  6b4e956d299c6ff Bump version to 2.4.105
  1d13cc1032bf66f amdgpu: add function of INFO ioctl for querying video caps
  50c98335c7b4013 amdgpu: sync up amdgpu_drm.h with latest from kernel
  b362850689d1b00 xf86drmMode: set FB_MODIFIERS flag when modifiers are supplied
  a5a400c9581c3b9 tests/amdgpu: fix bo eviction test issue
  af871ec1a6f017b drm/tests/amdgpu: fix Metadata test failed issue
  6d821612d9a4bc4 xf86drmMode: introduce drmModeGetPropertyType
  f5abbc303361980 test/amdgpu: remove static varible in Syncobj test
  cd3681976c3bbef intel: Keep libdrm working without pread/pwrite ioctls
  52f05d3d896480e meson: use library() instead of shared_library().
  7d6a1759900ffde xf86drm: fix null pointer deref in drmGetBufInfo
  2e67fef5f6c5870 intel: Add support for JSL
  a9bb32cfe1ee87f xf86drm: cap number of reported devices by drmGetDevice(2)
  06844b6eaefb03c Revert "xf86drm: cap number of reported devices by 
drmGetDevice(2)"
  632f59fcbfc790a xf86drm: warn about GEM handle reference counting
  523b3658aa8efa7 xf86drmMode: add drmIsKMS
  1225171bd55f65d amdgpu_drm: sync up with the latest amdgpu_drm.h based on 
drm-next (https://cgit.freedesktop.org/drm/drm)
  3b6cfb20fb3b7dd intel: add INTEL_ADLS_IDS to the pciids list
  9086ff9dafa87f9 intel: sync i915_pciids.h with kernel
  869ef0e4b22b8ba amdgpu: update marketing names
  a43cac24db2876b Avoid some compiler errors for 
tests/util/pattern.c62b9a3eee9bdaaf
  8cb12a2528d795c xf86drm: cap number of reported devices by drmGetDevice(2)
  19f0a9cb878da5b tests/amdgpu/vcn: clean abundant codes
  2315bcddd643b4b tests/amdgpu: add vcn test support for dimgrey_cavefish
  10377d661a31c7a tests/amdgpu: add vcn test support for navy_flounder
  5f85a6d98baba1d tests/util: Add mxsfb-drm driver
  62b9a3eee9bdaaf meson: Also search for rst2man.py
  10dd3eb6d5ab6c1 Use dep_rt in amdgpu/meson.build

  diffstat:
   amdgpu/amdgpu-symbols.txt|1
   amdgpu/amdgpu.h  |   17 +++
   amdgpu/amdgpu_gpu_info.c |   15 ++
   amdgpu/meson.build   |4 -
   core-symbols.txt |1
   data/amdgpu.ids  |6 ++
   etnaviv/meson.build  |2
   exynos/meson.build   |2
   freedreno/meson.build|2
   include/drm/amdgpu_drm.h |   51 +++---
   intel/i915_pciids.h  |  177 
+++--
   intel/intel_bufmgr_gem.c |   96 -
   intel/intel_chipset.c|2
   intel/meson.build|2
   libkms/meson.build   |2
   meson.build  |6 +-
   nouveau/meson.build  |2
   omap/meson.build |2
   radeon/meson.build   |2
   tegra/meson.build|2
   tests/amdgpu/amdgpu_test.c   |6 --
   tests/amdgpu/basic_tests.c   |   13 +++--
   tests/amdgpu/bo_tests.c  |4 -
   tests/amdgpu/syncobj_tests.c |2
   tests/amdgpu/vcn_tests.c |6 +-
   tests/util/kms.c |1
   tests/util/pattern.c |5 --
   xf86drm.c|   11 
   xf86drm.h|   18 +++
   xf86drmMode.c|   14 +-
   xf86drmMode.h|   12 +
   31 files changed, 365 insertions(+), 121 deletions(-)

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

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

[Touch-packages] [Bug 1925798] Update Released

[Brian Murray]

The verification of the Stable Release Update for gupnp has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  SRU the current 1.2.4 stable update

Status in gupnp package in Ubuntu:
  Fix Released
Status in gupnp source package in Focal:
  Fix Released

Bug description:
  * Impact

  That's the current GNOME stable update, including some bugfixes
  https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS

  * Test case

  The library is used by rygel for pnp media sharing. Enable the option
  from the settings and try browsing and playing for another computer
  using for example rhythmbox.

  * Regression potential

  The main fix is around IPv6 local resolution, check that if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1925798/+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 1925798] Re: SRU the current 1.2.4 stable update

[Launchpad Bug Tracker]

This bug was fixed in the package gupnp - 1.2.4-0ubuntu1

---
gupnp (1.2.4-0ubuntu1) focal; urgency=medium

  * New stable update (lp: #1925798)

 -- Sebastien Bacher   Fri, 23 Apr 2021 15:23:07
+0200

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

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

Title:
  SRU the current 1.2.4 stable update

Status in gupnp package in Ubuntu:
  Fix Released
Status in gupnp source package in Focal:
  Fix Released

Bug description:
  * Impact

  That's the current GNOME stable update, including some bugfixes
  https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS

  * Test case

  The library is used by rygel for pnp media sharing. Enable the option
  from the settings and try browsing and playing for another computer
  using for example rhythmbox.

  * Regression potential

  The main fix is around IPv6 local resolution, check that if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1925798/+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 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration

[Bill Wear]

** Changed in: maas
   Status: New => Triaged

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

Title:
  Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition -
  no manual nor automatic qeth device configuration

Status in MAAS:
  Triaged
Status in Ubuntu on IBM z Systems:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in s390-tools package in Ubuntu:
  New

Bug description:
  I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14
  DPM Partition.  The initrd fails to bring up network and thus fails to
  boot in MAAS. I haven't tried older versions of Ubuntu but suspect
  they also have the same bug.

  mount: mounting /dev on /root/dev failed: No such file or directory
  done.
  mount: mounting /run on /root/run failed: No such file or directory
  run-init: current directory on the same filesystem as the root: error 0
  Target filesystem doesn't have requested /sbin/init.
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  chvt: can't open console
  No init found. Try passing init= bootarg.
  Couldn't get a file descriptor referring to the console
  /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such 
device o
  r address
  /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or 
ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device 
or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or 
ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device 
or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or 
ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device 
or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or 
ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device 
or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or 
ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device 
or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or 
ad
  dress
   
   
  BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash)
  Enter 'help' for a list of built-in commands.
   
  (initramfs) [6n
  [   78.114530] random: crng init done
  [   78.114538] random: 7 urandom warning(s) missed due to ratelimiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1918970/+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 1791958] Re: iptables-restore is missing -w option

[Eric Desrochers]

New testpackage:  iptables - 1.6.1-2ubuntu2+testpkg20210706b8

Note: If that works as expected for Andreas. The only things that needed
would be to update the manpage, which I didn't do on this current test
pkg.

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

Title:
  iptables-restore is missing -w option

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  For CRIU we need to have iptables version 1.6.2 which includes the
  '-w' option in iptables-restore.

  This is a request to update iptables to 1.6.2 in 18.10 and if possible
  backport the necessary changes to 18.04.

  The CRIU project gets right now many bug reports (mostly in the
  combination LXD + CRIU) due to the missing '-w' option in iptables-
  restore. Especially as 18.04 will be around for some time it would be
  good to have iptables-restore available with '-w'.

  This is one example bug report: https://github.com/checkpoint-
  restore/criu/issues/551

  But not only CRIU would benefit from this change. It seems also
  problematic with Kubernetes:
  https://github.com/kubernetes/kubernetes/pull/60978

  So if possible, please update iptables to 1.6.2 (or backport changes)
  to support -w in iptables-restore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+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 1791958] Re: iptables-restore is missing -w option

[Eric Desrochers]

Both 'iptables' and 'ip*tables-restores' sleep and wait until the lock
is released if no 'wait' option. If 'wait' option is set, it wait for
the amount of time instructed and stop waiting.

I think the printed message make more sense now :


# time cat /etc/rules.v4 | iptables-restore -c
Another app is currently holding the xtables lock; still -9s 0us time ahead to 
have a chance to grab the lock...


# time cat /etc/rules.v4 | iptables-restore -c -w 2
Another app is currently holding the xtables lock. Stopped waiting after 2s.


# time cat /etc/rules.v4 | ip6tables-restore -c
Another app is currently holding the xtables lock; still -9s 0us time ahead to 
have a chance to grab the lock...


# time cat /etc/rules.v4 | ip6tables-restore -c -w 2
Another app is currently holding the xtables lock. Stopped waiting after 2s.

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

Title:
  iptables-restore is missing -w option

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  For CRIU we need to have iptables version 1.6.2 which includes the
  '-w' option in iptables-restore.

  This is a request to update iptables to 1.6.2 in 18.10 and if possible
  backport the necessary changes to 18.04.

  The CRIU project gets right now many bug reports (mostly in the
  combination LXD + CRIU) due to the missing '-w' option in iptables-
  restore. Especially as 18.04 will be around for some time it would be
  good to have iptables-restore available with '-w'.

  This is one example bug report: https://github.com/checkpoint-
  restore/criu/issues/551

  But not only CRIU would benefit from this change. It seems also
  problematic with Kubernetes:
  https://github.com/kubernetes/kubernetes/pull/60978

  So if possible, please update iptables to 1.6.2 (or backport changes)
  to support -w in iptables-restore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+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 1934147] Re: systemd leaks abandoned session scopes

[Dan Streetman]

** Also affects: systemd (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Impish)
   Importance: Undecided
 Assignee: Dan Streetman (ddstreet)
   Status: Confirmed

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

** Also affects: systemd (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Hirsute)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Groovy)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Impish)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  systemd leaks abandoned session scopes

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Groovy:
  New
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Confirmed

Bug description:
  On a system that is monitored via telegraf I found many abandoned
  systemd session which I believe are created by a potential race where
  systemd is reloading unit files and at the same time a user is
  connecting to the system via ssh or is executing the su command.

  The simple reproducer

  $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
  daemon-reload & ssh localhost sleep 1 & done

  Wait > 1 second

  $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL

  To clean out STOPPED jobs and

  $ systemctl status --all 2> /dev/null | grep --before-context 3
  abandoned

  will produce something similar to

     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned
  --
  ● session-273.scope - Session 273 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-274.scope - Session 274 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-30.scope - Session 30 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
  --
  ● session-302.scope - Session 302 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
  --
     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned

  The system in question is running Bionic, systemd-237-3ubuntu10.48

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

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

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

[audrey reed]

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

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

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

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

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

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

  nameserver 192.168.0.1
  nameserver 8.8.8.8

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

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

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

  server=192.168.0.1
  server=8.8.8.8

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

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

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

[Touch-packages] [Bug 1466103] Re: dnsmasq runs unconfined due to starting before apparmor on boot

[audrey reed]

** Changed in: dnsmasq (Ubuntu)
 Assignee: (unassigned) => audrey reed (mrsperkins74)

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

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

Title:
  dnsmasq runs unconfined due to starting before apparmor on boot

Status in dnsmasq package in Ubuntu:
  Fix Released

Bug description:
  Description and behavior are identical to Bug #573315.  However, the
  solution to that bug was to make a change to
  /etc/apparmor.d/usr.sbin.libvirtd.  There is no longer an apparmor
  profile /etc/apparmor.d/usr.sbin.libvirtd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466103/+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 1934559] Re: Typo in capital of Ukraine

[Steve Langasek]

The names of the timezones as presented in the installer aren't managed
by ubiquity, they're inherited from the tzdata upstream.  Reassigning to
the correct package for this bug; however, this is not something Ubuntu
is likely to deviate from the upstream on, so discussion regarding the
preferred English name for the city should ideally take place upstream
with the tzdata maintainers.

** Package changed: ubiquity (Ubuntu) => tzdata (Ubuntu)

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

Title:
  Typo in capital of Ukraine

Status in tzdata package in Ubuntu:
  New

Bug description:
  During installation on a map and in timezone settings there's "Kiev" city, 
but it's not correct.
  Should be Kyiv - https://en.wikipedia.org/wiki/Kyiv.
  Ubuntu 21.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1934559/+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 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received

[Dan Streetman]

** Description changed:

  [impact]
  
  networking changes, like RA events, can cause systemd-resolved to re-
  write the resolv.conf file, even if the contents didn't change,
  resulting in unnecessary increased amount of inotify events
  
  [test case]
  
  see original description for ipv6ra-related reproducer, or simple
  reproducer here:
  
+ configure networkd with some config for (e.g.) eth0, but not a config
+ that would result in /etc/resolv.conf changing when the interface goes
+ up/down - for example, use static config with no DNS search domains.
+ Then bring eth0 up/down while observing the md5sum (file content) does
+ not change but the mtime does change.
+ 
  root@lp1891215-h:~# ip l set down dev eth0
- root@lp1891215-h:~# md5sum /etc/resolv.conf 
+ root@lp1891215-h:~# md5sum /etc/resolv.conf
  db23e80078515192c312e5f321ff0340  /etc/resolv.conf
  root@lp1891215-h:~# stat -t -L /etc/resolv.conf
  /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238218 1625238216 
1625238216 0 4096
  root@lp1891215-h:~# ip l set up dev eth0
- root@lp1891215-h:~# md5sum /etc/resolv.conf 
+ root@lp1891215-h:~# md5sum /etc/resolv.conf
  db23e80078515192c312e5f321ff0340  /etc/resolv.conf
  root@lp1891215-h:~# stat -t -L /etc/resolv.conf
  /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238227 1625238226 
1625238226 0 4096
  
  [regression potential]
  
  regressions would result in incorrect or missing data in the resolv.conf
  file, possibly resulting in dns failures or errors
  
  [scope]
  
  this is needed for h and eralier
  
  this is (potentially) fixed upstream by
  f3e1f00d03445911ee73729219cea88c8a70c612 which in first included in
  v248, so this is needed in hirsute and earlier
  
  [original description]
  
  # Issue description:
  
  On 2 Linode VMs that are used as lxd hosts, we noticed that
  /run/systemd/resolve/*resolv.conf were re-created quite frequently (~
  once per second). We noticed because of the log noise from lxd's dnsmasq
  instance using inotify to watch the target of /etc/resolv.conf (which
  points to the stub-resolv.conf in our case). This was (wrongly) reported
  as a lxd bug (https://github.com/lxc/lxd/issues/7765) until it became
  apparent it was more likely to be a problem with systemd(-resolved)?.
  
  The log noise is the observable problem that would be nice to see
  addressed:
  
    root@lxd02:~# uptime
     17:55:48 up  9:52,  1 user,  load average: 0.18, 0.11, 0.05
    root@lxd02:~# journalctl -b0 | grep -cF dnsmasq
    158609
  
  Upon further investigation, it seems that systemd-resolved re-creates
  the resolv.conf and stub-resolv.conf files whenever an IPv6 RA is
  received.
  
  1) One can observe that by setting systemd-resolved's service in debug
  mode:
  
  $ sudo systemctl edit systemd-resolved
  
  and in the editor that is opened, add and save this content:
  
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  
  then restart systemd-resolved and watch the logs scroll by with:
  
  $ journalctl -fu systemd-resolved
  
  3) In another terminal, watch the files be recreated with:
  
  watch -d -n 0.1 stat /run/systemd/resolve/stub-resolv.conf
  
  3) In yet another terminal, run a packet capture and watch "ICMP6,
  router advertisement" messages come by:
  
  sudo tcpdump -ni eth0 icmp6
  
  You will see that every time a RA packet comes in, resolved's journal
  will log this:
  
    Aug 11 17:33:55 lxd02 systemd-resolved[15368]: Sent message
  type=signal sender=n/a destination=n/a path=/org/freedesktop/resolve1
  interface=org.freedesktop.DBus.Properties member=PropertiesChanged
  cookie=244 reply_cookie=0 signature=sa{sv}as error-name=n/a error-
  message=n/a
  
  And the stat monitoring terminal will blink to highlight the new inode
  and timestamps of the freshly replaced stub-resolv.conf file.
  
  # Additional information:
  
  root@lxd02:~# lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  
  root@lxd02:~# apt-cache policy systemd
  systemd:
    Installed: 245.4-4ubuntu3.2
    Candidate: 245.4-4ubuntu3.2
    Version table:
   *** 245.4-4ubuntu3.2 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  root@lxd02:~# uname -a
  Linux lxd01 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for
  every IPv6 RA received

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status 

[Touch-packages] [Bug 1934559] [NEW] Typo in capital of Ukraine

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

During installation on a map and in timezone settings there's "Kiev" city, but 
it's not correct.
Should be Kyiv - https://en.wikipedia.org/wiki/Kyiv.
Ubuntu 21.04.

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


** Tags: hirsute
-- 
Typo in capital of Ukraine 
https://bugs.launchpad.net/bugs/1934559
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to tzdata in Ubuntu.

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

[Touch-packages] [Bug 1791958] Re: iptables-restore is missing -w option

[Eric Desrochers]

I'll work to re-arrange the fprintf if 'wait' option is used or not and
see the outcome of it.

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

Title:
  iptables-restore is missing -w option

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  For CRIU we need to have iptables version 1.6.2 which includes the
  '-w' option in iptables-restore.

  This is a request to update iptables to 1.6.2 in 18.10 and if possible
  backport the necessary changes to 18.04.

  The CRIU project gets right now many bug reports (mostly in the
  combination LXD + CRIU) due to the missing '-w' option in iptables-
  restore. Especially as 18.04 will be around for some time it would be
  good to have iptables-restore available with '-w'.

  This is one example bug report: https://github.com/checkpoint-
  restore/criu/issues/551

  But not only CRIU would benefit from this change. It seems also
  problematic with Kubernetes:
  https://github.com/kubernetes/kubernetes/pull/60978

  So if possible, please update iptables to 1.6.2 (or backport changes)
  to support -w in iptables-restore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+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 1791958] Re: iptables-restore is missing -w option

[Eric Desrochers]

I have a new test pkg:

This pkg keeps the same behavior for 'iptables'


# Hold the lock:
flock /run/xtables.lock sleep 36000

# It holds and wait until flock() finishes or get killed, and then get executed.
 iptables -L

# With 'wait' option, it waits until the wait time is ended:
time iptables -L -w 3
Another app is currently holding the xtables lock. Stopped waiting after 3s.

real0m3.006s
user0m0.002s
sys 0m0.001s



---
# Hold the lock:
flock /run/xtables.lock sleep 36000

# cat /etc/rules.v4 | iptables-restore -c -w 5
Another app is currently holding the xtables lock. Perhaps you want to use the 
-w option?

real0m5.009s
user0m0.006s
sys 0m0.001s

The 'wait' option instruction is respected.
The message may be confusing as it is suggesting to use '-w' even if it was 
used.

This is the progress I have made so far.

- Eric

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

Title:
  iptables-restore is missing -w option

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  For CRIU we need to have iptables version 1.6.2 which includes the
  '-w' option in iptables-restore.

  This is a request to update iptables to 1.6.2 in 18.10 and if possible
  backport the necessary changes to 18.04.

  The CRIU project gets right now many bug reports (mostly in the
  combination LXD + CRIU) due to the missing '-w' option in iptables-
  restore. Especially as 18.04 will be around for some time it would be
  good to have iptables-restore available with '-w'.

  This is one example bug report: https://github.com/checkpoint-
  restore/criu/issues/551

  But not only CRIU would benefit from this change. It seems also
  problematic with Kubernetes:
  https://github.com/kubernetes/kubernetes/pull/60978

  So if possible, please update iptables to 1.6.2 (or backport changes)
  to support -w in iptables-restore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+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 1791958] Re: iptables-restore is missing -w option

[Eric Desrochers]

Version in comment #12 is "iptables - 1.6.1-2ubuntu2+testpkg20210706b4"

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

Title:
  iptables-restore is missing -w option

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  For CRIU we need to have iptables version 1.6.2 which includes the
  '-w' option in iptables-restore.

  This is a request to update iptables to 1.6.2 in 18.10 and if possible
  backport the necessary changes to 18.04.

  The CRIU project gets right now many bug reports (mostly in the
  combination LXD + CRIU) due to the missing '-w' option in iptables-
  restore. Especially as 18.04 will be around for some time it would be
  good to have iptables-restore available with '-w'.

  This is one example bug report: https://github.com/checkpoint-
  restore/criu/issues/551

  But not only CRIU would benefit from this change. It seems also
  problematic with Kubernetes:
  https://github.com/kubernetes/kubernetes/pull/60978

  So if possible, please update iptables to 1.6.2 (or backport changes)
  to support -w in iptables-restore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+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 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

[Mateusz Stachowski]

I've checked the latest focal live image and it has the exact same
glitches as my install.

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

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New

Bug description:
  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+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 1923845] Re: Please compress packages with zstd by default

[Launchpad Bug Tracker]

This bug was fixed in the package dpkg - 1.20.9ubuntu2

---
dpkg (1.20.9ubuntu2) impish; urgency=medium

  * build: Switch default dpkg-deb compression from xz to zstd. (LP: #1923845)
Keep compressing dpkg.deb with xz to help bootstrapping on non-Ubuntu
systems.

 -- Balint Reczey   Mon, 14 Jun 2021 16:04:10
+0200

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

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Committed
Status in reprepro source package in Groovy:
  Fix Committed
Status in reprepro source package in Hirsute:
  Fix Committed
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed

[Touch-packages] [Bug 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51

[Krzysztof Kozlowski]

Found on groovy/azure groovy/azure 5.8.0-1038.40


** Tags added: sru-20210621

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

Title:
  lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Groovy:
  Confirmed

Bug description:
  We seem to get failed dep8 testing on lxc in Groovy for a while. What
  we are interested in is knowing whether this is known problems in the
  testing or something that waits on kernel fixes (who would be driving
  those if this is the case).

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20210224_161232_5c8ac@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/lxc/20210224_202135_e7aed@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/l/lxc/20210224_172418_73aab@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/lxc/20210224_164056_06e00@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917601/+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 1934221] Re: systemd-resolve segfault

[Brian Murray]

** Tags added: rls-ff-incoming

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

Title:
  systemd-resolve segfault

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-resolve keep crashing and it is very annoying as sometimes it
  severely interrupt normal dns resolving.

  Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
  Typical error in dmesg: 
  systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 
7ffe2fd0b758 error 15

  apport hints me that problem is related to mdns

  #3  0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd
  /libsystemd-shared-245.so

  It might be (or not) related that some hosts with mdns in my network
  have ipv6 enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
  Uname: Linux 5.4.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  1 08:22:51 2021
  InstallationDate: Installed on 2018-12-05 (938 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X399-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

[Mic159]

This has caused bluetooth to become completely unavailable on my Dell XPS 13 
9300.
gnome-control-center says "No Bluetooth Found", "Plug in a gongle to use 
Bluetooth."

Downgrading the package back to 5.56-0ubuntu4.1 resolves the issue.


I am using ubuntu 21.04.

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in
  kernels 5.11 (approximately) onward. Devices are not refreshed in the
  list anymore.

  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893&r=1&w=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

[Timo Aaltonen]

hmm so it was impish which was fine, test hirsute too :)

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

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New

Bug description:
  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+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 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

[Timo Aaltonen]

please give the latest focal live image a go:

http://cdimages.ubuntu.com/focal/daily-live/current/


since impish live image worked fine according to bug 1925320, I'm hoping this 
one is fine too

** Also affects: mesa (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New

Bug description:
  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

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

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

Re: [Touch-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

[Thibaut Soubrié]

Hello,

Many thanks for the tool & instruction. However, the RtHDDump.exe generates
an empty file on my end, even if I run the application in admin mode.

Best Regards,
Thibaut

Le mar. 6 juil. 2021 à 02:15, Hui Wang <1918...@bugs.launchpad.net> a
écrit :

> this is the dumptool in the windows.
>
> ** Attachment added: "RtHDDump_V236.zip"
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+attachment/5509207/+files/RtHDDump_V236.zip
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1918458
>
> Title:
>   [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
>   problem, no sound from speakers, headphones ok
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Expect : sound from speaker
>   Instead, obtain : no sound.
>
>
>   Tried various configuration of /etc/modprobe.d/alsa-conf with :
>
>   options snd-hda-intel model= and
>   options snd-intel-dspcfg dsp_driver=3 or 1
>   and systematic reboot.
>
>   Either I get dummy output, or I get proper output detection, alsamixer
>   and pavucontrol seems 100% ok, but no sound comes from the speakers.
>
>   I'm under a dualboot with Windows 10, BIOS fast boot disabled.
>   Ubuntu 20.04.2 LTS
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
>   Uname: Linux 5.8.0-44-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.16
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  thibauts   1522 F pulseaudio
>/dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Mar 10 18:10:30 2021
>   InstallationDate: Installed on 2021-03-09 (1 days ago)
>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp
> failed
>   Symptom_Card: Cannon Point-LP High Definition Audio Controller -
> sof-hda-dsp
>   Symptom_Jack: Grey Speaker, Internal
>   Symptom_Type: Only some of outputs are working
>   Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal]
> Playback problem
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/24/2019
>   dmi.bios.release: 1.4
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: V1.04
>   dmi.board.asset.tag: Default string
>   dmi.board.name: Guinness_WL
>   dmi.board.vendor: WL
>   dmi.board.version: V1.04
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Acer
>   dmi.chassis.version: V1.04
>   dmi.ec.firmware.release: 1.6
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
>   dmi.product.family: Swift 5
>   dmi.product.name: Swift SF515-51T
>   dmi.product.sku: 
>   dmi.product.version: V1.04
>   dmi.sys.vendor: Acer
>   mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+subscriptions
>

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audi

[Touch-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack

[Mateusz Stachowski]

I've filed a separate bug.

https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-12 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1934783] [NEW] Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

[Mateusz Stachowski]

Public bug reported:

Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
Unity, Gnome Shell both sessions (X.org and Wayland).

Also most of the programs have glitches. However Firefox seems
unaffected.

CPU:
  Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
  min/max: 2200/3600 MHz
Graphics:
  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
  driver: amdgpu v: kernel
  Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
  unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
  OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
  5.4.0-79-generic LLVM 12.0.0)
  v: 4.6 Mesa 21.0.3

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


** Tags: focal

** Attachment added: "Gnome Shell glitches.jpg"
   
https://bugs.launchpad.net/bugs/1934783/+attachment/5509398/+files/Gnome%20Shell%20glitches.jpg

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

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  New

Bug description:
  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

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

[Matthias Klose]

no, that patch doesn't help.  the gdb 10.2 build was fine, working
correctly.

gdb: configured with: --build=s390x-linux-gnu
 --host=s390x-linux-gnu
 --prefix=/usr
 --libexecdir=${prefix}/lib/gdb
 --disable-werror
 --disable-maintainer-mode
 --disable-dependency-tracking
 --disable-silent-rules
 --disable-gdbtk
 --disable-shared
 --with-system-readline
 --with-pkgversion='Ubuntu 11.0.90.20210705-0ubuntu2'
 --srcdir=/<>
 --with-expat
 --with-system-zlib
 --without-guile
 --without-babeltrace
 --with-debuginfod
 --with-babeltrace
 --with-system-gdbinit=/etc/gdb/gdbinit
 --with-system-gdbinit-dir=/etc/gdb/gdbinit.d
 --enable-tui
 --with-lzma
 --with-python=python3
 --with-xxhash
 --with-mpfr

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505]

[Simark]

Created attachment 13540
Proposed patch

I managed to get a working qemu setup without much efforts using
Buildroot, and I can reproduce the issue.  Although if there is a ready-
to-use Ubuntu image I can use, I'd be happy to use it (I just don't want
to go through the trouble of installing the distro in qemu with the
installer).

See the attached patch, it does fix the issue for me.

However, the inferior always hits this when running:

Program received signal SIGSEGV, Segmentation fault.
0x03ffac312c6c in _dl_debug_initialize () from /lib/ld64.so.1

... and that was happening prior to my patches, and in GDB 10.  I guess
you don't see it?

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505]

[Matthias Klose]

for a s390x setup, maybe see
https://developer.ibm.com/components/ibm-linuxone/gettingstarted/

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505]

[Simark]

This is clearly related to my change.  I don't have access to an s390x
machine to test this... do you have an easy way to set up a qemu machine
or something like that?

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934757] Re: Pulseaudio does not recognize integrated audio device

[Jarno Suni]

** Description changed:

+ I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo"
+ in "~/.config/pulse/default.pa". It caused pulseaudio to fail with this
+ version. I removed the line and run pulseaudio.
+ 
  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)
  
- EDIT: oh, it works again. I'll keep track of this issue.
+ EDIT: oh, it works again. I'll keep track of this issue. Maybe I should
+ have started pulseaudio by systemd?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

Title:
  Pulseaudio does not recognize integrated audio device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-
  stereo" in "~/.config/pulse/default.pa". It caused pulseaudio to fail
  with this version. I removed the line and run pulseaudio.

  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)

  EDIT: oh, it works again. I'll keep track of this issue. Maybe I
  should have started pulseaudio by systemd?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934757/+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 1934757] Re: Pulseaudio does not recognize integrated audio device

[Jarno Suni]

** Description changed:

  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)
+ 
+ EDIT: oh, it works again. I'll keep track of this issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

Title:
  Pulseaudio does not recognize integrated audio device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-
  stereo" in "~/.config/pulse/default.pa". It caused pulseaudio to fail
  with this version. I removed the line and run pulseaudio.

  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)

  EDIT: oh, it works again. I'll keep track of this issue. Maybe I
  should have started pulseaudio by systemd?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934757/+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 1924689] Re: When changing screen scale in GNOME Xorg, gnome-initial-setup's window shadow should not be glitched

[Daniel van Vugt]

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1875
   Importance: Unknown
   Status: Unknown

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

Title:
  When changing screen scale in GNOME Xorg, gnome-initial-setup's window
  shadow should not be glitched

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  New
Status in gnome-initial-setup package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Ubuntu release:
  Ubuntu 20.04.2 LTS

  Issue description:
  When the gnome-initial-setup launched, if user changes the scale 200 -> 400 
or 100 -> 200.
  There is some garbage on the edge of the window.

  The issue is not seen if we login in wayland session.

  A video is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1924689/+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 1934757] [NEW] Pulseaudio does not recognize integrated audio device

[Jarno Suni]

Public bug reported:

Unrecognized device:
Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.11
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Jul  6 12:16:50 2021
InstallationDate: Installed on 2019-12-05 (578 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
dmi.bios.date: 06/28/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A30
dmi.board.name: 051FJ8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 9010
dmi.product.sku: OptiPlex 9010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal regression-update

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

Title:
  Pulseaudio does not recognize integrated audio device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Unrecognized device:
  Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition 
Audio Controller (rev 04)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jul  6 12:16:50 2021
  InstallationDate: Installed on 2019-12-05 (578 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934757/+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 1924689] Re: When changing screen scale in GNOME Xorg, gnome-initial-setup's window shadow should not be glitched

[Yao Wei]

Reported to upstream with stripped test case:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1875

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1875
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1875

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

Title:
  When changing screen scale in GNOME Xorg, gnome-initial-setup's window
  shadow should not be glitched

Status in OEM Priority Project:
  New
Status in gnome-initial-setup package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Ubuntu release:
  Ubuntu 20.04.2 LTS

  Issue description:
  When the gnome-initial-setup launched, if user changes the scale 200 -> 400 
or 100 -> 200.
  There is some garbage on the edge of the window.

  The issue is not seen if we login in wayland session.

  A video is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924689/+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 1934147] Re: systemd leaks abandoned session scopes

[Launchpad Bug Tracker]

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

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

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

Title:
  systemd leaks abandoned session scopes

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a system that is monitored via telegraf I found many abandoned
  systemd session which I believe are created by a potential race where
  systemd is reloading unit files and at the same time a user is
  connecting to the system via ssh or is executing the su command.

  The simple reproducer

  $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
  daemon-reload & ssh localhost sleep 1 & done

  Wait > 1 second

  $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL

  To clean out STOPPED jobs and

  $ systemctl status --all 2> /dev/null | grep --before-context 3
  abandoned

  will produce something similar to

     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned
  --
  ● session-273.scope - Session 273 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-274.scope - Session 274 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-30.scope - Session 30 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
  --
  ● session-302.scope - Session 302 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
  --
     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned

  The system in question is running Bionic, systemd-237-3ubuntu10.48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934147/+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 1925798] Re: SRU the current 1.2.4 stable update

[Sebastien Bacher]

Testing 1.2.4-0ubuntu1 browsing and playing in pnp shared media still
works as expected

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

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

Title:
  SRU the current 1.2.4 stable update

Status in gupnp package in Ubuntu:
  Fix Released
Status in gupnp source package in Focal:
  Fix Committed

Bug description:
  * Impact

  That's the current GNOME stable update, including some bugfixes
  https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS

  * Test case

  The library is used by rygel for pnp media sharing. Enable the option
  from the settings and try browsing and playing for another computer
  using for example rhythmbox.

  * Regression potential

  The main fix is around IPv6 local resolution, check that if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1925798/+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 1930910] Re: Fix micmute hotkeys on HP ProBooks

[Andy Chi]

Hi @ddstreet,
May I know when will you create a new systemd release for all the series?

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

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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 1934005] Re: abstractions/X: Possible regression of X session functionality by removing 'w' from /tmp/.X11-unix/* line?

[Chris Guiver]

UWN publish day today; so earlier today I loaded torbrowser on my impish system 
and today it worked :)
apparmor: 3.0.0-0ubuntu9

I have since zsync'd the lubuntu impish daily & it works there too now

summary of https://bugs.launchpad.net/ubuntu/+source/torbrowser-
launcher/+bug/1933886/comments/14

Thanks Thomas/teward

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

Title:
  abstractions/X: Possible regression of X session functionality by
  removing 'w' from /tmp/.X11-unix/* line?

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Hirsute:
  In Progress
Status in apparmor source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Any application that requires access to X11 sockets for the Display may want 
to include abstractions/X in the AppArmor rules, which usually will include 
rules that we would want for access to the Display socket for X.

  However, an upstream regression was made by changes to the
  abstractions/X to remove the 'w' and leave it read only.  This doesn't
  work - X11 needs readwrite on the sockets for it to properly interact
  with X11.

  This is a fundamental regression that has been fixed upstream.

  
  [Test Plan]

  Any application that needs X11 integration with apparmor rules should
  `#include `

  This is the problem with https://bugs.launchpad.net/ubuntu/+source
  /torbrowser-launcher/+bug/1933886 - while the fix for that would be to
  add `#include ` in the ruleset, it will not function
  with the existing abstractions.  This is our test case in Impish:

   - add `#include ` into 
`/etc/apparmor.d/torbrowser.Browser.firefox` and the apparmor rule.
   - `sudo systemctl restart apparmor.service`
   - Attempt to run torbrowser with torbrowser-launcher, which should now 
properly work with the revisions.  Without, torbrowser-launcher 'starts' Tor 
Browser but then it just segfaults and stops running.

  We don't have a full test case for Hirsute at this time.

  
  [Where problems could occur]

  Based on my understanding of X11 and the upstream AppArmor bugs on
  this (refer to comments), there is no breakage introduced by this, in
  fact the breakage was already introduced upstream, so this simply
  fixes and removes the breakage when an apparmor rule includes these X
  abstractions and need to write to the socket but can't.

  Therefore, I don't believe there are any 'problems' that can occur
  with this change.

  
  [Original Description]

  In Focal, abstractions/X has the following section in it:

    # the unix socket to use to connect to the display
    /tmp/.X11-unix/* rw,
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.X11-unix/X[0-9]*"),
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.ICE-unix/[0-9]*"),

  However, in Impish, this seems to have changed:

    # the unix socket to use to connect to the display
    /tmp/.X11-unix/* r,
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.X11-unix/X[0-9]*"),
    unix (connect, receive, send)
     type=stream
     peer=(addr="@/tmp/.ICE-unix/[0-9]*"),

  This in turn breaks torbrowser-launcher's Firefox from launching, even
  if we include the X abstractions, because the display sockets in
  /tmp/.X11-unix/* (X0 for Display :0 for example) are not read/write.

  This looks like a MAJOR regression by removing the permissions.  Or
  has Impish apparmor not been updated for any Ubuntu specific changes?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apparmor 3.0.0-0ubuntu8
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Tue Jun 29 14:39:00 2021
  InstallationDate: Installed on 2021-06-29 (0 days ago)
  InstallationMedia: Lubuntu 21.10 "Impish Indri" - Alpha amd64 (20210628)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.11.0-20-generic 
root=UUID=d042602b-0900-4b2e-acb1-f67436e9805f ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1934005/+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 1934584] Re: Text and Icons are not shown after resuming from sleep

[Daniel van Vugt]

** Tags added: nvidia

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: hybrid multi-gpu

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

Title:
  Text and Icons are not shown after resuming from sleep

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Sometimes when resuming from sleep, ubuntu (gnome) does not render all
  text and icons. Lots of text from menus are missing.

  I've added a couple of screenshots as an attachment to illustrate.

  This does not happen everywhere, for example, Chrome, Firefox, and
  Nautilus all look ok by themselves.


  System info:
  ```
  # lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1034.35-oem 5.10.41
  Uname: Linux 5.10.0-1034-oem 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  465.31  Thu May 13 22:24:36 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 07:55:42 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 465.31, 5.10.0-1033-oem, x86_64: installed
   nvidia, 465.31, 5.10.0-1034-oem, x86_64: installed
   nvidia, 465.31, 5.8.0-59-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:22c0]
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0]
  InstallationDate: Installed on 2020-12-15 (200 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20THCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1034-oem 
root=UUID=ea99ef49-df2d-48fa-9558-61bcea3e36cd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET30W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20THCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET30W(1.15):bd04/15/2021:br1.15:efr1.8:svnLENOVO:pn20THCTO1WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 3
  dmi.product.name: 20THCTO1WW
  dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3
  dmi.product.version: ThinkPad P1 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.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:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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