date:20210302

@stgraber Thank you. I'm including the originally proposed patch in the
next systemd upload and will switch to v248 when it is out to include
the full fix. Most likely final v248 will be out in a few weeks.


** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
  in LXC

Status in lxd package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  This regresses systemd's autopkgtest because it expects the system in
  the container to reach running state, but the system ends up in
  degraded state due to the service failing.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz
  ...

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", 
line 68, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 
chars]ine'] != []

  First list contains 1 additional elements.
  First extra element 0:
  '● NetworkManager-wait-online.service loaded failed failed Network Manager 
Wait Online'

  + []
  - ['● NetworkManager-wait-online.service loaded failed failed Network Manager 
'
  -  'Wait Online']

  --
  Ran 23 tests in 4.435s
  ...

  Reproducible locally by installing n-m from -proposed, then restarting
  the system in the LXC container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1917515] Re: System doesn't boot (root device never becomes available after entering encryption passphrase) after today's Hirsute updates

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

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

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

Title:
  System doesn't boot (root device never becomes available after
  entering encryption passphrase) after today's Hirsute updates

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Note: I'm guessing that lvm2 is the most likely culprit for this
  issue, but I don't know for certain.

  After today's Hirsute upgrades, my system won't boot. The boot gets to
  the point where it asks me for the passphrase for my encrypted root
  disk, and I enter it, and then it says that it was unlocked
  successfully, and then it spins for a while, and then I get the
  message shown in the attached photo.

  When I reboot with the older pre-Hirsute kernel (5.8.0-43-generic) I
  have installed the system boots successfully, but I don't think this
  is a kernel issue per se since I didn't upgrade the kernel today and
  my system has rebooted successfully before with the Hirsute kernel I
  currently have installed.

  Note: the two kernel messages shown at the beginning of the photo are
  not relevant; they occur even when I fall back to the old kernel and
  boot successfully.

  Attached: photo of console from failed boot, list of packages that
  were upgraded today.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lvm2 2.03.11-2ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  2 14:22:26 2021
  InstallationDate: Installed on 2019-01-02 (790 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to hirsute on 2021-02-21 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC

** Changed in: systemd (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
  in LXC

Status in lxd package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  This regresses systemd's autopkgtest because it expects the system in
  the container to reach running state, but the system ends up in
  degraded state due to the service failing.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz
  ...

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", 
line 68, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 
chars]ine'] != []

  First list contains 1 additional elements.
  First extra element 0:
  '● NetworkManager-wait-online.service loaded failed failed Network Manager 
Wait Online'

  + []
  - ['● NetworkManager-wait-online.service loaded failed failed Network Manager 
'
  -  'Wait Online']

  --
  Ran 23 tests in 4.435s
  ...

  Reproducible locally by installing n-m from -proposed, then restarting
  the system in the LXC container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1913763] Re: hyperv: unable to distinguish PTP devices

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

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

Title:
  hyperv: unable to distinguish PTP devices

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

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

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

Re: [Touch-packages] [Bug 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)

2021-03-02 Thread Jarryd Keir

Hi Dan,

I will test the patch today and report back to you

Thanks,
J

On Wed, 3 Mar 2021, 5:51 am Dan Streetman, <1906...@bugs.launchpad.net>
wrote:

> @marcin-kasperski, @buehmann, @jim-photojim, @jkeir, can any of you
> please test with the build from the ppa from comment 8?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1906331
>
> Title:
>   systemd-resolve crashes fairly often (and reports various assertions)
>
> Status in systemd package in Ubuntu:
>   In Progress
> Status in systemd source package in Focal:
>   In Progress
> Status in systemd source package in Groovy:
>   In Progress
> Status in systemd source package in Hirsute:
>   In Progress
>
> Bug description:
>   [impact]
>
>   systemd-resolved crashes
>
>   [test case]
>
>   see original description; I can't reproduce so I'm relying on the
>   reporter(s) to test/verify.
>
>   [regression potential]
>
>   any regression would likely occur while processing sd_event objects,
>   which are used throughout systemd code; this could result in crashes
>   in almost any part of systemd code. However a more likely regression
>   would be leaks of sd_event objects due to failure to release the final
>   ref for an object.
>
>   [scope]
>
>   This is needed for f/g/h
>
>   This might be fixed by upstream commit
>   f814c871e65df8552a055dd887bc94b074037833; if so, that commit isn't
>   included in any systemd release yet, and so is needed in h and
>   earlier.
>
>   [other info]
>
>   I believe this is caused by a freed sd_event object that is then
>   processed and calls the on_query_timeout callback with invalid state,
>   leading to failed assertion, which causes resolved to crash; that's
>   what analysis of the crash dump appears to indicate. This may be fixed
>   by the upstream commit referenced in [scope], which takes additional
>   refs during function calls. However I haven't reproduced this myself,
>   so I'm only guessing as to the cause and solution at this point.
>
>   I'm unsure why this would not occur in bionic, but per comment 5 it
>   seems it doesn't happen in that release.
>
>   [original description]
>
>   (Tested on regularly updated Ubuntu 20.04, currently i use systemd
>   245.4-4ubuntu3.2)
>
>   I observe fairly lot of segfaults of systemd-resolve. Frequency vary
>   but … see below.
>
>   I have no clue what is the reason. Specific feature of my machine is
>   that apart from normal cable connection (to OpenWRT router) I use
>   OpenVPN for business network (and this submits specific nameserver for
>   myorg.local domain).
>
>   ~
>   $ LC_ALL=C dmesg -T --level=info | grep systemd-resolve
>   [Sun Nov 29 11:47:37 2020] systemd-resolve[1629307]: segfault at
> 190eed7bdc6 ip 7fd98f771dc9 sp 7ffc2352a100 error 4 in
> libsystemd-shared-245.so[7fd98f74c000+16e000]
>   [Sun Nov 29 11:57:27 2020] systemd-resolve[1629787]: segfault at 1f ip
> 55ab7b0cb686 sp 7fff78ce4bd0 error 4 in
> systemd-resolved[55ab7b0a4000+3e000]
>   [Sun Nov 29 12:07:37 2020] systemd-resolve[1630481]: segfault at 191 ip
> 55ca69fed91c sp 7ffc4d757dc0 error 6 in
> systemd-resolved[55ca69fc2000+3e000]
>   [Sun Nov 29 13:12:26 2020] systemd-resolve[1638829]: segfault at
> 19224162371 ip 7fc1bc9b9dc9 sp 7ffc21378170 error 4 in
> libsystemd-shared-245.so[7fc1bc994000+16e000]
>   [Sun Nov 29 13:32:57 2020] systemd-resolve[1639886]: segfault at
> 1926d8126d3 ip 7f7ed17e9dc9 sp 7ffda2cea0b0 error 4 in
> libsystemd-shared-245.so[7f7ed17c4000+16e000]
>   [Sun Nov 29 13:42:37 2020] systemd-resolve[1640246]: segfault at 61 ip
> 558d992e2686 sp 7fff08906af0 error 4 in
> systemd-resolved[558d992bb000+3e000]
>   [Sun Nov 29 15:42:26 2020] systemd-resolve[1645397]: segfault at
> 1943c92afc7 ip 7fd4c1721dc9 sp 7fff25259ce0 error 4 in
> libsystemd-shared-245.so[7fd4c16fc000+16e000]
>   [Sun Nov 29 16:02:36 2020] systemd-resolve[1646052]: segfault at
> 1947ecb3726 ip 7f1008549dc9 sp 7fff44a6db70 error 4 in
> libsystemd-shared-245.so[7f1008524000+16e000]
>   [Sun Nov 29 17:42:35 2020] systemd-resolve[1649403]: segfault at 71 ip
> 55a37fe5a686 sp 7ffd9a160440 error 4 in
> systemd-resolved[55a37fe33000+3e000]
>   [Sun Nov 29 17:52:35 2020] systemd-resolve[1649759]: segfault at
> 558d292947d0 ip 558d292947d0 sp 7ffec7ab3bf8 error 15
>   [Sun Nov 29 19:17:55 2020] systemd-resolve[1652349]: segfault at
> 558995b77cf0 ip 558995b77cf0 sp 7ffe545ae4a8 error 15
>   [Sun Nov 29 19:32:35 2020] systemd-resolve[1652640]: segfault at
> 19773c20194 ip 7f66bb529dc9 sp 7fffd7066fc0 error 4 in
> libsystemd-shared-245.so[7f66bb504000+16e000]
>   [Sun Nov 29 20:03:54 2020] systemd-resolve[1653715]: segfault at
> 197e3aee918 ip 7fdc40b51dc9 sp 7ffde484fbf0 error 4 in
> libsystemd-shared-245.so[7fdc40b2c000+16e000]
>   [Sun Nov 29 20:22:24 2020] systemd-resolve[1654540]: segfault at
> 19820a05297 ip

[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

This bug was fixed in the package apt - 2.2.1

---
apt (2.2.1) unstable; urgency=medium

  [ Julian Andres Klode ]
  * Do not require force-loopbreak on Protected packages (Closes: #983014)
  * Branch of as 2.2.y for bullseye
  * configuration: Add missing #include 
  * Remove .travis.yml, we are using GitLab CI these days
  * RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026)
  * regression fix: do require force-loopbreak for Conflicts

  [ Алексей Шилин ]
  * Russian translation update (Closes: #983348)

 -- Julian Andres Klode   Mon, 01 Mar 2021 22:27:55
+0100

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

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in apt source package in Hirsute:
  Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
  In Progress

Bug description:
  As a long-time-user of ?ubuntu, with apt-get as tool of choice for 
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'. 
  In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu 
version; just all packages including new ones. Version updates had to be 
initiated manually, and I was always asked if I really wanted the new ?ubuntu 
version. Sounds appropriate.

  Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. 
I for one consider this kind of intrusive, though. 
  It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a 
number of times earlier; just to *check* if the upgrade was on offer; but this 
is only a guess.

  In *any* case, a pop-up asking "Are you sure? Are you connected
  through an adequate pipe? Are you sitting with full batteries; better
  a power supply?" would be convenient; since I am using my PC for
  urgent duties, and didn't want to fiddle with unexpected upgrade bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:48:39 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
  VarLogDistupgradeAptlog:
   Log time: 2020-09-29 19:44:28.696289
   Log time: 2020-09-29 19:44:33.573481

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898026/+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 1915579] Re: version 2.03.11-2ubuntu1 breaks initramfs

2021-03-02 Thread Filipe Milani de Souza

** Changed in: lvm2 (Ubuntu)
 Assignee: (unassigned) => Filipe Milani de Souza (filipemilanidesouza)

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

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

Title:
  version 2.03.11-2ubuntu1 breaks initramfs

Status in lvm2 package in Ubuntu:
  In Progress

Bug description:
  I upgraded lvm2 from 2.03.07-1ubuntu4 to 2.03.11-2ubuntu1 and my
  initramfs broke. I had to manually rollback to the old version to be
  able to boot. The error was something like:

  Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait long enough?)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
  ALERT! /dev/mapper/vgubuntu-root does not exist. Dropping to a shell! 

  And there was no neither my lvm lvs, nor lvm binary on initramfs.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lvm2 2.03.07-1ubuntu4
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 13 02:42:08 2021
  InstallationDate: Installed on 2019-11-01 (469 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1915579/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

You have systemd-networkd managing only a single interface, ens3.
Whatever your problem is, it's not at all the upstream bug you linked.

** Changed in: systemd (Ubuntu Focal)
   Status: Won't Fix => Invalid

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Invalid
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

  https://github.com/systemd/systemd/pull/16982

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1917515] Re: System doesn't boot (root device never becomes available after entering encryption passphrase) after today's Hirsute updates

2021-03-02 Thread Jonathan Kamens

** Attachment added: "list of packages upgraded today from dpkg.log"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+attachment/5471986/+files/upgraded.txt

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

Title:
  System doesn't boot (root device never becomes available after
  entering encryption passphrase) after today's Hirsute updates

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Note: I'm guessing that lvm2 is the most likely culprit for this
  issue, but I don't know for certain.

  After today's Hirsute upgrades, my system won't boot. The boot gets to
  the point where it asks me for the passphrase for my encrypted root
  disk, and I enter it, and then it says that it was unlocked
  successfully, and then it spins for a while, and then I get the
  message shown in the attached photo.

  When I reboot with the older pre-Hirsute kernel (5.8.0-43-generic) I
  have installed the system boots successfully, but I don't think this
  is a kernel issue per se since I didn't upgrade the kernel today and
  my system has rebooted successfully before with the Hirsute kernel I
  currently have installed.

  Note: the two kernel messages shown at the beginning of the photo are
  not relevant; they occur even when I fall back to the old kernel and
  boot successfully.

  Attached: photo of console from failed boot, list of packages that
  were upgraded today.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lvm2 2.03.11-2ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  2 14:22:26 2021
  InstallationDate: Installed on 2019-01-02 (790 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to hirsute on 2021-02-21 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+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 1917515] [NEW] System doesn't boot (root device never becomes available after entering encryption passphrase) after today's Hirsute updates

2021-03-02 Thread Jonathan Kamens

Public bug reported:

Note: I'm guessing that lvm2 is the most likely culprit for this issue,
but I don't know for certain.

After today's Hirsute upgrades, my system won't boot. The boot gets to
the point where it asks me for the passphrase for my encrypted root
disk, and I enter it, and then it says that it was unlocked
successfully, and then it spins for a while, and then I get the message
shown in the attached photo.

When I reboot with the older pre-Hirsute kernel (5.8.0-43-generic) I
have installed the system boots successfully, but I don't think this is
a kernel issue per se since I didn't upgrade the kernel today and my
system has rebooted successfully before with the Hirsute kernel I
currently have installed.

Note: the two kernel messages shown at the beginning of the photo are
not relevant; they occur even when I fall back to the old kernel and
boot successfully.

Attached: photo of console from failed boot, list of packages that were
upgraded today.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: lvm2 2.03.11-2ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  2 14:22:26 2021
InstallationDate: Installed on 2019-01-02 (790 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: lvm2
UpgradeStatus: Upgraded to hirsute on 2021-02-21 (9 days ago)

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


** Tags: amd64 apport-bug hirsute regression-release

** Attachment added: "photo of console after failed boot"
   
https://bugs.launchpad.net/bugs/1917515/+attachment/5471982/+files/PXL_20210302_191525480.jpg

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

Title:
  System doesn't boot (root device never becomes available after
  entering encryption passphrase) after today's Hirsute updates

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Note: I'm guessing that lvm2 is the most likely culprit for this
  issue, but I don't know for certain.

  After today's Hirsute upgrades, my system won't boot. The boot gets to
  the point where it asks me for the passphrase for my encrypted root
  disk, and I enter it, and then it says that it was unlocked
  successfully, and then it spins for a while, and then I get the
  message shown in the attached photo.

  When I reboot with the older pre-Hirsute kernel (5.8.0-43-generic) I
  have installed the system boots successfully, but I don't think this
  is a kernel issue per se since I didn't upgrade the kernel today and
  my system has rebooted successfully before with the Hirsute kernel I
  currently have installed.

  Note: the two kernel messages shown at the beginning of the photo are
  not relevant; they occur even when I fall back to the old kernel and
  boot successfully.

  Attached: photo of console from failed boot, list of packages that
  were upgraded today.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lvm2 2.03.11-2ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  2 14:22:26 2021
  InstallationDate: Installed on 2019-01-02 (790 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to hirsute on 2021-02-21 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+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 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)

@marcin-kasperski, @buehmann, @jim-photojim, @jkeir, can any of you
please test with the build from the ppa from comment 8?

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

Title:
  systemd-resolve crashes fairly often (and reports various assertions)

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  systemd-resolved crashes

  [test case]

  see original description; I can't reproduce so I'm relying on the
  reporter(s) to test/verify.

  [regression potential]

  any regression would likely occur while processing sd_event objects,
  which are used throughout systemd code; this could result in crashes
  in almost any part of systemd code. However a more likely regression
  would be leaks of sd_event objects due to failure to release the final
  ref for an object.

  [scope]

  This is needed for f/g/h

  This might be fixed by upstream commit
  f814c871e65df8552a055dd887bc94b074037833; if so, that commit isn't
  included in any systemd release yet, and so is needed in h and
  earlier.

  [other info]

  I believe this is caused by a freed sd_event object that is then
  processed and calls the on_query_timeout callback with invalid state,
  leading to failed assertion, which causes resolved to crash; that's
  what analysis of the crash dump appears to indicate. This may be fixed
  by the upstream commit referenced in [scope], which takes additional
  refs during function calls. However I haven't reproduced this myself,
  so I'm only guessing as to the cause and solution at this point.

  I'm unsure why this would not occur in bionic, but per comment 5 it
  seems it doesn't happen in that release.

  [original description]

  (Tested on regularly updated Ubuntu 20.04, currently i use systemd
  245.4-4ubuntu3.2)

  I observe fairly lot of segfaults of systemd-resolve. Frequency vary
  but … see below.

  I have no clue what is the reason. Specific feature of my machine is
  that apart from normal cable connection (to OpenWRT router) I use
  OpenVPN for business network (and this submits specific nameserver for
  myorg.local domain).

  ~
  $ LC_ALL=C dmesg -T --level=info | grep systemd-resolve
  [Sun Nov 29 11:47:37 2020] systemd-resolve[1629307]: segfault at 190eed7bdc6 
ip 7fd98f771dc9 sp 7ffc2352a100 error 4 in 
libsystemd-shared-245.so[7fd98f74c000+16e000]
  [Sun Nov 29 11:57:27 2020] systemd-resolve[1629787]: segfault at 1f ip 
55ab7b0cb686 sp 7fff78ce4bd0 error 4 in 
systemd-resolved[55ab7b0a4000+3e000]
  [Sun Nov 29 12:07:37 2020] systemd-resolve[1630481]: segfault at 191 ip 
55ca69fed91c sp 7ffc4d757dc0 error 6 in 
systemd-resolved[55ca69fc2000+3e000]
  [Sun Nov 29 13:12:26 2020] systemd-resolve[1638829]: segfault at 19224162371 
ip 7fc1bc9b9dc9 sp 7ffc21378170 error 4 in 
libsystemd-shared-245.so[7fc1bc994000+16e000]
  [Sun Nov 29 13:32:57 2020] systemd-resolve[1639886]: segfault at 1926d8126d3 
ip 7f7ed17e9dc9 sp 7ffda2cea0b0 error 4 in 
libsystemd-shared-245.so[7f7ed17c4000+16e000]
  [Sun Nov 29 13:42:37 2020] systemd-resolve[1640246]: segfault at 61 ip 
558d992e2686 sp 7fff08906af0 error 4 in 
systemd-resolved[558d992bb000+3e000]
  [Sun Nov 29 15:42:26 2020] systemd-resolve[1645397]: segfault at 1943c92afc7 
ip 7fd4c1721dc9 sp 7fff25259ce0 error 4 in 
libsystemd-shared-245.so[7fd4c16fc000+16e000]
  [Sun Nov 29 16:02:36 2020] systemd-resolve[1646052]: segfault at 1947ecb3726 
ip 7f1008549dc9 sp 7fff44a6db70 error 4 in 
libsystemd-shared-245.so[7f1008524000+16e000]
  [Sun Nov 29 17:42:35 2020] systemd-resolve[1649403]: segfault at 71 ip 
55a37fe5a686 sp 7ffd9a160440 error 4 in 
systemd-resolved[55a37fe33000+3e000]
  [Sun Nov 29 17:52:35 2020] systemd-resolve[1649759]: segfault at 558d292947d0 
ip 558d292947d0 sp 7ffec7ab3bf8 error 15
  [Sun Nov 29 19:17:55 2020] systemd-resolve[1652349]: segfault at 558995b77cf0 
ip 558995b77cf0 sp 7ffe545ae4a8 error 15
  [Sun Nov 29 19:32:35 2020] systemd-resolve[1652640]: segfault at 19773c20194 
ip 7f66bb529dc9 sp 7fffd7066fc0 error 4 in 
libsystemd-shared-245.so[7f66bb504000+16e000]
  [Sun Nov 29 20:03:54 2020] systemd-resolve[1653715]: segfault at 197e3aee918 
ip 7fdc40b51dc9 sp 7ffde484fbf0 error 4 in 
libsystemd-shared-245.so[7fdc40b2c000+16e000]
  [Sun Nov 29 20:22:24 2020] systemd-resolve[1654540]: segfault at 19820a05297 
ip 7f6a92839dc9 sp 7ffe4ba00440 error 4 in 
libsystemd-shared-245.so[7f6a92814000+16e000]
  [Sun Nov 29 21:13:10 2020] systemd-resolve[1660272]: segfault at 555f9a5915e0 
ip 555f9a5915e0 sp 7fff053e5e68 error 15
  [Sun Nov 29 21:32:34 2020] systemd-resolve[1661026]: segfault at

[Touch-packages] [Bug 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/399016

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

Title:
  systemd-resolve crashes fairly often (and reports various assertions)

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  systemd-resolved crashes

  [test case]

  see original description; I can't reproduce so I'm relying on the
  reporter(s) to test/verify.

  [regression potential]

  any regression would likely occur while processing sd_event objects,
  which are used throughout systemd code; this could result in crashes
  in almost any part of systemd code. However a more likely regression
  would be leaks of sd_event objects due to failure to release the final
  ref for an object.

  [scope]

  This is needed for f/g/h

  This might be fixed by upstream commit
  f814c871e65df8552a055dd887bc94b074037833; if so, that commit isn't
  included in any systemd release yet, and so is needed in h and
  earlier.

  [other info]

  I believe this is caused by a freed sd_event object that is then
  processed and calls the on_query_timeout callback with invalid state,
  leading to failed assertion, which causes resolved to crash; that's
  what analysis of the crash dump appears to indicate. This may be fixed
  by the upstream commit referenced in [scope], which takes additional
  refs during function calls. However I haven't reproduced this myself,
  so I'm only guessing as to the cause and solution at this point.

  I'm unsure why this would not occur in bionic, but per comment 5 it
  seems it doesn't happen in that release.

  [original description]

  (Tested on regularly updated Ubuntu 20.04, currently i use systemd
  245.4-4ubuntu3.2)

  I observe fairly lot of segfaults of systemd-resolve. Frequency vary
  but … see below.

  I have no clue what is the reason. Specific feature of my machine is
  that apart from normal cable connection (to OpenWRT router) I use
  OpenVPN for business network (and this submits specific nameserver for
  myorg.local domain).

  ~
  $ LC_ALL=C dmesg -T --level=info | grep systemd-resolve
  [Sun Nov 29 11:47:37 2020] systemd-resolve[1629307]: segfault at 190eed7bdc6 
ip 7fd98f771dc9 sp 7ffc2352a100 error 4 in 
libsystemd-shared-245.so[7fd98f74c000+16e000]
  [Sun Nov 29 11:57:27 2020] systemd-resolve[1629787]: segfault at 1f ip 
55ab7b0cb686 sp 7fff78ce4bd0 error 4 in 
systemd-resolved[55ab7b0a4000+3e000]
  [Sun Nov 29 12:07:37 2020] systemd-resolve[1630481]: segfault at 191 ip 
55ca69fed91c sp 7ffc4d757dc0 error 6 in 
systemd-resolved[55ca69fc2000+3e000]
  [Sun Nov 29 13:12:26 2020] systemd-resolve[1638829]: segfault at 19224162371 
ip 7fc1bc9b9dc9 sp 7ffc21378170 error 4 in 
libsystemd-shared-245.so[7fc1bc994000+16e000]
  [Sun Nov 29 13:32:57 2020] systemd-resolve[1639886]: segfault at 1926d8126d3 
ip 7f7ed17e9dc9 sp 7ffda2cea0b0 error 4 in 
libsystemd-shared-245.so[7f7ed17c4000+16e000]
  [Sun Nov 29 13:42:37 2020] systemd-resolve[1640246]: segfault at 61 ip 
558d992e2686 sp 7fff08906af0 error 4 in 
systemd-resolved[558d992bb000+3e000]
  [Sun Nov 29 15:42:26 2020] systemd-resolve[1645397]: segfault at 1943c92afc7 
ip 7fd4c1721dc9 sp 7fff25259ce0 error 4 in 
libsystemd-shared-245.so[7fd4c16fc000+16e000]
  [Sun Nov 29 16:02:36 2020] systemd-resolve[1646052]: segfault at 1947ecb3726 
ip 7f1008549dc9 sp 7fff44a6db70 error 4 in 
libsystemd-shared-245.so[7f1008524000+16e000]
  [Sun Nov 29 17:42:35 2020] systemd-resolve[1649403]: segfault at 71 ip 
55a37fe5a686 sp 7ffd9a160440 error 4 in 
systemd-resolved[55a37fe33000+3e000]
  [Sun Nov 29 17:52:35 2020] systemd-resolve[1649759]: segfault at 558d292947d0 
ip 558d292947d0 sp 7ffec7ab3bf8 error 15
  [Sun Nov 29 19:17:55 2020] systemd-resolve[1652349]: segfault at 558995b77cf0 
ip 558995b77cf0 sp 7ffe545ae4a8 error 15
  [Sun Nov 29 19:32:35 2020] systemd-resolve[1652640]: segfault at 19773c20194 
ip 7f66bb529dc9 sp 7fffd7066fc0 error 4 in 
libsystemd-shared-245.so[7f66bb504000+16e000]
  [Sun Nov 29 20:03:54 2020] systemd-resolve[1653715]: segfault at 197e3aee918 
ip 7fdc40b51dc9 sp 7ffde484fbf0 error 4 in 
libsystemd-shared-245.so[7fdc40b2c000+16e000]
  [Sun Nov 29 20:22:24 2020] systemd-resolve[1654540]: segfault at 19820a05297 
ip 7f6a92839dc9 sp 7ffe4ba00440 error 4 in 
libsystemd-shared-245.so[7f6a92814000+16e000]
  [Sun Nov 29 21:13:10 2020] systemd-resolve[1660272]: segfault at 555f9a5915e0 
ip 555f9a5915e0 sp 7fff053e5e68 error 15
  [Sun Nov 29 21:32:34 2020] systemd-resolve[1661026]: segfault at

[Touch-packages] [Bug 1913763] Re: hyperv: unable to distinguish PTP devices

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

Title:
  hyperv: unable to distinguish PTP devices

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1917458] Re: ptp0 device under hyperv may not be correct

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

** This bug has been marked a duplicate of bug 1913763
   hyperv: unable to distinguish PTP devices

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

Title:
  ptp0 device under hyperv may not be correct

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  the /dev/ptp0 device for a hyperv instance may not be the correct,
  hyperv-provided, ptp device.

  [test case]

  on some hyperv instance types, particularly those that might contain
  passthrough network card(s) that also provide ptp, the first ptp
  device may not be the correct one to use for ptp, e.g. there may be
  multiple ones:

  $ ls /dev/ptp*
  /dev/ptp0 /dev/ptp1
  $ cat /sys/class/ptp/ptp0/clock_name
  hyperv
  $ cat /sys/class/ptp/ptp1/clock_name
  mlx5_p2p

  the order can change across boots, so a consistent way of addressing
  the hyperv-provided one is needed

  [regression potential]

  any regression would involve failure to properly create the ptp
  symlink, or other failure while udev is processing newly detected ptp
  device(s)

  [scope]

  this is needed in all releases

  this was fixed upstream with the commit
  32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
  any release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1917458/+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 1913763] Re: hyperv: unable to distinguish PTP devices

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  hyperv: unable to distinguish PTP devices

Status in systemd package in Ubuntu:
  New

Bug description:
  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1913763] Re: hyperv: unable to distinguish PTP devices

2021-03-02 Thread Matthieu Clemenceau

** Tags added: rls-hh-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/1913763

Title:
  hyperv: unable to distinguish PTP devices

Status in systemd package in Ubuntu:
  New

Bug description:
  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1916485] Re: test -x fails inside shell scripts in containers

Following all the discussions fixing the container runtimes seems to be the way 
out of this.
For runc https://github.com/opencontainers/runc/pull/2750 should be SRUd to all 
releases.

** Also affects: docker.io (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  test -x fails inside shell scripts in containers

Status in docker.io package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Triaged
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  New
Status in docker.io source package in Hirsute:
  New
Status in glibc source package in Hirsute:
  Triaged
Status in libseccomp source package in Hirsute:
  Fix Committed
Status in runc source package in Hirsute:
  New

Bug description:
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement

  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation

  The simple Dockerfile to reproduce the error - "docker build -t foo ."

  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 

  USER root

  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -

  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.

  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.

  Flo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+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 1913763] Re: hyperv: unable to distinguish PTP devices

2021-03-02 Thread Gauthier Jolly

A fix has been merged upstream:
https://github.com/systemd/systemd/pull/18811/files

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

Title:
  hyperv: unable to distinguish PTP devices

Status in systemd package in Ubuntu:
  New

Bug description:
  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1916485] Re: test -x fails inside shell scripts in containers

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

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

Title:
  test -x fails inside shell scripts in containers

Status in glibc package in Ubuntu:
  Triaged
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  New
Status in glibc source package in Hirsute:
  Triaged
Status in libseccomp source package in Hirsute:
  Fix Committed
Status in runc source package in Hirsute:
  New

Bug description:
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement

  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation

  The simple Dockerfile to reproduce the error - "docker build -t foo ."

  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 

  USER root

  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -

  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.

  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.

  Flo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916485/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2021-03-02 Thread Niv Goldenberg

I'm still getting this bug.
Following this workaround:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1874513
solve the issue for me, but I need to repeat it each time I'm connecting my
Bose Q35 II via Bluetooth.

Specs:
pulseaudio 13.99.1
Ubuntu 20.04, 5.8.0-44-generic
Lenovo Thinkpad T14 Gen1 Intel

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

Title:
External audio device shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker, or none at
all.

Bug description:
[Impact]

Selected audio output device in Settings is ignored after upgrading to
Ubuntu 20.04.

[Test Case]

Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade
to 20.04. When done, attempt to connect a Bluetooth or USB audio
device and use it via Settings.

[Regression Potential]

[Original Bug Report]

Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

Tested with 2 different BT devices (one headset and one speaker) as
well as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1915579] Re: version 2.03.11-2ubuntu1 breaks initramfs

2021-03-02 Thread Filipe Milani de Souza

Good afternoon. I am having the least problem, but the example above did
not solve my problem.

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

Title:
  version 2.03.11-2ubuntu1 breaks initramfs

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I upgraded lvm2 from 2.03.07-1ubuntu4 to 2.03.11-2ubuntu1 and my
  initramfs broke. I had to manually rollback to the old version to be
  able to boot. The error was something like:

  Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait long enough?)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
  ALERT! /dev/mapper/vgubuntu-root does not exist. Dropping to a shell! 

  And there was no neither my lvm lvs, nor lvm binary on initramfs.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lvm2 2.03.07-1ubuntu4
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 13 02:42:08 2021
  InstallationDate: Installed on 2019-11-01 (469 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1915579/+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 1917458] [NEW] ptp0 device under hyperv may not be correct

Public bug reported:

[impact]

the /dev/ptp0 device for a hyperv instance may not be the correct,
hyperv-provided, ptp device.

[test case]

on some hyperv instance types, particularly those that might contain
passthrough network card(s) that also provide ptp, the first ptp device
may not be the correct one to use for ptp, e.g. there may be multiple
ones:

$ ls /dev/ptp*
/dev/ptp0 /dev/ptp1
$ cat /sys/class/ptp/ptp0/clock_name
hyperv
$ cat /sys/class/ptp/ptp1/clock_name
mlx5_p2p

the order can change across boots, so a consistent way of addressing the
hyperv-provided one is needed

[regression potential]

any regression would involve failure to properly create the ptp symlink,
or other failure while udev is processing newly detected ptp device(s)

[scope]

this is needed in all releases

this was fixed upstream with the commit
32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
any release

** Affects: systemd (Ubuntu)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: systemd (Ubuntu Bionic)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: systemd (Ubuntu Focal)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: systemd (Ubuntu Groovy)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: systemd (Ubuntu Hirsute)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  ptp0 device under hyperv may not be correct

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  the /dev/ptp0 device for a hyperv instance may not be the correct,
  hyperv-provided, ptp device.

  [test case]

  on some hyperv instance types, particularly those that might contain
  passthrough network card(s) that also provide ptp, the first ptp
  device may not be the correct one to use for ptp, e.g. there may be
  multiple ones:

  $ ls /dev/ptp*
  /dev/ptp0 /dev/ptp1
  $ cat /sys/class/ptp/ptp0/clock_name
  hyperv
  $ cat /sys/class/ptp/ptp1/clock_name
  mlx5_p2p

  the order can change across boots, so a consistent way of addressing
  the hyperv-provided one is needed

  [regression potential]

  any regression would involve failure to properly create the ptp
  symlink, or other failure while udev is processing newly detected ptp
  device(s)

  [scope]

  this is needed in all releases

  this was fixed upstream with the commit
  32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
  any release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1917458/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

** Description changed:

+ [impact]
+ 
+ systemd-resolved emits a disturbingly large amount of NXDOMAIN log
+ messages that do not actually indicate any real problem
+ 
+ [test case]
+ 
+ see original description, or look at any log from any recent Ubuntu
+ system, or search google for endless complaints about NXDOMAIN messages
+ logged by Ubuntu
+ 
+ [regression potential]
+ 
+ any regression would likely be isolated to systemd-resolved handling of
+ a NXDOMAIN response from its upstream nameserver, including possibly
+ failing to resolve a hostname or delays in resolving hostnames
+ 
+ [scope]
+ 
+ this is needed for all releases; the patch is not upstream, but carried
+ by Ubuntu
+ 
+ [original description]
+ 
  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:
  
  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
- --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf  
+ --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
-  [connectivity]
+  [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./
  
  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This removes
  a fair amount of NXDOMAIN error noise in journalctl.
  
- 
  Observing the issue and the fix requires 3 terminals:
  
  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f
  
  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
-  => observe the NXDOMAIN noise over a couple few minutes
-  
+  => observe the NXDOMAIN noise over a couple few minutes
+ 
  Now make the hostname absolute with the trailing dot above and run:
-systemctl reload NetworkManager
+    systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:
  
  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
-  => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes
+  => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes
  
  Originally reported at https://askubuntu.com/a/1242611/117217
  
  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

** Also affects: network-manager (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

** Also affects: network-manager (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: network-manager (Ubuntu Hirsute)
   Importance: Medium
   Status: Fix Released

** Also affects: systemd (Ubuntu Hirsute)
   Importance: Wishlist
   Status: Triaged

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

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

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

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

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

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

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

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in network-manager source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in network-manager source package in Focal:
  Confirmed
Status in network-manager source package in Groovy:
  New
Status in systemd source package in Groovy:
  In Progress
Status in network-manager source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Committed

Bug description:
  [impact]

  systemd-resolved emits a disturbingly large amount of NXDOMAIN log
  messages that do not actually indicate any real problem

  [test case]

  see original description, or look at any log from any recent Ubuntu
  system, or search google for endless complaints about NXDOMAIN
  messages logged by Ubuntu

  [regression potential]

  any regression would likely be isolated to systemd-resolved handling
  of a NXDOMAIN response from its upstream nameserver, including
  possibly failing to resolve a hostname or delays in resolving
  hostnames

  [scope]

  this is needed for all releases; the patch is not upstream, but
  carried by Ubuntu

[Touch-packages] [Bug 1917451] [NEW] audacious audacious-plugins dependancy issue

2021-03-02 Thread Owen

Public bug reported:

A recent update removed audacious. When trying to add it back it I get:

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.
 audacious : Depends: libaudcore5 (= 4.0.5-1) but 4.1-1build1~ubuntu20.10 is to 
be installed
 audacious-plugins : Depends: audacious-plugins-data (= 4.0.5-1) but 
4.1-0build1~ubuntu20.10 is to be installed
E: Unable to correct problems, you have held broken packages.

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

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

Title:
  audacious audacious-plugins dependancy issue

Status in lsb package in Ubuntu:
  New

Bug description:
  A recent update removed audacious. When trying to add it back it I
  get:

  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.
   audacious : Depends: libaudcore5 (= 4.0.5-1) but 4.1-1build1~ubuntu20.10 is 
to be installed
   audacious-plugins : Depends: audacious-plugins-data (= 4.0.5-1) but 
4.1-0build1~ubuntu20.10 is to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1917451/+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 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

> As for the zoom in/out, I meant this:

that's typically done by holding "Ctrl" down and using scroll up/down to
zoom.

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

Title:
  Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103:
  Invalid argument

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel
  5.4.0-42-generic on Dell Latitude E6440.  Upon examining the output of
  journalctl -b, I see this:

  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Show Plymouth Boot Screen being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Forward Password Requests to Plymouth Directory Watch being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Set Up Additional Binary Formats being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
File System Check on Root Device being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Rebuild Hardware Database being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Platform Persistent Storage Archival being skipped.
  Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized
  Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 
524288, num gpu pages 524288
  Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn 
acpi driver for receiving events
  Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to 
call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
  Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to 
call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument

  "Invalid argument" means that something goes wrong there, and I don't know 
what it is.
  On my laptop, event8 seems to be keyboard-related:

  $ sudo cat /proc/bus/input/devices | grep -C 5 event8
  I: Bus=0003 Vendor=045e Product=00db Version=0111
  N: Name="Microsoft Natural® Ergonomic Keyboard 4000"
  P: Phys=usb-:00:14.0-13.1/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9
  U: Uniq=
  H: Handlers=sysrq kbd event8 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdff3cf fffe
  B: MSC=10
  B: LED=107

  The issue report
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is
  probably related but marked as a duplicate of a no longer existing
  issue report (#1750855).

  The report
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415
  describes a similar issue for older kernels; the differences pertain
  to error message, error code, input..., and, opposed to #19 there, I
  have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine
  is not a dual-boot machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+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 1915579] Re: version 2.03.11-2ubuntu1 breaks initramfs

2021-03-02 Thread Bruno Redondi

The new version of lvm sets wrong file permissions to 
/usr/share/initramfs-tools/hooks/lvm2
This file should have 755 permission but after the upgrade it has 644.
If you "sudo chmod 755 /usr/share/initramfs-tools/hooks/lvm2 && sudo 
update-initramfs -u" the system will boot correctly.

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

Title:
  version 2.03.11-2ubuntu1 breaks initramfs

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I upgraded lvm2 from 2.03.07-1ubuntu4 to 2.03.11-2ubuntu1 and my
  initramfs broke. I had to manually rollback to the old version to be
  able to boot. The error was something like:

  Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait long enough?)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
  ALERT! /dev/mapper/vgubuntu-root does not exist. Dropping to a shell! 

  And there was no neither my lvm lvs, nor lvm binary on initramfs.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lvm2 2.03.07-1ubuntu4
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 13 02:42:08 2021
  InstallationDate: Installed on 2019-11-01 (469 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1915579/+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 1915579] Re: version 2.03.11-2ubuntu1 breaks initramfs