[Touch-packages] [Bug 2038892] Re: How To Contact +1(202-960-2084) McAfee Customer Service Number?

[William Grant]

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

** Information type changed from Public to Private

** Changed in: null-and-void
   Status: New => Invalid

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

Title:
  How To Contact +1(202-960-2084) McAfee Customer Service Number?

Status in NULL Project:
  Invalid

Bug description:
  o contact McAfee Customer Service Phone Number, you can follow these
  steps:

  Visit the McAfee Website: Start by going to the official McAfee
  website.

  Navigate to Support: Look for a “Support” or “Contact Us” link on the
  website. This is typically found at the top or bottom of the homepage.

  Choose Your Product: Select the McAfee product you need assistance
  with. They offer various security solutions, so make sure to pick the
  right one.

  Access the Help Center: Many common issues can be resolved by
  searching the McAfee Help Center. Try entering your problem or
  question in the search bar.

  Contact Options: If you can’t find a solution in the Help Center, look
  for contact options. This may include phone numbers, live chat, or
  email support. Click on the option that suits you best.

  Provide Information: When contacting McAfee, be prepared to provide
  information like your product key, account details, and a clear
  description of your issue.

  Follow Instructions: Follow the instructions provided by McAfee’s
  customer support team. They may guide you through troubleshooting
  steps or offer a solution tailored to your problem.

  Record Reference Numbers: If you speak to a customer service
  representative or open a support ticket, make sure to record any
  reference numbers or case IDs for future reference.

  Remember that McAfee’s contact options may vary depending on your
  location and the specific product you’re using. Always verify the
  contact details on their official website to ensure you’re reaching
  out to legitimate customer support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/2038892/+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 2036373] [NEW] package cups-bsd 2.3.1-9ubuntu1.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[William Ryan]

Public bug reported:

I am attempting to install Zoom onto my laptop. Any assistance would be
greatly appreciated. Thank you!

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups-bsd 2.3.1-9ubuntu1.5
ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116
Uname: Linux 5.15.0-83-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CupsErrorLog:
 
Date: Sun Sep 17 20:37:58 2023
DpkgHistoryLog:
 Start-Date: 2023-09-17  20:37:00
 Requested-By: ned_land (1000)
 Install: libgcc1:amd64 (1:10.5.0-1ubuntu1~20.04)
 Upgrade: libwebp6:amd64 (0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), 
libcups2:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), cups-server-common:amd64 
(2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), libwebpdemux2:amd64 
(0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), cups-ppdc:amd64 
(2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), firefox-locale-en:amd64 
(117.0+build2-0ubuntu0.20.04.1, 117.0.1+build2-0ubuntu0.20.04.1), 
libflac8:amd64 (1.3.3-1ubuntu0.1, 1.3.3-1ubuntu0.2), cups-daemon:amd64 
(2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), cups:amd64 (2.3.1-9ubuntu1.4, 
2.3.1-9ubuntu1.5), cups-client:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5)
DuplicateSignature:
 package:cups-bsd:2.3.1-9ubuntu1.5
 Setting up cups (2.3.1-9ubuntu1.5) ...
 Updating PPD files for cups ...
 dpkg: error processing package cups-bsd (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2020-09-07 (1105 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lpstat: device for HP_OfficeJet_Pro_6970_BE52B8_: 
implicitclass://HP_OfficeJet_Pro_6970_BE52B8_/
MachineType: LENOVO 80XS
Papersize: letter
PpdFiles: HP_OfficeJet_Pro_6970_BE52B8_: HP OfficeJet Pro 6970, driverless, 
cups-filters 1.27.4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=7dbb25c2-5410-4536-83ab-b1e2505c1318 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=7dbb25c2-5410-4536-83ab-b1e2505c1318 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: cups
Title: package cups-bsd 2.3.1-9ubuntu1.5 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2017
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: 5QCN18WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 320-15ABR
dmi.ec.firmware.release: 1.18
dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN18WW:bd07/13/2017:br1.18:efr1.18:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:skuLENOVO_MT_80XS_BU_idea_FM_ideapad320-15ABR:
dmi.product.family: ideapad 320-15ABR
dmi.product.name: 80XS
dmi.product.sku: LENOVO_MT_80XS_BU_idea_FM_ideapad 320-15ABR
dmi.product.version: Lenovo ideapad 320-15ABR
dmi.sys.vendor: LENOVO

** Affects: cups (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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/2036373

Title:
  package cups-bsd 2.3.1-9ubuntu1.5 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in cups package in Ubuntu:
  New

Bug description:
  I am attempting to install Zoom onto my laptop. Any assistance would
  be greatly appreciated. Thank you!

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: cups-bsd 2.3.1-9ubuntu1.5
  ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116
  Uname: Linux 5.15.0-83-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
   
  Date: Sun Sep 17 20:37:58 2023
  DpkgHistoryLog:
   Start-Date: 2023-09-17  20:37:00
   Requested-By: ned_land (1000)
   Install: libgcc1:amd64 (1:10.5.0-1ubuntu1~20.04)
   Upgrade: libwebp6:amd64 (0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), 
libcups2:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), cups-server-common:amd64 
(2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), libwebpdemux2:amd64 
(0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), cups-ppdc:amd64 
(2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), firefox-locale-en:amd64 
(117.0+build2-0ubuntu0.20.04.1, 117.0.1+build2-0ubuntu0.20.04.1), 
libflac8:amd64 (1.3.3-1ubuntu0.1, 

[Touch-packages] [Bug 1978079] Re: EFI pstore not cleared on boot

[William Tu]

** Also affects: linux-bluefield (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux-bluefield (Ubuntu Impish)

** No longer affects: linux-bluefield (Ubuntu Kinetic)

** Changed in: linux-bluefield (Ubuntu)
 Assignee: (unassigned) => William Tu (wtu)

** Changed in: linux-bluefield (Ubuntu Focal)
 Assignee: (unassigned) => William Tu (wtu)

** Changed in: linux-bluefield (Ubuntu Jammy)
 Assignee: (unassigned) => William Tu (wtu)

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

Title:
  EFI pstore not cleared on boot

Status in linux-bluefield package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-bluefield source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Impish:
  Won't Fix
Status in linux-bluefield source package in Jammy:
  New
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  Systemd has a systemd-pstore component that scans the pstore on boot
  and if non-empty, takes all previously created dumps, transfers them
  into its journal and removes the pstore elements. This is very
  important on UEFI systems, which only have a limited amount of space
  for variables.

  In Ubuntu, the kernel is configured with CONFIG_EFI_VARS_PSTORE=m
  which means the EFI pstore support gets loaded dynamically. In all of
  my boots, this dynamic module loading happened *after* systemd tried
  to check for pstore variables. So systemd-pstore never starts and
  never clears the UEFI variable store. I see this happening in AWS on
  Graviton instances, which eventually run out of space to store the
  dumps. On real hardware, this behavior may lead to unbootable systems.

  ```
  $ systemctl status systemd-pstore
  ○ systemd-pstore.service - Platform Persistent Storage Archival
   Loaded: loaded (/lib/systemd/system/systemd-pstore.service; enabled; 
vendor preset: enabled)
   Active: inactive (dead)
    Condition: start condition failed at Thu 2022-06-09 09:11:41 UTC; 29min ago
   └─ ConditionDirectoryNotEmpty=/sys/fs/pstore was not met
     Docs: man:systemd-pstore(8)

  Jun 09 09:11:41 ip-172-31-0-61 systemd[1]: Condition check resulted in
  Platform Persistent Storage Archival being skipped.

  $ ls -la /sys/fs/pstore
  total 0
  drwxr-x--- 2 root root0 Jun  9 09:11 .
  drwxr-xr-x 8 root root0 Jun  9 09:11 ..
  -r--r--r-- 1 root root 1803 Jun  9 09:07 dmesg-efi-165476562001001
  -r--r--r-- 1 root root 1777 Jun  9 09:07 dmesg-efi-165476562002001
  -r--r--r-- 1 root root 1773 Jun  9 09:07 dmesg-efi-165476562003001
  -r--r--r-- 1 root root 1815 Jun  9 09:07 dmesg-efi-165476562004001
  -r--r--r-- 1 root root 1826 Jun  9 09:07 dmesg-efi-165476562005001
  -r--r--r-- 1 root root 1754 Jun  9 09:07 dmesg-efi-165476562006001
  -r--r--r-- 1 root root 1821 Jun  9 09:07 dmesg-efi-165476562007001
  -r--r--r-- 1 root root 1767 Jun  9 09:07 dmesg-efi-165476562008001
  -r--r--r-- 1 root root 1729 Jun  9 09:07 dmesg-efi-165476562009001
  -r--r--r-- 1 root root 1819 Jun  9 09:07 dmesg-efi-165476562010001
  -r--r--r-- 1 root root 1767 Jun  9 09:07 dmesg-efi-165476562011001
  -r--r--r-- 1 root root 1775 Jun  9 09:07 dmesg-efi-165476562012001
  -r--r--r-- 1 root root 1802 Jun  9 09:07 dmesg-efi-165476562013001
  -r--r--r-- 1 root root 1812 Jun  9 09:07 dmesg-efi-165476562014001
  -r--r--r-- 1 root root 1764 Jun  9 09:07 dmesg-efi-165476562015001
  -r--r--r-- 1 root root 1795 Jun  9 09:11 dmesg-efi-165476589801001
  -r--r--r-- 1 root root 1785 Jun  9 09:11 dmesg-efi-165476589802001
  -r--r--r-- 1 root root 1683 Jun  9 09:11 dmesg-efi-165476589803001
  -r--r--r-- 1 root root 1785 Jun  9 09:11 dmesg-efi-165476589804001
  -r--r--r-- 1 root root 1771 Jun  9 09:11 dmesg-efi-165476589805001
  -r--r--r-- 1 root root 1797 Jun  9 09:11 dmesg-efi-165476589806001
  -r--r--r-- 1 root root 1805 Jun  9 09:11 dmesg-efi-165476589807001
  -r--r--r-- 1 root root 1781 Jun  9 09:11 dmesg-efi-165476589808001
  -r--r--r-- 1 root root 1806 Jun  9 09:11 dmesg-efi-165476589809001
  -r--r--r-- 1 root root 1821 Jun  9 09:11 dmesg-efi-165476589810001
  -r--r--r-- 1 root root 1763 Jun  9 09:11 dmesg-efi-165476589811001
  -r--r--r-- 1 root root 1783 Jun  9 09:11 dmesg-efi-165476589812001
  -r--r--r-- 1 root root 1788 Jun  9 09:11 dmesg-efi-165476589813001
  -r--r--r-- 1 root root 1788 Jun  9 09:11 dmesg-efi-165476589814001
  -r--r--r-- 1 root root 1786 Jun  9 09:11 dmesg-efi-165476589815001
  ```

  This problem affects (at least) Ubuntu 20.04 and 22.04. A quick fix
  would be to configure CONFIG_EFI_VARS_PSTORE=y so that it's always
  available. A long term fix would make systemd rescan the directory
  after all module probing settled.

  [Test Plan]

 

[Touch-packages] [Bug 2009502] Re: Enable /dev/sgx_vepc access for the group 'sgx'

[William Wilson]

The verification passed for jammy:

william@william-Latitude-E7470  ~  apt-cache policy udev
udev:
  Installed: 249.11-0ubuntu3.7
  Candidate: 249.11-0ubuntu3.9
  Version table:
 249.11-0ubuntu3.9 500 
500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
 *** 249.11-0ubuntu3.7 500 
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3 500 
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
 william@william-Latitude-E7470  ~  ls -l /dev/sgx_vepc
crw--- 1 root root 10, 125 Mar 24 12:42 /dev/sgx_vepc
william@william-Latitude-E7470  ~  apt-cache policy udev
udev:
  Installed: 249.11-0ubuntu3.9
  Candidate: 249.11-0ubuntu3.9
  Version table:
 *** 249.11-0ubuntu3.9 500 
500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.7 500 
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500 
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
 william@william-Latitude-E7470  ~  ls -l /dev/sgx_vepc  
crw-rw 1 root sgx 10, 125 Mar 24 12:48 /dev/sgx_vepc
 william@william-Latitude-E7470  ~ 


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

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

Title:
   Enable /dev/sgx_vepc access for the group 'sgx'

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  On systems where Intel SGX is available, access to a specific device
  node (/dev/sgx_vepc) must be enforced, with a specific permission
  (0660) and group (sgx).

  This allows KVM-based virtual machines to use such feature (the SGX
  "enclaves") in a proper fashion.  Without this, a manual udev rule
  needs to be created.

  [ Test Plan ]

  As the patch itself only tailors the permissions/group to the device
  node, in a system with Intel-SGX enabled, merely `ls -la` against the
  device node should show if the permissions and group are seen as
  expected.

  [ Where problems could occur ]

  N/A.  This seems to be a very straightforward inclusion, very specific
  to access enablement to the SGX reserved memory used for hosting
  enclaves.

  [ Other Info ]

  N/A.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009502/+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 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort

[William Ashley]

Thanks! I verified bionic and focal (via docker images) now successfully
run the libunwind-using tests updated earlier.

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

Title:
  arm64: broken c++ exception handler support leads to std::terminate()
  being called and program abort

Status in libunwind package in Ubuntu:
  Fix Released
Status in libunwind source package in Bionic:
  Fix Released
Status in libunwind source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On architectures other than i386 and amd64, the C++ exception support
  in libunwind appears to be broken, always failing and calling
  std::terminate() which leads to the program aborting.

  (gdb) bt
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
  #1  0xf7c2daac in __GI_abort () at abort.c:79
  #2  0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #3  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #4  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #5  0xf7e1f5e0 in __cxa_rethrow ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #6  0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #7  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #8  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #9  0xf7e1f574 in __cxa_throw ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9
  #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9

  Compiling libunwind with --enable-cxx-exceptions enabled leads to
  _Unwind_RaiseException being called during __cxa_throw(), which fails
  to find a handler, and the generic std::terminate() is called instead,
  aborting the program.

  On i386 and amd64 this doesn't seem to be the case, and the libunwind
  handlers seem to be present.

  To fix, we only enable the configure option --enable-cxx-exceptions on
  i386 and amd64 only, in debian/rules. This lets other architectures
  fall back to the symbols provided by libgcc_s, which implementation
  works correctly.

  [Testcase]

  Ali Sadi has provided a reproducer program.

  Start an arm64 instance, for example, a c6g.medium instance on AWS,
  with either Bionic or Focal.

  $ wget 
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz
  $ sudo apt install -y build-essential libunwind-dev
  $ tar xvf libunwind.tar.gz && cd test
  $ make all

  There are two executable, main and main_unwind. main is not linked to
  libunwind, and main_unwind is linked to libunwind.

  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  terminate called after throwing an instance of 'int'
  terminate called recursively
  Aborted (core dumped)

  If you install the test package available in the following ppa:

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

  $ make clean
  $ sudo apt install -y libunwind-dev
  $ make all
  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  int throws lib
  int caught main

  The exception is caught as expected the program does not abort.

  [Where problems could occur]

  For architectures other than i386 and amd64, we are changing from
  libunwind provided exception handlers for __cxa_throw(), and using
  those provided by libgcc_s instead.

  There are a few reverse dependencies for libunwind-dev and libunwind8,
  which need to be considered:

  $ apt rdepends libunwind-dev
  libunwind-dev
  Reverse Depends:
Depends: libunwind-setjmp0-dev (= 1.2.1-9build1)
Depends: libefl-all-dev

  t$ apt rdepends libunwind-dev8
  libunwind8
  Reverse Depends:
Depends: libunwind-dev (= 1.2.1-9build1)
Depends: xvfb
Depends: xnest
Depends: xdmx
Depends: xwayland
Depends: xserver-xorg-core
Depends: xserver-xephyr
Depends: linux-tools-5.4.0-*
Depends: linux-raspi-tools-*
Depends: linux-raspi2-tools-5.4.0-*
Depends: linux-raspi2-5.4-tools-5.4.0-*
Depends: linux-oracle-5.15-tools-5.15.0-*
Depends: linux-lowlatency-hwe-5.15-tools-5.15.0-*
Depends: linux-hwe-5.8-tools-5.8.0-*
Depends: linux-hwe-5.15-tools-5.15.0-*
Depends: linux-gke-tools-5.4.0-*
Depends: linux-gke-5.15-tools-5.15.0-*
Depends: linux-gcp-tools-5.4.0-*
Depends: linux-gcp-5.15-tools-5.15.0-*
Depends: linux-azure-tools-5.4.0-*
Depends: linux-azure-5.15-tools-5.15.0-*
Depends: linux-aws-tools-5.4.0-*
Depends: linux-aws-5.8-tools-5.8.0-*
Depends: linux-aws-5.15-tools-5.15.0-*
Depends: xvfb
Depends: xnest
Depends: xdmx
Depends: trafficserver

[Touch-packages] [Bug 2011722] [NEW] Move oem-config-setup steps into ubuntu-raspi-settings-desktop

[William Wilson]

Public bug reported:

When building images with livecd-rootfs, there is a hook to set up oem-
config for preinstalled raspi desktop images. As we move away from
livecd-rootfs (and the use of hooks in general), this step should be
moved into a package.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Move oem-config-setup steps into ubuntu-raspi-settings-desktop

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  When building images with livecd-rootfs, there is a hook to set up
  oem-config for preinstalled raspi desktop images. As we move away from
  livecd-rootfs (and the use of hooks in general), this step should be
  moved into a package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2011722/+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 2009502] Re: Enable /dev/sgx_vepc access for the group 'sgx'

[William Wilson]

The verification passed for jammy:

```
william@william-Latitude-E7470  ~  apt-cache policy udev
udev:
  Installed: 249.11-0ubuntu3.7
  Candidate: 249.11-0ubuntu3.8
  Version table:
 *** 249.11-0ubuntu3.8 500
500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.7 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
 william@william-Latitude-E7470  ~  ls -al /dev/sgx_vepc 
crw--- 1 root root 10, 125 Mar 14 14:01 /dev/sgx_vepc
william@william-Latitude-E7470  ~  apt-cache policy udev
udev:
  Installed: 249.11-0ubuntu3.8
  Candidate: 249.11-0ubuntu3.8
  Version table:
 *** 249.11-0ubuntu3.8 500
500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.7 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
 william@william-Latitude-E7470  ~  ls -al /dev/sgx_vepc 
crw-rw 1 root sgx 10, 125 Mar 14 14:01 /dev/sgx_vepc
```

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

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

Title:
   Enable /dev/sgx_vepc access for the group 'sgx'

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  On systems where Intel SGX is available, access to a specific device
  node (/dev/sgx_vepc) must be enforced, with a specific permission
  (0660) and group (sgx).

  This allows KVM-based virtual machines to use such feature (the SGX
  "enclaves") in a proper fashion.  Without this, a manual udev rule
  needs to be created.

  [ Test Plan ]

  As the patch itself only tailors the permissions/group to the device
  node, in a system with Intel-SGX enabled, merely `ls -la` against the
  device node should show if the permissions and group are seen as
  expected.

  [ Where problems could occur ]

  N/A.  This seems to be a very straightforward inclusion, very specific
  to access enablement to the SGX reserved memory used for hosting
  enclaves.

  [ Other Info ]

  N/A.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009502/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

[William]

You select your kernel in the grub boot menu. There is an option for
alternative boot configurations. I have a dual boot environment set up
so grub comes up every time for me. I think you hit esc to bring it up
if it normally boots straight into windows. If you have any trouble it
should come up in a search pretty quick.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

[William]

Booting with linux-image-5.19.0-35-generic appears to be the problem in
22.10. Booting with linux-image-5.19.0-21-generic lists the audio
devices again.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

[William]

This issue is also present in 22.10. After the update broke audio, I
reinstalled 22.10 from a live usb which fixed the issue until I updated
again and the issue reappeared.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort

[William Ashley]

Thank you for that thorough explanation and helping get this fix
released, Matthew.

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

Title:
  arm64: broken c++ exception handler support leads to std::terminate()
  being called and program abort

Status in libunwind package in Ubuntu:
  Fix Released
Status in libunwind source package in Bionic:
  Fix Committed
Status in libunwind source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  On architectures other than i386 and amd64, the C++ exception support
  in libunwind appears to be broken, always failing and calling
  std::terminate() which leads to the program aborting.

  (gdb) bt
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
  #1  0xf7c2daac in __GI_abort () at abort.c:79
  #2  0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #3  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #4  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #5  0xf7e1f5e0 in __cxa_rethrow ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #6  0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #7  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #8  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #9  0xf7e1f574 in __cxa_throw ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9
  #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9

  Compiling libunwind with --enable-cxx-exceptions enabled leads to
  _Unwind_RaiseException being called during __cxa_throw(), which fails
  to find a handler, and the generic std::terminate() is called instead,
  aborting the program.

  On i386 and amd64 this doesn't seem to be the case, and the libunwind
  handlers seem to be present.

  To fix, we only enable the configure option --enable-cxx-exceptions on
  i386 and amd64 only, in debian/rules. This lets other architectures
  fall back to the symbols provided by libgcc_s, which implementation
  works correctly.

  [Testcase]

  Ali Sadi has provided a reproducer program.

  Start an arm64 instance, for example, a c6g.medium instance on AWS,
  with either Bionic or Focal.

  $ wget 
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz
  $ sudo apt install -y build-essential libunwind-dev
  $ tar xvf libunwind.tar.gz && cd test
  $ make all

  There are two executable, main and main_unwind. main is not linked to
  libunwind, and main_unwind is linked to libunwind.

  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  terminate called after throwing an instance of 'int'
  terminate called recursively
  Aborted (core dumped)

  If you install the test package available in the following ppa:

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

  $ make clean
  $ sudo apt install -y libunwind-dev
  $ make all
  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  int throws lib
  int caught main

  The exception is caught as expected the program does not abort.

  [Where problems could occur]

  For architectures other than i386 and amd64, we are changing from
  libunwind provided exception handlers for __cxa_throw(), and using
  those provided by libgcc_s instead.

  There are a few reverse dependencies for libunwind-dev and libunwind8,
  which need to be considered:

  $ apt rdepends libunwind-dev
  libunwind-dev
  Reverse Depends:
Depends: libunwind-setjmp0-dev (= 1.2.1-9build1)
Depends: libefl-all-dev

  t$ apt rdepends libunwind-dev8
  libunwind8
  Reverse Depends:
Depends: libunwind-dev (= 1.2.1-9build1)
Depends: xvfb
Depends: xnest
Depends: xdmx
Depends: xwayland
Depends: xserver-xorg-core
Depends: xserver-xephyr
Depends: linux-tools-5.4.0-*
Depends: linux-raspi-tools-*
Depends: linux-raspi2-tools-5.4.0-*
Depends: linux-raspi2-5.4-tools-5.4.0-*
Depends: linux-oracle-5.15-tools-5.15.0-*
Depends: linux-lowlatency-hwe-5.15-tools-5.15.0-*
Depends: linux-hwe-5.8-tools-5.8.0-*
Depends: linux-hwe-5.15-tools-5.15.0-*
Depends: linux-gke-tools-5.4.0-*
Depends: linux-gke-5.15-tools-5.15.0-*
Depends: linux-gcp-tools-5.4.0-*
Depends: linux-gcp-5.15-tools-5.15.0-*
Depends: linux-azure-tools-5.4.0-*
Depends: linux-azure-5.15-tools-5.15.0-*
Depends: linux-aws-tools-5.4.0-*
Depends: linux-aws-5.8-tools-5.8.0-*
Depends: linux-aws-5.15-tools-5.15.0-*
Depends: xvfb
Depends: xnest
Depends: xdmx
Depends: trafficserver
Depends: tilix
Depends: 

[Touch-packages] [Bug 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort

[William Ashley]

How long will it take for these changes to be released to Focal and
Bionic?

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

Title:
  arm64: broken c++ exception handler support leads to std::terminate()
  being called and program abort

Status in libunwind package in Ubuntu:
  Fix Released
Status in libunwind source package in Bionic:
  Fix Committed
Status in libunwind source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  On architectures other than i386 and amd64, the C++ exception support
  in libunwind appears to be broken, always failing and calling
  std::terminate() which leads to the program aborting.

  (gdb) bt
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
  #1  0xf7c2daac in __GI_abort () at abort.c:79
  #2  0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #3  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #4  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #5  0xf7e1f5e0 in __cxa_rethrow ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #6  0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #7  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #8  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #9  0xf7e1f574 in __cxa_throw ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9
  #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9

  Compiling libunwind with --enable-cxx-exceptions enabled leads to
  _Unwind_RaiseException being called during __cxa_throw(), which fails
  to find a handler, and the generic std::terminate() is called instead,
  aborting the program.

  On i386 and amd64 this doesn't seem to be the case, and the libunwind
  handlers seem to be present.

  To fix, we only enable the configure option --enable-cxx-exceptions on
  i386 and amd64 only, in debian/rules. This lets other architectures
  fall back to the symbols provided by libgcc_s, which implementation
  works correctly.

  [Testcase]

  Ali Sadi has provided a reproducer program.

  Start an arm64 instance, for example, a c6g.medium instance on AWS,
  with either Bionic or Focal.

  $ wget 
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz
  $ sudo apt install -y build-essential libunwind-dev
  $ tar xvf libunwind.tar.gz && cd test
  $ make all

  There are two executable, main and main_unwind. main is not linked to
  libunwind, and main_unwind is linked to libunwind.

  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  terminate called after throwing an instance of 'int'
  terminate called recursively
  Aborted (core dumped)

  If you install the test package available in the following ppa:

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

  $ make clean
  $ sudo apt install -y libunwind-dev
  $ make all
  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  int throws lib
  int caught main

  The exception is caught as expected the program does not abort.

  [Where problems could occur]

  For architectures other than i386 and amd64, we are changing from
  libunwind provided exception handlers for __cxa_throw(), and using
  those provided by libgcc_s instead.

  There are a few reverse dependencies for libunwind-dev and libunwind8,
  which need to be considered:

  $ apt rdepends libunwind-dev
  libunwind-dev
  Reverse Depends:
Depends: libunwind-setjmp0-dev (= 1.2.1-9build1)
Depends: libefl-all-dev

  t$ apt rdepends libunwind-dev8
  libunwind8
  Reverse Depends:
Depends: libunwind-dev (= 1.2.1-9build1)
Depends: xvfb
Depends: xnest
Depends: xdmx
Depends: xwayland
Depends: xserver-xorg-core
Depends: xserver-xephyr
Depends: linux-tools-5.4.0-*
Depends: linux-raspi-tools-*
Depends: linux-raspi2-tools-5.4.0-*
Depends: linux-raspi2-5.4-tools-5.4.0-*
Depends: linux-oracle-5.15-tools-5.15.0-*
Depends: linux-lowlatency-hwe-5.15-tools-5.15.0-*
Depends: linux-hwe-5.8-tools-5.8.0-*
Depends: linux-hwe-5.15-tools-5.15.0-*
Depends: linux-gke-tools-5.4.0-*
Depends: linux-gke-5.15-tools-5.15.0-*
Depends: linux-gcp-tools-5.4.0-*
Depends: linux-gcp-5.15-tools-5.15.0-*
Depends: linux-azure-tools-5.4.0-*
Depends: linux-azure-5.15-tools-5.15.0-*
Depends: linux-aws-tools-5.4.0-*
Depends: linux-aws-5.8-tools-5.8.0-*
Depends: linux-aws-5.15-tools-5.15.0-*
Depends: xvfb
Depends: xnest
Depends: xdmx
Depends: trafficserver
Depends: tilix
Depends: 

[Touch-packages] [Bug 2004092] Re: casper fails to add any users because GID 999 is already taken

[William Wilson]

** Tags removed: rls-ll-incoming
** Tags added: foundations-todo

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

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

Title:
  casper fails to add any users because GID 999 is already taken

Status in casper package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  This bug is due to the latest systemd upload in Ubuntu. systemd-
  journald now uses GID 999, when casper explicitly sets the live user
  to that UID and GID.

  Rather than going through the painstaking task of updating systemd to
  use a *different* user, let's just update casper to use 1000, which is
  the first dynamically-allocated user account per Debian Policy[1].

  [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and-
  gid-classes

  [ Original Report ]

  Normally, when one first boots a live ISO, a desktop automatically
  appears, asking users if they want to try or install Ubuntu (or, in
  the case of Lubuntu, they are simply dropped into a working desktop
  with an installation desktop icon available). As of the Lubuntu ISO on
  January 27, 2023, this has stopped occuring. Plymouth shows the
  initial boot animation, but the user is then dropped to a solid black
  screen. No user input is accepted. Attempting to switch to a TTY and
  sign in fails with the default "lubuntu" username and a blank password
  (the error "Login incorrect" is displayed).

  On Ubuntu Desktop, the behavior is even stranger. Rather than being
  shown a "Try or Install Ubuntu" screen, an initial system setup wizard
  appears that takes the user through the process of creating a user
  account. On a live ISO. Only after this wizard is finished does the
  "Try or Install Ubuntu" screen appear. Attempting to log into a TTY
  using the default "ubuntu" username and a blank password fails the
  same way as Lubuntu does, if done before the wizard is finished.
  However, one can log into a TTY if they finish the wizard and then
  attempt to log into the TTY using the credentials provided during user
  account setup.

  This issue affects at least the Lubuntu ISOs as of January 27, 2023,
  and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is
  assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO
  from the 26th is most likely unaffected as there is successful testing
  information for Lubuntu on the 26th, so something likely happened
  between the 26th and the 27th to cause this breakage.

  Steps to reproduce:

  1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu.
  2. Boot the ISO (hardware is irrelevant - this appears to occur on both 
physical and virtual hardware).

  For Lubuntu:

  3. Wait until you are dropped to a black, blank screen.
  4. Wait a while, then attempt to switch to a TTY and attempt to log in using 
"lubuntu" as the username and a blank password. The login attempt will be 
denied.

  For Ubuntu Desktop:

  3. Wait until you are provided with an initial system setup wizard.
  4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a 
blank password. The login attempt will be denied.
  5. Switch back to the system setup wizard, and complete it.
  6. After completing the wizard, switch to a TTY again and attempt to log in 
using the credentials provided to the wizard. The login attempt will be 
successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2002318] Re: Please merge lsb 11.5 from Debian unstable.

[William Wilson]

This bug was fixed in the package lsb - 11.5
Sponsored for Dave Jones (waveform)

---
lsb (11.5) unstable; urgency=medium

  * Team upload.
  * Drop lsb-release, taken over by src:lsb-release-minimal.

 -- Adam Borowski   Wed, 02 Nov 2022 01:41:43 +0100

lsb (11.4) unstable; urgency=medium

  * Team upload.
  * lsb-base: add a dependency on sysvinit-utils 3.05-4 (Closes: #1019661)

 -- Adam Borowski   Tue, 13 Sep 2022 20:08:57 +0200

lsb (11.3) unstable; urgency=medium

  * Team upload.
  * Make the lsb-base package empty; debootstrap doesn't understand
"Provides".

 -- Adam Borowski   Mon, 12 Sep 2022 20:54:36 +0200

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

Title:
  Please merge lsb 11.5 from Debian unstable.

Status in lsb package in Ubuntu:
  Fix Released

Bug description:
  Please merge lsb 11.5 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/2002318/+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 2002318] Re: Please merge lsb 11.5 from Debian unstable.

[William Wilson]

After some internal team discussion we've agreed to do a force-sync from
Debian to only use the empty transitional package. till-kamppeter has
confirmed that printer drivers have moved to snap based rather than
needing lsb to install.

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

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

Title:
  Please merge lsb 11.5 from Debian unstable.

Status in lsb package in Ubuntu:
  Fix Released

Bug description:
  Please merge lsb 11.5 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/2002318/+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 2002428] Re: Autopkgtest failure due to moved testcase

[William Wilson]

Thanks for the patch! One comment, when a patch is ready for sponsoring
you can drop the "~ppa2" from the version number. I'll just go ahead and
do that before uploading for this one.

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

Title:
  Autopkgtest failure due to moved testcase

Status in coreutils package in Ubuntu:
  New

Bug description:
  In 9.1-1ubuntu1 (lunar), a testcase has been renamed from proc-
  selinux-segfault.sh to selinux-segfault.sh . This changes
  debian/tests/upstream to reflect the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2002428/+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 1999104] Re: libunwind causes crashes on arm64

[William Ashley]

The key difference that --enable-cxx-exceptions makes is that it results
in libunwind having _Unwind_RaiseException (and likely other functions),
which gets called during a C++ throw by __cxa_throw. Without libunwind,
this symbol is provided by libgcc_s, whose implementation works
correctly. For whatever reason, the one in libunwind, on aarch64, does
not succeed in finding a handler and instead calls terminate (which is
normal when there is no handler for an exception).

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

Title:
  libunwind causes crashes on arm64

Status in libunwind package in Ubuntu:
  New

Bug description:
  There is a bug in libunwind in both 18.04 and 20.04 on arm64 where
  when linked with libunwind instead of catching an exception, the
  program crashes. This was first seen on mcrouter, but attached is a
  small reproducer where `main_unwind` will crash. The libunwind
  shipping with 22.04 doesn't appear to have this problem, nor do
  unmodified upstream versions (including the 1.2.1 which is the 18.04
  and 20.04 version).

  Attached is a small reproducer that demonstrates the problem.

  Ubuntu 22.04:
  ```
  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  int throws lib
  int caught main
  ```

  Ubuntu 20.04:
  ```
  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  terminate called after throwing an instance of 'int'
  terminate called recursively
  Aborted (core dumped)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+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 1999104] Re: libunwind causes crashes on arm64

[William Ashley]

1.2.1-10 (https://launchpad.net/ubuntu/+source/libunwind/1.2.1-10)
resolves this issue on 20. It includes a change to not use --enable-cxx-
exceptions when building libunwind, and that is the key here. Even on
Ubuntu 22, with its much newer upstream version of libunwind, adding
that option triggers the same failures in C++ exceptions that we've
observed here on 18 and 20.

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

Title:
  libunwind causes crashes on arm64

Status in libunwind package in Ubuntu:
  New

Bug description:
  There is a bug in libunwind in both 18.04 and 20.04 on arm64 where
  when linked with libunwind instead of catching an exception, the
  program crashes. This was first seen on mcrouter, but attached is a
  small reproducer where `main_unwind` will crash. The libunwind
  shipping with 22.04 doesn't appear to have this problem, nor do
  unmodified upstream versions (including the 1.2.1 which is the 18.04
  and 20.04 version).

  Attached is a small reproducer that demonstrates the problem.

  Ubuntu 22.04:
  ```
  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  int throws lib
  int caught main
  ```

  Ubuntu 20.04:
  ```
  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  terminate called after throwing an instance of 'int'
  terminate called recursively
  Aborted (core dumped)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+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 1999104] Re: libunwind causes crashes on arm64

[William Ashley]

I've slimmed down the reproducer to a single main function and removed
any additional compiler arguments.

** Attachment added: "repro.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635160/+files/repro.tar.gz

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

Title:
  libunwind causes crashes on arm64

Status in libunwind package in Ubuntu:
  New

Bug description:
  There is a bug in libunwind in both 18.04 and 20.04 on arm64 where
  when linked with libunwind instead of catching an exception, the
  program crashes. This was first seen on mcrouter, but attached is a
  small reproducer where `main_unwind` will crash. The libunwind
  shipping with 22.04 doesn't appear to have this problem, nor do
  unmodified upstream versions (including the 1.2.1 which is the 18.04
  and 20.04 version).

  Attached is a small reproducer that demonstrates the problem.

  Ubuntu 22.04:
  ```
  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  int throws lib
  int caught main
  ```

  Ubuntu 20.04:
  ```
  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  terminate called after throwing an instance of 'int'
  terminate called recursively
  Aborted (core dumped)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+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 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface

[William Wilson]

** Tags added: foundations-todo

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

Title:
  initramfs need to mount efivarfs because kernel 6.0 deprecated
  'efivars' sysfs interface

Status in OEM Priority Project:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  New

Bug description:
  [ Impact ]

  kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC
  RAID, mdadm needs initramfs to mount efivarfs instead.

  [1] The commit:
  commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741
  Author: Ard Biesheuvel 
  Date: Mon Jun 20 13:34:03 2022 +0200

  efi: vars: Remove deprecated 'efivars' sysfs interface

  [ Test Plan ]

  1. Install initramfs-tools
  2. update-initramfs -u
  3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs
  4. Check if boot script 00_mount_efivarfs exists in directory 
/tmp/extract-initramfs/main/scripts/init-top/
  5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot 
script 00_mount_efivarfs will be execute before udev.

  [ Where problems could occur ]

  Not sure if there any other tools/utilities also need to mount efivarfs as 
early as mdadm but the probability of file conflict should be very low.
  Also, there are no impact mounting efivarfs multiple times.
  mount: /sys/firmware/efi/efivars: efivarfs already mounted on 
/sys/firmware/efi/efivars.

  [ Scope ]

  Jammy, Kinetic

  [ Other Info ]

  The private bug link
  https://bugs.launchpad.net/somerville/+bug/1990231

  debian MR:
  https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994936/+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 1994165] Re: CMS_final: do not ignore CMS_dataFinal result

[William Wilson]

** Tags added: foundations-triage-discuss

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

Title:
  CMS_final: do not ignore CMS_dataFinal result

Status in openssl package in Ubuntu:
  Triaged
Status in openssl source package in Jammy:
  Triaged
Status in openssl source package in Kinetic:
  Triaged

Bug description:
  https://github.com/openssl/openssl/pull/18876

  The CMS_dataFinal result is important as signature may fail, however, it
  is ignored while returning success from CMS_final.

  Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)"

  Thanks

  Upstream commit:

  ```
  commit 67c0460b89cc1b0644a1a59af78284dfd8d720af
  Author: Alon Bar-Lev 
  Date:   Tue Jul 26 15:17:06 2022 +0300

  Handle SMIME_crlf_copy return code
  
  Currently the SMIME_crlf_copy result is ignored in all usages. It does
  return failure when memory allocation fails.
  
  This patch handles the SMIME_crlf_copy return code in all occurrences.
  
  Signed-off-by: Alon Bar-Lev 
  
  Reviewed-by: Tomas Mraz 
  Reviewed-by: Paul Dale 
  Reviewed-by: Hugo Landau 
  (Merged from https://github.com/openssl/openssl/pull/18876)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise

[william mantly]

Same issue with a HP envy 15-ew0 Alder Lake-P and Realtek ALC245. I have
tried kernels 5.15, 5.19, 6 and 6.1 RC. I have tried Ubuntu 22.10,
22.04, Linux Mint 21, popOS and fedora 36. Speakers do not work on any
of them.

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

Title:
  [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal]
  No sound except loud crackling (popping) noise

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-
  LP audio controller. When playing any audio, the internal speaker
  plays no sound except periodic loud crackling noise. The 3.5mm jack
  does not work either, producing the same craclking noise alongside
  some eletrical noise. HDMI audio skimmishly tested, but also gave no
  sound. Curiously, USB headphone (along with microphone) works
  perfectly, also the internal microphone.

  As attempts to fix the problem, I have tried the following separately, with 
no avail:
  - Installing some Ubuntu OEM version of the 5.17 kernel
  - Updating to the v2.2 firmware from Sound Open Firmware Project 
(thesofproject on github), reverted afterwards

  I found exactly the same problem reported in the Fedora community:
  
https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086

  As the pre-installed Windows has been destroyed, no further test on
  Windows has been done.

  Since USB headphone and internal microphone work, I think that there
  is no problem on the Intel Tiger Lake-LP controller and its driver.
  The bug probably lies elsewhere, like in the handling of ALC245 on
  this new laptop model.

  Thank you very much for your time and effort in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Jul  7 10:59:22 2022
  InstallationDate: Installed on 2022-06-29 (7 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2022
  dmi.bios.release: 9.1
  dmi.bios.vendor: HP
  dmi.bios.version: T37 Ver. 01.09.01
  dmi.board.name: 8AB8
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 58.03.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 88.3
  dmi.modalias: 
dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G8 Notebook PC
  dmi.product.sku: 6A3P3AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239

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

[William Wilson]

This appears to be an issue with a missing `/etc/kernel/cmdline` file.
Did that file somehow get removed from your system?

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

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

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Oct 10 19:26:40 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992364/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken

[William Wilson]

** Tags added: foundations-triage-discuss

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

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fonts-dejavu package in Ubuntu:
  New

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

[William Wilson]

** Tags added: foundations-triage-discuss

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

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1978738] Re: systemd-oomd and zram-config services: "Swap is currently not detected; memory pressure usage will be degraded"

[William Wilson]

@Oibaf, this bug is fixed in the Ubuntu package in kinetic.

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

Title:
  systemd-oomd and zram-config services: "Swap is currently not
  detected; memory pressure usage will be degraded"

Status in systemd package in Ubuntu:
  Invalid
Status in zram-config package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  New
Status in zram-config source package in Jammy:
  New

Bug description:
  Problem summary:
  
  I've installed the zram-config package. By default it creates a zram swap 
device with half the physical memory size of the system. For instance, in an 
8GB RAM system:

  # swapon
  NAME   TYPE  SIZE USED PRIO
  /dev/zram0 partition 3,8G   1M5

  #zramctl
  NAME   ALGORITHM DISKSIZE  DATA COMPR TOTAL STREAMS MOUNTPOINT
  /dev/zram0 lzo-rle   3,8G  496K 74,9K  376K   4 [SWAP]

  The problem is that when systemd-oomd.service is started during boot
  it doesn't detect that zram swap device because zram-config.service is
  started later. So when systemd-oomd.service was started the zram
  device didn't exists yet. This is the message shown during boot:

  systemd-oomd[587]: Swap is currently not detected; memory pressure
  usage will be degraded

  If you restart systemd-oomd.service after boot it's correctly started
  because zram-config.service was previously loaded and zram device
  exists. So I think it's just a matter of dependencies during boot
  process; it's necessary to make zram-config.service be started before
  systemd-oomd.service (or to make systemd-oomd.service be restarted
  when zram-config.service is started).

  Aditional info:
  ---
  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  # apt-cache policy systemd-oomd
  systemd-oomd:
Instalados: 249.11-0ubuntu3.1
Candidato:  249.11-0ubuntu3.1
Tabla de versión:
   *** 249.11-0ubuntu3.1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   249.11-0ubuntu3 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

  # apt-cache policy zram-config
  zram-config:
Instalados: 0.7build1
Candidato:  0.7build1
Tabla de versión:
   *** 0.7build1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1978738/+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 1898207] Re: package logsave (not installed) failed to install/upgrade: no package named 'logsave' is installed, cannot configure

[William Wilson]

This "Operation not permitted" error looks suspicious. @rubiselprieto
can you check the permissions on your /etc/cron.d directory?

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

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

Title:
  package logsave (not installed) failed to install/upgrade: no package
  named 'logsave' is installed, cannot configure

Status in e2fsprogs package in Ubuntu:
  Incomplete

Bug description:
  updating crashes
  as suggested I did apt-get install -f
  now everything is working fine.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: logsave (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct  2 12:45:08 2020
  DpkgTerminalLog:
   dpkg: error processing package logsave (--configure):
no package named 'logsave' is installed, cannot configure
  ErrorMessage: no package named 'logsave' is installed, cannot configure
  InstallationDate: Installed on 2016-02-08 (1697 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: e2fsprogs
  Title: package logsave (not installed) failed to install/upgrade: no package 
named 'logsave' is installed, cannot configure
  UpgradeStatus: Upgraded to focal on 2020-10-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1898207/+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 1991553] Re: can't add a private PPA

[William Wilson]

** Tags added: foundations-triage-discuss

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

Title:
  can't add a private PPA

Status in software-properties package in Ubuntu:
  New

Bug description:
  As per today's discussion in ~is :

  add-apt-repository has a bug when adding a private PPA. Quoting
  ~cjwatson :

  ===
  It asks Launchpad for all your personal archive subscriptions _that have 
tokens_.  But `Person:+archivesubscriptions` also shows subscriptions without 
tokens - the token is generated when you click on Viewt here for the first time.

  Instead, `add-apt-repository` should call `getArchiveSubscriptionURL` (not 
`getArchiveSubscriptionURLs`) for the archive it's interested in.  That 
generates tokens on-demand.  Either it will get an HTTP 401, or it will get a 
URL which it can parse for the username and password.
  ===

  Thanks !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1991553/+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 1991525] Re: vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open shared object file”

[William Wilson]

I'm unable to recreate this issue on a jammy system that has been
upgraded from focal. Can you make sure all of your packages are up to
date? After poking through the vim source code there are no references
to libpng12, so it may be some dependency of vim that is out of date
trying to read it.

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

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

Title:
  vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open
  shared object file”

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  After upgrading a system running Ubuntu 20.04 to 22.04, vim.gtk3 no
  longer runs:

    $ vim.gtk3
    vim.gtk3: error while loading shared libraries: libpng12.so.0: cannot open 
shared object file: No such file or directory

  (vim.basic still runs fine).

  These are the vim packages we have installed, and their versions:

    vim:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-gtk3:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-gui-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-runtime:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-tiny:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate

  Previously I did have a PPA of Vim installed from
  http://ppa.launchpad.net/jonathonf/vim/ubuntu — but that has been
  purged, and as you can see all the vim packages now installed are
  official Ubuntu jammy versions.

  libpng12 isn't in Ubuntu any more, so I think the problem is that vim
  is trying to use it, not that it's missing.

  Attached is strace output of the failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1991525/+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 1990742] Re: screen not consistently locking when lid is closed

[William Wilson]

** Tags added: foundations-triage-discuss

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

Title:
  screen not consistently locking when lid is closed

Status in systemd package in Ubuntu:
  New

Bug description:
  I have GNOME configured to lock the screen when the screen is blanked,
  and to blank the screen when the lid is closed:

  org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
  org.gnome.desktop.screensaver lock-delay uint32 0
  org.gnome.desktop.screensaver lock-enabled true

  This worked fine in Jammy: whenever my screen was unlocked and I
  closed my laptop lid, it locked immediately, i.e., if I immediately
  reopened my lid, the screen was locked.

  After having just upgraded to Kinetic, however, sometimes when I close
  the lid it locks as described above, and sometimes it just... doesn't,
  i.e., when I open the lid again the screen is unlocked and I can just
  keep working.

  I have been unable to determine what the factors are which control
  whether the screen locks when I close the lid.

  There is a moderate security implication here, as it's problematic for
  someone's screen not to lock when they think that it did.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 17:57:37 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (1135 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990742/+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 1896540] Re: Incorrectly specified Touchpad size for Lenovo T490

[William Wilson]

@arutyun-akopov, can you try the workaround detailed in comment #1?

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

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

Title:
  Incorrectly specified Touchpad size for Lenovo T490

Status in libinput package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The vertical sensitivity of the touchpad on my laptop Lenovo T490
  seemed significantly higher than the horizontal sensitivity. After
  doing some research I found out that the touchpad size is incorrectly
  listed by the kernel.

  Touchpad size listed by the kernel: 77x107mm
  The real size of the touchpad: 68x100mm

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Systemd version: 245.4-4ubuntu3.2

  Output from the touchpad-edge-detector:

  miroslav@miroslav-ThinkPad-T490:~$ sudo touchpad-edge-detector 68x100 
/dev/input/event5
  Touchpad SynPS/2 Synaptics TouchPad on /dev/input/event5
  Move one finger around the touchpad to detect the actual edges
  Kernel says:  x [1266..5678], y [1162..4694]
  Touchpad sends:   x [1266..5678], y [1161..4694] -^C

  Touchpad size as listed by the kernel: 77x107mm
  User-specified touchpad size: 68x100mm
  Calculated ranges: 4412/3533

  Suggested udev rule:
  # 
  evdev:name:SynPS/2 Synaptics 
TouchPad:dmi:bvnLENOVO:bvrN2IET75W(1.53):bd08/21/2019:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:*
   EVDEV_ABS_00=1266:5678:65
   EVDEV_ABS_01=1161:4694:35
   EVDEV_ABS_35=1266:5678:65
   EVDEV_ABS_36=1161:4694:35

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1896540/+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 1833863] Re: Incorrect logic for

[William Wilson]

Marking as Won't Fix for pyxdg as it appears this bug has been solved
with fixes in other packages.

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

Title:
  Incorrect logic for 

Status in Garcon:
  Fix Released
Status in PyXDG:
  New
Status in garcon package in Ubuntu:
  Triaged
Status in pyxdg package in Ubuntu:
  Won't Fix
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released

Bug description:
  XFCE & Xubuntu use  in their menu files, which
  python-xdg currently (all current versions) does not handle correctly:

  https://gitlab.freedesktop.org/xdg/pyxdg/issues/12

  I think the fix is as simple as

  --- Menu.py.a   2019-06-23 17:44:24.992850139 +0100
  +++ Menu.py.b   2019-06-23 17:44:41.052807584 +0100
  @@ -997,7 +997,7 @@
   for menuentry in menu.MenuEntries:
   if menuentry not in tmp_e:
   menu.Entries.append(menuentry)
  -elif order[1] == "menus" or order[1] == "all":
  +if order[1] == "menus" or order[1] == "all":
   menu.Submenus.sort()
   for submenu in menu.Submenus:
   if submenu.Name not in tmp_s:

  But as it can also be trivially worked around by replacing  with , I
  wonder if this should be done in XFCE/Xubuntu?

To manage notifications about this bug go to:
https://bugs.launchpad.net/garcon/+bug/1833863/+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 1704416] Re: CAP_AUDIT_READ is not supported on Xenial

[William Wilson]

Marking this as won't fix because xenial is no longer supported. All
supported releases have libcap2 2.25 or newer, which fixes this bug.

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

Title:
  CAP_AUDIT_READ is not supported on Xenial

Status in libcap2 package in Ubuntu:
  Won't Fix

Bug description:
  I'm encountering the same issue as #1451601 describes. The fix, a more
  recent libcap2 2.25, has made it into the Yakkety distribution but not
  Xenial.

  Summary of the problem: One cannot raise or lower CAP_AUDIT_READ,
  which is equal to decimal value 37. As compiled, libcap2 2.24 supports
  up to CAP_BLOCK_SUSPEND (36).

  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy libcap2
  libcap2:
Installed: 1:2.24-12
Candidate: 1:2.24-12
Version table:
   *** 1:2.24-12 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  setcap cap_audit_read=eip /bin/ls
  fatal error: Invalid argument
  usage: setcap [-q] [-v] (-r|-|)  [ ... (-r|-|) 
 ]

   Note  must be a regular (non-symlink) file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1704416/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)

[William Wilson]

** Tags removed: foundations-triage-discuss

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0)

Status in apport package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  Triaged
Status in gtk+3.0 source package in Focal:
  Confirmed

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 1703377] Re: Gnome online account login prevents paste or autotype

[William J. Vallance]

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

Title:
  Gnome online account login prevents paste or autotype

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  On entering Login data to an online account such as google.

  Using keepass as password manager I now can not enter my password via
  paste nor via autotype. Trying any of them results in an invalid
  password.

  Ubuntu 16.10 - GNOME Shell 3.20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1703377/+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 1989381] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to install/upgrade: o subprocesso instalado, do pacote linux-firmware, o script post-installation retor

[William Wilson]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

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

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Tags added: no-boot-space

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

Title:
  package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to
  install/upgrade: o subprocesso instalado, do pacote linux-firmware, o
  script post-installation retornou erro do status de saída 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Eu ainda não tenho conhecimento profundo no linux, mas sempre que faço
  o comando apt upgrade, ao termino recebo a notificação de erro, ou
  falha

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  emymatos   1701 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Sep 12 18:30:36 2022
  Dependencies: firmware-sof-signed 2.0-1ubuntu3
  ErrorMessage: o subprocesso instalado, do pacote linux-firmware, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2022-09-11 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Sony Corporation VPCEH40EB
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=UUID=8325b648-2499-45d2-b7d7-417a59c2beb8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to 
install/upgrade: o subprocesso instalado, do pacote linux-firmware, o script 
post-installation retornou erro do status de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2012
  dmi.bios.release: 2.10
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0210Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 2.10
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0210Z9:bd06/21/2012:br2.10:efr2.10:svnSonyCorporation:pnVPCEH40EB:pvrC800BEL4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEH40EB
  dmi.product.sku: N/A
  dmi.product.version: C800BEL4
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1989381/+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 1988870] Re: apport-autoreport.service fails: whoopsie.path is not enabled

[William Wilson]

Can you check in the control panel under "Privacy" -> "Diagnostics"? If
"Send error reports to Canonical" is set to "Never" then the
whoopsie.path service will be disabled.

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

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

Title:
  apport-autoreport.service fails: whoopsie.path is not enabled

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  This is what the service reports. Aside from crash reports no longer
  uploading automatically, I'm having trouble pointing ubuntu-bug to
  crash reports in /var/crash - a window opens, but then a browser never
  opens. ubuntu-bug program-name does open the browser though.

  × apport-autoreport.service - Process error reports when automatic reporting 
is enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static)
   Active: failed (Result: exit-code) since Tue 2022-09-06 14:27:48 EDT; 
2min 33s ago
  TriggeredBy: ● apport-autoreport.path
   ● apport-autoreport.timer
  Process: 24994 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 
20 (code=exited, status=1/FAILURE)
 Main PID: 24994 (code=exited, status=1/FAILURE)
  CPU: 115ms

  Sep 06 14:27:48 mbp113 systemd[1]: Starting Process error reports when 
automatic reporting is enabled...
  Sep 06 14:27:48 mbp113 whoopsie-upload-all[24994]: ERROR: whoopsie.path is 
not enabled
  Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Main process 
exited, code=exited, status=1/FAILURE
  Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Failed with 
result 'exit-code'.
  Sep 06 14:27:48 mbp113 systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.23.0-0ubuntu1
  Uname: Linux 6.0.0-rc4 x86_64
  NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 20795) Tue Sep  6 14:26:35 2022: called for pid 3732, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 20795) Tue Sep  6 14:26:35 2022: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
   ERROR: apport (pid 20795) Tue Sep  6 14:26:36 2022: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 20795) Tue Sep  6 14:26:46 2022: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashReports:
   640:1000:123:43075180:2022-09-06 14:26:45.388720512 -0400:2022-09-06 
14:27:48.608538333 -0400:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:123:8681261:2022-08-29 22:32:29.231918756 -0400:2022-08-29 
20:57:41.939131333 -0400:/var/crash/_usr_libexec_goa-daemon.1000.crash
   640:1000:123:44557691:2022-08-30 08:01:54.998418753 -0400:2022-08-30 
08:01:50.202489325 -0400:/var/crash/_opt_google_chrome_chrome.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 14:29:03 2022
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1988870/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns

[William Bergmann Børresen]

To temporary mitigate the ImagePullBackOff I scaled up a new functional node 
(DNS wise) and used this command to reconcile the AKS cluster:
az resource update --resource-group  --name  
--namespace Microsoft.ContainerService  --resource-type ManagedClusters

This recovered CoreDNS in the kube-system namespace, which fixed the
ImagePullBackOff

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

Title:
  Update to systemd 237-3ubuntu10.54 broke dns

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Two servers today that updated systemd to "systemd 237-3ubuntu10.54" 
  https://ubuntu.com/security/notices/USN-5583-1

  could not resolve dns anymore.
  no dns servers, normally set through dhcp.

  Ubuntu 18.04

  Temp fix.
   1. Edit /etc/systemd/resolved.conf
   1. Add/Uncomment # FallbackDNS=168.63.129.16
   1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service
   1. Confirm dns working with systemd-resolve google.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation

[William Z Chadwick]

Huh, interesting. When I hover my cursor over the sound widgit in my top
panel bar, it says:

Output: 100%
0.00 dB
Built-in Audio Analog Stereo

And it says this even when I have something playing that ought to be
outputting sound.

Doesn't 0.00 db mean silence?

Reading this now to find out what I can:
https://sound.stackexchange.com/questions/25529/what-is-0-db-in-digital-
audio -- "So audio meters don't show the dBu, dBV or dBFS level of the
signal (some do, but as an extra). Instead they show 0dB as the standard
operating level of the system." Oddly fascinating read. I had no idea
that decibels were coined in relation to Bell labs.

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

Title:
  [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after
  fresh xubuntu 16.04 installation

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hardware sound device is available, according to:
  aplay -l
  sudo lspci

  
  https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  student1739 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 27 22:06:16 2016
  InstallationDate: Installed on 2016-04-24 (3 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  student1739 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575912/+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 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation

[William Z Chadwick]

Re:^^^ Oh, and I have the soundcard: Realtek ALC269VB Analog, also.

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

Title:
  [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after
  fresh xubuntu 16.04 installation

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hardware sound device is available, according to:
  aplay -l
  sudo lspci

  
  https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  student1739 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 27 22:06:16 2016
  InstallationDate: Installed on 2016-04-24 (3 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  student1739 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575912/+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 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation

[William Z Chadwick]

Hi,

This sounds similar to my bug.

I am pretty sure my physical speakers work, and even that they worked
when I first installed Ubuntu Mate 22.04, but very shortly afterwards
they stopped working.

The headphone jack also doesn't work. I installed a jack-detection repo
and now sometimes (not constantly) the headphones will shoot out max
volume white noise.

Here is my Alsa info: http://alsa-
project.org/db/?f=608937f066095ec6710e5f3bafc292815da99414

I've been trying to fix this problem for a couple weeks now. I've
followed different blogs on similar topics and read through various
solutions to similar problems posted on launchpad or stackoverflow.

Any help would be greatly appreciated.

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

Title:
  [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after
  fresh xubuntu 16.04 installation

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hardware sound device is available, according to:
  aplay -l
  sudo lspci

  
  https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  student1739 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 27 22:06:16 2016
  InstallationDate: Installed on 2016-04-24 (3 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  student1739 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575912/+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 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

[William Wilson]

** Changed in: powermgmt-base (Ubuntu)
   Importance: Undecided => High

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

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  Confirmed
Status in powermgmt-base source package in Kinetic:
  Confirmed

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+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 1976258] Re: icu ftbfs in the jammy release pocket

[William Wilson]

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

** Tags added: block-proposed-jammy

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

Title:
  icu ftbfs in the jammy release pocket

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  * icu is currently FTBFS in the jammy release pocket

  [Test Plan]
  * Build the package from -proposed against the jammy -proposed pocket
  * I have built it in a ppa: 
https://launchpad.net/~jawn-smith/+archive/ubuntu/ppa/+packages

  [Regression Potential]
  * The Canonical IDs for timezones change periodically. If a change
    made to them here is reverted in new uploads of tzdata, they
    will have to be updated again.
  * The change is in a build-time test only, and therefore will not
affect users.

  [Original Description]
  as seen in a test rebuild, this package fails to build in the jammy release 
pocket (note the log behind the link might go away):

  https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy-
  amd64.icu_70.1-2_BUILDING.txt.gz

  [...]
  make[4]: Leaving directory '/<>/source/test/cintltst'
  -
  | *** FAILING TEST SUMMARY FOR:  intltest
   TestCanonicalID
    TimeZoneTest
     format
  | *** END FAILING TEST SUMMARY FOR:  intltest
  ---
  ALL TESTS SUMMARY:
  ok:  testdata iotest cintltst
  = ERRS:  intltest
  make[3]: *** [Makefile:91: check-recursive] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1976258/+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 1976258] Re: icu ftbfs in the jammy release pocket

[William Wilson]

** Description changed:

- as seen in a test rebuild, this package fails to build in the jammy
- release pocket (note the log behind the link might go away):
+ [Impact]
+ * icu is currently FTBFS in the jammy release pocket
+ 
+ [Test Plan]
+ * Build the package from -proposed against the jammy -proposed pocket
+ * I have built it in a ppa: 
https://launchpad.net/~jawn-smith/+archive/ubuntu/ppa/+packages
+ 
+ [Regression Potential]
+ * The Canonical IDs for timezones change periodically. If a change
+   made to them here is reverted in new uploads of tzdata, they
+   will have to be updated again.
+ 
+ [Original Description]
+ as seen in a test rebuild, this package fails to build in the jammy release 
pocket (note the log behind the link might go away):
  
  https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy-
  amd64.icu_70.1-2_BUILDING.txt.gz
  
  [...]
  make[4]: Leaving directory '/<>/source/test/cintltst'
  -
- | *** FAILING TEST SUMMARY FOR:  intltest  
-  TestCanonicalID
-   TimeZoneTest
-format
+ | *** FAILING TEST SUMMARY FOR:  intltest
+  TestCanonicalID
+   TimeZoneTest
+    format
  | *** END FAILING TEST SUMMARY FOR:  intltest
  ---
  ALL TESTS SUMMARY:
  ok:  testdata iotest cintltst
  = ERRS:  intltest
  make[3]: *** [Makefile:91: check-recursive] Error 1

** Description changed:

  [Impact]
  * icu is currently FTBFS in the jammy release pocket
  
  [Test Plan]
  * Build the package from -proposed against the jammy -proposed pocket
  * I have built it in a ppa: 
https://launchpad.net/~jawn-smith/+archive/ubuntu/ppa/+packages
  
  [Regression Potential]
  * The Canonical IDs for timezones change periodically. If a change
-   made to them here is reverted in new uploads of tzdata, they
-   will have to be updated again.
+   made to them here is reverted in new uploads of tzdata, they
+   will have to be updated again.
+ * The change is in a build-time test only, and therefore will not
+   affect users.
  
  [Original Description]
  as seen in a test rebuild, this package fails to build in the jammy release 
pocket (note the log behind the link might go away):
  
  https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy-
  amd64.icu_70.1-2_BUILDING.txt.gz
  
  [...]
  make[4]: Leaving directory '/<>/source/test/cintltst'
  -
  | *** FAILING TEST SUMMARY FOR:  intltest
   TestCanonicalID
    TimeZoneTest
     format
  | *** END FAILING TEST SUMMARY FOR:  intltest
  ---
  ALL TESTS SUMMARY:
  ok:  testdata iotest cintltst
  = ERRS:  intltest
  make[3]: *** [Makefile:91: check-recursive] Error 1

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

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

Title:
  icu ftbfs in the jammy release pocket

Status in icu package in Ubuntu:
  New

Bug description:
  [Impact]
  * icu is currently FTBFS in the jammy release pocket

  [Test Plan]
  * Build the package from -proposed against the jammy -proposed pocket
  * I have built it in a ppa: 
https://launchpad.net/~jawn-smith/+archive/ubuntu/ppa/+packages

  [Regression Potential]
  * The Canonical IDs for timezones change periodically. If a change
    made to them here is reverted in new uploads of tzdata, they
    will have to be updated again.
  * The change is in a build-time test only, and therefore will not
affect users.

  [Original Description]
  as seen in a test rebuild, this package fails to build in the jammy release 
pocket (note the log behind the link might go away):

  https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy-
  amd64.icu_70.1-2_BUILDING.txt.gz

  [...]
  make[4]: Leaving directory '/<>/source/test/cintltst'
  -
  | *** FAILING TEST SUMMARY FOR:  intltest
   TestCanonicalID
    TimeZoneTest
     format
  | *** END FAILING TEST SUMMARY FOR:  intltest
  ---
  ALL TESTS SUMMARY:
  ok:  testdata iotest cintltst
  = ERRS:  intltest
  make[3]: *** [Makefile:91: check-recursive] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1976258/+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 1461530] Re: Translation make output hard to read

[William Andrea]

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

** This bug has been marked a duplicate of bug 1581433
   free output in german translation line up wrong colums

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

Title:
  Translation make output hard to read

Status in procps package in Ubuntu:
  New

Bug description:
  andreas@asterix:~/projects/uber/uber.data.processor/uber/data/processor$ free 
-m
   Gesamt Belegt Frei Gemeinsam Puffer Cache
  Speicher:  15965  14517   1447   1073204   5516
  -/+ Puffer/Cache:   8796   7168
  Auslagerungsdatei:   7982   3472   4510

  (bad to see with variable width fonts)

  Basically this is an issue with translations destroying the tabular
  output.

  This can be fixed in two ways, either fix all the translation strings,
  or make free truncate the output (even truncated labels should be
  useable for something like free, but then as a long time user I
  probably don't need labels, but without the column alignment the data
  is hard to read).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: procps 1:3.3.9-1ubuntu2.2
  ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9
  Uname: Linux 3.16.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  3 14:37:09 2015
  InstallationDate: Installed on 2015-05-15 (18 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: procps
  UpgradeStatus: No upgrade log present (user-confirmed fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1461530/+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 1581433] Re: free output in german translation line up wrong colums

[William Andrea]

Affects the French translation too.

** Attachment added: "free French sample.output"
   
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1581433/+attachment/5566379/+files/free%20French%20sample.output

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

Title:
  free output in german translation line up wrong colums

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Notice how the free column for swap shows 0 in the german translation.

  andreas@asterix:~$ free -m
gesamt   benutzt frei  gemns.  Puffer/Cache 
verfügbar
  Speicher:   159634934714411193884
9779
  Auslagerungsspeicher:7981   07981
  andreas@asterix:~$ LANG=C free -m
totalusedfree  shared  buff/cache   
available
  Mem:  159634935714211193886
9778
  Swap:  7981   07981
  andreas@asterix:~$ free 
gesamt   benutzt frei  gemns.  Puffer/Cache 
verfügbar
  Speicher:16346836 5051476 7317744 1144548 3977616
10017704
  Auslagerungsspeicher: 8173408   0 8173408
  andreas@asterix:~$ LANG=C free 
totalusedfree  shared  buff/cache   
available
  Mem:   16346836 5052300 7316848 1144292 3977688
10017188
  Swap:   8173408   0 8173408

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 13 10:14:05 2016
  InstallationDate: Installed on 2016-04-22 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: procps
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1581433/+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 1961805] Re: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main)

[William Wilson]

Excellent work. Just one comment, it's best practice to add the "please
merge" bug number in the changelog. That way this bug will be
automatically closed when the package is uploaded. I'll go ahead and add
that in before I sponsor it.

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

Title:
  Please merge procps 2:3.3.17-6 (main) from Debian unstable (main)

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

  Dropped changes:
  - debian/README.sysctl: Debian has added this information.
  - debian/procps.install: debian/protect-links.conf has been re-named to 
debian/99-protect-links.conf, so it can be safely installed again (see LP: 
#1938585 for background).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+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 1960460] Re: Fails to import ZFS rpool during boot

[William Wilson]

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

** This bug has been marked a duplicate of bug 1960083
   dirname applet missing from initramfs

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

Title:
  Fails to import ZFS rpool during boot

Status in systemd package in Ubuntu:
  New

Bug description:
  Fresh install using 20220202 Daily ISO with ZFS + Encryption selected
  from the installer

  The system ends up in busybox after entering the unlock key.

  Here is a part of the logs captured from the screen, the complete log
  can be found as an attachement:

  find: /dev/zvol/: No such file or directory 
  /init: line 971: dirname: not found
  BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu2) multi-call binary.

  Usage: basename FILE [SUFFIX]
  Strip directory path and SUFFIX from FILE 
  Please unlock disk keystore-:_

  Key load error: Failed to open key material file: No such file or
  directory

  Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: 
filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied 
  filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied 
  mount: mounting rpool/ROOT/ubuntu_u169ph on /root// failed: Permission denied 
Error: 1

  Failed to mount rpool/ROOT/ubuntu ui69ph on /root//.
  Manually mount the filesystem and exit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960460/+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 1960458] [NEW] patch git_socket_dir.patch causing FTBFS in gspell

[William Wilson]

Public bug reported:

With this patch applied gspell is FTBFS with the following errors:

Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus:
Failed to connect to socket debian/home/.cache/at-spi/bus: No such file
or directory

I removed the patch and rebuilt this package in a PPA. When built
against this PPA, gpsell is able to build again.

** Affects: at-spi2-core (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  patch git_socket_dir.patch causing FTBFS in gspell

Status in at-spi2-core package in Ubuntu:
  New

Bug description:
  With this patch applied gspell is FTBFS with the following errors:

  Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus:
  Failed to connect to socket debian/home/.cache/at-spi/bus: No such
  file or directory

  I removed the patch and rebuilt this package in a PPA. When built
  against this PPA, gpsell is able to build again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+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 1957126] [NEW] lscpu not showing number of sockets on arm64

[William Wilson]

Public bug reported:

When running `lscpu` on arm64, the number of sockets is not populated.
This is seen on both Raspberry Pi hardware and in the autopkgtest
environment. Example output:

Architecture:aarch64
  CPU op-mode(s):32-bit, 64-bit
  Byte Order:Little Endian
CPU(s):  4
  On-line CPU(s) list:   0-3
Vendor ID:   ARM
  Model name:Cortex-A72
Model:   3
Thread(s) per core:  1
Core(s) per cluster: 4
Socket(s):   -
Cluster(s):  1
Stepping:r0p3
CPU max MHz: 1500.
CPU min MHz: 600.
BogoMIPS:108.00
Flags:   fp asimd evtstrm crc32 cpuid
Vulnerabilities:
  Itlb multihit: Not affected
  L1tf:  Not affected
  Mds:   Not affected
  Meltdown:  Not affected
  Spec store bypass: Vulnerable
  Spectre v1:Mitigation; __user pointer sanitization
  Spectre v2:Vulnerable
  Srbds: Not affected
  Tsx async abort:   Not affected

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  lscpu not showing number of sockets on arm64

Status in util-linux package in Ubuntu:
  New

Bug description:
  When running `lscpu` on arm64, the number of sockets is not populated.
  This is seen on both Raspberry Pi hardware and in the autopkgtest
  environment. Example output:

  Architecture:aarch64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
  CPU(s):  4
On-line CPU(s) list:   0-3
  Vendor ID:   ARM
Model name:Cortex-A72
  Model:   3
  Thread(s) per core:  1
  Core(s) per cluster: 4
  Socket(s):   -
  Cluster(s):  1
  Stepping:r0p3
  CPU max MHz: 1500.
  CPU min MHz: 600.
  BogoMIPS:108.00
  Flags:   fp asimd evtstrm crc32 cpuid
  Vulnerabilities:
Itlb multihit: Not affected
L1tf:  Not affected
Mds:   Not affected
Meltdown:  Not affected
Spec store bypass: Vulnerable
Spectre v1:Mitigation; __user pointer sanitization
Spectre v2:Vulnerable
Srbds: Not affected
Tsx async abort:   Not affected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1957126/+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 1650688] Re: timedatectl set-timezone fails on UC16

[William Wilson]

** Tags added: rls-jj-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/1650688

Title:
  timedatectl set-timezone fails on UC16

Status in Snappy:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  SRU
  ===

  [Impact]

   * The bug prevents timedated from recognizing and correctly set the
  system's timezone when running Ubuntu Core 16, 18 and 20.

   * This causes by timedated fails to take Ubuntu Core's /etc/writable
  redirection into account.

   * The recognizing part is fixed by making the code take writable
  redirection into account.

   * The set part is fixed by making the code link to the absolute path
  instead of a relative one.

   * Currently core snaps worked around the set part by providing a
  wrapper script which re-create /etc/writable/localtime afterward.
  However this does not cover DBus users.

  [Test Plan]

   * On classics systems: ensure the proposed systemd package is installed.
     On Ubuntu Core systems: build a new core snap including proposed package, 
and install it. Replaces timedatectl with timedatectl.real to test skipping the 
wrapper.

  (Note that one can simulate core snap's /etc/writable redirection by
  running this image creation hook [1] on the system.)

  [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
  core/hooks/08-etc-writable.chroot?h=ubuntu/focal

   * On freshly boot system: query the timezone using `timedatectl`. The
  timezone should corresponds to `readlink -f /etc/localtime` and does
  not show `n/a`.

   * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`.
  `readlink -f /etc/localtime` should points to an existing file.

   * Run `sudo systemctl restart systemd-timedated.service`. Then, query
  the timezone again: `timedatectl`. It should show the previously set
  timezone and not `n/a`.

   * Run `sudo systemctl status systemd-timedated.service`. This should
  show no sign of timedated crashing.

  [Where problems could occur]

   * It's possible that the redirection handling code will be sub-par
  and causes crash. However, it's not likely because the similar pieces
  of code is in the previous patch since Ubuntu 16.04.

   * If it does: the patched `get_timezone()` function is used in 2
  places: the networkd's DHCP server [3] and the timedated itself.

     - Networkd is used primarily on servers where NetworkManage is
  absent. It's possible that this patch causes the user to loss access
  to the server due to networkd crash when setting up network
  interfaces, and requires physical access to fix. However, the code
  path is executed when DHCP is enabled only. I think it's not common
  for users to have networkd's DHCP server enabled: the feature seems to
  gear towards desktop users wanting to share internet connection, and
  in those cases they're more likely to use NetworkManager.

     - The timedated itself is likely used by the programs that involves
  in time-related functions. If a crash occur, in the worst case users
  won't be able to set time or timezone via timedated. However, users
  should still be able to e.g. set time using `date` or set timezone
  using /etc/localtime (assuming online guides still consider systems
  without systemd). Timedated is DBus-activated, and thus a crash should
  be self-healing.

   * The set part would also affects the clasic systems. However, I
  believe nothing else actually rely on /etc/localtime being a relative
  path, otherwise the /etc/writable redirection would causes even more
  problem, and would have been reported.

  [3] Yes, I'm surprised that there's a DHCP server inside systemd
  codebase.

  [Other Info]

   * This is also useful for UBports's Ubuntu Touch. We continue using
  system-image system where the rootfs is read-only, and thus is
  affected by this bug similarly to Ubuntu Core. I've tested the Focal
  version of the package on our (currently in development) Focal Ubuntu
  Touch image, and the fix works.

  

  [Original bug description]

  On a system running UC16, the file /etc/localtime is a link that
  points to /etc/writable/localtime.

  On a freshly installed system, /etc/writable/localtime is a fully-
  qualified link that points at /usr/share/zoneinfo/UTC.

  If timedatectl is used to set the timezone to something else,
  timedated updates the localtime symbolic link with a relative path to
  the zoneinfo directory, which results in an invalid link.

  $ sudo timedatectl set-timezone America/Detroit

  $ sudo timedatectl
    Local time: Fri 2016-12-16 18:18:49 EST
    Universal time: Fri 2016-12-16 23:18:49 UTC
  RTC time: Fri 2016-12-16 23:18:49
     Time zone: America/Detroit (EST, -0500)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  $ ls -l /etc/writable/localtime
  /etc/writable/localtime --> 

[Touch-packages] [Bug 1951161] Re: Please merge shadow 1:4.8.1-2 (main) from Debian unstable

[William Wilson]

** Patch added: "Diff from Debian"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+attachment/5541800/+files/debian_ubuntu.debdiff

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

Title:
  Please merge shadow 1:4.8.1-2 (main) from Debian unstable

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  This merge is necessary because there are changes present in Ubuntu
  that are not present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+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 1951161] Re: Please merge shadow 1:4.8.1-2 (main) from Debian unstable

[William Wilson]

** Patch added: "Diff from 1:4.8.1-1ubuntu9"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+attachment/5541799/+files/ubuntu_ubuntu.debdiff

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

Title:
  Please merge shadow 1:4.8.1-2 (main) from Debian unstable

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  This merge is necessary because there are changes present in Ubuntu
  that are not present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+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 1951161] Re: Please merge shadow 1:4.8.1-2 (main) from Debian unstable

[William Wilson]

Thanks for catching that alexmurray. I'll upload new debdiffs in a
moment.

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

Title:
  Please merge shadow 1:4.8.1-2 (main) from Debian unstable

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  This merge is necessary because there are changes present in Ubuntu
  that are not present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+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 1951161] Re: Please merge shadow 1:4.8.1-2 (main) from Debian unstable

[William Wilson]

** Patch added: "Diff from Debian"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+attachment/5541538/+files/debian_ubuntu.debdiff

** Changed in: shadow (Ubuntu)
 Assignee: William Wilson (jawn-smith) => (unassigned)

** Changed in: shadow (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  Please merge shadow 1:4.8.1-2 (main) from Debian unstable

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  This merge is necessary because there are changes present in Ubuntu
  that are not present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+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 1951161] Re: Please merge shadow 1:4.8.1-2 (main) from Debian unstable

[William Wilson]

** Patch added: "Diff from Debian"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+attachment/5541536/+files/debian_ubuntu.debdiff

** Changed in: shadow (Ubuntu)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

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

Title:
  Please merge shadow 1:4.8.1-2 (main) from Debian unstable

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  This merge is necessary because there are changes present in Ubuntu
  that are not present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+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 1951161] Re: Please merge shadow 1:4.8.1-2 (main) from Debian unstable

[William Wilson]

** Patch added: "Diff from 1:4.8.1-1ubuntu9"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+attachment/5541537/+files/ubuntu_ubuntu.debdiff

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

Title:
  Please merge shadow 1:4.8.1-2 (main) from Debian unstable

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  This merge is necessary because there are changes present in Ubuntu
  that are not present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+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 1951161] Re: Please merge shadow 1:4.8.1-2 (main) from Debian unstable

[William Wilson]

** Patch added: "Diff from 1:4.8.1-1ubuntu9"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+attachment/5541535/+files/ubuntu_ubuntu.debdiff

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

Title:
  Please merge shadow 1:4.8.1-2 (main) from Debian unstable

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  This merge is necessary because there are changes present in Ubuntu
  that are not present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+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 1951161] [NEW] Please merge shadow 1:4.8.1-2 (main) from Debian unstable

[William Wilson]

Public bug reported:

This merge is necessary because there are changes present in Ubuntu that
are not present in Debian.

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

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

Title:
  Please merge shadow 1:4.8.1-2 (main) from Debian unstable

Status in shadow package in Ubuntu:
  New

Bug description:
  This merge is necessary because there are changes present in Ubuntu
  that are not present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+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 1944621] Re: sshd in chroot has regression with glibc 2.34

[William Wilson]

This patch moves the configuration option to the appropriate section of
d/rules and adds a reference to this bug report.

** Patch added: "lp1944621.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+attachment/5528491/+files/lp1944621.debdiff

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

Title:
  sshd in chroot has regression with glibc 2.34

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  A regression to sshd running in a chroot exists under the following
  conditions:

  1) sshd was built with glibc 2.34
  2) sshd is running with a kernel that does not define the close_range syscall 
(kernel <= 5.8)
  3) /proc/self/fd does not exist in the chroot

  The glibc 2.34 implementation of fallback_closefrom fails if
  /proc/self/fd is not present, which is a valid sshd use case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+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 1944621] Re: sshd in chroot has regression with glibc 2.34

[William Wilson]

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

** Changed in: openssh (Ubuntu)
 Assignee: William Wilson (jawn-smith) => (unassigned)

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

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

Title:
  sshd in chroot has regression with glibc 2.34

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  A regression to sshd running in a chroot exists under the following
  conditions:

  1) sshd was built with glibc 2.34
  2) sshd is running with a kernel that does not define the close_range syscall 
(kernel <= 5.8)
  3) /proc/self/fd does not exist in the chroot

  The glibc 2.34 implementation of fallback_closefrom fails if
  /proc/self/fd is not present, which is a valid sshd use case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+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 1944621] Re: sshd in chroot has regression with glibc 2.34

[William Wilson]

** Patch added: "Configure without closefrom"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+attachment/5527126/+files/lp1944621.debdiff

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

Title:
  sshd in chroot has regression with glibc 2.34

Status in openssh package in Ubuntu:
  New

Bug description:
  A regression to sshd running in a chroot exists under the following
  conditions:

  1) sshd was built with glibc 2.34
  2) sshd is running with a kernel that does not define the close_range syscall 
(kernel <= 5.8)
  3) /proc/self/fd does not exist in the chroot

  The glibc 2.34 implementation of fallback_closefrom fails if
  /proc/self/fd is not present, which is a valid sshd use case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+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 1944621] Re: sshd in chroot has regression with glibc 2.34

[William Wilson]

I created upstream bugs to track this:

https://bugzilla.mindrot.org/show_bug.cgi?id=3349
https://sourceware.org/bugzilla/show_bug.cgi?id=28377

** Bug watch added: OpenSSH Portable Bugzilla #3349
   https://bugzilla.mindrot.org/show_bug.cgi?id=3349

** Bug watch added: Sourceware.org Bugzilla #28377
   https://sourceware.org/bugzilla/show_bug.cgi?id=28377

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

Title:
  sshd in chroot has regression with glibc 2.34

Status in openssh package in Ubuntu:
  New

Bug description:
  A regression to sshd running in a chroot exists under the following
  conditions:

  1) sshd was built with glibc 2.34
  2) sshd is running with a kernel that does not define the close_range syscall 
(kernel <= 5.8)
  3) /proc/self/fd does not exist in the chroot

  The glibc 2.34 implementation of fallback_closefrom fails if
  /proc/self/fd is not present, which is a valid sshd use case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+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 1944621] [NEW] sshd in chroot has regression with glibc 2.34

[William Wilson]

Public bug reported:

A regression to sshd running in a chroot exists under the following
conditions:

1) sshd was built with glibc 2.34
2) sshd is running with a kernel that does not define the close_range syscall 
(kernel <= 5.8)
3) /proc/self/fd does not exist in the chroot

The glibc 2.34 implementation of fallback_closefrom fails if
/proc/self/fd is not present, which is a valid sshd use case.

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Assignee: William Wilson (jawn-smith)
 Status: New

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

Title:
  sshd in chroot has regression with glibc 2.34

Status in openssh package in Ubuntu:
  New

Bug description:
  A regression to sshd running in a chroot exists under the following
  conditions:

  1) sshd was built with glibc 2.34
  2) sshd is running with a kernel that does not define the close_range syscall 
(kernel <= 5.8)
  3) /proc/self/fd does not exist in the chroot

  The glibc 2.34 implementation of fallback_closefrom fails if
  /proc/self/fd is not present, which is a valid sshd use case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable

[William Wilson]

Actually, a feature of openssh is being able to use a chroot that
doesn't look like a root filesystem, so we'll have to consider how to
move forward on this.

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

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable

[William Wilson]

Mounting /proc in the chroot fixed the test. I'll prepare a patch and an
upstream bug report.

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

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable

[William Wilson]

So this is fun, the upstream openssh actually has the same test failure
when running `make tests`. So it doesn't appear to be something we
introduced here, but it is definitely a problem that needs solving.

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

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable

[William Wilson]

Bryceh: I've been looking into this a bit. Removing the --oknodo had no
effect on the tests, and neither did removing the diff that we carry
from Debian. I've also noticed that the issue only occurs on kernel <=
5.8. The tests all pass when run in a test environment with kernel 5.11
or 5.13, which is how I missed this in my initial testing.

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

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1939751] Re: openssh FTBFS with glibc >= 2.34

[William Wilson]

paelzer: I worked the merge under
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799

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

Title:
  openssh FTBFS with glibc >= 2.34

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

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1939751/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable

[William Wilson]

** Patch added: "Diff from 1:8.4p1-5ubuntu2"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+attachment/5521261/+files/lp1941799-ubuntu-ubuntu.debdiff

** Changed in: openssh (Ubuntu)
 Assignee: William Wilson (jawn-smith) => (unassigned)

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

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

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable

[William Wilson]

This diff from Debian still includes the seccomp fixes pulled in for
glibc 2.33, as they are still relevant with glibc 2.34. These are in
upstream openssh version 8.5, so when Debian gets to 8.5 we can sync and
drop the diff.

** Patch added: "Diff from Debian"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+attachment/5521260/+files/lp1941799-debian-ubuntu.debdiff

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

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1941799] [NEW] Please merge openssh 1:8.4p1-6 from Debian unstable

[William Wilson]

Public bug reported:

This merge is needed because there are changes in Ubuntu that are not
present in Debian.

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Assignee: William Wilson (jawn-smith)
 Status: In Progress

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

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

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+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 1939751] Re: openssh FTBFS with glibc >= 2.34

[William Wilson]

@paelzer I would be happy to work on the merge if you would like.

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

Title:
  openssh FTBFS with glibc >= 2.34

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

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1939751/+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 1939751] Re: openssh FTBFS with glibc >= 2.34

[William Wilson]

** Patch added: "lp1939751.debdiff"
   
https://bugs.launchpad.net/debian/+source/openssh/+bug/1939751/+attachment/5517643/+files/lp1939751.debdiff

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

** Changed in: openssh (Ubuntu)
     Assignee: William Wilson (jawn-smith) => (unassigned)

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

Title:
  openssh FTBFS with glibc >= 2.34

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

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1939751/+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 1939751] Re: openssh FTBFS with glibc >= 2.34

[William Wilson]

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

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

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

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

Title:
  openssh FTBFS with glibc >= 2.34

Status in openssh package in Ubuntu:
  In Progress
Status in openssh package in Debian:
  Unknown

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1939751/+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 1939751] [NEW] openssh FTBFS with glibc >= 2.34

[William Wilson]

Public bug reported:

Due to an incompatible function prototype in openbsd-compat tests, this
package FTBFS with glibc >= 2.34. There is an upstream patch already in
place to address this.

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

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

Title:
  openssh FTBFS with glibc >= 2.34

Status in openssh package in Ubuntu:
  New

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1939751/+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 1939728] Re: Please merge icu 67.1-7 (main) from Debian unstable

[William Wilson]

** Patch added: "Diff from 67.1-6ubuntu2"
   
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1939728/+attachment/5517575/+files/lp1939728_ubuntu_ubuntu.debdiff

** Changed in: icu (Ubuntu)
 Assignee: William Wilson (jawn-smith) => (unassigned)

** Changed in: icu (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  Please merge icu 67.1-7 (main) from Debian unstable

Status in icu package in Ubuntu:
  Confirmed

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1939728/+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 1939728] Re: Please merge icu 67.1-7 (main) from Debian unstable

[William Wilson]

** Patch added: "Diff from 67.1-6ubuntu2"
   
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1939728/+attachment/5517573/+files/lp1939728_ubuntu_ubuntu.debdiff

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

Title:
  Please merge icu 67.1-7 (main) from Debian unstable

Status in icu package in Ubuntu:
  Confirmed

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1939728/+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 1939728] Re: Please merge icu 67.1-7 (main) from Debian unstable

[William Wilson]

** Patch added: "Diff from Debian"
   
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1939728/+attachment/5517574/+files/lp1939728_debian_ubuntu.debdiff

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

Title:
  Please merge icu 67.1-7 (main) from Debian unstable

Status in icu package in Ubuntu:
  Confirmed

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1939728/+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 1939728] Re: Please merge icu 67.1-7 (main) from Debian unstable

[William Wilson]

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

** Changed in: icu (Ubuntu)
 Assignee: (unassigned) => William Wilson (jawn-smith)

** Patch added: "Diff from Debian"
   
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1939728/+attachment/5517572/+files/lp1939728_debian_ubuntu.debdiff

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

Title:
  Please merge icu 67.1-7 (main) from Debian unstable

Status in icu package in Ubuntu:
  Confirmed

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1939728/+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 1939728] [NEW] Please merge icu 67.1-7 (main) from Debian unstable

[William Wilson]

Public bug reported:

This requires a merge because there are changes in the Ubuntu version
not present in the Debian version.

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

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

Title:
  Please merge icu 67.1-7 (main) from Debian unstable

Status in icu package in Ubuntu:
  New

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1939728/+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 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

[William Wilson]

This was fixed previously in hirsute by an upstream merge that resulted
in bluez 5.56-0ubuntu1

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

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

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

Title:
  Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Groovy:
  Won't Fix
Status in bluez source package in Hirsute:
  Fix Released

Bug description:
  Bluetooth stops working after updating to bluez version
  5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization
  timed out". Bluetooth is working again if bluez is reverted to version
  5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt.

  Release:  20.10
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14
  Uname: Linux 5.8.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: arm64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 16:09:03 2020
  ImageMediaBuild: 20200423.1
  InterestingModules: bnep bluetooth
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 
25EE
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 
smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 console=tty1 
root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: bluez
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago)
  acpidump:
   
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

The verification passed for focal.

jawn-smith@focal-vm:~$ apt-cache policy passwd
passwd:
  Installed: 1:4.8.1-1ubuntu5.20.04
  Candidate: 1:4.8.1-1ubuntu5.20.04.1
  Version table:
 1:4.8.1-1ubuntu5.20.04.1 500
500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
 *** 1:4.8.1-1ubuntu5.20.04 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:4.8.1-1ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
jawn-smith@focal-vm:~$ sudo useradd 123
jawn-smith@focal-vm:~$ grep "^123" /etc/passwd
123:x:1001:1001::/home/123:/bin/sh
jawn-smith@focal-vm:~$ sudo userdel 123
jawn-smith@focal-vm:~$ sudo apt install passwd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-5.8.0-43-generic linux-headers-5.8.0-50-generic 
linux-hwe-5.8-headers-5.8.0-43 linux-hwe-5.8-headers-5.8.0-50
  linux-image-5.8.0-43-generic linux-image-5.8.0-50-generic 
linux-modules-5.8.0-43-generic linux-modules-5.8.0-50-generic
  linux-modules-extra-5.8.0-43-generic linux-modules-extra-5.8.0-50-generic
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  passwd
1 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
Need to get 799 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 passwd 
amd64 1:4.8.1-1ubuntu5.20.04.1 [799 kB]
Fetched 799 kB in 0s (2,027 kB/s)
(Reading database ... 275608 files and directories currently installed.)
Preparing to unpack .../passwd_1%3a4.8.1-1ubuntu5.20.04.1_amd64.deb ...
Unpacking passwd (1:4.8.1-1ubuntu5.20.04.1) over (1:4.8.1-1ubuntu5.20.04) ...
Setting up passwd (1:4.8.1-1ubuntu5.20.04.1) ...
Processing triggers for man-db (2.9.1-1) ...
jawn-smith@focal-vm:~$ sudo useradd 123
useradd: invalid user name '123'
jawn-smith@focal-vm:~$ grep "^123" /etc/passwd
jawn-smith@focal-vm:~$


** 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 shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1927078

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Focal:
  Fix Committed
Status in shadow source package in Groovy:
  Won't Fix
Status in shadow source package in Hirsute:
  Fix Committed
Status in shadow source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * If a fully numeric username is created, it will cause
     problems with systemd. One example is that the user with
     this type of name can log in, but loginctl will not create
     a session for them.
   * This can also cause users to be unable to log in to a gdm
     environment

  [Test Case]

   * `useradd 123` (this command should succeed)
   * `userdel 123` to clean up the user that was just added
   * Install `shadow` from -proposed
   * `useradd 123` should now fail

  [Regression Potential]
   * If there were a logic error in the fix, it is possible
     that valid usernames would now be disallowed.
   * Many test cases have been added to ensure this is not
     the case, and --badnames would still provide a work-around
   * [racb] Users may have scripts that are currently using numeric usernames 
and these scripts will break as a consequence of this deliberate change in 
stable Ubuntu releases. However, based on the discussion in the bug, we think 
this is preferable to leaving such users with unstable behaviour such as 
systemd's behaviour described.

  [Original Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): 

[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

The verification passed for hirsute.

jawn-smith@lvm:~$ apt-cache policy passwd
passwd:
  Installed: 1:4.8.1-1ubuntu8
  Candidate: 1:4.8.1-1ubuntu8.1
  Version table:
 1:4.8.1-1ubuntu8.1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 
Packages
 *** 1:4.8.1-1ubuntu8 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
jawn-smith@lvm:~$ sudo useradd 123
jawn-smith@lvm:~$ grep "^123" /etc/passwd
123:x:1001:1001::/home/123:/bin/sh
jawn-smith@lvm:~$ sudo userdel 123
jawn-smith@lvm:~$ sudo apt install passwd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  passwd
1 upgraded, 0 newly installed, 0 to remove and 45 not upgraded.
Need to get 793 kB of archives.
After this operation, 298 kB disk space will be freed.
Get:1 http://us.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 passwd 
amd64 1:4.8.1-1ubuntu8.1 [793 kB]
Fetched 793 kB in 0s (1,711 kB/s)
(Reading database ... 188906 files and directories currently installed.)
Preparing to unpack .../passwd_1%3a4.8.1-1ubuntu8.1_amd64.deb ...
Unpacking passwd (1:4.8.1-1ubuntu8.1) over (1:4.8.1-1ubuntu8) ...
Setting up passwd (1:4.8.1-1ubuntu8.1) ...
Processing triggers for man-db (2.9.4-2) ...
jawn-smith@lvm:~$ useradd 123
useradd: invalid user name '123'
jawn-smith@lvm:~$ grep "^123" /etc/passwd
jawn-smith@lvm:~$

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

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Focal:
  Fix Committed
Status in shadow source package in Groovy:
  Won't Fix
Status in shadow source package in Hirsute:
  Fix Committed
Status in shadow source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * If a fully numeric username is created, it will cause
     problems with systemd. One example is that the user with
     this type of name can log in, but loginctl will not create
     a session for them.
   * This can also cause users to be unable to log in to a gdm
     environment

  [Test Case]

   * `useradd 123` (this command should succeed)
   * `userdel 123` to clean up the user that was just added
   * Install `shadow` from -proposed
   * `useradd 123` should now fail

  [Regression Potential]
   * If there were a logic error in the fix, it is possible
     that valid usernames would now be disallowed.
   * Many test cases have been added to ensure this is not
     the case, and --badnames would still provide a work-around
   * [racb] Users may have scripts that are currently using numeric usernames 
and these scripts will break as a consequence of this deliberate change in 
stable Ubuntu releases. However, based on the discussion in the bug, we think 
this is preferable to leaving such users with unstable behaviour such as 
systemd's behaviour described.

  [Original Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  2. With that same username, every successful authentication in gdm
  will loop back to gdm again instead of starting gnome, making the user
  unable to login.

  Making useradd fail (unless --badnames is set) when a fully numeric
  name is used will make the default OS behavior consistent.

  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:

[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

The attached patch fixes the issue in focal

** Patch added: "Focal SRU"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5510997/+files/lp197078_focal.debdiff

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

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

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Focal:
  Fix Committed
Status in shadow source package in Groovy:
  Won't Fix
Status in shadow source package in Hirsute:
  Fix Committed
Status in shadow source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * If a fully numeric username is created, it will cause
 problems with systemd. One example is that the user with
 this type of name can log in, but loginctl will not create
 a session for them.
   * This can also cause users to be unable to log in to a gdm
 environment

  [Test Case]

   * `useradd 123` (this command should succeed)
   * `userdel 123` to clean up the user that was just added
   * Install `shadow` from -proposed
   * `useradd 123` should now fail

  [Regression Potential]
   * If there were a logic error in the fix, it is possible
 that valid usernames would now be disallowed.
   * Many test cases have been added to ensure this is not
 the case, and --badnames would still provide a work-around

  [Original Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  2. With that same username, every successful authentication in gdm
  will loop back to gdm again instead of starting gnome, making the user
  unable to login.

  Making useradd fail (unless --badnames is set) when a fully numeric
  name is used will make the default OS behavior consistent.

  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

The attached patch fixes the issue for hirsute.

** Patch added: "Hirsute Patch"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5510996/+files/lp1927078_hirsute.debdiff

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Focal:
  Fix Committed
Status in shadow source package in Groovy:
  Won't Fix
Status in shadow source package in Hirsute:
  Fix Committed
Status in shadow source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * If a fully numeric username is created, it will cause
 problems with systemd. One example is that the user with
 this type of name can log in, but loginctl will not create
 a session for them.
   * This can also cause users to be unable to log in to a gdm
 environment

  [Test Case]

   * `useradd 123` (this command should succeed)
   * `userdel 123` to clean up the user that was just added
   * Install `shadow` from -proposed
   * `useradd 123` should now fail

  [Regression Potential]
   * If there were a logic error in the fix, it is possible
 that valid usernames would now be disallowed.
   * Many test cases have been added to ensure this is not
 the case, and --badnames would still provide a work-around

  [Original Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  2. With that same username, every successful authentication in gdm
  will loop back to gdm again instead of starting gnome, making the user
  unable to login.

  Making useradd fail (unless --badnames is set) when a fully numeric
  name is used will make the default OS behavior consistent.

  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

** Changed in: shadow (Ubuntu Hirsute)
 Assignee: (unassigned) => William Wilson (jawn-smith)

** Changed in: shadow (Ubuntu Focal)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

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

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Focal:
  In Progress
Status in shadow source package in Groovy:
  Won't Fix
Status in shadow source package in Hirsute:
  In Progress
Status in shadow source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * If a fully numeric username is created, it will cause
 problems with systemd. One example is that the user with
 this type of name can log in, but loginctl will not create
 a session for them.
   * This can also cause users to be unable to log in to a gdm
 environment

  [Test Case]

   * `useradd 123` (this command should succeed)
   * `userdel 123` to clean up the user that was just added
   * Install `shadow` from -proposed
   * `useradd 123` should now fail

  [Regression Potential]
   * If there were a logic error in the fix, it is possible
 that valid usernames would now be disallowed.
   * Many test cases have been added to ensure this is not
 the case, and --badnames would still provide a work-around

  [Original Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  2. With that same username, every successful authentication in gdm
  will loop back to gdm again instead of starting gnome, making the user
  unable to login.

  Making useradd fail (unless --badnames is set) when a fully numeric
  name is used will make the default OS behavior consistent.

  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

** Description changed:

- [Description]
+ [Impact]
+ 
+  * If a fully numeric username is created, it will cause
+problems with systemd. One example is that the user with
+this type of name can log in, but loginctl will not create
+a session for them.
+  * This can also cause users to be unable to log in to a gdm
+environment
+ 
+ [Test Case]
+ 
+  * `useradd 123` (this command should succeed)
+  * `userdel 123` to clean up the user that was just added
+  * Install `shadow` from -proposed
+  * `useradd 123` should now fail
+ 
+ [Regression Potential]
+  * If there were a logic error in the fix, it is possible
+that valid usernames would now be disallowed.
+  * Many test cases have been added to ensure this is not
+the case, and --badnames would still provide a work-around
+ 
+ [Original Description]
  
  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:
  
  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:
  
  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)
  
  ..
  
  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)
  
  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
-  16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
+  16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
- 0pts/0192.168.122.116:170.00s  0.00s  0.00s w  
+ 0pts/0192.168.122.116:170.00s  0.00s  0.00s w
  
  And pam-systemd shows the following message:
  
  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument
  
+ 2. With that same username, every successful authentication in gdm will
+ loop back to gdm again instead of starting gnome, making the user unable
+ to login.
  
- 2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.
- 
- 
- Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.
- 
+ Making useradd fail (unless --badnames is set) when a fully numeric name
+ is used will make the default OS behavior consistent.
  
  [Other info]
  
  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * If a fully numeric username is created, it will cause
 problems with systemd. One example is that the user with
 this type of name can log in, but loginctl will not create
 a session for them.
   * This can also cause users to be unable to log in to a gdm
 environment

  [Test Case]

   * `useradd 123` (this command should succeed)
   * `userdel 123` to clean up the user that was just added
   * Install `shadow` from -proposed
   * `useradd 123` should now fail

  [Regression Potential]
   * If there were a logic error in the fix, it is possible
 that valid usernames would now be disallowed.
   * Many test cases have been added to ensure this is not
 the case, and --badnames would still provide a work-around

  [Original Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 

[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

Per our discussion I just removed floating point checks altogether.
"0.123" is now considered valid because it is impossible to have a
floating point uid or gid so there will be no confusion with floating
point numbers. I have added those floating point numbers to the
"validUsernames" test, and added a few more cases that are almost
numeric, like "0xdeadbeefjawn-smith" to make sure they are seen as
valid.

** Patch added: "Removed float checks"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5510618/+files/lp1927078_removed_float_checks.debdiff

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

This one adds in a check for octal representation and some test cases
for octal representation.

** Patch added: "Octal included this time"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5510554/+files/lp1927078_fully_numeric_and_hex_and_octal.debdiff

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

This change disallows floating point and hexadecimal representations of
numbers as well as purely numeric, which should be a good compromise.
For example, 0x0 is now invalid, as well as 0x123456789 and 0.0, while
0x0x0x0x is considered valid. It also adds these new restrictions to the
man page.

** Patch added: "invalid hexadecimal and floating point"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5510089/+files/lp1927078_fully_numeric_and_hex.debdiff

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

This patch only disallows usernames that are strictly numeric per
vorlon's comment above. It also adds more test cases for invalid
usernames such as "0123456789" and valid usernames such as "0root" and
"0.o". This time I also remembered that '0' is a digit.

** Patch added: "Fully numeric and more tests patch"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5509701/+files/lp1927078_fully_numeric.debdiff

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

I'd be happy to make that change and add the test cases, but I'm still
not sure which patch we landed on. I'm rather indifferent so I will
leave the discussion to others before adding those test cases to
whichever method we decide.

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

Attached is a patch that disallows fully numeric usernames while still
allowing usernames such as 91jawn-smith.

** Patch added: "Disallow Fully Numeric Patch"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5505363/+files/lp1927078_fully_numeric.debdiff

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

@Seth that very incorrect comment is actually part of block of upstream
code that is commented out. It doesn't apply to the more relaxed Debian
username scheme.

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

This fix for impish uses sbeattie's suggestion of simply disallowing a
numeric character at the beginning of the username. It also includes a
test case.

** Patch added: "lp1927078.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5505076/+files/lp1927078.debdiff

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

** Changed in: shadow (Ubuntu Impish)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly

[William Wilson]

The attached patch cleans up the switch statement to not replicate the
xwarn.

** Patch added: "lp1903351_cleanup.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+attachment/5501733/+files/lp1903351_cleanup.debdiff

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

Title:
  ignore_eacces and ignore_erofs patches don't work properly

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Focal:
  In Progress
Status in procps source package in Groovy:
  In Progress
Status in procps source package in Hirsute:
  In Progress

Bug description:
  The patches used to ignore errors in containers no longer work as of
  3.3.16 due to upstream commit https://gitlab.com/procps-
  ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932

  The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not 
WriteSetting
  Both patches ignore the change that rc is no longer propagated up and instead 
everything is trapped by:

  if (!ignore_failure && errno != ENOENT)
  rc = -1;

  
  Versions affected: focal+

  
  root@bfee89058713:/tmp# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.10 (Groovy Gorilla)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.10"
  VERSION_ID="20.10"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=groovy
  UBUNTU_CODENAME=groovy

  
  root@bfee89058713:/# dpkg -l procps
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version   Architecture Description
  
+++-==-=--=
  ii  procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities

  
  root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf
  root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $?
  sysctl: setting key "kernel.shmmax": Read-only file system
  255
  root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf
  root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $?
  sysctl: setting key "kernel.shmmax": Read-only file system
  0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1928966] Re: Please merge procps 2:3.3.17-5 (main) from Debian unstable

[William Wilson]

This diff from the previous Ubuntu version of the package is very large.
That is mostly due to the new language packs and autoconf files present
in the new Debian version of the package.

This diff also addresses bug 1903351 by correcting the patches we carry
for ignore_erofs and ignore_eaccess

** Patch added: "Diff from 3.3.16-5ubuntu3"
   
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+attachment/5500330/+files/procps-ubuntu-ubuntu.debdiff

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

Title:
  Please merge procps 2:3.3.17-5 (main) from Debian unstable

Status in procps package in Ubuntu:
  New

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

  
  Justification of new diff:
- There is a new diff, which is an autopkgtest for the stack limit issue 
  that was seen in bug 1874824. This test has been submitted to 
  Debian so the patch can be dropped if they accept it.

  Justification of dropped patches
- missing_potfiles_in: Debian has now added this code in POTFILES.in
  so the patch is no longer needed
- pmap_test: This patch disables some tests that are not causing
  any problems. These tests are run in Debian so should be run
  in Ubuntu as well
- top_config_file_bwcompat: Debian has applied this code upstream so
  the patch is no longer needed
- tar-version: Debian has applied this code upstream so the patch is
  no longer needed
- stack_limit: Debian has applied this code upstream so the patch is
  no longer needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+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 1928966] Re: Please merge procps 2:3.3.17-5 (main) from Debian unstable

[William Wilson]

This diff from the previous Ubuntu version of the package is very large.
That is mostly due to the new language packs and autoconf files present
in the new Debian version of the package.

This diff also addresses bug 1903351 by correcting the patches we carry
for ignore_erofs and ignore_eaccess

** Patch added: "Diff from 3.3.16-5ubuntu3"
   
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+attachment/5500331/+files/procps-ubuntu-ubuntu.debdiff

** Description changed:

  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.
+ 
+ 
+ Justification of new diff:
+   - There is a new diff, which is an autopkgtest for the stack limit issue 
+ that was seen in bug 1874824. This test has been submitted to 
+ Debian so the patch can be dropped if they accept it.
+ 
+ Justification of dropped patches
+   - missing_potfiles_in: Debian has now added this code in POTFILES.in
+ so the patch is no longer needed
+   - pmap_test: This patch disables some tests that are not causing
+ any problems. These tests are run in Debian so should be run
+ in Ubuntu as well
+   - top_config_file_bwcompat: Debian has applied this code upstream so
+ the patch is no longer needed
+   - tar-version: Debian has applied this code upstream so the patch is
+ no longer needed
+   - stack_limit: Debian has applied this code upstream so the patch is
+ no longer needed

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

Title:
  Please merge procps 2:3.3.17-5 (main) from Debian unstable

Status in procps package in Ubuntu:
  New

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

  
  Justification of new diff:
- There is a new diff, which is an autopkgtest for the stack limit issue 
  that was seen in bug 1874824. This test has been submitted to 
  Debian so the patch can be dropped if they accept it.

  Justification of dropped patches
- missing_potfiles_in: Debian has now added this code in POTFILES.in
  so the patch is no longer needed
- pmap_test: This patch disables some tests that are not causing
  any problems. These tests are run in Debian so should be run
  in Ubuntu as well
- top_config_file_bwcompat: Debian has applied this code upstream so
  the patch is no longer needed
- tar-version: Debian has applied this code upstream so the patch is
  no longer needed
- stack_limit: Debian has applied this code upstream so the patch is
  no longer needed

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