[Touch-packages] [Bug 1995650] [NEW] Trivial: Unclosed tag in distro.py

[Sabri Ünal]

Public bug reported:

Hi, distro.py, line: 37 starts with a  tag but does not close it.

The code is here:


return(_("To improve the user experiece of Debian please take "
 "part in the popularity contest. If you do so the list of "
 "installed software and how often it was used will be "
 "collected and sent anonymously to the Debian project.\n\n"
 "The results are used to optimise the layout of the "
 "installation CDs."))

** 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/1995650

Title:
  Trivial: Unclosed  tag in distro.py

Status in software-properties package in Ubuntu:
  New

Bug description:
  Hi, distro.py, line: 37 starts with a  tag but does not close it.

  The code is here:

  
  return(_("To improve the user experiece of Debian please take "
   "part in the popularity contest. If you do so the list of "
   "installed software and how often it was used will be "
   "collected and sent anonymously to the Debian project.\n\n"
   "The results are used to optimise the layout of the "
   "installation CDs."))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1995650/+subscriptions


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

[Touch-packages] [Bug 1995647] [NEW] tdb-tools fails in dpkg, causing samba install to fail

[Cole Risch]

Public bug reported:

had lots of issues trying to get samba to work, eventually ripped all of
tdb-tools out and tried a "fresh install".  This is the relevant output:

Setting up tdb-tools (1.4.6-3) ...
update-alternatives: using /usr/bin/tdbbackup.tdbtools to provide /usr/bin/tdbba
ckup (tdbbackup) in auto mode
update-alternatives: error: unable to read link '/usr/bin/tdbbackup': Invalid ar
gument
dpkg: error processing package tdb-tools (--configure):
 installed tdb-tools package post-installation script subprocess returned error 
exit status 2
dpkg: dependency problems prevent configuration of samba:
 samba depends on tdb-tools; however:
  Package tdb-tools is not configured yet.

dpkg: error processing package samba (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup erro
r from a previous failure.
  Errors were encountered while processing:
 tdb-tools
 samba
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: tdb-tools 1.4.6-3
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  3 16:34:22 2022
InstallationDate: Installed on 2022-05-01 (186 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: tdb
UpgradeStatus: Upgraded to kinetic on 2022-11-03 (0 days ago)

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


** Tags: amd64 apport-bug kinetic

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

Title:
  tdb-tools fails in dpkg, causing samba install to fail

Status in tdb package in Ubuntu:
  New

Bug description:
  had lots of issues trying to get samba to work, eventually ripped all
  of tdb-tools out and tried a "fresh install".  This is the relevant
  output:

  Setting up tdb-tools (1.4.6-3) ...
  update-alternatives: using /usr/bin/tdbbackup.tdbtools to provide 
/usr/bin/tdbba
  ckup (tdbbackup) in auto mode
  update-alternatives: error: unable to read link '/usr/bin/tdbbackup': Invalid 
ar
  gument
  dpkg: error processing package tdb-tools (--configure):
   installed tdb-tools package post-installation script subprocess returned 
error 
  exit status 2
  dpkg: dependency problems prevent configuration of samba:
   samba depends on tdb-tools; however:
Package tdb-tools is not configured yet.

  dpkg: error processing package samba (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
erro
  r from a previous failure.
Errors were encountered while processing:
   tdb-tools
   samba
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: tdb-tools 1.4.6-3
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  3 16:34:22 2022
  InstallationDate: Installed on 2022-05-01 (186 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tdb
  UpgradeStatus: Upgraded to kinetic on 2022-11-03 (0 days ago)

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


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

[Touch-packages] [Bug 1993800] Re: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2>

[Bug Watch Updater]

** Changed in: llvm
   Status: New => 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/1993800

Title:
  LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8,
  Constant:i32<2>

Status in LLVM:
  Fix Released
Status in llvm-toolchain-15 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in llvm-toolchain-15 package in openSUSE:
  Unknown

Bug description:
  LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, 
Constant:i32<2>
    0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 
0x2f84090:1, Constant:i32<4>
  0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), 
> 0x2aad434, 0x2f63a30, Constant:i32<64>
    0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23
  0x2f51c10: i32 = Register %23
    0x2f82500: i32 = Constant<64>
  0x2f81b28: i32 = Constant<4>
    0x2f81e40: i32 = Constant<2>
  In function: fs_variant_partial

  [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic-
  armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz]

  Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't
  determine what project "fs_variant_partial" is in. Sounds like it
  might be in some old version of Mesa? The start of the log suggests
  it's running on focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/llvm/+bug/1993800/+subscriptions


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

[Touch-packages] [Bug 1777512] Re: key retrieval timeouts cause failures

[Canonical Juju QA Bot]

This bug has not been updated in 2 years, so we're marking it Low
importance. If you believe this is incorrect, please update the
importance.

** Tags added: expirebugs-bot

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

Title:
  key retrieval timeouts cause failures

Status in juju:
  Triaged
Status in software-properties package in Ubuntu:
  New

Bug description:
  We have been seeing keyserver timeouts causing failed runs at an
  increased rate recently (over the last 6+ months). Here is an example
  failure:

  [10.244.40.32] sudo: add-apt-repository -k https://keyserver.ubuntu.com/ 
--yes "ppa:curtin-dev/proposed"
  [10.244.40.32] out: Error: retrieving gpg key timed out.

  One idea is that this needs to be addressed by making the client
  (software-properties) more robust.

  
  We have an RT about this:
  https://portal.admin.canonical.com/C112309/

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1777512/+subscriptions


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

[Touch-packages] [Bug 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Simon IJskes]

reported upstream:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7626

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7626
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7626

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

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1971901] Re: dlltool uses non-unique temp filenames

[Kevin Puetz]

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

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

Title:
  dlltool uses non-unique temp filenames

Status in binutils:
  Fix Released
Status in Wine:
  Won't Fix
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils-mingw-w64 package in Ubuntu:
  Triaged
Status in binutils source package in Jammy:
  Fix Released
Status in binutils-mingw-w64 source package in Jammy:
  Triaged

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1

  /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like

  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.delay.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec
  Assembler messages:
  Error: can't open winmm_dll_t.s for reading: No such file or directory
  /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited 
with status 1
  /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: 
winmm_dll_t.o: No such file or directory
  winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1
  make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1
  make: *** Waiting for unfinished jobs
  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.cross.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec

  Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for
  it's temp file - these are not unique when building libwinmm.delay.a
  and libwinmm.cross.a in parallel. (This can of course affect any dll
  wine is building import libs for, winmm is just the one I happaned to
  get caught on).

  This is regression newly introduced in binutils 2.38 vs older versions
  which used getpid() as the basis of their temp name. We just
  encountered it as part of updating our CI for a winelib application
  from focal to jammy, but it seems to have been discovered by others
  already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885

  There is an upstream fix on master (2.39) which is already backported
  to the binutils-2_38 branch:
  https://sourceware.org/git/gitweb.cgi?p=binutils-
  gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just
  be a matter of cherry-picking. Hopefully the fact it's a regression
  from impish->jammy and that upstream already backported it to 2.38
  might make this a candidate for jammy-updates?

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1971901/+subscriptions


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

[Touch-packages] [Bug 1995613] [NEW] CUPS snap not available for all architectures

[Heinrich Schuchardt]

Public bug reported:

If the CUPS open printing snap is ever to become a replacement for the
CUPS deb package, it needs to be available on all architectures.
Currently only amd64, arm64, armhf are built; riscv64, ppc64el, and
s390x are missing.

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

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

Title:
  CUPS snap not available for all architectures

Status in cups package in Ubuntu:
  New

Bug description:
  If the CUPS open printing snap is ever to become a replacement for the
  CUPS deb package, it needs to be available on all architectures.
  Currently only amd64, arm64, armhf are built; riscv64, ppc64el, and
  s390x are missing.

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


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

[Touch-packages] [Bug 1995611] [NEW] Apport closes itself when "examine locally" or "show details"

[Benjamin Drung]

Public bug reported:

On GNOME, run:

```
apport-bug _usr_share_apport_apport-gtk.1000.crash
```

then click on "show details" or "example locally" (install apport-
retrace for it). The GTK UI will close without printing anything on
stdout/stderr.

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

** Attachment added: "_usr_share_apport_apport-gtk.1000.crash"
   
https://bugs.launchpad.net/bugs/1995611/+attachment/5628923/+files/_usr_share_apport_apport-gtk.1000.crash

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

Title:
  Apport closes itself when "examine locally" or "show details"

Status in apport package in Ubuntu:
  New

Bug description:
  On GNOME, run:

  ```
  apport-bug _usr_share_apport_apport-gtk.1000.crash
  ```

  then click on "show details" or "example locally" (install apport-
  retrace for it). The GTK UI will close without printing anything on
  stdout/stderr.

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


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

[Touch-packages] [Bug 1992454] Re: iptables: segfault when renaming a chain

[Louis Bouchard]

** Description changed:

+ [ Impact ]
+  * An explanation of the effects of the bug on users
+ 
  This is the description for the upstream fix of this bug[1] :
  
  This is an odd bug: If the number of chains is right and one renames the
- last one in the list, libiptc dereferences a NULL pointer.
+ last one in the list, libiptc dereferences a NULL pointer. * An explanation 
of the effects of the bug on users and
  
- Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug upstream.
- This bug is to have the fix included in Ubuntu in order to avoid such
- segmentation faults.
+  * justification for backporting the fix to the stable release.
+ Without this patch, users may experience segmentation fault when using
+ the following versions of iptables :
  
- For Jammy and onward, iptables uses the new nft libraries so the problem
- does not appear unless the -legacy commands are used.
+   - Bionic : iptables
+   - Focal  : iptables
+   - Jammy  : iptables-legacy
  
- The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
+  * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+ 
+ The upstream fix adjust the size of the chain_index if the element is the
+ last chain in the list.
+ 
+ [1]
+ 
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f
+ 
+ [ Test Plan ]
+ 
+  * detailed instructions how to reproduce the bug
+ 
+  The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
  8<
  #!/bin/bash
  #
  # Cover for a bug in libiptc:
  # - the chain 'node-98-tmp' is the last in the list sorted by name
  # - there are 81 chains in total, so three chain index buckets
  # - the last index bucket contains only the 'node-98-tmp' chain
  # => rename temporarily removes it from the bucket, leaving a NULL bucket
- #behind which is dereferenced later when inserting the chain again with 
new
- #name again
+ # behind which is dereferenced later when inserting the chain again with new
+ # name again
  
  (
-   echo "*filter"
-   for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
-   echo ":$chain - [0:0]"
-   done
-   echo "COMMIT"
+  echo "*filter"
+  for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
+   echo ":$chain - [0:0]"
+  done
+  echo "COMMIT"
  ) | $XT_MULTI iptables-legacy-restore
  $XT_MULTI iptables-legacy -E node-98-tmp node-98
  exit $?
  >8
  
- [1]
- 
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f
+ [ Where problems could occur ]
+ 
+ For Jammy and onward, only users of the -legacy commands may be affected.
+ Since Jammy, iptables uses the new nft libraries which are not affected
+ by the bug.
+ 
+ For Bionic and Focal users, the regular iptables command is affected by
+ the change.
+ 
+ As stated in the manpage :
+ E, --rename-chain old-chain new-chain
+   Rename the user specified chain to the user supplied name.  
This is cosmetic, and has no effect on the structure of the table.
+ 
+ In case of a problem, only the modification of the name would be affected
+ as this is clearly outlined as a cosmetic only change.
+ 
+ [ Other Info ]

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

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  In Progress
Status in iptables source package in 

[Touch-packages] [Bug 1995209] Re: tzdata 2022f release

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2022f-0ubuntu0.18.04.0

---
tzdata (2022f-0ubuntu0.18.04.0) bionic; urgency=medium

  * New upstream release (LP: #1995209):
- Mexico will no longer observe DST except near the US border.
- Chihuahua has moved to year-round -06 on 2022-10-30.
- Fiji no longer observes DST.

 -- Steve Langasek   Mon, 31 Oct 2022
02:02:00 +0100

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

Title:
  tzdata 2022f release

Status in tzdata package in Ubuntu:
  New
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Kinetic:
  Fix Released
Status in tzdata source package in Lunar:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Mexico will no longer observe DST except near the US border.
Chihuahua moves to year-round -06 on 2022-10-30.
  - Fiji no longer observes DST.

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


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

[Touch-packages] [Bug 1995209] Re: tzdata 2022f release

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2022f-0ubuntu0.20.04.0

---
tzdata (2022f-0ubuntu0.20.04.0) focal; urgency=medium

  * New upstream release (LP: #1995209):
- Mexico will no longer observe DST except near the US border.
- Chihuahua has moved to year-round -06 on 2022-10-30.
- Fiji no longer observes DST.
  * No ICU data update yet as none is yet available upstream.

 -- Steve Langasek   Mon, 31 Oct 2022
02:02:00 +0100

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

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

Title:
  tzdata 2022f release

Status in tzdata package in Ubuntu:
  New
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Kinetic:
  Fix Released
Status in tzdata source package in Lunar:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Mexico will no longer observe DST except near the US border.
Chihuahua moves to year-round -06 on 2022-10-30.
  - Fiji no longer observes DST.

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


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

[Touch-packages] [Bug 1995209] Re: tzdata 2022f release

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2022f-0ubuntu0.22.04.0

---
tzdata (2022f-0ubuntu0.22.04.0) jammy; urgency=medium

  * New upstream release (LP: #1995209):
- Mexico will no longer observe DST except near the US border.
- Chihuahua has moved to year-round -06 on 2022-10-30.
- Fiji no longer observes DST.
  * No ICU data update yet as none is yet available upstream.

 -- Steve Langasek   Mon, 31 Oct 2022
02:02:00 +0100

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

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

Title:
  tzdata 2022f release

Status in tzdata package in Ubuntu:
  New
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Kinetic:
  Fix Released
Status in tzdata source package in Lunar:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Mexico will no longer observe DST except near the US border.
Chihuahua moves to year-round -06 on 2022-10-30.
  - Fiji no longer observes DST.

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


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

[Touch-packages] [Bug 1995209] Update Released

[Brian Murray]

The verification of the Stable Release Update for tzdata 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 tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1995209

Title:
  tzdata 2022f release

Status in tzdata package in Ubuntu:
  New
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Kinetic:
  Fix Released
Status in tzdata source package in Lunar:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Mexico will no longer observe DST except near the US border.
Chihuahua moves to year-round -06 on 2022-10-30.
  - Fiji no longer observes DST.

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


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

[Touch-packages] [Bug 1995209] Re: tzdata 2022f release

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2022f-0ubuntu0.22.10.0

---
tzdata (2022f-0ubuntu0.22.10.0) kinetic; urgency=medium

  * New upstream release (LP: #1995209):
- Mexico will no longer observe DST except near the US border.
- Chihuahua has moved to year-round -06 on 2022-10-30.
- Fiji no longer observes DST.
  * No ICU data update yet as none is yet available upstream.

 -- Steve Langasek   Mon, 31 Oct 2022
02:02:00 +0100

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

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

Title:
  tzdata 2022f release

Status in tzdata package in Ubuntu:
  New
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Kinetic:
  Fix Released
Status in tzdata source package in Lunar:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Mexico will no longer observe DST except near the US border.
Chihuahua moves to year-round -06 on 2022-10-30.
  - Fiji no longer observes DST.

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


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

[Touch-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

[agoodm]

The reason blocking pings prevents the IP address change is because a
lot of DHCP servers ping the IP before they (re)allocate the address.
If the device responds to the ping then the DHCP server abandons the IP
and leases a new one.

For this reason the network stack should; in my opinion ignore IPv4 ICMP
echo requests during the DHCP part of the roam process.  Indeed I
believe that this was the behaviour previously.

Blocking IPv4 pings isnt impacting any other functionality for me.

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

Title:
  Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle
  of WiFi roam events which is causing the IP address to change every
  time it roams on the WiFi network.  This is a huge problem for me
  because I install WiFi networks for a living but in general it causes
  every TCP connection over IPv4 to die every time the laptop roams to a
  new wifi cell.

  00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)

  I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18.

  Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate 
with 86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE 
elem, Disable HE
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0110] 
device (wlp0s20f3): supplicant interface state: completed -> authenticating
  Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> 
authenticating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (wlp0s20f3): ip:dhcp4: restarting
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): canceled DHCP transaction
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): state changed no lease
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0113] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to 
associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 
MHz)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0463] 
device (wlp0s20f3): supplicant interface state: authenticating -> associating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0464] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: 
authenticating -> associating
  Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated
  Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp 
from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 
86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (wlp0s20f3): supplicant interface state: associating -> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associating 
-> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0799] 
device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0800] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associated 
-> 4way_handshake
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key 
negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP]
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=]
  Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 
20:11:15.091] [4119] (discord.cpp:551): JS console: 
["%c[GatewaySocket]","Performing an expedited heartbeat reason: network 
detected online."]
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000
  Jul 11 

[Touch-packages] [Bug 1995601] [NEW] tzdata 2022f ICU data update

[Simon Chopin]

Public bug reported:

The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:

https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f

The following Python script should work with the update and crash on
obsolete data:

from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
before = datetime(2022, 10, 1)
after = datetime(2022, 11, 2)
assert(tz.utcoffset(before) == tz.utcoffset(after))

** Affects: tzdata (Ubuntu)
 Importance: High
 Status: Triaged

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

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

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

** Affects: tzdata (Ubuntu Lunar)
 Importance: High
 Status: Triaged


** Tags: foundations-todo

** Also affects: tzdata (Ubuntu Lunar)
   Importance: High
   Status: Triaged

** Also affects: tzdata (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: tzdata (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

Title:
  tzdata 2022f ICU data update

Status in tzdata package in Ubuntu:
  Triaged
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Jammy:
  New
Status in tzdata source package in Kinetic:
  New
Status in tzdata source package in Lunar:
  Triaged

Bug description:
  The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
  upload, still matching the 2022e data instead. It's been updated
  upstream, so we need to do another round of SRUs for it:

  https://github.com/unicode-org/icu-
  data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c522f

  The following Python script should work with the update and crash on
  obsolete data:

  from datetime import datetime
  from icu import ICUtzinfo, TimeZone
  tz = ICUtzinfo(TimeZone.createTimeZone("America/Chihuahua"))
  before = datetime(2022, 10, 1)
  after = datetime(2022, 11, 2)
  assert(tz.utcoffset(before) == tz.utcoffset(after))

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


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

[Touch-packages] [Bug 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Timo Aaltonen]

Upstream does not follow downstream bugs, no.

That said, I don't know how to avoid this issue though. But you could
file it upstream at

https://gitlab.freedesktop.org/mesa/mesa/-/issues

and see what happens. Let us know the bug# too.

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

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

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1

[Nick Rosbrook]

I have verified each test case using openssh-server 1:9.0p1-1ubuntu7.1
from kinetic-proposed:

Test #1:

root@jammy:~# grep "^ListenAddress" /etc/ssh/sshd_config
ListenAddress 0.0.0.0:1234
root@jammy:~# systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
Drop-In: /run/systemd/system/service.d
 └─zzz-lxc-service.conf
 Active: active (running) since Thu 2022-11-03 10:22:04 UTC; 30s ago
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 868 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
   Main PID: 869 (sshd)
  Tasks: 1 (limit: 18901)
 Memory: 1.7M
CPU: 19ms
 CGroup: /system.slice/ssh.service
 └─869 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

Nov 03 10:22:04 jammy systemd[1]: Starting OpenBSD Secure Shell server...
Nov 03 10:22:04 jammy sshd[869]: Server listening on 0.0.0.0 port 1234.
Nov 03 10:22:04 jammy systemd[1]: Started OpenBSD Secure Shell server.
root@jammy:~# vi /etc/apt/sources.list
root@jammy:~# cat /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu kinetic main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu kinetic-updates main restricted universe 
multiverse
deb http://archive.ubuntu.com/ubuntu kinetic-proposed main restricted universe 
multiverse
deb http://security.ubuntu.com/ubuntu kinetic-security main restricted universe 
multiverse
root@jammy:~# apt update && apt dist-upgrade -y
[...]
root@jammy:~# cat /etc/systemd/system/ssh.socket.d/addresses.conf 
[Socket]
ListenStream=
ListenStream=0.0.0.0:1234
root@jammy:~# systemctl status ssh.socket
● ssh.socket - OpenBSD Secure Shell server socket
 Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.socket.d
 └─addresses.conf
 Active: active (listening) since Thu 2022-11-03 10:31:12 UTC; 23s ago
  Until: Thu 2022-11-03 10:31:12 UTC; 23s ago
   Triggers: ● ssh.service
 Listen: 0.0.0.0:1234 (Stream)
  Tasks: 0 (limit: 18901)
 Memory: 8.0K
CPU: 332us
 CGroup: /system.slice/ssh.socket

Nov 03 10:31:12 jammy systemd[1]: Listening on OpenBSD Secure Shell server 
socket.
---
Test #2:

root@jammy:~# grep "^ListenAddress" /etc/ssh/sshd_config
ListenAddress 0.0.0.0:1234
ListenAddress [::]:4321
root@jammy:~# systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
Drop-In: /run/systemd/system/service.d
 └─zzz-lxc-service.conf
 Active: active (running) since Thu 2022-11-03 10:33:34 UTC; 4s ago
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 868 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
   Main PID: 869 (sshd)
  Tasks: 1 (limit: 18901)
 Memory: 1.7M
CPU: 42ms
 CGroup: /system.slice/ssh.service
 └─869 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

Nov 03 10:33:34 jammy systemd[1]: Starting OpenBSD Secure Shell server...
Nov 03 10:33:34 jammy sshd[869]: Server listening on :: port 4321.
Nov 03 10:33:34 jammy sshd[869]: Server listening on 0.0.0.0 port 1234.
Nov 03 10:33:34 jammy systemd[1]: Started OpenBSD Secure Shell server.
root@jammy:~# vi /etc/apt/sources.list
root@jammy:~# cat /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu kinetic main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu kinetic-updates main restricted universe 
multiverse
deb http://archive.ubuntu.com/ubuntu kinetic-proposed main restricted universe 
multiverse
deb http://security.ubuntu.com/ubuntu kinetic-security main restricted universe 
multiverse
root@jammy:~# apt update && apt dist-upgrade -y
[...]
root@jammy:~# ls -alh /etc/systemd/system/ssh*
lrwxrwxrwx 1 root root 31 Nov  3 10:33 /etc/systemd/system/sshd.service -> 
/lib/systemd/system/ssh.service
root@jammy:~# systemctl status ssh.socket
○ ssh.socket - OpenBSD Secure Shell server socket
 Loaded: loaded (/lib/systemd/system/ssh.socket; disabled; preset: enabled)
 Active: inactive (dead)
   Triggers: ● ssh.service
 Listen: [::]:22 (Stream)
root@jammy:~# systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; preset: enabled)
Drop-In: /run/systemd/system/service.d
 └─zzz-lxc-service.conf
 Active: active (running) since Thu 2022-11-03 10:38:25 UTC; 33s ago
   Docs: man:sshd(8)
 man:sshd_config(5)
   Main PID: 7153 (sshd)
  Tasks: 1 (limit: 18901)
 Memory: 1.4M
CPU: 13ms
 CGroup: /system.slice/ssh.service
 └─7153 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

Nov 03 10:38:25 jammy systemd[1]: Starting OpenBSD Secure Shell server...
Nov 03 10:38:25 jammy sshd[7153]: Server listening on :: port 4321.
Nov 03 

[Touch-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

[Kevin Pulo]

The only upstream bug that seems potentially related is
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024
.  But that's more about ensuring that WPA auth has completed before
starting the DHCP renewal, and it's not clear to me how blocking ICMP
could avoid that problem.  So it might not actually be related.  The fix
for that issue went into development version NM 1.39.9, so I may try
building and trying an upstream version which includes it, to see if
that fixes the problem (but I won't be able to try before next week at
the earliest).

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1024
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024

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

Title:
  Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle
  of WiFi roam events which is causing the IP address to change every
  time it roams on the WiFi network.  This is a huge problem for me
  because I install WiFi networks for a living but in general it causes
  every TCP connection over IPv4 to die every time the laptop roams to a
  new wifi cell.

  00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)

  I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18.

  Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate 
with 86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE 
elem, Disable HE
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0110] 
device (wlp0s20f3): supplicant interface state: completed -> authenticating
  Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> 
authenticating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (wlp0s20f3): ip:dhcp4: restarting
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): canceled DHCP transaction
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): state changed no lease
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0113] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to 
associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 
MHz)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0463] 
device (wlp0s20f3): supplicant interface state: authenticating -> associating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0464] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: 
authenticating -> associating
  Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated
  Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp 
from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 
86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (wlp0s20f3): supplicant interface state: associating -> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associating 
-> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0799] 
device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0800] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associated 
-> 4way_handshake
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key 
negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP]
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=]
  Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 
20:11:15.091] [4119] (discord.cpp:551): JS 

[Touch-packages] [Bug 1995294] Re: rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty

[Nick Rosbrook]

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

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

Title:
  rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory
  not empty

Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  If a user a has an existing drop-in config for ssh.socket in
  /etc/systemd/system/ssh.socket.d upgrades to kinetic, and openssh-
  server.postint determines it should *not* perform migration to socket-
  activated ssh, they will receive an error from dpkg:

  Errors were encountered while processing:
   openssh-server
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A 
  recovery will run now (dpkg --configure -a). 

  Please report this bug in a browser at 
  http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug 
  and attach the files in /var/log/dist-upgrade/ to the bug report. 
  E:Sub-process /usr/bin/dpkg returned an error code (1) 

  Setting up openssh-server (1:9.0p1-1ubuntu7) ...
  rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not 
empty
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server

  [Test Plan]

  * On a Jammy machine, install openssh-server if necessary. Edit
  /etc/ssh/sshd_config to contain the following:

  $ cat /etc/ssh/sshd_config
  [... defaults everywhere else ...]

  #Port 22
  #AddressFamily any
  ListenAddress 0.0.0.0
  ListenAddress ::

  [... defaults everywhere else ...]

  * Create a trivial drop-in override for ssh.socket:

  $ systemctl edit ssh.socket
  $ cat /etc/systemd/system/ssh.socket.d/override.conf 
  [Unit]
  Description=Testing

  * Now perform an upgrade to Kinetic, and observe the dpkg error.

  [Where problems could occur]
  The solution should be to use rmdir's --ignore-fail-on-empty flag. If the 
flag was mis-spelled, that would produce a new error.

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


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

[Touch-packages] [Bug 1995209] Re: tzdata 2022f release

[Simon Chopin]

All verifications done (except for ICU data which wasn't ready) on
bionic, focal, jammy and kinetic using fresh LXC containers and the
instructions from
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984 adjusted
for the new data updates.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done verification-done-bionic 
verification-done-focal verification-done-jammy verification-done-kinetic

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

Title:
  tzdata 2022f release

Status in tzdata package in Ubuntu:
  New
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Mexico will no longer observe DST except near the US border.
Chihuahua moves to year-round -06 on 2022-10-30.
  - Fiji no longer observes DST.

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


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

[Touch-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

[Kevin Pulo]

I have the same symptoms on Ubuntu 22.04.1 on a 12th-gen Framework
laptop with Intel Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) device.
Every time wpa-supplicant chooses to associate with a different BSSID
(of the same SSID), the interface ends up being given a new IP address
by the DHCP server (usually the sequentially next address).

I don't have access to the DHCP server or its logs, but I tried the
above suggested workaround of setting net.ipv4.icmp_echo_ignore_all=1
and this prevents the problem from occurring.  So I expect the root
cause is the same.  (And as an aside, there is nothing in the client-
side logs to indicate that ICMP pings could be in any way related;
without this report it would have much more difficult to diagnose and
work around the problem.)

A different laptop running 18.04 on the same network is able to keep its
IP address when roaming, so presumably this is due to a change in
NetworkManager behaviour.

The problem makes it difficult to work in an enterprise office
environment (ie. moving around between desks and meeting rooms), because
all TCP connections are lost when the IP address changes, which is
especially impactful for ssh connections.

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

Title:
  Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle
  of WiFi roam events which is causing the IP address to change every
  time it roams on the WiFi network.  This is a huge problem for me
  because I install WiFi networks for a living but in general it causes
  every TCP connection over IPv4 to die every time the laptop roams to a
  new wifi cell.

  00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)

  I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18.

  Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate 
with 86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE 
elem, Disable HE
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0110] 
device (wlp0s20f3): supplicant interface state: completed -> authenticating
  Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> 
authenticating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (wlp0s20f3): ip:dhcp4: restarting
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): canceled DHCP transaction
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): state changed no lease
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0113] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to 
associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 
MHz)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0463] 
device (wlp0s20f3): supplicant interface state: authenticating -> associating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0464] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: 
authenticating -> associating
  Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated
  Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp 
from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 
86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (wlp0s20f3): supplicant interface state: associating -> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associating 
-> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0799] 
device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0800] 
device (p2p-dev-wlp0s20f3): supplicant 

[Touch-packages] [Bug 1988859] Re: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)]

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => 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/1988859

Title:
  Periodic black frames and stutter [Failed to post KMS update:
  drmModeAddFB does not support format 'AR24' (0x34325241)]

Status in Mesa:
  New
Status in Mutter:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Every so often, the desktop will go black and then re appear on Ubuntu
  22.10 Wayland Session which should not be occurring (this does not
  happen on 22.04.) Note that only the cursor can be seen.

  Reporting this before release so that it can be patched for (at least)
  the RasPi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8
  Uname: Linux 5.19.0-1001-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 16:10:37 2022
  DisplayManager: gdm3
  ImageMediaBuild: 20220826
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

** Tags added: fr-2934

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  

[Touch-packages] [Bug 1995294] Re: rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty

[Nick Rosbrook]

I have verified the fix using openssh-server from kinetic-proposed:

root@jammy:~# grep "^ListenAddress" /etc/ssh/sshd_config
ListenAddress 0.0.0.0
ListenAddress ::
root@jammy:~# systemctl edit ssh.socket
root@jammy:~# cat /etc/systemd/system/ssh.socket.d/override.conf 
[Unit]
Description=SRU verification
root@jammy:~# systemctl daemon-reload
root@jammy:~# systemctl status ssh.socket
○ ssh.socket - SRU verification
 Loaded: loaded (/lib/systemd/system/ssh.socket; disabled; vendor preset: 
enabled)
Drop-In: /etc/systemd/system/ssh.socket.d
 └─override.conf
 Active: inactive (dead)
 Listen: [::]:22 (Stream)
   Accepted: 0; Connected: 0;
root@jammy:~# vi /etc/apt/sources.list
root@jammy:~# cat /etc/apt/sources.list
# Generated by distrobuilder
deb http://archive.ubuntu.com/ubuntu kinetic main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu kinetic-updates main restricted universe 
multiverse
deb http://security.ubuntu.com/ubuntu kinetic-security main restricted universe 
multiverse
deb http://security.ubuntu.com/ubuntu kinetic-proposed main restricted universe 
multiverse
root@jammy:~# apt update && apt dist-upgrade
[ ... ]
root@jammy:~# apt-cache policy openssh-server
openssh-server:
  Installed: 1:9.0p1-1ubuntu7.1
  Candidate: 1:9.0p1-1ubuntu7.1
  Version table:
 *** 1:9.0p1-1ubuntu7.1 500
500 http://security.ubuntu.com/ubuntu kinetic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1:9.0p1-1ubuntu7 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages

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

Title:
  rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory
  not empty

Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  If a user a has an existing drop-in config for ssh.socket in
  /etc/systemd/system/ssh.socket.d upgrades to kinetic, and openssh-
  server.postint determines it should *not* perform migration to socket-
  activated ssh, they will receive an error from dpkg:

  Errors were encountered while processing:
   openssh-server
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A 
  recovery will run now (dpkg --configure -a). 

  Please report this bug in a browser at 
  http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug 
  and attach the files in /var/log/dist-upgrade/ to the bug report. 
  E:Sub-process /usr/bin/dpkg returned an error code (1) 

  Setting up openssh-server (1:9.0p1-1ubuntu7) ...
  rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not 
empty
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server

  [Test Plan]

  * On a Jammy machine, install openssh-server if necessary. Edit
  /etc/ssh/sshd_config to contain the following:

  $ cat /etc/ssh/sshd_config
  [... defaults everywhere else ...]

  #Port 22
  #AddressFamily any
  ListenAddress 0.0.0.0
  ListenAddress ::

  [... defaults everywhere else ...]

  * Create a trivial drop-in override for ssh.socket:

  $ systemctl edit ssh.socket
  $ cat /etc/systemd/system/ssh.socket.d/override.conf 
  [Unit]
  Description=Testing

  * Now perform an upgrade to Kinetic, and observe the dpkg error.

  [Where problems could occur]
  The solution should be to use rmdir's --ignore-fail-on-empty flag. If the 
flag was mis-spelled, that would produce a new error.

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


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

[Touch-packages] [Bug 1995305] Re: Cursor blurry with fractional scaling in some apps

[Daniel van Vugt]

** Tags added: kinetic

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

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

Title:
  Cursor blurry with fractional scaling in some apps

Status in mutter package in Ubuntu:
  New

Bug description:
  When using fractional scaling, the mouse cursor is blurry in some
  applications. Notably, this includes Settings and Nautilus. See the
  two screenshots for comparison.

  I'm on Ubuntu 22.10 on Wayland.

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


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

[Touch-packages] [Bug 1995305] Re: Cursor blurry with fractional scaling in some apps

[Mirosław Marszałek]

It's a blind shot, I have no idea which package should it be. But since
it's related to fractional scaling, I'm guessing wayland is a good place
to start.

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

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

Title:
  Cursor blurry with fractional scaling in some apps

Status in mutter package in Ubuntu:
  New

Bug description:
  When using fractional scaling, the mouse cursor is blurry in some
  applications. Notably, this includes Settings and Nautilus. See the
  two screenshots for comparison.

  I'm on Ubuntu 22.10 on Wayland.

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


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

[Touch-packages] [Bug 1988859] Re: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)]

[Daniel van Vugt]

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7621
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7621

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7621
   Importance: Unknown
   Status: Unknown

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

Title:
  Periodic black frames and stutter [Failed to post KMS update:
  drmModeAddFB does not support format 'AR24' (0x34325241)]

Status in Mesa:
  Unknown
Status in Mutter:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Every so often, the desktop will go black and then re appear on Ubuntu
  22.10 Wayland Session which should not be occurring (this does not
  happen on 22.04.) Note that only the cursor can be seen.

  Reporting this before release so that it can be patched for (at least)
  the RasPi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8
  Uname: Linux 5.19.0-1001-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 16:10:37 2022
  DisplayManager: gdm3
  ImageMediaBuild: 20220826
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1995305] [NEW] Cursor blurry with fractional scaling in some apps

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When using fractional scaling, the mouse cursor is blurry in some
applications. Notably, this includes Settings and Nautilus. See the two
screenshots for comparison.

I'm on Ubuntu 22.10 on Wayland.

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


** Tags: bot-comment
-- 
Cursor blurry with fractional scaling in some apps
https://bugs.launchpad.net/bugs/1995305
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland 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 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

[Launchpad Bug Tracker]

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

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

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

Title:
  Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle
  of WiFi roam events which is causing the IP address to change every
  time it roams on the WiFi network.  This is a huge problem for me
  because I install WiFi networks for a living but in general it causes
  every TCP connection over IPv4 to die every time the laptop roams to a
  new wifi cell.

  00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)

  I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18.

  Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate 
with 86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE 
elem, Disable HE
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0110] 
device (wlp0s20f3): supplicant interface state: completed -> authenticating
  Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> 
authenticating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (wlp0s20f3): ip:dhcp4: restarting
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): canceled DHCP transaction
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): state changed no lease
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0113] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to 
associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 
MHz)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0463] 
device (wlp0s20f3): supplicant interface state: authenticating -> associating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0464] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: 
authenticating -> associating
  Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated
  Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp 
from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 
86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (wlp0s20f3): supplicant interface state: associating -> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associating 
-> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0799] 
device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0800] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associated 
-> 4way_handshake
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key 
negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP]
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=]
  Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 
20:11:15.091] [4119] (discord.cpp:551): JS console: 
["%c[GatewaySocket]","Performing an expedited heartbeat reason: network 
detected online."]
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0970] 
device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0975] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: 
4way_handshake -> completed

  Jul 11 20:11:17 gateway-ycs dhcpd: 

[Touch-packages] [Bug 1995209] Re: tzdata 2022f release

[Adolfo Jayme Barrientos]

** Also affects: tzdata (Ubuntu Lunar)
   Importance: Critical
   Status: New

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

Title:
  tzdata 2022f release

Status in tzdata package in Ubuntu:
  New
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  New

Bug description:
  New timezone data, with the following timezones impacted:
  - Mexico will no longer observe DST except near the US border.
Chihuahua moves to year-round -06 on 2022-10-30.
  - Fiji no longer observes DST.

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


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