[Touch-packages] [Bug 1935617] [NEW] systemd autopkgtest broken on ppc64el with qemu 6.0

[Christian Ehrhardt ]

Public bug reported:

I'm not sure yet if this is flaky or a real issue, but I'm filing it to
avoid multiple people analyzing the same.

The Qemu 6.0 upload 
https://launchpad.net/ubuntu/+source/qemu/1:6.0+dfsg-1~ubuntu2 triggers a test 
failure like
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20210708_223311_e3bbb@/log.gz

I have tested the new qemu on ppc64 and it worked fine for device emulation and 
migration cases.
But this is suspicious.
Of the last tests exactly and only those with the new qemu failed.


impish
  ppc64el
tests-in-lxd   (F  5% f  0% S  0% B  0% => P 95%/) 
F.F.
systemd-fsckd  (F  0% f  0% S 100% B  0% => P  0%/) 

upstream-1 (F 15% f  0% S  0% B  0% => P 85%/) 
F..F
upstream-2 (F 12% f  0% S  0% B  0% => P 87%/) 
F...


For an insight in flakyness/reproducibility I've retriggered the missing qemu 
and the non-qemu cases a few times. If those reproduce all-bad vs all-good 
again this would further indicate a real issue.

Unfortunately the ppc maas seems down right now and canonistack also
isn't too nice this week - overall that inhibits the testing a bit :-/

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

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


** Tags: update-excuse

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

** Tags added: update-excuse

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

Title:
  systemd autopkgtest broken on ppc64el with qemu 6.0

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

Bug description:
  I'm not sure yet if this is flaky or a real issue, but I'm filing it
  to avoid multiple people analyzing the same.

  The Qemu 6.0 upload 
https://launchpad.net/ubuntu/+source/qemu/1:6.0+dfsg-1~ubuntu2 triggers a test 
failure like
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20210708_223311_e3bbb@/log.gz

  I have tested the new qemu on ppc64 and it worked fine for device emulation 
and migration cases.
  But this is suspicious.
  Of the last tests exactly and only those with the new qemu failed.

  
  impish
ppc64el
  tests-in-lxd   (F  5% f  0% S  0% B  0% => P 95%/) 
F.F.
  systemd-fsckd  (F  0% f  0% S 100% B  0% => P  0%/) 

  upstream-1 (F 15% f  0% S  0% B  0% => P 85%/) 
F..F
  upstream-2 (F 12% f  0% S  0% B  0% => P 87%/) 
F...

  
  For an insight in flakyness/reproducibility I've retriggered the missing qemu 
and the non-qemu cases a few times. If those reproduce all-bad vs all-good 
again this would further indicate a real issue.

  Unfortunately the ppc maas seems down right now and canonistack also
  isn't too nice this week - overall that inhibits the testing a bit :-/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1935617/+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 1935570] Re: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem

[Hui Wang]

Please plug the mic in, and run pa-info > pa-info.txt, then upload the
pa-info.txt

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

Title:
  [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

  the mic does not work in my Ubuntu OS. Can you guys do something i am
  very frustrated?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ravisah96   1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 19:57:18 2021
  InstallationDate: Installed on 2021-06-08 (30 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Front
  Symptom_Type: None of the above
  Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2012
  dmi.bios.release: 2.83
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.83
  dmi.board.asset.tag: MXL312111Y
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL312111Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.product.sku: C6Z93UT#ABA
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935570/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Jerry Lee]

As the ModemManager is only considered, mbim-proxy is started by the
ModemManager service:

"Jul 09 08:20:21 ubuntu-ThinkEdge-SE30 ModemManager[578]: spawning new
mbim-proxy (try 1)..."


And, the execution path is decided at 
https://github.com/linux-mobile-broadband/libmbim/blob/master/src/libmbim-glib/mbim-device.c#L1421:

   argc[0] = g_strdup (LIBEXEC_PATH "/mbim-proxy");

This looks like that the mbim-proxy is only used by the ModemManager
service.

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in modemmanager source package in Focal:
  Fix Committed
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.

  3. Check if the modem can be enabled

    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  = Certification Validation =

  Additionally to the aforementioned test cases, the Certification Team
  will perform some coverage testing across supported devices to make
  sure the other modems still work as expected.

  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  [Other Info]

  We need to upgrade to these 3 packages

Re: [Touch-packages] [Bug 1935570] Re: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem

[Rabi Sah]

Hi,

When I plug the headphones in it detects microphone as input but I don't
get the microphone working and then I don't get output sound.

On Thu, Jul 8, 2021, 9:50 PM Hui Wang <1935...@bugs.launchpad.net>
wrote:

> After you plug a mic to the mic jack, does the system detect this
> plugging?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1935570
>
> Title:
>   [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording
>   problem
>
> Status in alsa-driver package in Ubuntu:
>   New
>
> Bug description:
>   Hi,
>
>   the mic does not work in my Ubuntu OS. Can you guys do something i am
>   very frustrated?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
>   Uname: Linux 5.8.0-59-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.18
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  ravisah96   1576 F pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Jul  8 19:57:18 2021
>   InstallationDate: Installed on 2021-06-08 (30 days ago)
>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   PackageArchitecture: all
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
>   Symptom_Card: Built-in Audio - HDA Intel PCH
>   Symptom_Jack: Black Mic, Front
>   Symptom_Type: None of the above
>   Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front]
> Recording problem
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/29/2012
>   dmi.bios.release: 2.83
>   dmi.bios.vendor: Hewlett-Packard
>   dmi.bios.version: K01 v02.83
>   dmi.board.asset.tag: MXL312111Y
>   dmi.board.name: 339A
>   dmi.board.vendor: Hewlett-Packard
>   dmi.chassis.asset.tag: MXL312111Y
>   dmi.chassis.type: 6
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.modalias:
> dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
>   dmi.product.family: 103C_53307F G=D
>   dmi.product.name: HP Compaq Pro 6300 MT
>   dmi.product.sku: C6Z93UT#ABA
>   dmi.sys.vendor: Hewlett-Packard
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935570/+subscriptions
>

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

Title:
  [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

  the mic does not work in my Ubuntu OS. Can you guys do something i am
  very frustrated?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ravisah96   1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 19:57:18 2021
  InstallationDate: Installed on 2021-06-08 (30 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Front
  Symptom_Type: None of the above
  Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2012
  dmi.bios.release: 2.83
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.83
  dmi.board.asset.tag: MXL312111Y
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL312111Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.product.sku: C6Z93UT#ABA
  dmi.sys.vendor: Hewlett-Packard

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

-- 
M

[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot

[Bin Li]

Checked the proposed channel, the 3.8 was not ready yet, will check it
later.

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  Prompt error message "Failed to unmount /oldroot" when shutdown or
  reboot

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  root fs is not cleanly unmounted on shutdown

  [test case]

  create a file in /etc/binfmt.d/TestFormat.conf with the following
  content:

  :TestFormat:M::XX::/bin/true:F

  reboot the system, and then shutdown or reboot again, and watch the
  serial console for the error message:

  sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy

  [regression potential]

  any regression would likely cause problems on shutdown and/or reboot,
  or may cause problems with unmounted root fs on shutdown/reboot

  [scope]

  this is needed only for f

  this is fixed upstream with PR 15566 which is included in v246, so
  this is fixed already in g and later

  this isn't reproducable on b

  [original description]

  On ubuntu 20.04, with latest kernel and systemd, it will show error on
  ThinkPad X1.

  sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy

  systemd 245.4-4ubuntu3.6
  kernel: 5.8.0-53

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1928200/+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 1935570] Re: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem

[Hui Wang]

After you plug a mic to the mic jack, does the system detect this
plugging?

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

Title:
  [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

  the mic does not work in my Ubuntu OS. Can you guys do something i am
  very frustrated?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ravisah96   1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 19:57:18 2021
  InstallationDate: Installed on 2021-06-08 (30 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Front
  Symptom_Type: None of the above
  Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2012
  dmi.bios.release: 2.83
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.83
  dmi.board.asset.tag: MXL312111Y
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL312111Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.product.sku: C6Z93UT#ABA
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935570/+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 1935570] [NEW] [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem

[Rabi Sah]

Public bug reported:

Hi,

the mic does not work in my Ubuntu OS. Can you guys do something i am
very frustrated?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ravisah96   1576 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  8 19:57:18 2021
InstallationDate: Installed on 2021-06-08 (30 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Mic, Front
Symptom_Type: None of the above
Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2012
dmi.bios.release: 2.83
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.83
dmi.board.asset.tag: MXL312111Y
dmi.board.name: 339A
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: MXL312111Y
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Pro 6300 MT
dmi.product.sku: C6Z93UT#ABA
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug focal

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

Title:
  [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

  the mic does not work in my Ubuntu OS. Can you guys do something i am
  very frustrated?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ravisah96   1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 19:57:18 2021
  InstallationDate: Installed on 2021-06-08 (30 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Front
  Symptom_Type: None of the above
  Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2012
  dmi.bios.release: 2.83
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.83
  dmi.board.asset.tag: MXL312111Y
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL312111Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.product.sku: C6Z93UT#ABA
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935570/+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 1935568] Re: after having a bug reported, locked screen, and coming back, ubuntu-bug -w leaves a gksudo dialog for dmesg open

[Henning Sprang]

see screenshot - it looks like this after:

* reporting a bug with ubuntu-bug
* locking screen
* logging back in


The dialog does not react on clicks or keyboard input, all input apperas to be 
going to the underlying app, firefox here.

** Attachment added: "Screenshot from 2021-07-09 01-43-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1935568/+attachment/5509993/+files/Screenshot%20from%202021-07-09%2001-43-22.png

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

Title:
  after having a bug reported, locked screen, and coming back, ubuntu-
  bug -w leaves a gksudo dialog for dmesg open

Status in apport package in Ubuntu:
  New

Bug description:
  I reported two bugs today, and both times, after having finished
  reporting the bug, locking my screen, and logging back in, suddenly
  there was a dialog asking for my sudo password so it can execute
  dmesg.

  But I could neither hit cancel nor could I enter my password, it
  apperaded that anything I did, especially clicks, made the window
  *below* the dialog react.

  First time I solved it by rebooting (because I had some packages to
  upgrade anyway), second time by killing gnome-shell and letting it
  restart.

  This dialog definitely did not appear in the process of reporting the
  bug, the first time it appeared on screen was minutes after completing
  the bugreports in launchpad, plus locking and unlocking the screen
  afterwards.

  Might also be a problem with gnome-shell or gksudo(?), but it only
  ever happened to me when using ubuntu-bug -w.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50.7
  ProcVersionSignature: Ubuntu 5.8.0-59.66-lowlatency 5.8.18
  Uname: Linux 5.8.0-59-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   644:1000:124:0:2021-07-08 04:45:57.713189974 +0200:2021-07-08 
04:45:57.713189974 +0200:/var/crash/_usr_bin_jackd.1000.upload
   600:118:124:37:2021-07-08 04:46:00.914606508 +0200:2021-07-08 
04:46:00.906605467 +0200:/var/crash/_usr_bin_jackd.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  9 01:44:39 2021
  InstallationDate: Installed on 2020-04-12 (452 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to groovy on 2020-11-03 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1935568/+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 1935568] [NEW] after having a bug reported, locked screen, and coming back, ubuntu-bug -w leaves a gksudo dialog for dmesg open

[Henning Sprang]

Public bug reported:

I reported two bugs today, and both times, after having finished
reporting the bug, locking my screen, and logging back in, suddenly
there was a dialog asking for my sudo password so it can execute dmesg.

But I could neither hit cancel nor could I enter my password, it
apperaded that anything I did, especially clicks, made the window
*below* the dialog react.

First time I solved it by rebooting (because I had some packages to
upgrade anyway), second time by killing gnome-shell and letting it
restart.

This dialog definitely did not appear in the process of reporting the
bug, the first time it appeared on screen was minutes after completing
the bugreports in launchpad, plus locking and unlocking the screen
afterwards.

Might also be a problem with gnome-shell or gksudo(?), but it only ever
happened to me when using ubuntu-bug -w.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu50.7
ProcVersionSignature: Ubuntu 5.8.0-59.66-lowlatency 5.8.18
Uname: Linux 5.8.0-59-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
 644:1000:124:0:2021-07-08 04:45:57.713189974 +0200:2021-07-08 
04:45:57.713189974 +0200:/var/crash/_usr_bin_jackd.1000.upload
 600:118:124:37:2021-07-08 04:46:00.914606508 +0200:2021-07-08 
04:46:00.906605467 +0200:/var/crash/_usr_bin_jackd.1000.uploaded
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul  9 01:44:39 2021
InstallationDate: Installed on 2020-04-12 (452 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to groovy on 2020-11-03 (247 days ago)

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


** Tags: amd64 apport-bug groovy

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

Title:
  after having a bug reported, locked screen, and coming back, ubuntu-
  bug -w leaves a gksudo dialog for dmesg open

Status in apport package in Ubuntu:
  New

Bug description:
  I reported two bugs today, and both times, after having finished
  reporting the bug, locking my screen, and logging back in, suddenly
  there was a dialog asking for my sudo password so it can execute
  dmesg.

  But I could neither hit cancel nor could I enter my password, it
  apperaded that anything I did, especially clicks, made the window
  *below* the dialog react.

  First time I solved it by rebooting (because I had some packages to
  upgrade anyway), second time by killing gnome-shell and letting it
  restart.

  This dialog definitely did not appear in the process of reporting the
  bug, the first time it appeared on screen was minutes after completing
  the bugreports in launchpad, plus locking and unlocking the screen
  afterwards.

  Might also be a problem with gnome-shell or gksudo(?), but it only
  ever happened to me when using ubuntu-bug -w.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50.7
  ProcVersionSignature: Ubuntu 5.8.0-59.66-lowlatency 5.8.18
  Uname: Linux 5.8.0-59-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   644:1000:124:0:2021-07-08 04:45:57.713189974 +0200:2021-07-08 
04:45:57.713189974 +0200:/var/crash/_usr_bin_jackd.1000.upload
   600:118:124:37:2021-07-08 04:46:00.914606508 +0200:2021-07-08 
04:46:00.906605467 +0200:/var/crash/_usr_bin_jackd.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  9 01:44:39 2021
  InstallationDate: Installed on 2020-04-12 (452 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to groovy on 2020-11-03 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1935568/+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 1932352] Re: Fix micmute hotkeys on HP Elite Dragonfly

[Brian Murray]

Hello jeremyszu, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.8 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

Title:
  Fix micmute hotkeys on HP Elite Dragonfly

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Mic mute key is no function on HP Elite Dragonfly.

  [Fix]
  After confirming with HP, there are two model names for Dragonfly:
  * HP Elite Dragonfly G2 Notebook PC
  * HP Elite Dragonfly Max Notebook PC
  Thus, the commit 
  Commit c1b8c966eccb7be1cae0a30670f5e1fcd88b47fa maps the 81 scan code to mic 
mute key.

  [Test]
  After patching it, the mic mute key could functioned well on my Dragonfly 
laptop.

  [Where problems could occur]
  There is not old rule for Dragonfly dmi string in current hwdb.
  Which means the Dragonfly is using default HP key map:
  ```
  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:*

   KEYBOARD_KEY_81=fn_esc
  ```
  This patch will change the HP machine (if product name contains 
pnHPEliteDragonfly*) to map 81 to mic mute key.
  If a machine (pnHPEliteDragonfly*) works good in the past then this patch may 
cause it's mic mute key become malfunction.
  However, this rule is confirmed/provided from HP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932352/+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 1931578] Re: ActivationPolicy=down causes delay at boot

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.8 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

Title:
  ActivationPolicy=down causes delay at boot

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

Bug description:
  [impact]

  The ActivationPolicy= parameter was backported in bug 1664844, but
  when this is set to down (or always-down or manual) without also
  specifying RequiredForOnline=no, then there is a hang at boot waiting
  for the network to finish coming online.

  [test case]

  With the latest systemd, which includes support for ActivationPolicy=,
  configure an interface with ActivationPolicy=down and reboot. The boot
  will be delayed waiting for that interface.

  [regression potential]

  any regression would likely cause the system to encounter delay at
  boot, or to boot before configured interface(s) are fully online at
  boot, or to fail to correctly/fully configure interface(s).

  [scope]

  this is needed for all releases

  this is proposed upstream in:
  https://github.com/systemd/systemd/pull/19883

  [other info]

  this is only needed for convenience, as any configuration using
  ActivationPolicy=down can also easily add RequiredForOnline=no

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

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

[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

[Brian Murray]

Hello Kai-Heng, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.8 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

Title:
  Fix micmute hotkeys on HP ProBooks

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+subscriptions

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

[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot

[Brian Murray]

Hello Bin, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.8 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  Prompt error message "Failed to unmount /oldroot" when shutdown or
  reboot

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  root fs is not cleanly unmounted on shutdown

  [test case]

  create a file in /etc/binfmt.d/TestFormat.conf with the following
  content:

  :TestFormat:M::XX::/bin/true:F

  reboot the system, and then shutdown or reboot again, and watch the
  serial console for the error message:

  sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy

  [regression potential]

  any regression would likely cause problems on shutdown and/or reboot,
  or may cause problems with unmounted root fs on shutdown/reboot

  [scope]

  this is needed only for f

  this is fixed upstream with PR 15566 which is included in v246, so
  this is fixed already in g and later

  this isn't reproducable on b

  [original description]

  On ubuntu 20.04, with latest kernel and systemd, it will show error on
  ThinkPad X1.

  sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy

  systemd 245.4-4ubuntu3.6
  kernel: 5.8.0-53

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1928200/+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 1933402] Re: net card set VF and altname display blurred character

[Brian Murray]

Hello Fred, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.8 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

Title:
  net card set VF  and altname display blurred  character

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-20.04-hwe series:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  When running with the HWE kernel (5.4 didn't support altnames), altnames 
containing garbage (uninitialized memory) may get assigned to a NIC. This is 
100% reproducible on arm64. The upstream commit message suggests that this has 
been seen to cause segfaults.

  [Test Case]
  1) echo 1 > /sys/class/net/enp189s0f0/device/sriov_numvfs
  2) ip a
  3)
  10: eno1v0:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
  link/ether 1e:d8:e1:e9:ae:25 brd ff:ff:ff:ff:ff:ff
  altname @▒ު▒
  altname enp125s0f0v0
  11: enp189s0f0v0:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
  link/ether 76:ea:f4:65:dd:33 brd ff:ff:ff:ff:ff:ff
  altname ▒b▒ު▒
  altname ▒▒

  [Fix]
  There's a one liner upstream fix that simply initializes a variable:
  
https://github.com/systemd/systemd/commit/61fd7d6720c562c88ab79062ff8d131e5e3c7b1b

  [What Could Go Wrong]
  The fix itself is innocuous - just initializing a variable to NULL. So the 
real risk here would seem to be limited to the common risks in updating a core 
package in the Ubuntu distribution.

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

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

[Touch-packages] [Bug 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received

[Brian Murray]

Hello Simon, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.8 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

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

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed

Bug description:
  [impact]

  networking changes, like RA events, can cause systemd-resolved to re-
  write the resolv.conf file, even if the contents didn't change,
  resulting in unnecessary increased amount of inotify events

  [test case]

  see original description for ipv6ra-related reproducer, or simple
  reproducer here:

  configure networkd with some config for (e.g.) eth0, but not a config
  that would result in /etc/resolv.conf changing when the interface goes
  up/down - for example, use static config with no DNS search domains.
  Then bring eth0 up/down while observing the md5sum (file content) does
  not change but the mtime does change.

  root@lp1891215-h:~# ip l set down dev eth0
  root@lp1891215-h:~# md5sum /etc/resolv.conf
  db23e80078515192c312e5f321ff0340  /etc/resolv.conf
  root@lp1891215-h:~# stat -t -L /etc/resolv.conf
  /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238218 1625238216 
1625238216 0 4096
  root@lp1891215-h:~# ip l set up dev eth0
  root@lp1891215-h:~# md5sum /etc/resolv.conf
  db23e80078515192c312e5f321ff0340  /etc/resolv.conf
  root@lp1891215-h:~# stat -t -L /etc/resolv.conf
  /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238227 1625238226 
1625238226 0 4096

  [regression potential]

  regressions would result in incorrect or missing data in the
  resolv.conf file, possibly resulting in dns failures or errors

  [scope]

  this is needed for h and eralier

  this is (potentially) fixed upstream by
  f3e1f00d03445911ee73729219cea88c8a70c612 which in first included in
  v248, so this is needed in hirsute and earlier

  [original description]

  # Issue description:

  On 2 Linode VMs that are used as lxd hosts, we noticed that
  /run/systemd/resolve/*resolv.conf were re-created quite frequently (~
  once per second). We noticed because of the log noise from lxd's
  dnsmasq instance using inotify to watch the target of /etc/resolv.conf
  (which points to the stub-resolv.conf in our case). This was (wrongly)
  reported as a lxd bug (https://github.com/lxc/lxd/issues/7765) until
  it became apparent it was more likely to be a problem with
  systemd(-resolved)?.

  The log noise is the observable problem that would be nice to see
  addressed:

    root@lxd02:~# uptime
     17:55:48 up  9:52,  1 user,  load average: 0.18, 0.11, 0.05
    root@lxd02:~# journalctl -b0 | grep -cF dnsmasq
    158609

  Upon further investigation, it seems that systemd-resolved re-creates
  the resolv.conf and stub-resolv.conf files whenever an IPv6 RA is
  received.

  1) One can observe that by setting systemd-resolved's service in debug
  mode:

  $ sudo systemctl edit systemd-resolved

  and in the editor that is opened, add and save this content:

  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  then restart systemd-resolved and watch the logs scroll by with:

  $ journalctl -fu systemd-resolved

  3) In another terminal, watch the files be recreated with:

  watch -d -n 0.1 stat /run/systemd/resolve/stub-resolv.conf

  3) In yet an

[Touch-packages] [Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

[Brian Murray]

Hello Mason, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.8 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  with systemd-resolved disabled, dhclient doesn't correctly notify
  resolvconf about dns server(s)

  [test case]

  install resolvconf and ifupdown and disable systemd-resolved and
  systemd-networkd, use ifupdown to get a dhcp address where the lease
  includes a dns nameserver, verify resolvconf is using that dhcp-
  provided nameserver

  [regression potential]

  failure to correctly notify systemd-resolved about new dhclient-
  provided nameserver(s)

  [scope]

  this is needed for f and earlier

  in g and later the hook script is moved to the isc-dhcp package, and
  edited to correctly check is-enabled systemd-resolved instead of only
  checking for the existence of the binary

  [original description]

  The functionality exists to allow users to revert to the traditional ifupdown
  package for network configuration. Alongside this, systemd's often-buggy
  resolver can be disabled. However, there's a logic error in the systemd-
  supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system
  from populating /etc/resolv.conf properly when systemd-resolved is disabled.
  The issue is here:

  if [ -x /lib/systemd/systemd-resolved ] ; then

  Instead of checking to see if the systemd-resolved service is enabled or
  active, which would be the correct behaviour, this checks for the existence of
  a binary, assuming that if it exists it's supposed to be used.

  I've not tested this in the absence of resolvconf, but if systemd-resolved
  isn't enabled, it's difficult to imagine this code wanting to run. I've tested
  this with resolvconf and ifupdown driving dhclient, and it corrects the
  behaviour that was broken with the introduction of systemd-resolved.

  I'm attaching a patch, and am also including it here for easy access:

  *** resolved.broken 2019-11-19 15:01:28.785588838 +
  --- resolved2019-11-19 15:08:06.519430073 +
  ***
  *** 14,20 
    #   (D) = master script downs interface
    #   (-) = master script does nothing with this

  ! if [ -x /lib/systemd/systemd-resolved ] ; then
    # For safety, first undefine the nasty default make_resolv_conf()
    make_resolv_conf() { : ; }
    case "$reason" in
  --- 14,21 
    #   (D) = master script downs interface
    #   (-) = master script does nothing with this

  ! systemctl is-active systemd-resolved > /dev/null 2>&1
  ! if [ $? -eq 0 ]; then
    # For safety, first undefine the nasty default make_resolv_conf()
    make_resolv_conf() { : ; }
    case "$reason" in

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+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 1858210] Re: timedatectl doesn't list all timezones

[Brian Murray]

Hello mlx, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.8 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

Title:
  timedatectl doesn't list all timezones

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

Bug description:
  [impact]

  timedatectl list-timezones doesn't show many common timezones that are
  actually considered 'aliases', such as Europe/Bratislava or
  US/Eastern.

  [test case]

  $ timedatectl list-timezones | grep Eastern
  $

  [regression potential]

  any regression would likely result in an incorrect list of timezones
  shown from list-timezones, or failure to correctly set a timezone

  [scope]

  this is needed in f and later

  this is fixed upstream with PR 20066 which was just merged, so this is
  needed in all releases in ubuntu

  in bionic, the 'tzdata.zi' file that the new code uses isn't present,
  so this won't work on bionic, thus marking it wontfix

  [original description]

  Is there some filter determining which timezones are displayed by
  `timedatectl list-timezones`? My zone, Europe/Bratislava, is missing.
  Even stranger, it can successfully be set by timedatectl.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  Date: Fri Jan  3 15:36:03 2020
  Lspci:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.systemd.resolved.conf: 2020-01-03T01:02:47.779343

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858210/+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 1894622] Re: Missing manpage for systemd-resolve

[Brian Murray]

Hello Fabrizio, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.8 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

Title:
  Missing manpage for systemd-resolve

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [impact]

  'man systemd-resolve' fails

  [test case]

  $ man systemd-resolve
  No manual entry for systemd-resolve

  [regression potential]

  incorrect man page result for resolvectl or resolvconf, or possibly
  users using deprecated systemd-resolve longer than they should

  [scope]

  this is needed in f and later

  systemd-resolve was replaced with resolvectl between b and f, so the
  man page exists in b

  [other info]

  the systemd-resolve binary is a symlink to the real binary resolvectl, and 
users should use resolvectl for all new uses. A patch to the upstream man page 
was proposed and merged in this PR:
  https://github.com/systemd/systemd/pull/20064

  however that is being discussed and may be reverted in this PR:
  https://github.com/systemd/systemd/pull/20077

  as discussed in the revert PR, it's ok for upstream to elide docs
  about deprecated tooling; however distros should include deprecation
  info and thus I believe it's appropriate to include the man page
  symlink so users trying 'man systemd-resolve' will get the correct
  'resolvectl' man page, which includes doc about how they shoudl start
  using 'resolvectl' instead

  [original description]

  On my Focal machine there is no file /usr/share/man/man1/systemd-resolve.1.gz
  This means that man systemd-resolve fails.

  http://manpages.ubuntu.com/manpages/bionic/en/man1/systemd-
  resolve.1.html exists and has a link on top to 20.04LTS: it points to
  http://manpages.ubuntu.com/manpages/focal/en/man1/systemd-
  resolve.1.html , that however 404's, and one ends up being redirected
  to Bionic's.

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

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

[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

[Brian Murray]

Hello Kai-Heng, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.5 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  Fix micmute hotkeys on HP ProBooks

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+subscriptions

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

[Touch-packages] [Bug 1858210] Re: timedatectl doesn't list all timezones

[Brian Murray]

Hello mlx, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.5 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  timedatectl doesn't list all timezones

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

Bug description:
  [impact]

  timedatectl list-timezones doesn't show many common timezones that are
  actually considered 'aliases', such as Europe/Bratislava or
  US/Eastern.

  [test case]

  $ timedatectl list-timezones | grep Eastern
  $

  [regression potential]

  any regression would likely result in an incorrect list of timezones
  shown from list-timezones, or failure to correctly set a timezone

  [scope]

  this is needed in f and later

  this is fixed upstream with PR 20066 which was just merged, so this is
  needed in all releases in ubuntu

  in bionic, the 'tzdata.zi' file that the new code uses isn't present,
  so this won't work on bionic, thus marking it wontfix

  [original description]

  Is there some filter determining which timezones are displayed by
  `timedatectl list-timezones`? My zone, Europe/Bratislava, is missing.
  Even stranger, it can successfully be set by timedatectl.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  Date: Fri Jan  3 15:36:03 2020
  Lspci:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.systemd.resolved.conf: 2020-01-03T01:02:47.779343

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858210/+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 1931578] Re: ActivationPolicy=down causes delay at boot

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.5 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  ActivationPolicy=down causes delay at boot

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

Bug description:
  [impact]

  The ActivationPolicy= parameter was backported in bug 1664844, but
  when this is set to down (or always-down or manual) without also
  specifying RequiredForOnline=no, then there is a hang at boot waiting
  for the network to finish coming online.

  [test case]

  With the latest systemd, which includes support for ActivationPolicy=,
  configure an interface with ActivationPolicy=down and reboot. The boot
  will be delayed waiting for that interface.

  [regression potential]

  any regression would likely cause the system to encounter delay at
  boot, or to boot before configured interface(s) are fully online at
  boot, or to fail to correctly/fully configure interface(s).

  [scope]

  this is needed for all releases

  this is proposed upstream in:
  https://github.com/systemd/systemd/pull/19883

  [other info]

  this is only needed for convenience, as any configuration using
  ActivationPolicy=down can also easily add RequiredForOnline=no

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

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

[Touch-packages] [Bug 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received

[Brian Murray]

Hello Simon, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.5 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

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

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

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

Bug description:
  [impact]

  networking changes, like RA events, can cause systemd-resolved to re-
  write the resolv.conf file, even if the contents didn't change,
  resulting in unnecessary increased amount of inotify events

  [test case]

  see original description for ipv6ra-related reproducer, or simple
  reproducer here:

  configure networkd with some config for (e.g.) eth0, but not a config
  that would result in /etc/resolv.conf changing when the interface goes
  up/down - for example, use static config with no DNS search domains.
  Then bring eth0 up/down while observing the md5sum (file content) does
  not change but the mtime does change.

  root@lp1891215-h:~# ip l set down dev eth0
  root@lp1891215-h:~# md5sum /etc/resolv.conf
  db23e80078515192c312e5f321ff0340  /etc/resolv.conf
  root@lp1891215-h:~# stat -t -L /etc/resolv.conf
  /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238218 1625238216 
1625238216 0 4096
  root@lp1891215-h:~# ip l set up dev eth0
  root@lp1891215-h:~# md5sum /etc/resolv.conf
  db23e80078515192c312e5f321ff0340  /etc/resolv.conf
  root@lp1891215-h:~# stat -t -L /etc/resolv.conf
  /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238227 1625238226 
1625238226 0 4096

  [regression potential]

  regressions would result in incorrect or missing data in the
  resolv.conf file, possibly resulting in dns failures or errors

  [scope]

  this is needed for h and eralier

  this is (potentially) fixed upstream by
  f3e1f00d03445911ee73729219cea88c8a70c612 which in first included in
  v248, so this is needed in hirsute and earlier

  [original description]

  # Issue description:

  On 2 Linode VMs that are used as lxd hosts, we noticed that
  /run/systemd/resolve/*resolv.conf were re-created quite frequently (~
  once per second). We noticed because of the log noise from lxd's
  dnsmasq instance using inotify to watch the target of /etc/resolv.conf
  (which points to the stub-resolv.conf in our case). This was (wrongly)
  reported as a lxd bug (https://github.com/lxc/lxd/issues/7765) until
  it became apparent it was more likely to be a problem with
  systemd(-resolved)?.

  The log noise is the observable problem that would be nice to see
  addressed:

    root@lxd02:~# uptime
     17:55:48 up  9:52,  1 user,  load average: 0.18, 0.11, 0.05
    root@lxd02:~# journalctl -b0 | grep -cF dnsmasq
    158609

  Upon further investigation, it seems that systemd-resolved re-creates
  the resolv.conf and stub-resolv.conf files whenever an IPv6 RA is
  received.

  1) One can observe that by setting systemd-resolved's service in debug
  mode:

  $ sudo systemctl edit systemd-resolved

  and in the editor that is opened, add and save this content:

  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  then restart systemd-resolved and watch the logs scroll by with:

  $ journalctl -fu systemd-resolved

  3) In another terminal, watch the files be recreated with:

  watch -d -n 0.1 stat /run/systemd/resolve/stub-resolv.conf

  3) In ye

[Touch-packages] [Bug 1894622] Re: Missing manpage for systemd-resolve

[Brian Murray]

Hello Fabrizio, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.5 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  Missing manpage for systemd-resolve

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [impact]

  'man systemd-resolve' fails

  [test case]

  $ man systemd-resolve
  No manual entry for systemd-resolve

  [regression potential]

  incorrect man page result for resolvectl or resolvconf, or possibly
  users using deprecated systemd-resolve longer than they should

  [scope]

  this is needed in f and later

  systemd-resolve was replaced with resolvectl between b and f, so the
  man page exists in b

  [other info]

  the systemd-resolve binary is a symlink to the real binary resolvectl, and 
users should use resolvectl for all new uses. A patch to the upstream man page 
was proposed and merged in this PR:
  https://github.com/systemd/systemd/pull/20064

  however that is being discussed and may be reverted in this PR:
  https://github.com/systemd/systemd/pull/20077

  as discussed in the revert PR, it's ok for upstream to elide docs
  about deprecated tooling; however distros should include deprecation
  info and thus I believe it's appropriate to include the man page
  symlink so users trying 'man systemd-resolve' will get the correct
  'resolvectl' man page, which includes doc about how they shoudl start
  using 'resolvectl' instead

  [original description]

  On my Focal machine there is no file /usr/share/man/man1/systemd-resolve.1.gz
  This means that man systemd-resolve fails.

  http://manpages.ubuntu.com/manpages/bionic/en/man1/systemd-
  resolve.1.html exists and has a link on top to 20.04LTS: it points to
  http://manpages.ubuntu.com/manpages/focal/en/man1/systemd-
  resolve.1.html , that however 404's, and one ends up being redirected
  to Bionic's.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1894622/+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 1932352] Re: Fix micmute hotkeys on HP Elite Dragonfly

[Brian Murray]

Hello jeremyszu, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.5 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  Fix micmute hotkeys on HP Elite Dragonfly

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Mic mute key is no function on HP Elite Dragonfly.

  [Fix]
  After confirming with HP, there are two model names for Dragonfly:
  * HP Elite Dragonfly G2 Notebook PC
  * HP Elite Dragonfly Max Notebook PC
  Thus, the commit 
  Commit c1b8c966eccb7be1cae0a30670f5e1fcd88b47fa maps the 81 scan code to mic 
mute key.

  [Test]
  After patching it, the mic mute key could functioned well on my Dragonfly 
laptop.

  [Where problems could occur]
  There is not old rule for Dragonfly dmi string in current hwdb.
  Which means the Dragonfly is using default HP key map:
  ```
  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:*

   KEYBOARD_KEY_81=fn_esc
  ```
  This patch will change the HP machine (if product name contains 
pnHPEliteDragonfly*) to map 81 to mic mute key.
  If a machine (pnHPEliteDragonfly*) works good in the past then this patch may 
cause it's mic mute key become malfunction.
  However, this rule is confirmed/provided from HP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932352/+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 1931578] Re: ActivationPolicy=down causes delay at boot

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.2 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  ActivationPolicy=down causes delay at boot

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

Bug description:
  [impact]

  The ActivationPolicy= parameter was backported in bug 1664844, but
  when this is set to down (or always-down or manual) without also
  specifying RequiredForOnline=no, then there is a hang at boot waiting
  for the network to finish coming online.

  [test case]

  With the latest systemd, which includes support for ActivationPolicy=,
  configure an interface with ActivationPolicy=down and reboot. The boot
  will be delayed waiting for that interface.

  [regression potential]

  any regression would likely cause the system to encounter delay at
  boot, or to boot before configured interface(s) are fully online at
  boot, or to fail to correctly/fully configure interface(s).

  [scope]

  this is needed for all releases

  this is proposed upstream in:
  https://github.com/systemd/systemd/pull/19883

  [other info]

  this is only needed for convenience, as any configuration using
  ActivationPolicy=down can also easily add RequiredForOnline=no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931578/+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 1858210] Re: timedatectl doesn't list all timezones

[Brian Murray]

Hello mlx, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.2 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  timedatectl doesn't list all timezones

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

Bug description:
  [impact]

  timedatectl list-timezones doesn't show many common timezones that are
  actually considered 'aliases', such as Europe/Bratislava or
  US/Eastern.

  [test case]

  $ timedatectl list-timezones | grep Eastern
  $

  [regression potential]

  any regression would likely result in an incorrect list of timezones
  shown from list-timezones, or failure to correctly set a timezone

  [scope]

  this is needed in f and later

  this is fixed upstream with PR 20066 which was just merged, so this is
  needed in all releases in ubuntu

  in bionic, the 'tzdata.zi' file that the new code uses isn't present,
  so this won't work on bionic, thus marking it wontfix

  [original description]

  Is there some filter determining which timezones are displayed by
  `timedatectl list-timezones`? My zone, Europe/Bratislava, is missing.
  Even stranger, it can successfully be set by timedatectl.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  Date: Fri Jan  3 15:36:03 2020
  Lspci:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.systemd.resolved.conf: 2020-01-03T01:02:47.779343

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858210/+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 1894622] Re: Missing manpage for systemd-resolve

[Brian Murray]

Hello Fabrizio, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.2 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  Missing manpage for systemd-resolve

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [impact]

  'man systemd-resolve' fails

  [test case]

  $ man systemd-resolve
  No manual entry for systemd-resolve

  [regression potential]

  incorrect man page result for resolvectl or resolvconf, or possibly
  users using deprecated systemd-resolve longer than they should

  [scope]

  this is needed in f and later

  systemd-resolve was replaced with resolvectl between b and f, so the
  man page exists in b

  [other info]

  the systemd-resolve binary is a symlink to the real binary resolvectl, and 
users should use resolvectl for all new uses. A patch to the upstream man page 
was proposed and merged in this PR:
  https://github.com/systemd/systemd/pull/20064

  however that is being discussed and may be reverted in this PR:
  https://github.com/systemd/systemd/pull/20077

  as discussed in the revert PR, it's ok for upstream to elide docs
  about deprecated tooling; however distros should include deprecation
  info and thus I believe it's appropriate to include the man page
  symlink so users trying 'man systemd-resolve' will get the correct
  'resolvectl' man page, which includes doc about how they shoudl start
  using 'resolvectl' instead

  [original description]

  On my Focal machine there is no file /usr/share/man/man1/systemd-resolve.1.gz
  This means that man systemd-resolve fails.

  http://manpages.ubuntu.com/manpages/bionic/en/man1/systemd-
  resolve.1.html exists and has a link on top to 20.04LTS: it points to
  http://manpages.ubuntu.com/manpages/focal/en/man1/systemd-
  resolve.1.html , that however 404's, and one ends up being redirected
  to Bionic's.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1894622/+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 1925827] Re: [v247] backport routing policy rule fix

[Brian Murray]

Hello Zhang, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.2 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  [v247] backport routing policy rule fix

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

Bug description:
  [impact]

  routing policy rules not correctly configured

  [test case]

  more detail in upstream bug linked from original description.

  configure interface with:

  [Match]
  Name = ens3

  [Network]
  Address = 10.0.0.1/32

  [RoutingPolicyRule]
  Family = both
  IncomingInterface = ens3
  Table = 42
  Priority = 42

  
  then networkctl reload. then update the network file with:

  [Route]
  Table = 42
  Destination = 10.0.0.0/24
  Gateway = 0.0.0.0

  and run networkctl reload again, checking systemd-networkd for error.

  [regression potential]

  failure to properly configure networking in general, or policy routes.

  [scope]

  this is needed only for h.

  this is fixed already in i, and this is not reproducable in g.

  see original descrption for link to specific upstream issue and pr.

  [original description]

  The original issue can be found at 
https://github.com/systemd/systemd/issues/18107.
  I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) 
against v247-stable branch, which got merged and released in v247.4.
  However due to the freezing state of Debian bullseye, upstream systemd 
package is frozen at v247.3.
  Please apply this patchset for Ubuntu if possible.
  Thanks.

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

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

[Touch-packages] [Bug 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received

[Brian Murray]

Hello Simon, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.2 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

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

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

Bug description:
  [impact]

  networking changes, like RA events, can cause systemd-resolved to re-
  write the resolv.conf file, even if the contents didn't change,
  resulting in unnecessary increased amount of inotify events

  [test case]

  see original description for ipv6ra-related reproducer, or simple
  reproducer here:

  configure networkd with some config for (e.g.) eth0, but not a config
  that would result in /etc/resolv.conf changing when the interface goes
  up/down - for example, use static config with no DNS search domains.
  Then bring eth0 up/down while observing the md5sum (file content) does
  not change but the mtime does change.

  root@lp1891215-h:~# ip l set down dev eth0
  root@lp1891215-h:~# md5sum /etc/resolv.conf
  db23e80078515192c312e5f321ff0340  /etc/resolv.conf
  root@lp1891215-h:~# stat -t -L /etc/resolv.conf
  /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238218 1625238216 
1625238216 0 4096
  root@lp1891215-h:~# ip l set up dev eth0
  root@lp1891215-h:~# md5sum /etc/resolv.conf
  db23e80078515192c312e5f321ff0340  /etc/resolv.conf
  root@lp1891215-h:~# stat -t -L /etc/resolv.conf
  /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238227 1625238226 
1625238226 0 4096

  [regression potential]

  regressions would result in incorrect or missing data in the
  resolv.conf file, possibly resulting in dns failures or errors

  [scope]

  this is needed for h and eralier

  this is (potentially) fixed upstream by
  f3e1f00d03445911ee73729219cea88c8a70c612 which in first included in
  v248, so this is needed in hirsute and earlier

  [original description]

  # Issue description:

  On 2 Linode VMs that are used as lxd hosts, we noticed that
  /run/systemd/resolve/*resolv.conf were re-created quite frequently (~
  once per second). We noticed because of the log noise from lxd's
  dnsmasq instance using inotify to watch the target of /etc/resolv.conf
  (which points to the stub-resolv.conf in our case). This was (wrongly)
  reported as a lxd bug (https://github.com/lxc/lxd/issues/7765) until
  it became apparent it was more likely to be a problem with
  systemd(-resolved)?.

  The log noise is the observable problem that would be nice to see
  addressed:

    root@lxd02:~# uptime
     17:55:48 up  9:52,  1 user,  load average: 0.18, 0.11, 0.05
    root@lxd02:~# journalctl -b0 | grep -cF dnsmasq
    158609

  Upon further investigation, it seems that systemd-resolved re-creates
  the resolv.conf and stub-resolv.conf files whenever an IPv6 RA is
  received.

  1) One can observe that by setting systemd-resolved's service in debug
  mode:

  $ sudo systemctl edit systemd-resolved

  and in the editor that is opened, add and save this content:

  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  then restart systemd-resolved and watch the logs scroll by with:

  $ journalctl -fu systemd-resolved

  3) In another terminal, watch the files be recreated with:

  watch -d -n 0.1 stat /run/systemd/resolve/stub-

[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

[Brian Murray]

Hello Kai-Heng, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.2 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  Fix micmute hotkeys on HP ProBooks

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+subscriptions

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

[Touch-packages] [Bug 1932352] Re: Fix micmute hotkeys on HP Elite Dragonfly

[Brian Murray]

Hello jeremyszu, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.2 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  Fix micmute hotkeys on HP Elite Dragonfly

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Mic mute key is no function on HP Elite Dragonfly.

  [Fix]
  After confirming with HP, there are two model names for Dragonfly:
  * HP Elite Dragonfly G2 Notebook PC
  * HP Elite Dragonfly Max Notebook PC
  Thus, the commit 
  Commit c1b8c966eccb7be1cae0a30670f5e1fcd88b47fa maps the 81 scan code to mic 
mute key.

  [Test]
  After patching it, the mic mute key could functioned well on my Dragonfly 
laptop.

  [Where problems could occur]
  There is not old rule for Dragonfly dmi string in current hwdb.
  Which means the Dragonfly is using default HP key map:
  ```
  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:*

   KEYBOARD_KEY_81=fn_esc
  ```
  This patch will change the HP machine (if product name contains 
pnHPEliteDragonfly*) to map 81 to mic mute key.
  If a machine (pnHPEliteDragonfly*) works good in the past then this patch may 
cause it's mic mute key become malfunction.
  However, this rule is confirmed/provided from HP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932352/+subscriptions

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

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

[Andreas Hasenack]

I tested this last change, and it does exactly what we wanted for
iptables, the tool. And since that behavior is shared with all tools of
the iptables suite, it means iptables-restore got that fix too (good!),
but it also introduces a change in behavior for iptables-restore (bad!).

When compared to the bionic 1.6.1 iptables:
(a) straight backport from 1.6.2
- iptables loses the implicit -w parameter, meaning it will fail right away if 
it encounters the lock
- iptables-restore maintains the behavior, and grows the extra -w option

(b) massaged patches from comment #16
- iptables keeps the same behavior as in 1.6.1
- iptables-restore grows the implicit -w option, meaning it will block until 
the lock is released

The locking code is shared by all tools in one .c file. Making it behave
differently whether it's iptables or iptables-restore being used is
kumbersome, and would make ubuntu the only one with this behavior.

Alternatively, this bug has actually a very decent workaround: wrap
iptables-restore in flock. That's the same locking mechanism that
iptables itself does, just internally.

Quick example: you want iptables-restore -w 2 file.iptables

Use:
flock -w 2 -x /run/xtables.lock iptables-restore file.iptables

You can even augment that a bit with -E , and have flock return
 if the lock cannot be acquired in the specified amount of time.


Of the two patch sets, it feels like (b) introduces the less worse behavior 
change. Before iptables-restore would fail right away, now it can get stuck for 
as long as the lock is held. Which is the iptables behavior already. But it's 
still a change, and your script could stall for as long as the lock exists. You 
should change it to use -w .

Option (a) has the danger that if you are not checking for errors in
your script, one or more iptables calls could fail, and you wouldn't
notice, leaving your firewall incomplete. I think this is a dangerous
change.

Considering bionic is an LTS, and the existence of the flock workaround
which is exactly what the code itself does, what do you guys think about
this SRU? Should we pick a patch and go with it, or reject the change
and recommend the flock() alternative?

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

Title:
  iptables-restore is missing -w option

Status in iptables package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1935050] Re: After uninstall apt autoremove removes keyring, but repo remains and throws error on 'sudo apt update'

[Alf HP Lund]

Thank you for clarifying this.

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

Title:
  After uninstall apt autoremove removes keyring, but repo remains and
  throws error on 'sudo apt update'

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I manually added a repository to install a program (brave-browser).
  After testing for a while I decided the browswer does not suit my
  needs and did "sudo apt purge brave-browser", then "sudo apt
  autoremove".

  Expected result: my system works as before, just without brave-
  browser.

  What happened: "sudo apt autoremove" deleted the keyring of brave-
  browser, but left the file /etc/apt/sources.list.d/brave-browser-
  release.list

  Subsequently "sudo apt update" throws these messages:

  "W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
https://brave-browser-apt-release.s3.brave.com stable InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY A8580BDC82D3DC6C
  W: Failed to fetch 
https://brave-browser-apt-release.s3.brave.com/dists/stable/InRelease  The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY A8580BDC82D3DC6C
  W: Some index files failed to download. They have been ignored, or old ones 
used instead."

  Uninstalling a program should keep the keyring if it is needed to
  verify repositories. There could be an option to remove both (though I
  think removing the repo while keeping the keyring would not return
  errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.6
  ProcVersionSignature: Ubuntu 5.4.0-77.86-lowlatency 5.4.119
  Uname: Linux 5.4.0-77-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jul  8 15:04:54 2021
  InstallationDate: Installed on 2021-02-07 (150 days ago)
  InstallationMedia: Kubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1935050/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Brian Murray]

Looking at the changes in the libmbim upload for Focal I noticed that
mbim-proxy was moved from /usr/lib/libmbim/ to /usr/libexec/. This ends
up moving a binary that is not included in $PATH and is installed by
default on Ubuntu 20.04 LTS afaict. I don't know how many people would
have scripts expecting libmbim to be in /usr/lib/libmbim/ but I don't
think changing it out from under them is great. Could we patch the
package so it exists in both places?

libmbim (1.22.0-2.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Bump debhelper to 12, no further changes
  * Bump Standards-Version to 4.5.0 (no further changes)
  * Move mbim-proxy to /usr/libexec (Closes: #954145)
...

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in modemmanager source package in Focal:
  Fix Committed
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.

  3. Check if the modem can be enabled

    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  = Certification Validation =

  Additionally to the aforementioned test cases, the Certification Team
  will perform some coverage testing across supported devices to make
  sure the other modems still work as 

[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Brian Murray]

Hello Jerry, or anyone else affected,

Accepted modemmanager into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.16.6-2~20.04 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: modemmanager (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in modemmanager source package in Focal:
  Fix Committed
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to m

[Touch-packages] [Bug 1934286] Please test proposed package

[Brian Murray]

Hello Jerry, or anyone else affected,

Accepted libqmi into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/libqmi/1.28.6-1~21.04
in a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result 

[Touch-packages] [Bug 1934286] Please test proposed package

[Brian Murray]

Hello Jerry, or anyone else affected,

Accepted libmbim into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libmbim/1.24.8-1~21.04 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: libqmi (Ubuntu Hirsute)
   Status: New => Fix Committed

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages ar

[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Brian Murray]

Hello Jerry, or anyone else affected,

Accepted modemmanager into hirsute-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.16.6-2~21.04 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: modemmanager (Ubuntu Hirsute)
   Status: New => Fix Committed

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

** Changed in: libmbim (Ubuntu Hirsute)
   Status: New => Fix Committed

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of

[Touch-packages] [Bug 1932331] Re: ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

[Georgia Garcia]

After downloading the apparmor source from hirsute-proposed and running
the regression tests, I was able to confirm that the i18n test is now
passing for arm64.

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

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

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

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

Bug description:
  It only affects arm64:

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Brian Murray]

I'm modifying the description to indicate that the packages should be
installed from -proposed on Focal and Hirsute and not from impish (which
is what it currently says).

** Description changed:

  [Impact]
  
  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.
  
  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem
  
  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits
  
  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6
  
  The ModemManager suite in the Impish release meets the requirements.
  
  [Test Plan]
  
  = How to Reproduce the Bug =
  
  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:
  
  $ mmcli --list-modems
  No modems were found
  
  = Test Procedure =
  
  1. Install the Ubuntu system on the tested hardware
  
    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso
  
  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )
  
    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/
  
  3. Install the ModemManager suite ( for Hirsute and Focal releases )
  
-   The ModemManager suite will be installed from Impish:
+   The ModemManager suite will be installed from the -proposed component:
  
  $ sudo apt update
- $ sudo apt install modemmanager/impish
- $ sudo apt install libqmi-utils/impish
+ $ sudo apt install modemmanager
+ $ sudo apt install libqmi-utils
  
  4. Execute the following commands
  
  4.1 Get the run-time environment
  
  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V
  
  4.2 Check the status of the ModemManager service
  
  $ sudo systemctl status ModemManager.service
  
  4.3 List the detected modems
  
  $ mmcli --list-modems
  
  4.4 Check the modem’s status
  
  $ mmcli --modem 0
  
  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only
  )
  
  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap
  
  4.6 Enable the detected modem
  
  $ sudo mmcli --modem 0 --enable
  
  4.7 Check the modem’s status
  
  $ mmcli --modem 0
  
  = Analyze the Tested Result =
  
  1. Check if installed packages are working
  
    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.
  
  2. Check if the supported modem can be detected
  
    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.
  
  3. Check if the modem can be enabled
  
    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.
  
- 
  = Certification Validation =
  
  Additionally to the aforementioned test cases, the Certification Team
  will perform some coverage testing across supported devices to make sure
  the other modems still work as expected.
  
  [Where problems could occur]
  
  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.
  
  [Other Info]
  
  We need to upgrade to these 3 packages (in Impish) at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6
  
  To support the mentioned 2 modems, the system needs to use kernels which 
include specific patches and  kernel config options .
  For ex., there is a patched 5.11 kernel which is working for: 
https://bugs.launchpad.net/austin/+bug/1928665/comments/7

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New

[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault

[Brian Murray]

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

** Tags added: fr-1490

** Tags removed: rls-ff-incoming

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

Title:
  systemd-resolve segfault

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

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

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

  apport hints me that problem is related to mdns

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

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

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

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

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

[Touch-packages] [Bug 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-logind crash when suspend with nvidia-suspend.service masked,
  bringing session down with it

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a 
restart, run `sudo apt autoremove nvidia-driver-465`.
  2. Leaving the terminal open, suspend the machine.

  Expected behavior: the machine suspend successfully and can be woken up 
successfully.
  Actual behavior: the machine doesn't suspend. It either:
  - hang with no respond other than SysRq+REISUB (or maybe network, but I 
didn't test), or
  - return you back to the login screen. Upon logging in, you'll notice that 
the terminal you opened is gone.

  Upon further inspection (on a session that doesn't hang), it's been
  found that X server died with:

  Fatal server error:
  [66.422] (EE) systemd-logind disappeared (stopped/restarted?)

  And checking journal for systemd-logind log, it said:

  Error during inhibitor-delayed operation (already returned success to
  client): Unit nvidia-suspend.service is masked.

  before the new process takes it place.

  The system is Ubuntu 20.04, X.org session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 29 03:34:00 2021
  InstallationDate: Installed on 2021-03-15 (105 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=th_TH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN31WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55756 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1933880/+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 1931958] Re: 0~git20200629+e7aa92a-8 is FTFBS

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/gstreamer1.0/+git/gstreamer1.0/+merge/405405

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

Title:
  0~git20200629+e7aa92a-8 is FTFBS

Status in gstreamer1.0 package in Ubuntu:
  New
Status in libcamera package in Ubuntu:
  New

Bug description:
  Fails to build due to gstreamer using deprecated g_memdup:

  /usr/include/gstreamer-1.0/gst/base/gstbytereader.h: In function ‘guint8* 
gst_byte_reader_dup_data_unchecked(GstByteReader*, guint)’:
  /usr/include/gstreamer-1.0/gst/base/gstbytereader.h:365:41: error: ‘void* 
g_memdup(gconstpointer, guint)’ is deprecated: Use 'g_memdup2' instead 
[-Werror=deprecated-declarations]
365 |   return (guint8 *) g_memdup (data, size);
| ^
  In file included from /usr/include/glib-2.0/glib.h:82,
   from /usr/include/gstreamer-1.0/gst/gst.h:27,
   from ../src/gstreamer/gstlibcamerasrc.h:12,
   from ../src/gstreamer/gstlibcamerasrc.cpp:34:
  /usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here
257 | gpointer  g_memdup (gconstpointer mem,

  Fixed in gstreamer upstream:
  
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/b16e96dd878e0c5e7baeb8fad62ca43de1f66982

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1931958/+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 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead

[Dan Streetman]

** Description changed:

+ [impact]
+ 
+ suspend-then-hibernate not possible using systemctl
+ 
+ [test case]
+ 
+ configure a system to allow suspend-then-hibernate but not hybrid-sleep,
+ e.g. by editing /etc/systemd/sleep.conf to set
+ AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it:
+ 
+ $ sudo systemctl suspend-then-hibernate
+ Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
+ 
+ [regression potential]
+ 
+ failure to correctly enter hybrid-sleep and/or suspend-then-hibernate,
+ or other issues around suspending/hibernating
+ 
+ [scope]
+ 
+ This is needed in f and later.
+ 
+ The bug appears to have been introduced by a typo in the original
+ suspend-then-hibernate commit c58493c00af, and then fixed with larger
+ changes in commit c8cd8ca3986.
+ 
+ [other info]
+ 
+ note that if hybrid-sleep is allowed/possible, then calling 'systemctl
+ suspend-then-hibernate' does actually perform suspend-then-hibernate;
+ this typo only controls what suspend action logind checks for support
+ of, not what suspend action it actually performs.
+ 
+ [original description]
+ 
  ```
  systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
  ```
  
  Note the verb change!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 08:54:01 2021
  InstallationDate: Installed on 2021-07-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/username-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
-  [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
-  [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
-  [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
-  
-  3 overridden configuration files found.
+  [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
+  [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
+  [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
+ 
+  3 overridden configuration files found.
  SystemdFailedUnits:
-  Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
-  Unit \xe2\x97\x8f.service could not be found.
+  Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
+  Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0PP9G2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321

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

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

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

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

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

Title:
  systemctl suspend-then-hibernate attempts hybrid-sleep instead

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

Bug description:
  [impact]

  suspend-then-hibernate not possible using systemctl

  [test case]

  configure a system to allow suspend-then-hibernate but not hybrid-
  sleep, e.g. by editing /etc/systemd/sleep.conf to set
  AllowSuspendThenHibernate=yes and AllowH

[Touch-packages] [Bug 1926843] Re: online accounts integration with fb isn't working

[Lars Martin Hambro]

https://www.asus.com/Motherboards-
Components/Motherboards/Accessories/TPM-M-R2-0/

can you confirm its should works with gnome-online-accounts  this TPM_M modules 
or other?
so user id be stored on motherboard?

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

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Focal:
  Fix Released
Status in gnome-online-accounts source package in Hirsute:
  Fix Released

Bug description:
  * Impact

  The online accounts setting are proposing a facebook item which isn't
  working

  * Test case

  Go to settings -> online account, browse the accounts option proposed,
  facebook shouldn't be in the list since it doesn't work.

  * Regression potential

  The change is to disable the facebook provider using the upstream
  provided build option. Check that facebook isn't listed anymore but
  that the other providers still are. Since it's a build option change
  it could fail to build so check for that as well on launchpad.

  Since the facebook service currently doesn't consider gnome-online-
  accounts as a valid client there should be no user with that provider
  configured. Even if there were since the service isn't working they
  would see a functional regression.

  ---

  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1934992] Re: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x

[Wayne Davison]

That said, of course, 0.8.0 is the better choice for the most possible
features (if it is available).

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

Title:
  rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x

Status in rsync package in Ubuntu:
  New

Bug description:
  **Problem**

$ rsync root@focal-system:/etc/.pwd.lock . 
ERROR: .pwd.lock failed verification -- update discarded.
rsync error: some files/attrs were not transferred (see previous errors)
  (code 23) at main.c(1816) [generator=3.2.3]

  
$ rsync root@focal-system:/etc/.pwd.lock . --debug=all
opening connection using: ssh -l root focal-system rsync --server --sender \
  -e.LsfxCIvu . /etc/.pwd.lock  (10 args)
(Client) Protocol versions: remote=31, negotiated=31
Client negotiated checksum: xxh128
...

  
  **Cause**

focal-system# dpkg -l | grep -E 'libxxhash|rsync'
ii  libxxhash0:amd64  0.7.3-1 amd64
ii  rsync 3.2.3-2ubuntu1  amd64

  
  **Why this affects only us and not more people?**

  On Ubuntu/Focal, there is no rsync 3.2.3, only 3.1.3-8. But because we
  need the lz4 compression support we've fetched a newer rsync (from
  Groovy).

  However: the rsync 3.2.3 depends on libxxhash0 0.7.1+, while in fact
  it needs 0.8+.

  
  **Details**

  On a Ubuntu/Focal system we have installed a rsync 3.2.3 package from 
Ubuntu/Groovy because we need the lz4 compression support.

  
  focal-system# apt-cache show rsync
  Package: rsync
  ...
  Version: 3.2.3-2ubuntu1
  Depends: lsb-base, libacl1 (>= 2.2.23), libc6 (>= 2.15),
liblz4-1 (>= 0.0~r130), libpopt0 (>= 1.14), libssl1.1 (>= 1.1.0),
libxxhash0 (>= 0.7.1), libzstd1 (>= 1.3.8), zlib1g (>= 1:1.1.4)
  ...

  
  Alongside this we had libxxhash0 0.7.3-1 from Focal:

  focal-system# apt-cache policy libxxhash0
  libxxhash0:
Installed: 0.7.3-1
Candidate: 0.7.3-1
Version table:
   *** 0.7.3-1 500
  500 http://ARCHIVE/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  According to the dependencies, this should work. But the combination does 
not, as this quote from the rsync maintainer would tell you:
  https://github.com/WayneD/rsync/issues/122#issuecomment-737690913
  > Yeah, Cyan4973 could have told you that the 128-bit xxhash only
  > just stabilized in its 0.8.0 release, so anything older than
  > that isn't compatible.

  
  **The fix**

  As the maintainer points out, version 0.7 is not stable (= broken for
  our intents and purposes) and thus not fit for use with rsync 3.2.

  I would argue that it's a good idea to bump the dependency of rsync
  3.2.3 on Groovy to libxxhash0>=0.8

  After all, in Groovy there is a libxxhash0 0.8.0-1ubuntu1.20.10.1, so
  that would not be a problem. And it would fix issues for those mixing
  and matching packages.

  
  Thanks!

  Walter Doekes
  OSSO B.V.

  
  (*) possible patch:

  $ diff -pu debian/control{.orig,}
  --- debian/control.orig   2021-07-08 09:56:57.646861644 +0200
  +++ debian/control2021-07-08 09:57:38.499029903 +0200
  @@ -8,7 +8,7 @@ Build-Depends: debhelper-compat (= 13),
  libacl1-dev,
  libpopt-dev,
  liblz4-dev,
  -   libxxhash-dev,
  +   libxxhash-dev (>= 0.8),
  libzstd-dev,
  zlib1g-dev,
  libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1934992/+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 1934992] Re: rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x

[Wayne Davison]

You misread my comments. It's only the 128-bit hash that depends on
0.8.0. The 0.7 version works fine with rsync, giving it the 64-bit and
32-bit hashes.

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

Title:
  rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x

Status in rsync package in Ubuntu:
  New

Bug description:
  **Problem**

$ rsync root@focal-system:/etc/.pwd.lock . 
ERROR: .pwd.lock failed verification -- update discarded.
rsync error: some files/attrs were not transferred (see previous errors)
  (code 23) at main.c(1816) [generator=3.2.3]

  
$ rsync root@focal-system:/etc/.pwd.lock . --debug=all
opening connection using: ssh -l root focal-system rsync --server --sender \
  -e.LsfxCIvu . /etc/.pwd.lock  (10 args)
(Client) Protocol versions: remote=31, negotiated=31
Client negotiated checksum: xxh128
...

  
  **Cause**

focal-system# dpkg -l | grep -E 'libxxhash|rsync'
ii  libxxhash0:amd64  0.7.3-1 amd64
ii  rsync 3.2.3-2ubuntu1  amd64

  
  **Why this affects only us and not more people?**

  On Ubuntu/Focal, there is no rsync 3.2.3, only 3.1.3-8. But because we
  need the lz4 compression support we've fetched a newer rsync (from
  Groovy).

  However: the rsync 3.2.3 depends on libxxhash0 0.7.1+, while in fact
  it needs 0.8+.

  
  **Details**

  On a Ubuntu/Focal system we have installed a rsync 3.2.3 package from 
Ubuntu/Groovy because we need the lz4 compression support.

  
  focal-system# apt-cache show rsync
  Package: rsync
  ...
  Version: 3.2.3-2ubuntu1
  Depends: lsb-base, libacl1 (>= 2.2.23), libc6 (>= 2.15),
liblz4-1 (>= 0.0~r130), libpopt0 (>= 1.14), libssl1.1 (>= 1.1.0),
libxxhash0 (>= 0.7.1), libzstd1 (>= 1.3.8), zlib1g (>= 1:1.1.4)
  ...

  
  Alongside this we had libxxhash0 0.7.3-1 from Focal:

  focal-system# apt-cache policy libxxhash0
  libxxhash0:
Installed: 0.7.3-1
Candidate: 0.7.3-1
Version table:
   *** 0.7.3-1 500
  500 http://ARCHIVE/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  According to the dependencies, this should work. But the combination does 
not, as this quote from the rsync maintainer would tell you:
  https://github.com/WayneD/rsync/issues/122#issuecomment-737690913
  > Yeah, Cyan4973 could have told you that the 128-bit xxhash only
  > just stabilized in its 0.8.0 release, so anything older than
  > that isn't compatible.

  
  **The fix**

  As the maintainer points out, version 0.7 is not stable (= broken for
  our intents and purposes) and thus not fit for use with rsync 3.2.

  I would argue that it's a good idea to bump the dependency of rsync
  3.2.3 on Groovy to libxxhash0>=0.8

  After all, in Groovy there is a libxxhash0 0.8.0-1ubuntu1.20.10.1, so
  that would not be a problem. And it would fix issues for those mixing
  and matching packages.

  
  Thanks!

  Walter Doekes
  OSSO B.V.

  
  (*) possible patch:

  $ diff -pu debian/control{.orig,}
  --- debian/control.orig   2021-07-08 09:56:57.646861644 +0200
  +++ debian/control2021-07-08 09:57:38.499029903 +0200
  @@ -8,7 +8,7 @@ Build-Depends: debhelper-compat (= 13),
  libacl1-dev,
  libpopt-dev,
  liblz4-dev,
  -   libxxhash-dev,
  +   libxxhash-dev (>= 0.8),
  libzstd-dev,
  zlib1g-dev,
  libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1934992/+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 1925745] Update Released

[Łukasz Zemczak]

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

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

Title:
  Hirsute: Cannot install ubuntu-desktop due to unmet dependencies

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Phased upgrades were only applied to already installed packages, so if we had 
a source package foo building foo-core and foo-extra, and foo-core=1 was 
installed, and we tried to install foo-extra, it would fail because it would 
try to install 0% foo-extra=2 while blocking foo-core as it's "not for us".

  [Test Plan]
  The autopkgtests ensure we don't regress and they kind of check this by 
checking the policy output to see that "foo-extra=2" above is also not the 
candidate, but foo-extra=1 is (so installing it alongside foo-core=1 would work 
fine) but they don't install it, so it might be nice to verify this too:

  Find a package that is phased, but not for us (maybe just setting the
  never-include-phased flag?), install one binary from it from the
  release pocket, and then try to install another from the updates
  pocket.

  At the moment, installing libsystemd-dev would trigger it.

  [Where problems could occur]
  This is a change in behavior when installing new packages that might cause 
regression in image building tools for example, if those don't use a chroot 
(chroots being detected).

  Apart from that risk, the change is just removing a flag check inside
  an if, so not much else.

  [Original bug report]

  I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute
  desktop machines so I can automate the installation.

  After installation, I'm trying to install the desktop via "apt install
  ubuntu-desktop".

  This fails with:
  "Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 
1:21.04.11) but 1:21.04.10 is to be installed
     Depends: python3-distupgrade (= 1:21.04.11) 
but 1:21.04.10 is to be installed
  E: Unable to correct problems, you have held broken packages."

  "apt policy ubuntu-release-upgrader-core" shows:
  "ubuntu-release-upgrader-core:
    Installed: 1:21.04.10
    Candidate: 1:21.04.10
    Version table:
   1:21.04.11 1 (phased 20%)
  500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:21.04.10 500
  500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status"

  I could not find any information what "phased 20%" means. It's
  obviously a major problem not being able to install the desktop on a
  fresh installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925745/+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 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.2.4ubuntu0.1

---
apt (2.2.4ubuntu0.1) hirsute; urgency=medium

  * Merge 2.2.4 from Debian unstable
  * Extend the JSON hook fixes with support for version 0.2 (LP: #1926150)
- json: Add origins fields to version
- upgrade: Add JSON hook support (AptCli::Hooks::Upgrade)
- json: Add `package-list` and `statistics` install hooks
- json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes)

apt (2.2.4) unstable; urgency=medium

  [ Julian Andres Klode ]
  * Various bugfixes to the JSON hooks:
- encoder fixes:
  + json: Escape strings using \u escape sequences, add test
  + json: Actually pop states
  + json: Encode NULL strings as null
- json: Flush standard file descriptors before calling hooks
  (this avoids output from hooks in middle of apt output)
- Non-installed JSON changes:
  + test/json: Make the test hook more reliable
  + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray)
  * Avoid infinite loop on EOF on media change prompt (LP: #1928687)
  * Turn TLS handshake issues into transient errors (LP: #1928100),
this makes behavior consistent with TCP and enables Acquire::Retries
  * policy: Apply phasing to uninstalled packages too (LP: #1925745),
this prevents inconsistencies when installing new binaries that depend
on the same version of an already installed binary.

  [ David Kalnischkies ]
  * URI encode Filename field of Packages files (again). This fixes a
regression introduced in 2.1.15 that causes download failures of
packages with an epoch included in their filename (LP: #1931874).

 -- Julian Andres Klode   Mon, 14 Jun 2021 16:27:40
+0200

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

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

Title:
  Hirsute: Cannot install ubuntu-desktop due to unmet dependencies

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Phased upgrades were only applied to already installed packages, so if we had 
a source package foo building foo-core and foo-extra, and foo-core=1 was 
installed, and we tried to install foo-extra, it would fail because it would 
try to install 0% foo-extra=2 while blocking foo-core as it's "not for us".

  [Test Plan]
  The autopkgtests ensure we don't regress and they kind of check this by 
checking the policy output to see that "foo-extra=2" above is also not the 
candidate, but foo-extra=1 is (so installing it alongside foo-core=1 would work 
fine) but they don't install it, so it might be nice to verify this too:

  Find a package that is phased, but not for us (maybe just setting the
  never-include-phased flag?), install one binary from it from the
  release pocket, and then try to install another from the updates
  pocket.

  At the moment, installing libsystemd-dev would trigger it.

  [Where problems could occur]
  This is a change in behavior when installing new packages that might cause 
regression in image building tools for example, if those don't use a chroot 
(chroots being detected).

  Apart from that risk, the change is just removing a flag check inside
  an if, so not much else.

  [Original bug report]

  I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute
  desktop machines so I can automate the installation.

  After installation, I'm trying to install the desktop via "apt install
  ubuntu-desktop".

  This fails with:
  "Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 
1:21.04.11) but 1:21.04.10 is to be installed
     Depends: python3-distupgrade (= 1:21.04.11) 
but 1:21.04.10 is to be installed
  E: Unable to correct problems, you have held broken packages."

  "apt policy ubuntu-release-upgrader-core" shows:
  "ubuntu-release-upgrader-core:
    Installed: 1:21.04.10
    Candidate: 1:21.04.10
    Version table:
   1:21.04.11 1 (phased 20%)
  500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:21.04.10 500
  500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status"

  I could not find any information what "phased 20%" means. It's
  obviously a major problem not being able to install the desktop on a
  fresh installation.

To manage notifications about this bug go 

[Touch-packages] [Bug 1928100] Update Released

[Łukasz Zemczak]

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

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

Title:
  TLS handshake is fatal, not transient - hence not retried

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  TLS handshakes are reported as fatal errors rather than transient errors like 
other connection errors on unencrypted connections. This seems wrong - a server 
may just be spinning up or down and fail during the handshake, and prevents 
retrying such downloads

  [Test plan]

  A test case has been added to the integration test suite that ensures
  handshake errors are retried upon configuration.

  [Where problems could occur]
  Transient errors do not cause an error exit from apt update, so scripts 
relying on errors from TLS handshakes in such situations will fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1928100/+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 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies

[Łukasz Zemczak]

Ok, the autopkgtest regression now fixed and released, let's unblock.

** Tags removed: block-proposed-hirsute

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

Title:
  Hirsute: Cannot install ubuntu-desktop due to unmet dependencies

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Phased upgrades were only applied to already installed packages, so if we had 
a source package foo building foo-core and foo-extra, and foo-core=1 was 
installed, and we tried to install foo-extra, it would fail because it would 
try to install 0% foo-extra=2 while blocking foo-core as it's "not for us".

  [Test Plan]
  The autopkgtests ensure we don't regress and they kind of check this by 
checking the policy output to see that "foo-extra=2" above is also not the 
candidate, but foo-extra=1 is (so installing it alongside foo-core=1 would work 
fine) but they don't install it, so it might be nice to verify this too:

  Find a package that is phased, but not for us (maybe just setting the
  never-include-phased flag?), install one binary from it from the
  release pocket, and then try to install another from the updates
  pocket.

  At the moment, installing libsystemd-dev would trigger it.

  [Where problems could occur]
  This is a change in behavior when installing new packages that might cause 
regression in image building tools for example, if those don't use a chroot 
(chroots being detected).

  Apart from that risk, the change is just removing a flag check inside
  an if, so not much else.

  [Original bug report]

  I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute
  desktop machines so I can automate the installation.

  After installation, I'm trying to install the desktop via "apt install
  ubuntu-desktop".

  This fails with:
  "Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 
1:21.04.11) but 1:21.04.10 is to be installed
     Depends: python3-distupgrade (= 1:21.04.11) 
but 1:21.04.10 is to be installed
  E: Unable to correct problems, you have held broken packages."

  "apt policy ubuntu-release-upgrader-core" shows:
  "ubuntu-release-upgrader-core:
    Installed: 1:21.04.10
    Candidate: 1:21.04.10
    Version table:
   1:21.04.11 1 (phased 20%)
  500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:21.04.10 500
  500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status"

  I could not find any information what "phased 20%" means. It's
  obviously a major problem not being able to install the desktop on a
  fresh installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925745/+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 1926150] Re: [SRU] Backport JSON hooks 0.2

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.2.4ubuntu0.1

---
apt (2.2.4ubuntu0.1) hirsute; urgency=medium

  * Merge 2.2.4 from Debian unstable
  * Extend the JSON hook fixes with support for version 0.2 (LP: #1926150)
- json: Add origins fields to version
- upgrade: Add JSON hook support (AptCli::Hooks::Upgrade)
- json: Add `package-list` and `statistics` install hooks
- json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes)

apt (2.2.4) unstable; urgency=medium

  [ Julian Andres Klode ]
  * Various bugfixes to the JSON hooks:
- encoder fixes:
  + json: Escape strings using \u escape sequences, add test
  + json: Actually pop states
  + json: Encode NULL strings as null
- json: Flush standard file descriptors before calling hooks
  (this avoids output from hooks in middle of apt output)
- Non-installed JSON changes:
  + test/json: Make the test hook more reliable
  + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray)
  * Avoid infinite loop on EOF on media change prompt (LP: #1928687)
  * Turn TLS handshake issues into transient errors (LP: #1928100),
this makes behavior consistent with TCP and enables Acquire::Retries
  * policy: Apply phasing to uninstalled packages too (LP: #1925745),
this prevents inconsistencies when installing new binaries that depend
on the same version of an already installed binary.

  [ David Kalnischkies ]
  * URI encode Filename field of Packages files (again). This fixes a
regression introduced in 2.1.15 that causes download failures of
packages with an epoch included in their filename (LP: #1931874).

 -- Julian Andres Klode   Mon, 14 Jun 2021 16:27:40
+0200

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

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

Title:
  [SRU] Backport JSON hooks 0.2

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  We want to be able to use JSON hooks 0.2 in xenial and later releases to 
display messages to users during dist-upgrade.

  For xenial, we backport the JSON hook support in its entirety, whereas
  for later releases, we only need to cherry-pick bugfixes and the v0.2
  improvements.

  [Test plan]
  We have included unit and integration tests for the new JSON code to test the 
writer and prevent regressions in future changes. Regressions in other parts of 
the code should be caught by the test suite.

  
  [Where problems could occur]
  There may be bugs in the JSON code (apt-private/private-json-hooks.*) and in 
the integration thereof. The JSON hook code is identical to 2.3.2, whereas the 
integration code needed slight adjustments.

  The integration changes are limited to adding the hooks, and (for
  xenial, already in later releases) collecting all unknown package
  names. We believe the regression potential of these changes to be
  fairly limited.

  However, errors in JSON hooks are fatal, so once JSON hooks are
  running, they can cause apt to fail, which has to be kept in mind.

  Existing JSON hooks might not expect the new notifications, and break,
  but we are only aware of the snapd hook and it ignores any unknown
  notifications, so that should not pose a problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926150/+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 1928100] Re: TLS handshake is fatal, not transient - hence not retried

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.2.4ubuntu0.1

---
apt (2.2.4ubuntu0.1) hirsute; urgency=medium

  * Merge 2.2.4 from Debian unstable
  * Extend the JSON hook fixes with support for version 0.2 (LP: #1926150)
- json: Add origins fields to version
- upgrade: Add JSON hook support (AptCli::Hooks::Upgrade)
- json: Add `package-list` and `statistics` install hooks
- json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes)

apt (2.2.4) unstable; urgency=medium

  [ Julian Andres Klode ]
  * Various bugfixes to the JSON hooks:
- encoder fixes:
  + json: Escape strings using \u escape sequences, add test
  + json: Actually pop states
  + json: Encode NULL strings as null
- json: Flush standard file descriptors before calling hooks
  (this avoids output from hooks in middle of apt output)
- Non-installed JSON changes:
  + test/json: Make the test hook more reliable
  + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray)
  * Avoid infinite loop on EOF on media change prompt (LP: #1928687)
  * Turn TLS handshake issues into transient errors (LP: #1928100),
this makes behavior consistent with TCP and enables Acquire::Retries
  * policy: Apply phasing to uninstalled packages too (LP: #1925745),
this prevents inconsistencies when installing new binaries that depend
on the same version of an already installed binary.

  [ David Kalnischkies ]
  * URI encode Filename field of Packages files (again). This fixes a
regression introduced in 2.1.15 that causes download failures of
packages with an epoch included in their filename (LP: #1931874).

 -- Julian Andres Klode   Mon, 14 Jun 2021 16:27:40
+0200

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

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

Title:
  TLS handshake is fatal, not transient - hence not retried

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  TLS handshakes are reported as fatal errors rather than transient errors like 
other connection errors on unencrypted connections. This seems wrong - a server 
may just be spinning up or down and fail during the handshake, and prevents 
retrying such downloads

  [Test plan]

  A test case has been added to the integration test suite that ensures
  handshake errors are retried upon configuration.

  [Where problems could occur]
  Transient errors do not cause an error exit from apt update, so scripts 
relying on errors from TLS handshakes in such situations will fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1928100/+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 1931874] Update Released

[Łukasz Zemczak]

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

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

Title:
  Failure to download packages with epochs (Regression from 2.1.15)

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Packages where the epoch is encoded in the filename cannot be retrieved, as 
we overlooked some places when changing the acquire system to always use % 
encoded URLs.

  [Test plan]
  A test is included in the comprehensive test suite.

  [Where problems could occur]
  Regressions could occur in places that download debs with filenames that need 
quoting or are already quoted. You can argue this also changes the API 
slightly, since ArchiveURI() now returns encoded URLs, rather than just 
appending the file path to the host. Although, this could actually improve 
things too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1931874/+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 1931874] Re: Failure to download packages with epochs (Regression from 2.1.15)

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.2.4ubuntu0.1

---
apt (2.2.4ubuntu0.1) hirsute; urgency=medium

  * Merge 2.2.4 from Debian unstable
  * Extend the JSON hook fixes with support for version 0.2 (LP: #1926150)
- json: Add origins fields to version
- upgrade: Add JSON hook support (AptCli::Hooks::Upgrade)
- json: Add `package-list` and `statistics` install hooks
- json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes)

apt (2.2.4) unstable; urgency=medium

  [ Julian Andres Klode ]
  * Various bugfixes to the JSON hooks:
- encoder fixes:
  + json: Escape strings using \u escape sequences, add test
  + json: Actually pop states
  + json: Encode NULL strings as null
- json: Flush standard file descriptors before calling hooks
  (this avoids output from hooks in middle of apt output)
- Non-installed JSON changes:
  + test/json: Make the test hook more reliable
  + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray)
  * Avoid infinite loop on EOF on media change prompt (LP: #1928687)
  * Turn TLS handshake issues into transient errors (LP: #1928100),
this makes behavior consistent with TCP and enables Acquire::Retries
  * policy: Apply phasing to uninstalled packages too (LP: #1925745),
this prevents inconsistencies when installing new binaries that depend
on the same version of an already installed binary.

  [ David Kalnischkies ]
  * URI encode Filename field of Packages files (again). This fixes a
regression introduced in 2.1.15 that causes download failures of
packages with an epoch included in their filename (LP: #1931874).

 -- Julian Andres Klode   Mon, 14 Jun 2021 16:27:40
+0200

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

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

Title:
  Failure to download packages with epochs (Regression from 2.1.15)

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Packages where the epoch is encoded in the filename cannot be retrieved, as 
we overlooked some places when changing the acquire system to always use % 
encoded URLs.

  [Test plan]
  A test is included in the comprehensive test suite.

  [Where problems could occur]
  Regressions could occur in places that download debs with filenames that need 
quoting or are already quoted. You can argue this also changes the API 
slightly, since ArchiveURI() now returns encoded URLs, rather than just 
appending the file path to the host. Although, this could actually improve 
things too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1931874/+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 1928687] Re: Avoid infinite loop on EOF on media change prompt

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.2.4ubuntu0.1

---
apt (2.2.4ubuntu0.1) hirsute; urgency=medium

  * Merge 2.2.4 from Debian unstable
  * Extend the JSON hook fixes with support for version 0.2 (LP: #1926150)
- json: Add origins fields to version
- upgrade: Add JSON hook support (AptCli::Hooks::Upgrade)
- json: Add `package-list` and `statistics` install hooks
- json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes)

apt (2.2.4) unstable; urgency=medium

  [ Julian Andres Klode ]
  * Various bugfixes to the JSON hooks:
- encoder fixes:
  + json: Escape strings using \u escape sequences, add test
  + json: Actually pop states
  + json: Encode NULL strings as null
- json: Flush standard file descriptors before calling hooks
  (this avoids output from hooks in middle of apt output)
- Non-installed JSON changes:
  + test/json: Make the test hook more reliable
  + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray)
  * Avoid infinite loop on EOF on media change prompt (LP: #1928687)
  * Turn TLS handshake issues into transient errors (LP: #1928100),
this makes behavior consistent with TCP and enables Acquire::Retries
  * policy: Apply phasing to uninstalled packages too (LP: #1925745),
this prevents inconsistencies when installing new binaries that depend
on the same version of an already installed binary.

  [ David Kalnischkies ]
  * URI encode Filename field of Packages files (again). This fixes a
regression introduced in 2.1.15 that causes download failures of
packages with an epoch included in their filename (LP: #1931874).

 -- Julian Andres Klode   Mon, 14 Jun 2021 16:27:40
+0200

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

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

Title:
  Avoid infinite loop on EOF on media change prompt

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  The cdrom media change prompt hangs on EOF. This causes the autopkgtest to 
hang when run in a debian lxd container for unknown reasons related to 
lxd/systemd isolation likely (it works fine in Ubuntu), but it's also 
surprising behavior in general.

  [Test plan]
  We did not really come up with a test for this except running autopkgtest -- 
lxd autopkgtest/debian/$suite/$arch. That being said, the change is minimal, 
and we do test the positive case in the test suite.

  [Where problems could occur]
  This change is isolated to the handling of pressing 'c' or hitting EOF inside 
the media change prompt, so any regressions would occur solely within that 
space. We do not foresee any regressions from the change as intended, as it 
seems unlikely that "hanging" is what you actually want.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1928687/+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 1935050] Re: After uninstall apt autoremove removes keyring, but repo remains and throws error on 'sudo apt update'

[Julian Andres Klode]

Thank you for your bug report. Unfortunately, this is an issue in a
third-party package, and not in Ubuntu. I suggest you raise it with
them.

Presumably they are a Chrome-like package and this is a side-effect of
https://bugs.chromium.org/p/chromium/issues/detail?id=1106309&q=&can=4 -
if they install a proper file into trusted.gpg.d, it will be removed
alongside the sources.list.d file on purge only.

** Changed in: apt (Ubuntu)
   Status: New => Invalid

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

Title:
  After uninstall apt autoremove removes keyring, but repo remains and
  throws error on 'sudo apt update'

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I manually added a repository to install a program (brave-browser).
  After testing for a while I decided the browswer does not suit my
  needs and did "sudo apt purge brave-browser", then "sudo apt
  autoremove".

  Expected result: my system works as before, just without brave-
  browser.

  What happened: "sudo apt autoremove" deleted the keyring of brave-
  browser, but left the file /etc/apt/sources.list.d/brave-browser-
  release.list

  Subsequently "sudo apt update" throws these messages:

  "W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
https://brave-browser-apt-release.s3.brave.com stable InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY A8580BDC82D3DC6C
  W: Failed to fetch 
https://brave-browser-apt-release.s3.brave.com/dists/stable/InRelease  The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY A8580BDC82D3DC6C
  W: Some index files failed to download. They have been ignored, or old ones 
used instead."

  Uninstalling a program should keep the keyring if it is needed to
  verify repositories. There could be an option to remove both (though I
  think removing the repo while keeping the keyring would not return
  errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.6
  ProcVersionSignature: Ubuntu 5.4.0-77.86-lowlatency 5.4.119
  Uname: Linux 5.4.0-77-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jul  8 15:04:54 2021
  InstallationDate: Installed on 2021-02-07 (150 days ago)
  InstallationMedia: Kubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1935050/+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 1935051] Re: systemd pid 1 memory leak

[Sergey Borodavkin]

** Attachment added: "pmap_pid1_focal"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+attachment/5509911/+files/pmap_pid1_focal

** Description changed:

  Hi everybody.
  
  We've meet a memory leak of pid1 process on the focal release.
  When we launch chef-client, several systemd .service and .timers are checked 
for state.
  Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen 
on xenial and bionic releases.
  I straced pid1 when that leak happen and found brk call.
  On pmap view of pid 1 it's anon memory grow on the same address and all 
marked as dirty.
+ All that leak memory can be freed by calling systemctl daemon-reexec.
  
  Searching in systemd github repo i found this commit
  
https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d
  - it may be related to this leak.
  
- 

+ 
  
  Environment:
-   Distributor ID: Ubuntu
-   Description:Ubuntu 20.04.2 LTS
-   Release:20.04
-   Codename:   focal
-   Uname:  5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 
x86_64
+   Distributor ID: Ubuntu
+   Description:Ubuntu 20.04.2 LTS
+   Release:20.04
+   Codename:   focal
+   Uname:  5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 
x86_64
  
  Package:
-   systemd:
- Installed: 245.4-4ubuntu3.7
+   systemd:
+ Installed: 245.4-4ubuntu3.7

** Tags added: pid1

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

Title:
  systemd pid 1 memory leak

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi everybody.

  We've meet a memory leak of pid1 process on the focal release.
  When we launch chef-client, several systemd .service and .timers are checked 
for state.
  Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen 
on xenial and bionic releases.
  I straced pid1 when that leak happen and found brk call.
  On pmap view of pid 1 it's anon memory grow on the same address and all 
marked as dirty.
  All that leak memory can be freed by calling systemctl daemon-reexec.

  Searching in systemd github repo i found this commit
  
https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d
  - it may be related to this leak.

  

  Environment:
    Distributor ID: Ubuntu
    Description:Ubuntu 20.04.2 LTS
    Release:20.04
    Codename:   focal
    Uname:  5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 
x86_64

  Package:
    systemd:
  Installed: 245.4-4ubuntu3.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+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 1935051] [NEW] systemd pid 1 memory leak

[Sergey Borodavkin]

Public bug reported:

Hi everybody.

We've meet a memory leak of pid1 process on the focal release.
When we launch chef-client, several systemd .service and .timers are checked 
for state.
Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on 
xenial and bionic releases.
I straced pid1 when that leak happen and found brk call.
On pmap view of pid 1 it's anon memory grow on the same address and all marked 
as dirty.
All that leak memory can be freed by calling systemctl daemon-reexec.

Searching in systemd github repo i found this commit
https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d
- it may be related to this leak.



Environment:
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal
  Uname:  5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 
x86_64

Package:
  systemd:
Installed: 245.4-4ubuntu3.7

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


** Tags: pid1 systemd

** Attachment added: "pid1 strace focal"
   
https://bugs.launchpad.net/bugs/1935051/+attachment/5509910/+files/pid1_strace_focal

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

Title:
  systemd pid 1 memory leak

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi everybody.

  We've meet a memory leak of pid1 process on the focal release.
  When we launch chef-client, several systemd .service and .timers are checked 
for state.
  Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen 
on xenial and bionic releases.
  I straced pid1 when that leak happen and found brk call.
  On pmap view of pid 1 it's anon memory grow on the same address and all 
marked as dirty.
  All that leak memory can be freed by calling systemctl daemon-reexec.

  Searching in systemd github repo i found this commit
  
https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d
  - it may be related to this leak.

  

  Environment:
    Distributor ID: Ubuntu
    Description:Ubuntu 20.04.2 LTS
    Release:20.04
    Codename:   focal
    Uname:  5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 
x86_64

  Package:
    systemd:
  Installed: 245.4-4ubuntu3.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+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 1935050] [NEW] After uninstall apt autoremove removes keyring, but repo remains and throws error on 'sudo apt update'

[Alf HP Lund]

Public bug reported:

I manually added a repository to install a program (brave-browser).
After testing for a while I decided the browswer does not suit my needs
and did "sudo apt purge brave-browser", then "sudo apt autoremove".

Expected result: my system works as before, just without brave-browser.

What happened: "sudo apt autoremove" deleted the keyring of brave-
browser, but left the file /etc/apt/sources.list.d/brave-browser-
release.list

Subsequently "sudo apt update" throws these messages:

"W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
https://brave-browser-apt-release.s3.brave.com stable InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY A8580BDC82D3DC6C
W: Failed to fetch 
https://brave-browser-apt-release.s3.brave.com/dists/stable/InRelease  The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY A8580BDC82D3DC6C
W: Some index files failed to download. They have been ignored, or old ones 
used instead."

Uninstalling a program should keep the keyring if it is needed to verify
repositories. There could be an option to remove both (though I think
removing the repo while keeping the keyring would not return errors).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apt 2.0.6
ProcVersionSignature: Ubuntu 5.4.0-77.86-lowlatency 5.4.119
Uname: Linux 5.4.0-77-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Jul  8 15:04:54 2021
InstallationDate: Installed on 2021-02-07 (150 days ago)
InstallationMedia: Kubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Summary changed:

- After uninstall apt autoremove removes keyring, but repo remains and throws 
error
+ After uninstall apt autoremove removes keyring, but repo remains and throws 
error on 'sudo apt update'

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

Title:
  After uninstall apt autoremove removes keyring, but repo remains and
  throws error on 'sudo apt update'

Status in apt package in Ubuntu:
  New

Bug description:
  I manually added a repository to install a program (brave-browser).
  After testing for a while I decided the browswer does not suit my
  needs and did "sudo apt purge brave-browser", then "sudo apt
  autoremove".

  Expected result: my system works as before, just without brave-
  browser.

  What happened: "sudo apt autoremove" deleted the keyring of brave-
  browser, but left the file /etc/apt/sources.list.d/brave-browser-
  release.list

  Subsequently "sudo apt update" throws these messages:

  "W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
https://brave-browser-apt-release.s3.brave.com stable InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY A8580BDC82D3DC6C
  W: Failed to fetch 
https://brave-browser-apt-release.s3.brave.com/dists/stable/InRelease  The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY A8580BDC82D3DC6C
  W: Some index files failed to download. They have been ignored, or old ones 
used instead."

  Uninstalling a program should keep the keyring if it is needed to
  verify repositories. There could be an option to remove both (though I
  think removing the repo while keeping the keyring would not return
  errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.6
  ProcVersionSignature: Ubuntu 5.4.0-77.86-lowlatency 5.4.119
  Uname: Linux 5.4.0-77-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jul  8 15:04:54 2021
  InstallationDate: Installed on 2021-02-07 (150 days ago)
  InstallationMedia: Kubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1934505]

[Simark]

(In reply to Matthias Klose from comment #8)
> looking at a 20210706 build, the fix seems to work.  Unsure what I did wrong
> yesterday.  So the fix would be needed on the trunk and the branch.

Ok, glad to hear that!

Patch posted here: https://sourceware.org/pipermail/gdb-
patches/2021-July/180752.html

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

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

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

[Touch-packages] [Bug 1935043] [NEW] sshpass does not report file not found with -v -f, instead hangs

[Tgkprog]

Public bug reported:

Using sshpass to send a password to ssh-add

When I use a valid file path and give command :

I get the expected output
SSHPASS searching for password prompt using match "pass"
SSHPASS read: Enter passphrase for /home/tushar/.ssh/t/tgkprogOct2020: 
SSHPASS detected prompt. Sending password.
SSHPASS read: 

Identity added: /home/tushar/.ssh/t/tgkprogOct2020 (Tushar G Kapila
 tgkprog  in github, stackoverflow, twitter, fb and
other places)

But when I use :

sshpass -v -f /home/tushar/work/pwdPathDoesNotExist  -P "pass"  ssh-add
~/.ssh/t/tgkprogOct2020

Where I have mistakenly put an incorrect path or file name, it does not
report that the file does not exist, should do that first, instead if
continues with issuing the command, looks for the text marker per -P and
then tries to give it the password, and then hangs, as I guess there is
no password to give and ssh-add keeps waiting. No error or warning
emited.

Output:
SSHPASS searching for password prompt using match "pass"
SSHPASS read: Enter passphrase for /home/tushar/.ssh/t/tgkprogOct2020: 
SSHPASS detected prompt. Sending password.

* After this command does not complete, hangs here

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

** Attachment added: "Terminal screen with commands & output as described in 
bug description"
   
https://bugs.launchpad.net/bugs/1935043/+attachment/5509903/+files/Screenshot%20from%202021-07-08%2018-47-47.png

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

Title:
  sshpass does not report file not found with -v -f, instead hangs

Status in apt package in Ubuntu:
  New

Bug description:
  Using sshpass to send a password to ssh-add

  When I use a valid file path and give command :

  I get the expected output
  SSHPASS searching for password prompt using match "pass"
  SSHPASS read: Enter passphrase for /home/tushar/.ssh/t/tgkprogOct2020: 
  SSHPASS detected prompt. Sending password.
  SSHPASS read: 

  Identity added: /home/tushar/.ssh/t/tgkprogOct2020 (Tushar G Kapila
   tgkprog  in github, stackoverflow, twitter, fb and
  other places)

  But when I use :

  sshpass -v -f /home/tushar/work/pwdPathDoesNotExist  -P "pass"  ssh-
  add ~/.ssh/t/tgkprogOct2020

  Where I have mistakenly put an incorrect path or file name, it does
  not report that the file does not exist, should do that first, instead
  if continues with issuing the command, looks for the text marker per
  -P and then tries to give it the password, and then hangs, as I guess
  there is no password to give and ssh-add keeps waiting. No error or
  warning emited.

  Output:
  SSHPASS searching for password prompt using match "pass"
  SSHPASS read: Enter passphrase for /home/tushar/.ssh/t/tgkprogOct2020: 
  SSHPASS detected prompt. Sending password.

  * After this command does not complete, hangs here

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1935043/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Łukasz Zemczak]

Ok, thanks for the info! I uploaded both libqmi and libmbim to both
hirsute and focal queues. Now it needs someone to review the SRUs and
accept them (I can poke around).

I'll also modify the description to mention the additional testing that
the Certification Team will perform on the packages as it will really
make the SRU look safer. The more tests performed, the better.

Removing ubuntu-sponsors.

** Description changed:

  [Impact]
  
  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.
  
  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem
  
  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits
  
  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6
  
  The ModemManager suite in the Impish release meets the requirements.
  
  [Test Plan]
  
  = How to Reproduce the Bug =
  
  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:
  
  $ mmcli --list-modems
  No modems were found
  
  = Test Procedure =
  
  1. Install the Ubuntu system on the tested hardware
  
    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso
  
  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )
  
    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/
  
  3. Install the ModemManager suite ( for Hirsute and Focal releases )
  
    The ModemManager suite will be installed from Impish:
  
  $ sudo apt update
  $ sudo apt install modemmanager/impish
  $ sudo apt install libqmi-utils/impish
  
  4. Execute the following commands
  
  4.1 Get the run-time environment
  
  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V
  
  4.2 Check the status of the ModemManager service
  
  $ sudo systemctl status ModemManager.service
  
  4.3 List the detected modems
  
  $ mmcli --list-modems
  
  4.4 Check the modem’s status
  
  $ mmcli --modem 0
  
  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only
  )
  
  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap
  
  4.6 Enable the detected modem
  
  $ sudo mmcli --modem 0 --enable
  
  4.7 Check the modem’s status
  
  $ mmcli --modem 0
  
  = Analyze the Tested Result =
  
  1. Check if installed packages are working
  
    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.
  
  2. Check if the supported modem can be detected
  
    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.
  
  3. Check if the modem can be enabled
  
    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.
  
+ 
+ = Certification Validation =
+ 
+ Additionally to the aforementioned test cases, the Certification Team
+ will perform some coverage testing across supported devices to make sure
+ the other modems still work as expected.
+ 
  [Where problems could occur]
  
  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.
  
  [Other Info]
  
  We need to upgrade to these 3 packages (in Impish) at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6
  
  To support the mentioned 2 modems, the system needs to use kernels which 
include specific patches and  kernel config options .
  For ex., there is a patched 5.11 kernel which is working for: 
https://bugs.launchpad.net/austin/+bug/1928665/comments/7

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confi

[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Łukasz Zemczak]

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

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

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from Impish:

  $ sudo apt update
  $ sudo apt install modemmanager/impish
  $ sudo apt install libqmi-utils/impish

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.

  3. Check if the modem can be enabled

    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  [Other Info]

  We need to upgrade to these 3 packages (in Impish) at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  To support the mentioned 2 modems, the system needs to use kernels which 
include specific patches and  kernel config options .
  For ex., there is a patched 5.11 kernel which is working for: 
https://bugs.launchpad.net/austin/+bug/1928665/comments/7

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934286/+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 1934995] Re: Broken on ppc64el (toolchain bug?)

[Chris Halse Rogers]

Yeah, whatever change in dependencies causes this it goes back to
hirsute release.

Running mir 2.3.3's tests against 0.15.4-1 from the hirsute archive
works; running those tests against 0.15.4-1 rebuilt in a hirsute chroot
fails.

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

Title:
  Broken on ppc64el (toolchain bug?)

Status in umockdev package in Ubuntu:
  New

Bug description:
  umockdev appears to be broken on ppc64el in impish. Running it on one
  of Mir's umockdev-using tests results in:

  (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
  MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
  LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
  exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
  *** stack smashing detected ***: terminated
  umockdev-run: unable to propagate signal 6 to child 15833: No such process

  (You can also see this in the Mir 2.4.1-0ubuntu1 build log:
  https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
  ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

  Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
  results in those tests passing.

  Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild
  environment results in packages that do *not* pass those tests,
  suggesting a toolchain change might be responsible.

  Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
  vala 0.48.12-1 in Impish and none of these appear to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: umockdev 0.16.1-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 16:04:15 2021
  InstallationDate: Installed on 2021-06-26 (11 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: umockdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Jerry Lee]

Yes:
* there are no series-specific changes. (just one line in the change log from 
Impish)
* those are essentially straight backports to hirsute and focal

I've corrected the libmbim version to be the same as in Impish.

Thanks a lot!

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from Impish:

  $ sudo apt update
  $ sudo apt install modemmanager/impish
  $ sudo apt install libqmi-utils/impish

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.

  3. Check if the modem can be enabled

    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  [Other Info]

  We need to upgrade to these 3 packages (in Impish) at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  To support the mentioned 2 modems, the system needs to use kernels which 
include specific patches and  kernel config options .
  For ex., there is a patched 5.11 kernel which is working for: 
https://bugs.launchpad.net/austin/+bug/1928665/comments/7

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934286/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Jerry Lee]

** Description changed:

  [Impact]
  
  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.
  
  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem
  
  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits
  
  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
- * libmbim: 1.24.6
+ * libmbim: 1.24.8
  * libqmi : 1.28.6
  
  The ModemManager suite in the Impish release meets the requirements.
  
  [Test Plan]
  
  = How to Reproduce the Bug =
  
  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:
  
  $ mmcli --list-modems
  No modems were found
  
  = Test Procedure =
  
  1. Install the Ubuntu system on the tested hardware
  
    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso
  
  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )
  
    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/
  
  3. Install the ModemManager suite ( for Hirsute and Focal releases )
  
    The ModemManager suite will be installed from Impish:
  
  $ sudo apt update
  $ sudo apt install modemmanager/impish
  $ sudo apt install libqmi-utils/impish
  
  4. Execute the following commands
  
  4.1 Get the run-time environment
  
  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V
  
  4.2 Check the status of the ModemManager service
  
  $ sudo systemctl status ModemManager.service
  
  4.3 List the detected modems
  
  $ mmcli --list-modems
  
  4.4 Check the modem’s status
  
  $ mmcli --modem 0
  
  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only
  )
  
  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap
  
  4.6 Enable the detected modem
  
  $ sudo mmcli --modem 0 --enable
  
  4.7 Check the modem’s status
  
  $ mmcli --modem 0
  
  = Analyze the Tested Result =
  
  1. Check if installed packages are working
  
    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.
  
  2. Check if the supported modem can be detected
  
    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.
  
  3. Check if the modem can be enabled
  
    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.
  
  [Where problems could occur]
  
  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.
  
  [Other Info]
  
  We need to upgrade to these 3 packages (in Impish) at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6
  
  To support the mentioned 2 modems, the system needs to use kernels which 
include specific patches and  kernel config options .
  For ex., there is a patched 5.11 kernel which is working for: 
https://bugs.launchpad.net/austin/+bug/1928665/comments/7

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn 

[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Jerry Lee]

** Description changed:

  [Impact]
  
  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.
  
  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
- * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 
-  
+ * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem
+ 
  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits
  
  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.6
  * libqmi : 1.28.6
  
  The ModemManager suite in the Impish release meets the requirements.
  
  [Test Plan]
  
  = How to Reproduce the Bug =
  
  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:
  
  $ mmcli --list-modems
  No modems were found
  
- 
  = Test Procedure =
  
  1. Install the Ubuntu system on the tested hardware
  
-   The following images will be used to verify the version of the ModemManager 
suite: 
-   * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
-   * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
-   * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso
+   The following images will be used to verify the version of the ModemManager 
suite:
+   * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
+   * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
+   * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso
  
  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )
  
-   The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
-   We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/
+   The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
+   We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/
  
  3. Install the ModemManager suite ( for Hirsute and Focal releases )
  
-   The ModemManager suite will be installed from Impish:
+   The ModemManager suite will be installed from Impish:
  
  $ sudo apt update
  $ sudo apt install modemmanager/impish
  $ sudo apt install libqmi-utils/impish
- 
  
  4. Execute the following commands
  
  4.1 Get the run-time environment
  
  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V
  
  4.2 Check the status of the ModemManager service
  
  $ sudo systemctl status ModemManager.service
  
- 
  4.3 List the detected modems
  
  $ mmcli --list-modems
- 
  
  4.4 Check the modem’s status
  
  $ mmcli --modem 0
  
- 
- 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only )
+ 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only
+ )
  
  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap
  
- 
  4.6 Enable the detected modem
  
  $ sudo mmcli --modem 0 --enable
- 
  
  4.7 Check the modem’s status
  
  $ mmcli --modem 0
  
  = Analyze the Tested Result =
  
  1. Check if installed packages are working
  
-   The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
-   If the Modemmanager.service is active(running), the packages are working.
+   The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
+   If the Modemmanager.service is active(running), the packages are working.
  
  2. Check if the supported modem can be detected
  
-   The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
-   The supported modems should be listed.
+   The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
+   The supported modems should be listed.
  
  3. Check if the modem can be enabled
  
-   If the modem can be enabled, the state of the modem in the test
+   If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.
- 
  
  [Where problems could occur]
  
  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.
  
+ [Other Info]
  
- [Other Info]
-  
- We need to upgrade to these 3 packages at the same time:
+ We need to upgrade to these 3 packages (in Impish) at the same time:
  * ModemManager: 

[Touch-packages] [Bug 1925320] Autopkgtest regression report (xorg-server/2:1.20.11-1ubuntu1~20.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xorg-server 
(2:1.20.11-1ubuntu1~20.04.2) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.20-0ubuntu1 (s390x)
notepadqq/2.0.0~beta1-1build1 (armhf)
apport/2.20.11-0ubuntu27.18 (amd64)
saods9/8.1+repack-1 (amd64)
xmobar/0.29.4-2build3 (arm64)
bambam/1.0.1+dfsg-1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#xorg-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Backport packages for 20.04.3 HWE stack

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

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

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

  [What could go wrong]

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions

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

[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Łukasz Zemczak]

hm, so I sponsored the modemmanager bits, but seeing the description we
still need to get libqmi from impish into hirsute and focal + libmbim
from hirsute to focal, right? Should I prepare backports of those as
well?

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 
   
  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.6
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  
  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

The following images will be used to verify the version of the ModemManager 
suite: 
* Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
* Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
* Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

The ModemManager suite will be installed from Impish:

  $ sudo apt update
  $ sudo apt install modemmanager/impish
  $ sudo apt install libqmi-utils/impish

  
  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  
  4.3 List the detected modems

  $ mmcli --list-modems

  
  4.4 Check the modem’s status

  $ mmcli --modem 0

  
  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  
  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  
  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
The supported modems should be listed.

  3. Check if the modem can be enabled

If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  
  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  
  [Other Info]
   
  We need to upgrade to these 3 packages at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.6
  * libqmi : 1.28.6

  To support the mentioned 2 modems, the system needs to use kernels which 
include specific patches and  kernel config options .
  For ex., there is a patched 5.11 kernel which is working for: 
https://bugs.launchpad.net/austin/+bug/1928665/comments/7

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934286/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Łukasz Zemczak]

Thank you for providing the debdiffs! From what I see there are no
series-specific changes, right? So those are essentially straight
backports to hirsute and focal? Anyway, I treated those as such and
sponsored both (with slight changelog adjustments) - they are now in the
hirsute and focal Unapproved queues, waiting for SRU review.

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 
   
  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.6
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  
  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

The following images will be used to verify the version of the ModemManager 
suite: 
* Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
* Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
* Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

The ModemManager suite will be installed from Impish:

  $ sudo apt update
  $ sudo apt install modemmanager/impish
  $ sudo apt install libqmi-utils/impish

  
  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  
  4.3 List the detected modems

  $ mmcli --list-modems

  
  4.4 Check the modem’s status

  $ mmcli --modem 0

  
  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  
  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  
  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
The supported modems should be listed.

  3. Check if the modem can be enabled

If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  
  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  
  [Other Info]
   
  We need to upgrade to these 3 packages at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.6
  * libqmi : 1.28.6

  To support the mentioned 2 modems, the system needs to use kernels which 
include specific patches and  kernel config options .
  For ex., there is a patched 5.11 kernel which is working for: 
https://bugs.launchpad.net/austin/+bug/1928665/comments/7

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934286/+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/ListHel

[Touch-packages] [Bug 1833198] Re: CURL shipped with Ubuntu 18.04 contained bug #2303

[Ramonskie]

is there anyway that we can bring this bug report back to life?

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

Title:
  CURL shipped with Ubuntu 18.04  contained bug #2303

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Bionic:
  Triaged

Bug description:
  Ubuntu 18.04 
  lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS

  
  ships with cURL version ...

  apt-cache policy curl
  curl:
Installed: 7.58.0-2ubuntu3.7
Candidate: 7.58.0-2ubuntu3.7
Version table:
   *** 7.58.0-2ubuntu3.7 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.58.0-2ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  which contains bug #2303
  https://github.com/curl/curl/issues/2303

  The Ubuntu package needs to updated to take a version that contains a
  fix for this bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1833198/+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 1934995] Re: Broken on ppc64el (toolchain bug?)

[Chris Halse Rogers]

Seb has rebuilt bolt in impish, which uses umockdev for some of its
tests, and that apparently works (
https://matrix.to/#/!cVrEyzKyyNYOVfcQsb:libera.chat/$az_4Y_uIkZ02vMS6WjfQlkTvOH_ikJQTCkqRsAcOBfY?via=libera.chat&via=matrix.org&via=cooperteam.net
)

The stack-smashing backtrace implicates LTTNG, so maybe there's some
strange interaction there?

I'm not sure this is an upstream bug, as rebuilding 0.15.4 makes the
crash appear.

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

Title:
  Broken on ppc64el (toolchain bug?)

Status in umockdev package in Ubuntu:
  New

Bug description:
  umockdev appears to be broken on ppc64el in impish. Running it on one
  of Mir's umockdev-using tests results in:

  (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
  MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
  LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
  exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
  *** stack smashing detected ***: terminated
  umockdev-run: unable to propagate signal 6 to child 15833: No such process

  (You can also see this in the Mir 2.4.1-0ubuntu1 build log:
  https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
  ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

  Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
  results in those tests passing.

  Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild
  environment results in packages that do *not* pass those tests,
  suggesting a toolchain change might be responsible.

  Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
  vala 0.48.12-1 in Impish and none of these appear to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: umockdev 0.16.1-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 16:04:15 2021
  InstallationDate: Installed on 2021-06-26 (11 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: umockdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1934995] Re: Broken on ppc64el (toolchain bug?)

[Martin Pitt]

Dang, we already found a ppc64el SIGBUS issue in 0.16.0, which got fixed
in https://github.com/martinpitt/umockdev/commit/277c80243a . But this
is reported against 0.16.1 already.

There is a tiny chance that
https://github.com/martinpitt/umockdev/commit/264cabbb will magically
fix this, but otherwise this needs some investigation. I.e. not known
upstream yet.

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

Title:
  Broken on ppc64el (toolchain bug?)

Status in umockdev package in Ubuntu:
  New

Bug description:
  umockdev appears to be broken on ppc64el in impish. Running it on one
  of Mir's umockdev-using tests results in:

  (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
  MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
  LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
  exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
  *** stack smashing detected ***: terminated
  umockdev-run: unable to propagate signal 6 to child 15833: No such process

  (You can also see this in the Mir 2.4.1-0ubuntu1 build log:
  https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
  ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

  Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
  results in those tests passing.

  Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild
  environment results in packages that do *not* pass those tests,
  suggesting a toolchain change might be responsible.

  Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
  vala 0.48.12-1 in Impish and none of these appear to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: umockdev 0.16.1-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 16:04:15 2021
  InstallationDate: Installed on 2021-06-26 (11 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: umockdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1934995] [NEW] Broken on ppc64el (toolchain bug?)

[Chris Halse Rogers]

Public bug reported:

umockdev appears to be broken on ppc64el in impish. Running it on one of
Mir's umockdev-using tests results in:

(impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
*** stack smashing detected ***: terminated
umockdev-run: unable to propagate signal 6 to child 15833: No such process

(You can also see this in the Mir 2.4.1-0ubuntu1 build log:
https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
results in those tests passing.

Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild environment
results in packages that do *not* pass those tests, suggesting a
toolchain change might be responsible.

Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
vala 0.48.12-1 in Impish and none of these appear to work.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: umockdev 0.16.1-1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  8 16:04:15 2021
InstallationDate: Installed on 2021-06-26 (11 days ago)
InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
SourcePackage: umockdev
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Broken on ppc64el (toolchain bug?)

Status in umockdev package in Ubuntu:
  New

Bug description:
  umockdev appears to be broken on ppc64el in impish. Running it on one
  of Mir's umockdev-using tests results in:

  (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
  MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
  LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
  exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
  *** stack smashing detected ***: terminated
  umockdev-run: unable to propagate signal 6 to child 15833: No such process

  (You can also see this in the Mir 2.4.1-0ubuntu1 build log:
  https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
  ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

  Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
  results in those tests passing.

  Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild
  environment results in packages that do *not* pass those tests,
  suggesting a toolchain change might be responsible.

  Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
  vala 0.48.12-1 in Impish and none of these appear to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: umockdev 0.16.1-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 16:04:15 2021
  InstallationDate: Installed on 2021-06-26 (11 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: umockdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1934992] [NEW] rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x

[wdoekes]

Public bug reported:

**Problem**

  $ rsync root@focal-system:/etc/.pwd.lock . 
  ERROR: .pwd.lock failed verification -- update discarded.
  rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1816) [generator=3.2.3]


  $ rsync root@focal-system:/etc/.pwd.lock . --debug=all
  opening connection using: ssh -l root focal-system rsync --server --sender \
-e.LsfxCIvu . /etc/.pwd.lock  (10 args)
  (Client) Protocol versions: remote=31, negotiated=31
  Client negotiated checksum: xxh128
  ...


**Cause**

  focal-system# dpkg -l | grep -E 'libxxhash|rsync'
  ii  libxxhash0:amd64  0.7.3-1 amd64
  ii  rsync 3.2.3-2ubuntu1  amd64


**Why this affects only us and not more people?**

On Ubuntu/Focal, there is no rsync 3.2.3, only 3.1.3-8. But because we
need the lz4 compression support we've fetched a newer rsync (from
Groovy).

However: the rsync 3.2.3 depends on libxxhash0 0.7.1+, while in fact it
needs 0.8+.


**Details**
  
On a Ubuntu/Focal system we have installed a rsync 3.2.3 package from 
Ubuntu/Groovy because we need the lz4 compression support.


focal-system# apt-cache show rsync
Package: rsync
...
Version: 3.2.3-2ubuntu1
Depends: lsb-base, libacl1 (>= 2.2.23), libc6 (>= 2.15),
  liblz4-1 (>= 0.0~r130), libpopt0 (>= 1.14), libssl1.1 (>= 1.1.0),
  libxxhash0 (>= 0.7.1), libzstd1 (>= 1.3.8), zlib1g (>= 1:1.1.4)
...


Alongside this we had libxxhash0 0.7.3-1 from Focal:

focal-system# apt-cache policy libxxhash0
libxxhash0:
  Installed: 0.7.3-1
  Candidate: 0.7.3-1
  Version table:
 *** 0.7.3-1 500
500 http://ARCHIVE/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status


According to the dependencies, this should work. But the combination does not, 
as this quote from the rsync maintainer would tell you:
https://github.com/WayneD/rsync/issues/122#issuecomment-737690913
> Yeah, Cyan4973 could have told you that the 128-bit xxhash only
> just stabilized in its 0.8.0 release, so anything older than
> that isn't compatible.


**The fix**

As the maintainer points out, version 0.7 is not stable (= broken for
our intents and purposes) and thus not fit for use with rsync 3.2.

I would argue that it's a good idea to bump the dependency of rsync
3.2.3 on Groovy to libxxhash0>=0.8

After all, in Groovy there is a libxxhash0 0.8.0-1ubuntu1.20.10.1, so
that would not be a problem. And it would fix issues for those mixing
and matching packages.


Thanks!

Walter Doekes
OSSO B.V.


(*) possible patch:

$ diff -pu debian/control{.orig,}
--- debian/control.orig 2021-07-08 09:56:57.646861644 +0200
+++ debian/control  2021-07-08 09:57:38.499029903 +0200
@@ -8,7 +8,7 @@ Build-Depends: debhelper-compat (= 13),
libacl1-dev,
libpopt-dev,
liblz4-dev,
-   libxxhash-dev,
+   libxxhash-dev (>= 0.8),
libzstd-dev,
zlib1g-dev,
libssl-dev

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

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

Title:
  rsync 3.2.x in Groovy depends on broken libxxhash 0.7.x

Status in rsync package in Ubuntu:
  New

Bug description:
  **Problem**

$ rsync root@focal-system:/etc/.pwd.lock . 
ERROR: .pwd.lock failed verification -- update discarded.
rsync error: some files/attrs were not transferred (see previous errors)
  (code 23) at main.c(1816) [generator=3.2.3]

  
$ rsync root@focal-system:/etc/.pwd.lock . --debug=all
opening connection using: ssh -l root focal-system rsync --server --sender \
  -e.LsfxCIvu . /etc/.pwd.lock  (10 args)
(Client) Protocol versions: remote=31, negotiated=31
Client negotiated checksum: xxh128
...

  
  **Cause**

focal-system# dpkg -l | grep -E 'libxxhash|rsync'
ii  libxxhash0:amd64  0.7.3-1 amd64
ii  rsync 3.2.3-2ubuntu1  amd64

  
  **Why this affects only us and not more people?**

  On Ubuntu/Focal, there is no rsync 3.2.3, only 3.1.3-8. But because we
  need the lz4 compression support we've fetched a newer rsync (from
  Groovy).

  However: the rsync 3.2.3 depends on libxxhash0 0.7.1+, while in fact
  it needs 0.8+.

  
  **Details**

  On a Ubuntu/Focal system we have installed a rsync 3.2.3 package from 
Ubuntu/Groovy because we need the lz4 compression support.

  
  focal-system# apt-cache show rsync
  Package: rsync
  ...
  Version: 3.2.3-2ubuntu1
  Depends: lsb-base, libacl1 (>= 2.2.23), libc6 (>= 2.15),
liblz4-1 (>= 0.0~r130), libpopt0 (>= 1.14), libssl1.1 (>= 1.1.0),
libxxhash0 (>= 0.7.1), libzstd1 (>= 1.3.8), zlib1g (>= 1:1.1.4)
  ...

  
  Alongside this we had libxxhash0 0.7.3-1 from Focal:

  focal-system# apt-cache policy libxxhash0
  libxxhash0:
Installed: 0.7.3-1
Candidate: 0.7.3-1
Version table

[Touch-packages] [Bug 1933979] Re: [MIR] busybox package

[Didier Roche]

Note: this is not a full review of the busybox package but rather a
difference assessement between the busybox-static and busybox package
(as part of this request).

The binary package "busybox" is quite similar to the static one and replaces 
it. It produces a binary with the same name, linked against libc6 only.
A man page (same than the busybox-static one) is provided and a simple trigger 
for update-initramfs is in place.
There is nothing special in the control or rules files.

I think this is thus +1 on the MIR-team side. However, as discussed,
switching for some part from a statically linked, in a limited
environment where busybox-static was running to a dynamically linked,
opened one. As discussed during the MIR meeting, this would need a
security assessment.

** Changed in: busybox (Ubuntu)
 Assignee: Didier Roche (didrocks) => Ubuntu Security Team (ubuntu-security)

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

Title:
   [MIR] busybox package

Status in busybox package in Ubuntu:
  New

Bug description:
  [Availability]
  ==
  src:busybox was introduced in Dapper (2006) and has been in main since then. 
src:busybox & bin:busybox-static are in main, to be more precise. And this 
request is to promote bin:busybox from src:busybox in main, too. It only 
depends on the libc6 package, which is in main already. The package builds on 
all the architectures; is Arch:any.

  [Rationale]
  ===
  This package is to be included in our partner's cloud images, going back to 
Bionic. As cloud images are to ship only packages from main this request is to 
see that happen.

  [Security]
  ==
  The binary doesn't install services / daemons (/etc/init.d/*, /etc/init/*, 
/lib/systemd/system/*). Just ships the "busybox" binary, its docs, and a man 
page.

  [Dependencies]
  ==
  libc6, which is in main already.

  [Maintenance]
  =
  Server team.

  [Background information]
  
  Tiny utilities for small and embedded systems.

  ---
  Upstream: https://git.busybox.net/busybox/
  Launchpad page: https://launchpad.net/ubuntu/+source/busybox
  Ubuntu bugs: https://bugs.launchpad.net/ubuntu/+source/busybox
  Debian Package Tracker: https://tracker.debian.org/pkg/busybox
  Debian bugs: 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=busybox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1933979/+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 1934981] [NEW] systemctl suspend-then-hibernate attempts hybrid-sleep instead

[Robert Collins]

Public bug reported:

```
systemctl suspend-then-hibernate
Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" 
not supported
```

Note the verb change!

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: systemd 247.3-3ubuntu3
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  8 08:54:01 2021
InstallationDate: Installed on 2021-07-06 (1 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. XPS 13 9300
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/username-root ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
 [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: 
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/03/2021
dmi.bios.release: 1.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.0
dmi.board.name: 0PP9G2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9300
dmi.product.sku: 096D
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321

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


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

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

Title:
  systemctl suspend-then-hibernate attempts hybrid-sleep instead

Status in systemd package in Ubuntu:
  New

Bug description:
  ```
  systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
  ```

  Note the verb change!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 08:54:01 2021
  InstallationDate: Installed on 2021-07-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/username-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0PP9G2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321

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