[Touch-packages] [Bug 1971474] Re: SRU: Update gdb to the final 12.1 release in 22.04 LTS

[Brian Murray]

** Tags added: rls-jj-incoming

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

Title:
  SRU: Update gdb to the final 12.1 release in 22.04 LTS

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with
  the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes
  up to the final release are:

   - updated gnulib library
   - Fix for PR mi/29002 (Windows only)
   - gdb: fix 'remote show FOO-packet' aliases
   - various testsuite fixes
   - fixing compiler warnings
   - Fix bug in Ada number lexing
   - Remove "Ada Settings" node from the manual
   - Handle TLS variable lookups when using separate debug files.
   - PR 28980: gdb: don't copy entirely optimized out values in value_copy
   - gdb/mi: fix use after free of frame_info causing spurious notifications

  Comparing the test results between the two builds doesn't show any
  regression on any architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474/+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 1973747] Re: Please Flatpak by default

[Brian Murray]

** Package changed: ubuntu => ubuntu-meta (Ubuntu)

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

Title:
  Please Flatpak by default

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,
  First, thank you for your hard work on Ubuntu!

  Adding Flatpak could make the user experience easier and better for
  new users, and it has much more apps than Snap has.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1973747/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

Has anybody encountered this recently when upgrading a fully update to
date Focal system to Jammy?

** Changed in: dbus (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1972115] Re: ubuntu-bug exits after dialog instead of sending data

[Brian Murray]

>From #ubuntu-meeting on 2022-05-12:

08:24 < ubottu> Bug 1972115 in apport (Ubuntu) 
"ubuntu-bug  exits after 
dialog instead of sending data" 
[Undecided, New] 
https://launchpad.net/bugs/1972115
08:25 < bdmurray> I think that's of Low importance given 
  its been like that forever
08:25 < bdmurray> Having said that Launchpad is the only 
  way to have a conversation with a 
  crash reporter at this point in time
08:25 < bdmurray> So it might be nice
08:25 < bdrung> would it make sense to have two options 
in that case "send" and "create bug 
report"?
08:26 < bdmurray> I wouldn't want it to be that 
  accessible and have everyone clicking 
  "create bug report".
08:27 < bdrung> so then maybe a command line parameter 
to enable it?
08:28 < bdmurray> If somebody deliberately runs 
  ubuntu-bug with a crash file it should 
  go to both.
08:28 < bdmurray> Or a command line parameter.
08:28 < bdmurray> Anyway, let's go ahead and card this.

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

** Also affects: apport (Ubuntu Kinetic)
   Importance: Low
   Status: New

** Changed in: apport (Ubuntu Jammy)
   Importance: Undecided => Low

** Tags removed: rls-jj-incoming

** Tags added: fr-2372

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

Title:
  ubuntu-bug  exits after dialog instead of sending data

Status in apport package in Ubuntu:
  New
Status in apport source package in Jammy:
  New
Status in apport source package in Kinetic:
  New

Bug description:
  After a gnome-shell crash, I am trying to manually submit it by
  running 'ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash'.  This
  results in an apport-gtk prompt asking me "Send problem report to the
  developers?"  When I click 'send', the dialog disappears and ubuntu-
  bug exits, without uploading data to launchpad or interfacing with the
  browser.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1972115/+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 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level

[Brian Murray]

** Tags added: fr-2369

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

Title:
  [openssl3] please sync openssl.cnf to ease changing security level

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Jammy:
  Confirmed
Status in openssl source package in Kinetic:
  Confirmed
Status in openssl package in Debian:
  Fix Released

Bug description:
  openssl.cnf as provided misses some directive, which make it a bit
  difficult to change security level, which since openssl 3 disables
  SHA1 signatures.

  See also this Debian bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1010360 and the committed fix:
  
https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4

  Can you please sync this change in Ubuntu openssl?

  This way one should just add a single directive to change the security
  level.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+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 1973149] Re: system uses merged-usr-via-aliased-dirs, going behind dpkg's back, breaking its core assumptions

[Brian Murray]

** Tags removed: rls-kk-incoming

** Also affects: dpkg (Ubuntu Kinetic)
   Importance: Undecided
   Status: Triaged

** Also affects: systemd (Ubuntu Kinetic)
   Importance: Undecided
   Status: Invalid

** Tags added: fr-2370

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

Title:
  system uses merged-usr-via-aliased-dirs, going behind dpkg's  back,
  breaking its core assumptions

Status in dpkg package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid
Status in dpkg source package in Kinetic:
  Triaged
Status in systemd source package in Kinetic:
  Invalid

Bug description:
  Got this warning on Kinetic, Mate flavor:

  Paramétrage de dpkg (1.21.7ubuntu3) ...
  dpkg: warning:

   This system uses merged-usr-via-aliased-dirs, going behind dpkg's
  back, breaking its core assumptions. This can cause silent file
  overwrites and disappearances, and its general tools misbehavior.

   See .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  Package: dpkg 1.21.7ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Tags: kinetic package-from-proposed third-party-packages
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1973149/+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 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level

[Brian Murray]

** Also affects: openssl (Ubuntu Kinetic)
   Importance: Medium
   Status: Confirmed

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

** Changed in: openssl (Ubuntu Jammy)
   Importance: Undecided => Medium

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

** Tags removed: rls-jj-incoming rls-kk-incoming

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

Title:
  [openssl3] please sync openssl.cnf to ease changing security level

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Jammy:
  Confirmed
Status in openssl source package in Kinetic:
  Confirmed
Status in openssl package in Debian:
  Fix Released

Bug description:
  openssl.cnf as provided misses some directive, which make it a bit
  difficult to change security level, which since openssl 3 disables
  SHA1 signatures.

  See also this Debian bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1010360 and the committed fix:
  
https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4

  Can you please sync this change in Ubuntu openssl?

  This way one should just add a single directive to change the security
  level.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+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 1972115] Re: ubuntu-bug exits after dialog instead of sending data

[Brian Murray]

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

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

Title:
  ubuntu-bug  exits after dialog instead of sending data

Status in apport package in Ubuntu:
  New

Bug description:
  After a gnome-shell crash, I am trying to manually submit it by
  running 'ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash'.  This
  results in an apport-gtk prompt asking me "Send problem report to the
  developers?"  When I click 'send', the dialog disappears and ubuntu-
  bug exits, without uploading data to launchpad or interfacing with the
  browser.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1972115/+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 1971425] Re: The "look" cli dictionary only sees capitalized words

[Brian Murray]

** Tags removed: rls-jj-incoming

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

Title:
  The "look" cli dictionary only sees capitalized words

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04;
  ~ > look accident
  accident
  accident's
  accidental
  accidental's
  accidentally
  accidentals
  accidents
  In Ubuntu 22.04;
  ~ > look accident
  (nothing)
  ~ > look acc
  Accenture
  Accenture's
  Accra
  Accra's
  Digging deeper; the dictionary at /usr/share/dict/words seems OK.
  If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it 
works;
  ~ > ./look accident
  accident
  accidental
  accidentally
  accidental's
  accidentals
  accident's
  accidents

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bsdextrautils 2.37.2-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue May  3 14:19:57 2022
  InstallationDate: Installed on 2018-09-07 (1334 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level

[Brian Murray]

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

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

Title:
  [openssl3] please sync openssl.cnf to ease changing security level

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

Bug description:
  openssl.cnf as provided misses some directive, which make it a bit
  difficult to change security level, which since openssl 3 disables
  SHA1 signatures.

  See also this Debian bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1010360 and the committed fix:
  
https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4

  Can you please sync this change in Ubuntu openssl?

  This way one should just add a single directive to change the security
  level.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+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 1618522] Re: netplan does not generates .network files just for ethernet

[Brian Murray]

** Tags removed: rls-kk-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/1618522

Title:
  netplan does not generates .network files just for ethernet

Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  On my pi3 I have an image with the ubuntu-core snap rev 354 and I get
  the following netplan configuration file after the first boot:

  ubuntu@localhost:~$ cat /etc/netplan/00-initial-config.yaml
  network:
   version: 2
   ethernets:
     all:
  match:
   name: "*"
  dhcp4: true

  This generates the following .networkd file

  ubuntu@localhost:~$ cat /run/systemd/network/10-netplan-all.network
  [Match]
  Name=*

  [Network]
  DHCP=ipv4

  If I look now at the output of networkctl I see it also tries to
  manage my mlan0 device which is a WiFi one and should be managed
  according to the netplan rule:

  ubuntu@localhost:~$ networkctl
  IDX LINK TYPE   OPERATIONAL SETUP
    1 lo   loopback   carrier configured
    5 eth1 ether  no-carrier  configuring
    6 eth0 ether  routableconfigured
    7 mlan0wlan   no-carrier  configuring

  In summary, the networkd generator inside netplan currently does not
  limit the generated .network file to tell networkd to only look at
  ethernet devices but rather tell it to control every device available
  on the system.

  Expectation: Specifying a wildcard rule in a netplan configuration
  file for ethernet devices should tell the configured networking system
  to only consider ethernet devices and nothing else.

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

[Brian Murray]

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

Title:
  aborted (core dumped) when using ConnectTimeout > 2147483

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Focal:
  Fix Released
Status in openssh source package in Impish:
  Fix Committed
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the
  ssh client to crash. This happens due to an integer overflow which was
  fixed upstream with the patch being proposed for this SRU, which caps
  the effective value for that option at INT_MAX/1000.

  While use cases triggering the bug may be uncommon, the patch is
  straightforward and the fix could be staged for the next time an
  upload is needed.

  
  [Test Plan]

  Running

  ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max =
  int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost

  triggers the error. In this case, the ssh client will crash and

  Aborted

  will be printed to stderr.

  By applying the proposed fix, running the same command should allow
  the ssh connection to proceed to the authentication steps.

  [Where problems could occur]

  Most problems would manifest due to rebuilding the package (e.g.,
  dependency changes). Since this proposal is to stage these SRUs, such
  risk is being deferred to be shared with the next, more critical,
  upload.

  [Other Info]
   
  All the SRUs proposed here should be staged due to the low priority nature of 
the bug.

  [Original bug report]

  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.

  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 
docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1

  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.

  What happened:

  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1903516/+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 1966591] Update Released

[Brian Murray]

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

Title:
  ssh-keygen -R changes known_hosts file permissions (mode)

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Focal:
  Fix Released
Status in openssh source package in Impish:
  Fix Released
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  When using "ssh-keygen -R" to remove a host from "known_hosts" the
  command changes permissions on the file.  This can cause problems
  particularly when used on the global "known_hosts" file
  (/etc/ssh/ssh_known_hosts), because then only root can read it.
  Programs running non-interactively as non-root users suddenly fail to
  SSH and it's not immediately obvious why.

  [Test Plan]

  The problem happens on Bionic and Focal.

  $ lxc launch ubuntu-daily:focal openssh-bug1966591
  $ lxc shell openssh-bug1966591
  # ssh-keyscan github.com > test_known_hosts
  # chmod 644 test_known_hosts
  # ssh-keygen -R github.com -f test_known_hosts
  # stat test_known_hosts
  ...
  Access: (0600/-rw---) ...
  ...

  [Where problems could occur]

  The upstream patch is very simple and it is unlikely that it will
  cause any regressions.  An indirect problem that could occur is that
  users might expect to see a more strict set of permissions on a
  "known_hosts" file after using "ssh-keygen -R", but arguably this is
  not defined behaviour and should not be relied upon.  Of course, there
  is always a (very) small risk of introducing problems when rebuilding
  packages using newer versions of its dependencies (especially on
  Bionic, because it's older).

  [Original Description]

  When I use ssh-keygen -R to remove a host from known_hosts it changes
  permissions on the file. This causes problems particularly when used
  on the global known hosts file (/etc/ssh/ssh_known_hosts), because
  then only root can read it. Programs running non-interactively as non-
  root users suddenly fail to SSH and it's not immediately obvious why.

  To reproduce:

  $ ssh-keyscan github.com >test_known_hosts
  $ chmod 741 test_known_hosts
  $ ssh-keygen -R github.com -f test_known_hosts
  $ stat test_known_hosts
  ...
  Access: (0600/-rw---) ...

  Expected behavior: file permissions remain unchanged (mode 0741 in
  this example).

  $ lsb_release -rd
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04

  $ apt-cache policy openssh-client
  openssh-client:
    Installed: 1:7.6p1-4ubuntu0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1966591/+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 1966591] Re: ssh-keygen -R changes known_hosts file permissions (mode)

[Brian Murray]

Please investigate the gvfs autopkgtests failures for impish and focal
as these are blocking the release of openssh for those releases and
subsequently the release for bionic too.

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

Title:
  ssh-keygen -R changes known_hosts file permissions (mode)

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Impish:
  Fix Released
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  When using "ssh-keygen -R" to remove a host from "known_hosts" the
  command changes permissions on the file.  This can cause problems
  particularly when used on the global "known_hosts" file
  (/etc/ssh/ssh_known_hosts), because then only root can read it.
  Programs running non-interactively as non-root users suddenly fail to
  SSH and it's not immediately obvious why.

  [Test Plan]

  The problem happens on Bionic and Focal.

  $ lxc launch ubuntu-daily:focal openssh-bug1966591
  $ lxc shell openssh-bug1966591
  # ssh-keyscan github.com > test_known_hosts
  # chmod 644 test_known_hosts
  # ssh-keygen -R github.com -f test_known_hosts
  # stat test_known_hosts
  ...
  Access: (0600/-rw---) ...
  ...

  [Where problems could occur]

  The upstream patch is very simple and it is unlikely that it will
  cause any regressions.  An indirect problem that could occur is that
  users might expect to see a more strict set of permissions on a
  "known_hosts" file after using "ssh-keygen -R", but arguably this is
  not defined behaviour and should not be relied upon.  Of course, there
  is always a (very) small risk of introducing problems when rebuilding
  packages using newer versions of its dependencies (especially on
  Bionic, because it's older).

  [Original Description]

  When I use ssh-keygen -R to remove a host from known_hosts it changes
  permissions on the file. This causes problems particularly when used
  on the global known hosts file (/etc/ssh/ssh_known_hosts), because
  then only root can read it. Programs running non-interactively as non-
  root users suddenly fail to SSH and it's not immediately obvious why.

  To reproduce:

  $ ssh-keyscan github.com >test_known_hosts
  $ chmod 741 test_known_hosts
  $ ssh-keygen -R github.com -f test_known_hosts
  $ stat test_known_hosts
  ...
  Access: (0600/-rw---) ...

  Expected behavior: file permissions remain unchanged (mode 0741 in
  this example).

  $ lsb_release -rd
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04

  $ apt-cache policy openssh-client
  openssh-client:
    Installed: 1:7.6p1-4ubuntu0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1966591/+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 1973032] Re: Can't report a bug anymore

[Brian Murray]

When you run ubuntu-bug does it create a file in /var/crash ? If so can
you please add it to this bug report?  Thanks in advance.

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

Title:
  Can't report a bug anymore

Status in apport package in Ubuntu:
  New

Bug description:
  Hi guy's!

  I got some GPU lock-ups or freezes today an last weekend and want to
  report it (x-org). But every time I go through ubuntu-bug it says at
  the end, that the bug can't be reported because it isn't a official
  release and I have to uninstall all 3rd party packages first.

  I have no idea what's wrong. I'm using Ubuntu 20.04.3 LTS with Kernel
  5.4.0-97-generic and the latest Nvidia 510.60.02 GPU driver.

  If you need some more informations please tell me.

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

[Brian Murray]

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

Title:
  [SRU] Enable support for Zed Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Released

Bug description:
  Please add support for:

     cloud-archive:zed
     cloud-archive:zed-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the zed cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:zed
  sudo add-apt-repository cloud-archive:zed-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970244/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

[Brian Murray]

Hello Marco, or anyone else affected,

Accepted libnotify into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libnotify/0.7.9-1ubuntu3.20.04.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-
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: libnotify (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 libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/1802483

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  Fix Released
Status in libnotify source package in Focal:
  Fix Committed
Status in libnotify source package in Jammy:
  Fix Committed

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap (or install it from the attached files to this bug):
    git clone https://github.com/3v1n0/notify-send-test-snap
    snapcraft prime
    snap try prime

  To use the pre-built snap 
(https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7)
    snap install --dangerous notify-send-test-snap_*.snap

  Check that icons are shown when launching:
    notify-send-test-snap
    notify-send-test-snap.image-path
notify-send-test-snap.image-uri

  Ensure that desktop entry is correctly sent, monitoring the dbus
  session:

   In a terminal:
     dbus-monitor --session --monitor 
"interface='org.freedesktop.Notifications'"

   In the other:
     notify-send-test-snap.desktop-entry
     notify-send-test-snap.desktop-entry-explicit-id
     notify-send-test-snap.desktop-entry-explicit-file-name
     notify-send-test-snap.desktop-entry-explicit-path
     notify-send-test-snap.desktop-entry-explicit-uri
     notify-send-test-snap.desktop-entry-explicit-snapped-uri

  The
   `desktop-entry` value sent to dbus should be either:
     - A `notify-send-test-snap_`-prefixed desktop ID
     - A .desktop file path (readable from both inside and outside the snap)
     - A .desktop file uri (readable from both inside and outside the snap)

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1970647] Re: notify-send exit code doesn't match result

[Brian Murray]

Hello Marco, or anyone else affected,

Accepted libnotify into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libnotify/0.7.9-1ubuntu3.20.04.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-
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: libnotify (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 libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/1970647

Title:
  notify-send exit code doesn't match result

Status in libnotify package in Ubuntu:
  Fix Released
Status in libnotify source package in Focal:
  Fix Committed
Status in libnotify source package in Jammy:
  Fix Committed

Bug description:
  No error exit code is returned by notify-send on failure

  [ Test case ]

  1. Run:
 jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error
  2. In a terminal "error" should be printed

  [ Regression potential ]

  Programs relying on notify-send may have errors when they did not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 1747499] Please test proposed package

[Brian Murray]

Hello Andreas, or anyone else affected,

Accepted unattended-upgrades into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/unattended-
upgrades/2.3ubuntu0.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-
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.

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Focal:
  Fix Committed
Status in update-notifier source package in Focal:
  Fix Committed

Bug description:
  
  [Impact]

   * If a system is using canonical livepatch, has it enabled, and
  patches are applied, it could be confusing for a user to receive a
  "system restart required" messages in the MOTD when logging in.

   * Livepatch is available on LTS releases. Thus, the users can be
  confused following a kernel update on 20.04.

   * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
  Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.

  [Test Plan]

   * how to reproduce the bug:

 1. Install and boot a 20.04 server VM
 2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
 3. Enable Livepatch using the following command:
 $ ua attach # replace  by an actual contract token
 4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
 5. Upon logging in again, the motd will show ***System restart required***.

   * other testing appropriate to perform before landing this update:

* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.

  [Where problems could occur]

   * The change updates a hook script in /etc/kernel/postinst.d/.
  Scripts in this directory are executing when upgrading / installing a
  kernel. If somehow the script is broken, it can prevent dpkg for
  succeeding when upgrading / installing the kernel.

   * If the implementation is wrong, we might end up "losing" the
  ***System restart required*** message when livepatch is disabled

  [Original bug description]

  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

[Brian Murray]

Hello Andreas, or anyone else affected,

Accepted update-notifier into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.192.30.11 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: update-notifier (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

** Changed in: unattended-upgrades (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Focal:
  Fix Committed
Status in update-notifier source package in Focal:
  Fix Committed

Bug description:
  
  [Impact]

   * If a system is using canonical livepatch, has it enabled, and
  patches are applied, it could be confusing for a user to receive a
  "system restart required" messages in the MOTD when logging in.

   * Livepatch is available on LTS releases. Thus, the users can be
  confused following a kernel update on 20.04.

   * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
  Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.

  [Test Plan]

   * how to reproduce the bug:

 1. Install and boot a 20.04 server VM
 2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
 3. Enable Livepatch using the following command:
 $ ua attach # replace  by an actual contract token
 4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
 5. Upon logging in again, the motd will show ***System restart required***.

   * other testing appropriate to perform before landing this update:

* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.

  [Where problems could occur]

   * The change updates a hook script in /etc/kernel/postinst.d/.
  Scripts in this directory are executing when upgrading / installing a
  kernel. If somehow the script is broken, it can prevent dpkg for
  succeeding when upgrading / installing the kernel.

   * If the implementation is wrong, we might end up "losing" the
  ***System restart required*** message when livepatch is disabled

  [Original bug description]

  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+s

[Touch-packages] [Bug 1971895] Re: Warning messages from stat printed on installation with no user crontabs

[Brian Murray]

** Tags added: regression-security

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

Title:
  Warning messages from stat printed on installation with no user
  crontabs

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  On installation of cron on a new system, or (I expect) an upgrade with
  no user crontab files the following is printed:

  Setting up cron (3.0pl1-128.1ubuntu1.1) ...
  stat: cannot stat '*': No such file or directory
  stat: cannot stat '*': No such file or directory
  stat: cannot stat '*': No such file or directory
  Warning: * is not a regular file!

  This is related to the fix for CVE-2017-9525 introduced in
  3.0pl1-128.1ubuntu1.1. The for loop at line 66 of cron.postinst needs
  to have a guard like the following added to it:

  [ "$tab_name" = "*" ] && continue

  We have observed this with Bionic, I haven't checked any other Ubuntu
  releases.

  Cheers,
  Andrew

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1971895/+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 1969934] Please test proposed package

[Brian Murray]

Hello Jeremy, or anyone else affected,

Accepted evolution-data-server into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/evolution-data-
server/3.44.1-0ubuntu2 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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1969934

Title:
  Update evolution-data-server to 3.44.1

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series (corresponding with GNOME 42).

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.1/NEWS

  It is required to update evolution to 3.44.1 (LP: #1969935)

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+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 1966179] Update Released

[Brian Murray]

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

Title:
  The airplane hotkey does not work on lots of HP platforms

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

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  [Where problems could occur]
  If we don't have whitelist in focal and impish, then the airplane key won't 
work on new HP platforms.

  Please refer to Bug #1955997 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966179/+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 1966179] Re: The airplane hotkey does not work on lots of HP platforms

[Brian Murray]

** Changed in: systemd (Ubuntu Impish)
   Status: Incomplete => 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/1966179

Title:
  The airplane hotkey does not work on lots of HP platforms

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

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  [Where problems could occur]
  If we don't have whitelist in focal and impish, then the airplane key won't 
work on new HP platforms.

  Please refer to Bug #1955997 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966179/+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 1971005] Re: locate returns nothing

[Brian Murray]

What file system are you using for your / partition?

** Package changed: findutils (Ubuntu) => plocate (Ubuntu)

** Changed in: plocate (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  locate returns nothing

Status in plocate package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 22.04 LTS I found locate command not operable. For
  example:

  locate fstab

  returns nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: findutils 4.8.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Apr 30 01:08:18 2022
  InstallationDate: Installed on 2019-04-13 (1112 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: findutils
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plocate/+bug/1971005/+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 1971158] Re: ssh connect to server stop on "SSH2_MSG_KEXINIT sent"

[Brian Murray]

This is documented in the release note for Jammy Jellyfish
(https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668):

ssh-rsa is now disabled by default in OpenSSH 237.

The release notes also contain a link to a way to continue connetcing to
servers configured with ssh-rsa.

** Changed in: openssh (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  ssh connect to server  stop on "SSH2_MSG_KEXINIT sent"

Status in openssh package in Ubuntu:
  Won't Fix

Bug description:
  After upgrade on Ubuntu 22.04 i can't connect to several servers. Connecting 
stopped on  SSH2_MSG_KEXINIT sent
  ```
   ssh -vvv -o KexAlgorithms=diffie-hellman-group-exchange-sha256 
-oHostKeyAlgorithms=+ssh-rsa  -X vld@sansa
  OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022
  debug1: Reading configuration data /home/ruslan/.ssh/config
  debug3: kex names ok: [diffie-hellman-group1-sha1]
  debug3: kex names ok: 
[diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1]
  debug3: kex names ok: [diffie-hellman-group1-sha1]
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> 
'/home/ruslan/.ssh/known_hosts'
  debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> 
'/home/ruslan/.ssh/known_hosts2'
  debug2: resolving "sansa" port 22
  debug3: resolve_host: lookup sansa:22
  debug3: ssh_connect_direct: entering
  debug1: Connecting to sansa [172.16.xx.xx] port 22.
  debug3: set_sock_tos: set socket 3 IP_TOS 0x10
  debug1: Connection established.
  debug1: identity file /home/ruslan/.ssh/id_rsa type -1
  debug1: identity file /home/ruslan/.ssh/id_rsa-cert type -1
  debug1: identity file /home/ruslan/.ssh/id_ecdsa type -1
  debug1: identity file /home/ruslan/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/ruslan/.ssh/id_ecdsa_sk type -1
  debug1: identity file /home/ruslan/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /home/ruslan/.ssh/id_ed25519 type -1
  debug1: identity file /home/ruslan/.ssh/id_ed25519-cert type -1
  debug1: identity file /home/ruslan/.ssh/id_ed25519_sk type -1
  debug1: identity file /home/ruslan/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /home/ruslan/.ssh/id_xmss type -1
  debug1: identity file /home/ruslan/.ssh/id_xmss-cert type -1
  debug1: identity file /home/ruslan/.ssh/id_dsa type -1
  debug1: identity file /home/ruslan/.ssh/id_dsa-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3
  debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
  debug1: compat_banner: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c02
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to sansa:22 as 'vld'
  debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or 
directory
  debug3: order_hostkeyalgs: no algorithms matched; accept original
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent

  
  ```
  I'm checking connection on old version Ubuntu 20.04, it's working. Remote 
server use 
  KexAlgorithms=diffie-hellman-group-exchange-sha256 and 
HostKeyAlgorithms=ssh-rsa

  On Ubuntu 21.04 ssh was work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1971158/+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 1971425] Re: The "look" cli dictionary only sees capitalized words

[Brian Murray]

Curiously some words starting with b seem fine:

 $ look butter
butter
buttercup
buttercup's
buttercups
buttered
butterfat
..


** Tags added: rls-jj-incoming

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

Title:
  The "look" cli dictionary only sees capitalized words

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04;
  ~ > look accident
  accident
  accident's
  accidental
  accidental's
  accidentally
  accidentals
  accidents
  In Ubuntu 22.04;
  ~ > look accident
  (nothing)
  ~ > look acc
  Accenture
  Accenture's
  Accra
  Accra's
  Digging deeper; the dictionary at /usr/share/dict/words seems OK.
  If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it 
works;
  ~ > ./look accident
  accident
  accidental
  accidentally
  accidental's
  accidentals
  accident's
  accidents

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bsdextrautils 2.37.2-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue May  3 14:19:57 2022
  InstallationDate: Installed on 2018-09-07 (1334 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 1970244] Re: [SRU] Enable support for Zed Cloud Archive

[Brian Murray]

Hello Corey, or anyone else affected,

Accepted software-properties into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.22.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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: software-properties (Ubuntu Jammy)
   Status: New => Fix Committed

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

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

Title:
  [SRU] Enable support for Zed Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Committed

Bug description:
  Please add support for:

     cloud-archive:zed
     cloud-archive:zed-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the zed cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:zed
  sudo add-apt-repository cloud-archive:zed-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970244/+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 1970647] Re: notify-send exit code doesn't match result

[Brian Murray]

Hello Marco, or anyone else affected,

Accepted libnotify into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libnotify/0.7.9-3ubuntu5.22.04.1 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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: libnotify (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Title:
  notify-send exit code doesn't match result

Status in libnotify package in Ubuntu:
  Fix Released
Status in libnotify source package in Focal:
  In Progress
Status in libnotify source package in Jammy:
  Fix Committed

Bug description:
  No error exit code is returned by notify-send on failure

  [ Test case ]

  1. Run:
 jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error
  2. In a terminal "error" should be printed

  [ Regression potential ]

  Programs relying on notify-send may have errors when they did not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

[Brian Murray]

Hello Marco, or anyone else affected,

Accepted libnotify into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libnotify/0.7.9-3ubuntu5.22.04.1 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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: libnotify (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  Fix Released
Status in libnotify source package in Focal:
  In Progress
Status in libnotify source package in Jammy:
  Fix Committed

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap (or install it from the attached files to this bug):
    git clone https://github.com/3v1n0/notify-send-test-snap
    snapcraft prime
    snap try prime

  To use the pre-built snap 
(https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7)
    snap install --dangerous notify-send-test-snap_*.snap

  Check that icons are shown when launching:
    notify-send-test-snap
    notify-send-test-snap.image-path
notify-send-test-snap.image-uri

  Ensure that desktop entry is correctly sent, monitoring the dbus
  session:

   In a terminal:
     dbus-monitor --session --monitor 
"interface='org.freedesktop.Notifications'"

   In the other:
     notify-send-test-snap.desktop-entry
     notify-send-test-snap.desktop-entry-explicit-id
     notify-send-test-snap.desktop-entry-explicit-file-name
     notify-send-test-snap.desktop-entry-explicit-path
     notify-send-test-snap.desktop-entry-explicit-uri
     notify-send-test-snap.desktop-entry-explicit-snapped-uri

  The
   `desktop-entry` value sent to dbus should be either:
     - A `notify-send-test-snap_`-prefixed desktop ID
     - A .desktop file path (readable from both inside and outside the snap)
     - A .desktop file uri (readable from both inside and outside the snap)

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1969934] Re: Update evolution-data-server to 3.44.1

[Brian Murray]

Hello Jeremy, or anyone else affected,

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

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

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

Title:
  Update evolution-data-server to 3.44.1

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series (corresponding with GNOME 42).

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.1/NEWS

  It is required to update evolution to 3.44.1 (LP: #1969935)

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+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 1966179] Re: The airplane hotkey does not work on lots of HP platforms

[Brian Murray]

I don't see any indication that "evdev:name:Intel HID
events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookStudio16.0InchMobileWorkstationPC:pvr*"
is still working (which was asked to be tested in comment #8). Is it?

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

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

Title:
  The airplane hotkey does not work on lots of HP platforms

Status in OEM Priority Project:
  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 Impish:
  Incomplete

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  [Where problems could occur]
  If we don't have whitelist in focal and impish, then the airplane key won't 
work on new HP platforms.

  Please refer to Bug #1955997 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966179/+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 1967038] Update Released

[Brian Murray]

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

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  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 Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

** Attachment added: "dist-upgrade-timing"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+attachment/5584814/+files/dist-upgrade-timing

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

I also did an upgrade from Focal to Jammy and recorded the upgrade
process using script and there was no long pause on dbus. I'll attach
both the timing file and recording.

One could watch the upgrade using `scriptreplay dist-upgrade-timing
dist-upgrade` and pass the `-d` argument if you don't want to watch it
in real time.

** Attachment added: "dist-upgrade"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+attachment/5584813/+files/dist-upgrade

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1840375] [shadow/xenial] verification still needed

[Brian Murray]

The fix for this bug has been awaiting testing feedback in the -proposed
repository for xenial for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  groupdel doesn't support extrausers

Status in snapd:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Fix Committed
Status in shadow source package in Bionic:
  Fix Released
Status in shadow source package in Disco:
  Won't Fix

Bug description:
  snapd needs the ability to call 'groupdel --extrausers foo' to clean
  up after itself, but --extrausers is currently unsupported.

  [Impact]
  On ubuntu-core systems we want to be able to manage "extrausers" in the same
  way as regular users. This requires updates to the various 
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.

  This is an important feature for Ubuntu Core

  [Test Case]
  0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
  1. install the libnss-extrausers and add "extrauers" to the passwd and shadow 
line (see /usr/share/doc/libnss-extrausers/README for the modifications in 
sswitch.conf)
  2. run "groupadd --extrausers foo" and verify "grep foo 
/var/lib/extrausers/group"
  3  check /var/lib/extrausers/group for the new "foo" group
  4. run "groupdel --extrausers foo"
  5. check /var/lib/extrausers/group and ensure the "foo" group is removed

  [Regression Potential]

   * low: this adds a new (optional) option which is off by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

I tested an upgrade from Impish to Jammy today in a virtual machine and
from what I could tell (I didn't watch the whole process) the upgrade
did not stop when dbus was installed although the message posted in the
screenshots was display. Looking at my /var/log/dist-upgrade/main.log we
can see that the total upgrade took only 16 minutes so it's unlikely
that 10 of that was spent waiting.

2022-04-28 10:17:16,728 DEBUG quirks: running StartUpgrade
2022-04-28 10:17:16,728 DEBUG running Quirks.StartUpgrade
2022-04-28 10:17:16,728 DEBUG skipping 'README' (no '.')
2022-04-28 10:17:16,728 DEBUG killing update-notifier
2022-04-28 10:17:16,735 DEBUG killing kblueplugd kbluetooth4
2022-04-28 10:17:16,744 INFO cache.commit()
2022-04-28 10:31:57,413 DEBUG cache.commit() returned None
2022-04-28 10:31:57,542 DEBUG openCache()
2022-04-28 10:31:59,650 DEBUG Comparing 5.13.0-19 with
2022-04-28 10:31:59,650 DEBUG Comparing 5.13.0-30 with 5.13.0-19
2022-04-28 10:31:59,650 DEBUG Comparing 5.13.0-40 with 5.13.0-30
2022-04-28 10:31:59,650 DEBUG Comparing 5.15.0-27 with 5.13.0-40
2022-04-28 10:31:59,751 DEBUG /openCache(), new cache size 71806
2022-04-28 10:31:59,751 DEBUG quirks: running jammyPostUpgrade
2022-04-28 10:31:59,751 DEBUG running Quirks.jammyPostUpgrade

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install

[Brian Murray]

There was a question about whether or not this error prevents non-
interactive vim from working, the answer is no.

ubuntu@ubuntu:~$ view /var/log/syslog
E1187: Failed to source defaults.vim
Press ENTER or type command to continue
ubuntu@ubuntu:/tmp$ cat junk.txt
abc
ubuntu@ubuntu:/tmp$ vi -c "%s/abc/ABC" -c ":xa" junk.txt
ubuntu@ubuntu:/tmp$ cat junk.txt
ABC

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

Title:
  vim.tiny reports 'E1187: Failed to source defaults.vim' on execution
  in default install

Status in vim package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04

  When running vim.tiny it says:

  $ vim.tiny
  E1187: Failed to source defaults.vim
  Press ENTER or type command to continue

  This is due to the defaults.vim file not being available.  If you just
  run it as vi

  $ vi

  this message does not appear as vim.tiny runs in compatibility mode.  I found 
mention of this issue in:
  https://github.com/grml/grml-etc-core/issues/99

  The defaults.vim file is provided by the package vim-runtime.

  I'm unsure what the issue is, if something needs to be in
  /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg
  claims vimrc is in vim-common, but no file is installed for me from
  that package, or if vim-runtime needs to be a required package for
  vim-tiny

  $ dpkg -S /etc/vim/vimrc
  vim-common: /etc/vim/vimrc
  $ ls -al /etc/vim/vimrc
  ls: cannot access '/etc/vim/vimrc': No such file or directory

  I discovered this because my .selected-editor was vim.tiny after
  running crontab -e

  $ crontab -e

  Select an editor.  To change later, run 'select-editor'.
    1. /bin/nano< easiest
    2. /usr/bin/vim.tiny
    3. /bin/ed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: vim-tiny 2:8.2.3995-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
  Uname: Linux 5.15.0-1005-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 13 11:56:35 2022
  ImageMediaBuild: 20201022
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+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 1962454] Re: Oops pages show wrong time window in JournalErrors

[Brian Murray]

** Tags added: fr-2321

** Tags removed: fr-2321 rls-jj-incoming
** Tags added: jammy

** Tags added: fr-2321

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

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

** Changed in: apport (Ubuntu Jammy)
   Importance: Undecided => Medium

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

Title:
  Oops pages show wrong time window in JournalErrors

Status in Apport:
  New
Status in Errors:
  Invalid
Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Jammy:
  Triaged

Bug description:
  For example, I just experienced a crash at:

Feb 28 17:31:12

  And the JournalErrors entries are:

Feb 28 17:31:30 - Feb 28 17:31:41

  So don't relate to the crash.

  But it should be possible to tell journalctl to collect entries
  starting *before* the crash and cover the full crash timeframe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1962454/+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 1896772] Re: systemd-resolved configures no Current Scopes on start

[Brian Murray]

** Tags added: fr-2319

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

** Also affects: isc-dhcp (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

** Changed in: isc-dhcp (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: isc-dhcp (Ubuntu Jammy)
   Importance: Undecided => High

** Tags removed: rls-jj-incoming

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

Title:
  systemd-resolved configures no Current Scopes on start

Status in ifupdown package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed
Status in ifupdown source package in Jammy:
  Fix Released
Status in isc-dhcp source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  Running groovy on the desktop, with the systemd packages that migrated
  today(/overnight EDT).

  # Steps to reproduce:

  1) `systemctl restart systemd-resolved.service`

  (This is a minimal reproducer, but I first saw this after an apt
  upgrade of systemd.)

  # Expected behaviour:

  DNS continues to work, status looks like this:

  Link 2 (enp5s0)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
Current DNS Server: 192.168.1.1
   DNS Servers: 192.168.1.1
DNS Domain: ~.
lan

  # Actual behaviour:

  DNS is unconfigured:

  Link 2 (enp5s0)
Current Scopes: none
  DefaultRoute setting: no
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  # Workaround

  Disconnecting and reconnecting my network connection restored DNS
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: i3
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Sep 23 09:05:42 2020
  InstallationDate: Installed on 2019-05-07 (504 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  RebootRequiredPkgs: gnome-shell
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 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: Upgraded to groovy on 2020-06-22 (92 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated

[Brian Murray]

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

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

** Tags removed: rls-ff-incoming rls-jj-incoming

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

Title:
  "machinectl shell" connections immediately terminated

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

Bug description:
  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

** Changed in: dbus (Ubuntu)
   Importance: Undecided => High

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1969375] Re: systemd-cryptenroll does not support TPM2 devices

[Brian Murray]

** Tags removed: rls-jj-incoming

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

Title:
  systemd-cryptenroll does not support TPM2 devices

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-cryptenroll can make use of tpm2 modules to bind against
  secure boot pcrs and enable auto unlocking of luks devices.

  Following the instructions here:
  https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll

  the following commands fail on ubuntu jammy (5.15.0-25-generic)

  root@testbox:~# systemd-cryptenroll --tpm2-device=list
  TPM2 not supported on this build.
  root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3
  🔐 Please enter current passphrase for disk /dev/sda3: ***
  root@testbox:~# echo $?
  1

  It appears that this issue has been resolved in the debian build for
  systemd here:  https://salsa.debian.org/systemd-
  team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8

  Can we get the same modifications to the Jammy systemd build?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969375/+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 1896772] Re: systemd-resolved configures no Current Scopes on start

[Brian Murray]

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  systemd-resolved configures no Current Scopes on start

Status in ifupdown package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Running groovy on the desktop, with the systemd packages that migrated
  today(/overnight EDT).

  # Steps to reproduce:

  1) `systemctl restart systemd-resolved.service`

  (This is a minimal reproducer, but I first saw this after an apt
  upgrade of systemd.)

  # Expected behaviour:

  DNS continues to work, status looks like this:

  Link 2 (enp5s0)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
Current DNS Server: 192.168.1.1
   DNS Servers: 192.168.1.1
DNS Domain: ~.
lan

  # Actual behaviour:

  DNS is unconfigured:

  Link 2 (enp5s0)
Current Scopes: none
  DefaultRoute setting: no
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  # Workaround

  Disconnecting and reconnecting my network connection restored DNS
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: i3
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Sep 23 09:05:42 2020
  InstallationDate: Installed on 2019-05-07 (504 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  RebootRequiredPkgs: gnome-shell
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 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: Upgraded to groovy on 2020-06-22 (92 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1896772/+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 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install

[Brian Murray]

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

** Tags removed: rls-jj-incoming
** Tags added: rls-jj-notfixing

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

Title:
  vim.tiny reports 'E1187: Failed to source defaults.vim' on execution
  in default install

Status in vim package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04

  When running vim.tiny it says:

  $ vim.tiny
  E1187: Failed to source defaults.vim
  Press ENTER or type command to continue

  This is due to the defaults.vim file not being available.  If you just
  run it as vi

  $ vi

  this message does not appear as vim.tiny runs in compatibility mode.  I found 
mention of this issue in:
  https://github.com/grml/grml-etc-core/issues/99

  The defaults.vim file is provided by the package vim-runtime.

  I'm unsure what the issue is, if something needs to be in
  /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg
  claims vimrc is in vim-common, but no file is installed for me from
  that package, or if vim-runtime needs to be a required package for
  vim-tiny

  $ dpkg -S /etc/vim/vimrc
  vim-common: /etc/vim/vimrc
  $ ls -al /etc/vim/vimrc
  ls: cannot access '/etc/vim/vimrc': No such file or directory

  I discovered this because my .selected-editor was vim.tiny after
  running crontab -e

  $ crontab -e

  Select an editor.  To change later, run 'select-editor'.
    1. /bin/nano< easiest
    2. /usr/bin/vim.tiny
    3. /bin/ed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: vim-tiny 2:8.2.3995-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
  Uname: Linux 5.15.0-1005-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 13 11:56:35 2022
  ImageMediaBuild: 20201022
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04

[Brian Murray]

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

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

Title:
  Initrd out of memory error after upgrade to 22.04

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 22.04 system is unbootable because of "out of memory" 
error when loading initial ramdisk. I was able to fix it by editing cat 
/etc/initramfs-tools/initramfs.conf
  and changing configuration to:
  MODULES=dep
  COMPRESS=xz
  RUNSIZE=15%

  Not sure which one helped, but I can test it if needed.

  System information:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  initramfs-tools:
Installed: 0.140ubuntu13
Candidate: 0.140ubuntu13
Version table:
   *** 0.140ubuntu13 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8

[Brian Murray]

** Also affects: openssl (Ubuntu Kinetic)
   Importance: Critical
 Assignee: Simon Chopin (schopin)
   Status: In Progress

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

** Tags removed: rls-jj-incoming

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

Title:
  openssl has catastrophic issues when locale set to TR_UTF8

Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Jammy:
  New
Status in openssl source package in Kinetic:
  In Progress

Bug description:
  I noticed this when I checked "ua status". It alerted me that I should
  check my openssl configuration.

  "ua status
  Failed to access URL: 
https://contracts.canonical.com/v1/resources?architecture=amd64&kernel=5.15.0-25-generic&series=jammy
  Cannot verify certificate of server
  Please check your openssl configuration."

  I also figured wget&curl doesn't work with https:// URLs at all.

  On web I found:
  https://github.com/openssl/openssl/issues/18039

  So I changed locale to C_UTF-8

  #locale
  LANG=tr_TR.UTF-8
  LANGUAGE=
  LC_CTYPE="tr_TR.UTF-8"
  LC_NUMERIC=tr_TR.UTF-8
  LC_TIME=tr_TR.UTF-8
  LC_COLLATE="tr_TR.UTF-8"
  LC_MONETARY=tr_TR.UTF-8
  LC_MESSAGES="tr_TR.UTF-8"
  LC_PAPER=tr_TR.UTF-8
  LC_NAME=tr_TR.UTF-8
  LC_ADDRESS=tr_TR.UTF-8
  LC_TELEPHONE=tr_TR.UTF-8
  LC_MEASUREMENT=tr_TR.UTF-8
  LC_IDENTIFICATION=tr_TR.UTF-8
  LC_ALL=
  casaba@ship-macbook:/backups$ sudo locale-gen c
  ca_AD   ca_ES.UTF-8 ca_IT   ckb_IQ  cs_CZ 
  cy_GB.UTF-8
  ca_AD.UTF-8 ca_ES@valencia  ca_IT.UTF-8 cmn_TW  cs_CZ.UTF-8   
  
  ca_ES   ca_FR   ce_RU   crh_UA  cv_RU 
  
  ca_ES@euro  ca_FR.UTF-8 chr_US  csb_PL  cy_GB 
  
  casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 
  Generating locales (this might take a while)...
C.UTF-8... done
  Generation complete.
  casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8
  casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8

  Now the result is (after logout/login)

  ua status
  SERVICE   ENTITLED  STATUSDESCRIPTION
  cc-ealyes   n/a   Common Criteria EAL2 Provisioning Packages
  cis   yes   n/a   Security compliance and audit tools
  esm-infra yes   n/a   UA Infra: Extended Security Maintenance 
(ESM)
  fips  yes   n/a   NIST-certified core packages
  fips-updates  yes   n/a   NIST-certified core packages with priority 
security updates
  livepatch yes   n/a   Canonical Livepatch service

  Enable services with: ua enable 

   Account: il...@fastmail.fm
  Subscription: il...@fastmail.fm

  If Ubuntu 22 ships with current configuration, entire TR will suffer
  considering you can't find http:// downloads anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssl 3.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 14 10:21:09 2022
  InstallationDate: Installed on 2021-12-29 (105 days ago)
  InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago)
  mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505

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

[Brian Murray]

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

Title:
  Jammy's /etc/os-release missing LTS string in VERSION

Status in base-files package in Ubuntu:
  Fix Committed
Status in base-files source package in Jammy:
  Fix Released

Bug description:
  [Description]

  In Jammy (base-files 12ubuntu4) we have:

  $ grep VERSION= /etc/os-release 
  VERSION="22.04 (Jammy Jellyfish)"

  but expected is:

  VERSION="22.04 LTS (Jammy Jellyfish)"

  Compare with Focal:

  $ grep VERSION= /etc/os-release 
  VERSION="20.04.4 LTS (Focal Fossa)"

  [Impact]

  Having VERSION without LTS is inconsistent with the previous LTS
  releases and is wrong, as the official name of the release is "22.04
  LTS". This can confuse users.

  Any script relying on VERSION to detect if the Ubuntu version it is
  running on in an LTS won't be work as expected.

  [Test Plan]

  1. grep VERSION= /etc/os-release 
  2. check that it is: VERSION="22.04 LTS (Jammy Jellyfish)"

  [Where problems could occur]

  Software already packaged in Jammy may already have adapted to the
  fact that VERSION doesn't have the LTS string in it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1969960/+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 1969960] Re: Jammy's /etc/os-release missing LTS string in VERSION

[Brian Murray]

...
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 base-files 
amd64 12ubuntu4.1 [62.8 kB]
Fetched 62.8 kB in 1s (123 kB/s)
The system does not support apt-btrfs-snapshot
(Reading database ... 454507 files and directories currently installed.)
Preparing to unpack .../base-files_12ubuntu4.1_amd64.deb ...
Unpacking base-files (12ubuntu4.1) over (12ubuntu4) ...
Setting up base-files (12ubuntu4.1) ...
motd-news.service is a disabled or a static unit not running, not starting it.
Processing triggers for cracklib-runtime (2.9.6-3.4build4) ...
...
 $ grep VERSION /etc/os-release
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy


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

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

Title:
  Jammy's /etc/os-release missing LTS string in VERSION

Status in base-files package in Ubuntu:
  Fix Committed
Status in base-files source package in Jammy:
  Fix Released

Bug description:
  [Description]

  In Jammy (base-files 12ubuntu4) we have:

  $ grep VERSION= /etc/os-release 
  VERSION="22.04 (Jammy Jellyfish)"

  but expected is:

  VERSION="22.04 LTS (Jammy Jellyfish)"

  Compare with Focal:

  $ grep VERSION= /etc/os-release 
  VERSION="20.04.4 LTS (Focal Fossa)"

  [Impact]

  Having VERSION without LTS is inconsistent with the previous LTS
  releases and is wrong, as the official name of the release is "22.04
  LTS". This can confuse users.

  Any script relying on VERSION to detect if the Ubuntu version it is
  running on in an LTS won't be work as expected.

  [Test Plan]

  1. grep VERSION= /etc/os-release 
  2. check that it is: VERSION="22.04 LTS (Jammy Jellyfish)"

  [Where problems could occur]

  Software already packaged in Jammy may already have adapted to the
  fact that VERSION doesn't have the LTS string in it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1969960/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

** Tags added: rls-jj-incoming

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04

[Brian Murray]

** Package changed: ubuntu => initramfs-tools (Ubuntu)

** Tags added: rls-jj-incoming

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

Title:
  Initrd out of memory error after upgrade to 22.04

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After upgrading to 22.04 system is unbootable because of "out of memory" 
error when loading initial ramdisk. I was able to fix it by editing cat 
/etc/initramfs-tools/initramfs.conf
  and changing configuration to:
  MODULES=dep
  COMPRESS=xz
  RUNSIZE=15%

  Not sure which one helped, but I can test it if needed.

  System information:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  initramfs-tools:
Installed: 0.140ubuntu13
Candidate: 0.140ubuntu13
Version table:
   *** 0.140ubuntu13 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1969291] Re: apport-collect & ubuntu-bug failing to switch to firefox

[Brian Murray]

** Tags added: lubuntu

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

Title:
  apport-collect & ubuntu-bug failing to switch to firefox

Status in apport package in Ubuntu:
  New

Bug description:
  In attempting to file a bug report on Lubuntu jammy ISO 
  (QA-test installed yesterday using ISO 2020-04-15)

  --
  guiverc@dc7700-2re:~$ apport-collect 1969290
  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj&allow_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Waiting to hear from Launchpad about your decision...
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj&allow_permission=DESKTOP_INTEGRATION'
  ---

  On attempting to file using `ubuntu-bug apport`

  ---
  guiverc@dc7700-2re:~$ ubuntu-bug apport

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  . 

   


   
  *** Send problem report to the developers?

   


   
  After the problem report has been sent, please fill out the form in the   

   
  automatically opened web browser. 

   


   
  What would you like to do? Your options are:  

   
S: Send report (5.0 KB) 

   
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  96%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?'
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sun Apr 17 12:34:57 2022
  InstallationDate: Installed on 2022-04-16 (0 days ago)
  InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 
(20220415)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969291/+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 1969477] Re: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection

[Brian Murray]

If direct access to Launchpad is blocked how was a bug report filed in
the first place? apport-collect is designed to gather information from a
system about an existing bug report. Additionally, apport-collect looks
at the bug report in Launchpad to determine which package is affected
and to to determine which apport-package hook to run. Without the
connection Launchpad only general information about the system would be
gathered.

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

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

Title:
  apport-collect needs to be able to save logs to a file instead of
  requiring a launchpad connection

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  We very often tell our hardware partners to "file a bug" when they
  encounter issues.  This requires them to run apport-collect to gather
  and submit logs for the bug.

  However, very often, the hardware that has the problem is in a lab
  that has tight security restrictions and direct access to launchpad is
  blocked.  This makes it nearly impossible for them to gather any
  requested logs, since apport-collect requires a direct line to
  Launchpad.

  apport-collect needs to adopt the --save feature of apport-bug/ubuntu-
  bug to save the prescribed logs and system data in a tarball that can
  then be attached to a bug after the fact.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.23
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl 
icp nvidia_modeset zcommon znvpair nvidia
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 19 10:25:54 2022
  InstallationDate: Installed on 2016-02-11 (2258 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969477/+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 1959475] Re: "machinectl shell" connections immediately terminated

[Brian Murray]

** Tags added: 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/1959475

Title:
  "machinectl shell" connections immediately terminated

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install

[Brian Murray]

** Tags added: rls-jj-incoming

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

Title:
  vim.tiny reports 'E1187: Failed to source defaults.vim' on execution
  in default install

Status in vim package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04

  When running vim.tiny it says:

  $ vim.tiny
  E1187: Failed to source defaults.vim
  Press ENTER or type command to continue

  This is due to the defaults.vim file not being available.  If you just
  run it as vi

  $ vi

  this message does not appear as vim.tiny runs in compatibility mode.  I found 
mention of this issue in:
  https://github.com/grml/grml-etc-core/issues/99

  The defaults.vim file is provided by the package vim-runtime.

  I'm unsure what the issue is, if something needs to be in
  /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg
  claims vimrc is in vim-common, but no file is installed for me from
  that package, or if vim-runtime needs to be a required package for
  vim-tiny

  $ dpkg -S /etc/vim/vimrc
  vim-common: /etc/vim/vimrc
  $ ls -al /etc/vim/vimrc
  ls: cannot access '/etc/vim/vimrc': No such file or directory

  I discovered this because my .selected-editor was vim.tiny after
  running crontab -e

  $ crontab -e

  Select an editor.  To change later, run 'select-editor'.
    1. /bin/nano< easiest
    2. /usr/bin/vim.tiny
    3. /bin/ed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: vim-tiny 2:8.2.3995-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
  Uname: Linux 5.15.0-1005-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 13 11:56:35 2022
  ImageMediaBuild: 20201022
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+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 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install

[Brian Murray]

I also noticed this by launching "view /var/log/installer/syslog" on a
freshly installed Ubuntu desktop system.

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

Title:
  vim.tiny reports 'E1187: Failed to source defaults.vim' on execution
  in default install

Status in vim package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04

  When running vim.tiny it says:

  $ vim.tiny
  E1187: Failed to source defaults.vim
  Press ENTER or type command to continue

  This is due to the defaults.vim file not being available.  If you just
  run it as vi

  $ vi

  this message does not appear as vim.tiny runs in compatibility mode.  I found 
mention of this issue in:
  https://github.com/grml/grml-etc-core/issues/99

  The defaults.vim file is provided by the package vim-runtime.

  I'm unsure what the issue is, if something needs to be in
  /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg
  claims vimrc is in vim-common, but no file is installed for me from
  that package, or if vim-runtime needs to be a required package for
  vim-tiny

  $ dpkg -S /etc/vim/vimrc
  vim-common: /etc/vim/vimrc
  $ ls -al /etc/vim/vimrc
  ls: cannot access '/etc/vim/vimrc': No such file or directory

  I discovered this because my .selected-editor was vim.tiny after
  running crontab -e

  $ crontab -e

  Select an editor.  To change later, run 'select-editor'.
    1. /bin/nano< easiest
    2. /usr/bin/vim.tiny
    3. /bin/ed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: vim-tiny 2:8.2.3995-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
  Uname: Linux 5.15.0-1005-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 13 11:56:35 2022
  ImageMediaBuild: 20201022
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+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 1969212] Re: libssl1.x dependencies can't be met on 22.04 beta

[Brian Murray]

** Tags added: jammy

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

Title:
  libssl1.x dependencies can't be met on 22.04 beta

Status in openssl package in Ubuntu:
  New

Bug description:
  Since Ubuntu 22.04 beta includes only openssl 3.0, any and all
  packages that do not recognize newer openssl versions and depend on
  previous versions can't be properly installed.

  As an example, in my isolated case I'm trying to install SafeNet
  Authentication Client to be able to use eToken hardware key:

  # dpkg -i /SAC/safenetauthenticationclient_10.8.28_amd64.deb 
  Selecting previously unselected package safenetauthenticationclient.
  (Reading database ... 202999 files and directories currently installed.)
  Preparing to unpack .../safenetauthenticationclient_10.8.28_amd64.deb ...
  Unpacking safenetauthenticationclient (10.8.28) ...
  dpkg: dependency problems prevent configuration of 
safenetauthenticationclient:
   safenetauthenticationclient depends on libssl1.0.2 | libssl1.0.0 | 
libssl1.1; however:
Package libssl1.0.2 is not installed.
Package libssl1.0.0 is not installed.
Package libssl1.1:amd64 is not installed.

  dpkg: error processing package safenetauthenticationclient (--install):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.35-0ubuntu3) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
  Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
  Errors were encountered while processing:
   safenetauthenticationclient

  The package depends on "libssl1.0.2 | libssl1.0.0 | libssl1.1" and at
  the moment this dependency cannot be met without resorting to manually
  installing the required library, which is not a good way to go.

  Thanks in advance.

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

[Brian Murray]

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

Title:
  Journalctl -f --file some.journal causes coredump

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

Bug description:
  [impact]

  journalctl -f --file FILE results in segfault

  [test case]

  $ journalctl -f --file $FILENAME

  [regression potential]

  journalctl segfault or failure to properly operate

  [scope]

  needed in focal

  fixed upstream in 2b6df46d21a at v246, so fixed already in h and later

  [original description]

  Focal latest systemd 245.

  Journalctl -f --file path/to/file.journal.  Will allways causes
  journalctl crash...

  The same doesnt happen on centos8 systemd 239... I couldnt test on any
  more systems atm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1946388/+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 1955997] Update Released

[Brian Murray]

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

Title:
  The airplane hotkey has no function on a HP platform

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

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1871538] Update Released

[Brian Murray]

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Released
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Released
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Kesch

[Touch-packages] [Bug 1962038] Update Released

[Brian Murray]

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

Title:
  wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

Status in procps package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in procps source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  Fix Released
Status in procps source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  I've just learned that systemd is setting kernel.sysrq to 16 in
  /usr/lib/sysctl.d/50-default.conf.  This is inconsistent with
  /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176
  by default.  systemd should drop its setting to defer to the file that
  we have been carrying in procps for a very long time.

  Therefore, users can only sync their storage but not do any other
  actions using the magic sysrq key.

  [Test Plan]

  $ sysctl kernel.sysrq
  => This should show "kernel.sysrq = 176" as set by 
/etc/sysctl.d/10-magic-sysrq.conf
  $ sysctl net.ipv4.conf.all.rp_filter
  => This should show "net.ipv4.conf.all.rp_filter=2" as set by 
/etc/sysctl.d/10-network-security.conf

  [Where problems could occur]

   * This patch changes systemd's sysctl configuration in /lib/sysctl.d/*.conf
   * If something is broken it could fail to apply any of systemd's sysctl 
configuration, but Ubuntu's defaults from /etc/sysctl.d/*.conf would still be 
in place.

  [Other Info]
   
   * None

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

[Brian Murray]

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

Title:
  systemd: autopkgtest: tests-in-lxd fails because of remaining snap
  .mount units

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Impish:
  Fix Released

Bug description:
  This build log provides an example of the problem:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz.

  During setup for tests-in-lxd, an attempt is made to purge snapd, but
  this fails:

  [ ... ]
  Purging configuration files for snapd (2.54.3+21.10.1ubuntu0.2) ...
  Stopping snap.lxd.activate.service
  Stopping unit snap.lxd.activate.service
  Waiting until unit snap.lxd.activate.service is stopped [attempt 1]
  snap.lxd.activate.service is stopped.
  Removing snap.lxd.activate.service
  Stopping snap.lxd.daemon.service
  Stopping unit snap.lxd.daemon.service
  Waiting until unit snap.lxd.daemon.service is stopped [attempt 1]
  snap.lxd.daemon.service is stopped.
  Removing snap.lxd.daemon.service
  Stopping snap.lxd.user-daemon.service
  Stopping unit snap.lxd.user-daemon.service
  Waiting until unit snap.lxd.user-daemon.service is stopped [attempt 1]
  snap.lxd.user-daemon.service is stopped.
  Removing snap.lxd.user-daemon.service
  Stopping snap-core20-1378.mount
  Stopping unit snap-core20-1378.mount
  Waiting until unit snap-core20-1378.mount is stopped [attempt 1]
  snap-core20-1378.mount is stopped.
  Removing snap core20 and revision 1378
  Removing snap-core20-1378.mount
  Stopping snap-lxd-22672.mount
  Stopping unit snap-lxd-22672.mount
  Waiting until unit snap-lxd-22672.mount is stopped [attempt 1]
  snap-lxd-22672.mount is stopped.
  Removing snap lxd and revision 22672
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/meminfo': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/stat': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/uptime': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/diskstats': 
Function not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/swaps': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/loadavg': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/slabinfo': 
Function not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpu0': Operation not 
permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpuidle': Operation 
not permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/uevent': Function 
not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/svm': Function not 
implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/hotplug': Operation 
not permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/offline': Function 
not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/present': Function 
not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/power': Operation 
not permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/dscr_default': 
Function not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/probe': Function not 
implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/smt': Operation not 
permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/vulnerabilities': 
Operation not permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpufreq': Operation 
not permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/isolated': Function 
not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/kernel_max': 
Function not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/modalias': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/c

[Touch-packages] [Bug 1958284] Update Released

[Brian Murray]

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

Title:
  shutdown hangs at "Waiting for process: ..." for 90s, ignoring
  DefaultTimeoutStopSec

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

Bug description:
  [Impact]

  The systemd shutdown sequence does not honor systemd-system.conf
  settings when waiting for remaining processes. This means that, for
  example, if a systemd service specifies KillMode=process and a process
  remaining from that service does not properly handle SIGTERM, then the
  remaining process will not be killed until after the compiled-in
  default value of DefaultTimeoutStopSec (90s), even if the user has
  changed the setting of DefaultTimeoutStopSec. In such cases, this
  impacts users by significantly increasing the time required for
  shutdown/reboot.

  [Test Plan]

  * Create a new script, /usr/local/bin/loop-ignore-sigterm:
```
#!/bin/bash
loop_forever() {
while true; do sleep 1; done
}

(
trap 'echo Ignoring SIGTERM...' SIGTERM
loop_forever
)

loop_forever
```

This script will spawn a subshell which will loop forever and ignore 
SIGTERM. This will force systemd to wait for the subprocess at 
reboot/shutdown, and eventually send SIGKILL after TimeoutStopSec 
(DefaultTimeoutStopSec in this case).

  * Make the script executable: 
$ chmod +x /usr/local/bin/loop-ignore-sigterm

  * Create a systemd service for this script. Add the following to 
/etc/systemd/system/loop-ignore-sigterm.service:
```
[Service]
KillMode=process
ExecStart=/usr/local/bin/loop-ignore-sigterm
```

  * Start the service:
$ systemctl start loop-ignore-sigterm.service

  * Edit /etc/systemd/system.conf, and uncomment the 
   'DefaultTimeoutStopSec=90s' line. Modify 90s to something much shorter, 
e.g. 20s.

  * Re-exec the daemon so this new default takes effect:
$ systemctl daemon-reexec

  * Reboot, and monitor the logs. Observe that systemd-shutdown will wait 
for the loop-ignore-sigterm process for 90s, instead of the 20s 
configured earlier.

  [Where problems could occur]

  The patch moves the reset_arguments() call to the end of main, which
  means reset_arguments() is no longer called before daemon re-execution
  (if that branch is taken). If anything in that code path relied on
  reset_arguments() being called before re-executing, those assumptions
  could be broken. Any such problems would potentially be seen during
  daemon re-execution, e.g. when calling systemctl daemon-reexec.

  [ Original Description ]

  With systemd v245 as shipped with 20.04, the shutdown sequence does
  not use the value of `DefaultTimeoutStopSec` to wait for remaining
  processes, it instead uses the compiled in default of 90s.

  This is most visible with services that use `KillMode=process`
  (docker, k8s, k3s, etc...), especially if the remaining processes do
  not handle `SIGTERM` or choose to ignore it.

  For example:
  ```
  [ OK ] Finished Reboot.
  [ OK ] Reached target Reboot.
  [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, 
containerd-shim, containerd-shim, fluent-bit

  --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower
  value ---

  ```

  The bug has been fixed upstream here:
  https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22

  Marc was kind enough to package the patch for 20.04 so I could test it
  
(https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing-
  archive-extra) and with that package, I can confirm that it indeed
  fixes the issue.

  Here's a few github issues I stumbled upon while trying to debug this,
  along with a short writeup of the workaround I ended up using:

  - https://github.com/moby/moby/issues/41831
  - https://github.com/k3s-io/k3s/issues/2400
  - https://github.com/systemd/systemd/issues/16991
  - https://raby.sh/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html

  Of course, it would be much better if all the processes would properly
  handle `SIGTERM`, but having a way to enforce a maximum wait time at
  shutdown is a decent workaround.

  Given that the patch is relatively simple, would it be possible to add
  it the package for 20.04?

  Thanks

To manage notifications about this bug go to:
https://bug

[Touch-packages] [Bug 1968855] Re: apport fails when trying to report a problem about Cheese

[Brian Murray]

This is probably an issue with the apport package hook provided by
cheese and located in /usr/share/apport/package-hooks/source_cheese.py.
Subsequently, I'm reassigning this to the cheese package.

** Package changed: apport (Ubuntu) => cheese (Ubuntu)

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

Title:
  apport fails when trying to report a problem about Cheese

Status in cheese package in Ubuntu:
  New

Bug description:
  There is a problem with Cheese on 22.04 beta (image shows up scrambled
  even though it works as expected when I visit www.webcamtests.com)[1].

  I tried to report the problem using `ubuntu-bug cheese`.

  I am asked if the problem is with Cheese, or with the image shown in
  Cheese. I select the latter option, then after around 20 seconds, the
  error

  -
  Setting pipeline to PAUSED ...
  Failed to set pipeline to PAUSED.
  Setting pipeline to NULL ...
  ERROR: from element 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
 Internal data stream error.
  Additional debug info:
  ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
  streaming stopped, reason not-negotiated (-4)
  ERROR: pipeline doesn't want to preroll.
  Freeing pipeline ...

  (cheese:25538): cheese-WARNING **: 16:22:49.180: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)
  -

  shows up in the terminal where I had launched `ubuntu-bug apport`.

  Finally, Cheese is launched with a black screen instead of the webcam
  picture and the text "There was an error playing the video from the
  webcam".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:124:24532:2022-04-13 10:33:31.216692388 +0800:2022-04-13 
10:33:31.216692388 
+0800:/var/crash/_usr_bin_checkbox-support-eddystone_scanner.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 16:24:43 2022
  InstallationDate: Installed on 2022-04-01 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

  
  [1] https://gitlab.gnome.org/GNOME/cheese/-/issues/139

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1968855/+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 1903516] Please test proposed package

[Brian Murray]

Hello Bert, or anyone else affected,

Accepted openssh into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.2p1-4ubuntu0.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-
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: openssh (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  aborted (core dumped) when using ConnectTimeout > 2147483

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Impish:
  Fix Committed
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the
  ssh client to crash. This happens due to an integer overflow which was
  fixed upstream with the patch being proposed for this SRU, which caps
  the effective value for that option at INT_MAX/1000.

  While use cases triggering the bug may be uncommon, the patch is
  straightforward and the fix could be staged for the next time an
  upload is needed.

  
  [Test Plan]

  Running

  ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max =
  int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost

  triggers the error. In this case, the ssh client will crash and

  Aborted

  will be printed to stderr.

  By applying the proposed fix, running the same command should allow
  the ssh connection to proceed to the authentication steps.

  [Where problems could occur]

  Most problems would manifest due to rebuilding the package (e.g.,
  dependency changes). Since this proposal is to stage these SRUs, such
  risk is being deferred to be shared with the next, more critical,
  upload.

  [Other Info]
   
  All the SRUs proposed here should be staged due to the low priority nature of 
the bug.

  [Original bug report]

  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.

  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 
docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1

  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.

  What happened:

  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1903516/+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 1903516] Please test proposed package

[Brian Murray]

Hello Bert, or anyone else affected,

Accepted openssh into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.4p1-6ubuntu2.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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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: openssh (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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1903516

Title:
  aborted (core dumped) when using ConnectTimeout > 2147483

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Impish:
  Fix Committed
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the
  ssh client to crash. This happens due to an integer overflow which was
  fixed upstream with the patch being proposed for this SRU, which caps
  the effective value for that option at INT_MAX/1000.

  While use cases triggering the bug may be uncommon, the patch is
  straightforward and the fix could be staged for the next time an
  upload is needed.

  
  [Test Plan]

  Running

  ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max =
  int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost

  triggers the error. In this case, the ssh client will crash and

  Aborted

  will be printed to stderr.

  By applying the proposed fix, running the same command should allow
  the ssh connection to proceed to the authentication steps.

  [Where problems could occur]

  Most problems would manifest due to rebuilding the package (e.g.,
  dependency changes). Since this proposal is to stage these SRUs, such
  risk is being deferred to be shared with the next, more critical,
  upload.

  [Other Info]
   
  All the SRUs proposed here should be staged due to the low priority nature of 
the bug.

  [Original bug report]

  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.

  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 
docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1

  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.

  What happened:

  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1903516/+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 1903516] Re: aborted (core dumped) when using ConnectTimeout > 2147483

[Brian Murray]

Given that openssh occasionally has security updates I wonder how long
this will last in -proposed but since the work was already done I'll
accept it.

** Changed in: openssh (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  aborted (core dumped) when using ConnectTimeout > 2147483

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Impish:
  Fix Committed
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the
  ssh client to crash. This happens due to an integer overflow which was
  fixed upstream with the patch being proposed for this SRU, which caps
  the effective value for that option at INT_MAX/1000.

  While use cases triggering the bug may be uncommon, the patch is
  straightforward and the fix could be staged for the next time an
  upload is needed.

  
  [Test Plan]

  Running

  ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max =
  int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost

  triggers the error. In this case, the ssh client will crash and

  Aborted

  will be printed to stderr.

  By applying the proposed fix, running the same command should allow
  the ssh connection to proceed to the authentication steps.

  [Where problems could occur]

  Most problems would manifest due to rebuilding the package (e.g.,
  dependency changes). Since this proposal is to stage these SRUs, such
  risk is being deferred to be shared with the next, more critical,
  upload.

  [Other Info]
   
  All the SRUs proposed here should be staged due to the low priority nature of 
the bug.

  [Original bug report]

  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.

  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 
docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1

  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.

  What happened:

  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1903516/+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 1903516] Please test proposed package

[Brian Murray]

Hello Bert, or anyone else affected,

Accepted openssh into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:7.6p1-4ubuntu0.7 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  aborted (core dumped) when using ConnectTimeout > 2147483

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Impish:
  Fix Committed
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the
  ssh client to crash. This happens due to an integer overflow which was
  fixed upstream with the patch being proposed for this SRU, which caps
  the effective value for that option at INT_MAX/1000.

  While use cases triggering the bug may be uncommon, the patch is
  straightforward and the fix could be staged for the next time an
  upload is needed.

  
  [Test Plan]

  Running

  ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max =
  int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost

  triggers the error. In this case, the ssh client will crash and

  Aborted

  will be printed to stderr.

  By applying the proposed fix, running the same command should allow
  the ssh connection to proceed to the authentication steps.

  [Where problems could occur]

  Most problems would manifest due to rebuilding the package (e.g.,
  dependency changes). Since this proposal is to stage these SRUs, such
  risk is being deferred to be shared with the next, more critical,
  upload.

  [Other Info]
   
  All the SRUs proposed here should be staged due to the low priority nature of 
the bug.

  [Original bug report]

  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.

  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 
docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1

  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.

  What happened:

  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1903516/+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 1966591] Please test proposed package

[Brian Murray]

Hello Evgeny, or anyone else affected,

Accepted openssh into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:7.6p1-4ubuntu0.7 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  ssh-keygen -R changes known_hosts file permissions (mode)

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Impish:
  Fix Released
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  When using "ssh-keygen -R" to remove a host from "known_hosts" the
  command changes permissions on the file.  This can cause problems
  particularly when used on the global "known_hosts" file
  (/etc/ssh/ssh_known_hosts), because then only root can read it.
  Programs running non-interactively as non-root users suddenly fail to
  SSH and it's not immediately obvious why.

  [Test Plan]

  The problem happens on Bionic and Focal.

  $ lxc launch ubuntu-daily:focal openssh-bug1966591
  $ lxc shell openssh-bug1966591
  # ssh-keyscan github.com > test_known_hosts
  # chmod 644 test_known_hosts
  # ssh-keygen -R github.com -f test_known_hosts
  # stat test_known_hosts
  ...
  Access: (0600/-rw---) ...
  ...

  [Where problems could occur]

  The upstream patch is very simple and it is unlikely that it will
  cause any regressions.  An indirect problem that could occur is that
  users might expect to see a more strict set of permissions on a
  "known_hosts" file after using "ssh-keygen -R", but arguably this is
  not defined behaviour and should not be relied upon.  Of course, there
  is always a (very) small risk of introducing problems when rebuilding
  packages using newer versions of its dependencies (especially on
  Bionic, because it's older).

  [Original Description]

  When I use ssh-keygen -R to remove a host from known_hosts it changes
  permissions on the file. This causes problems particularly when used
  on the global known hosts file (/etc/ssh/ssh_known_hosts), because
  then only root can read it. Programs running non-interactively as non-
  root users suddenly fail to SSH and it's not immediately obvious why.

  To reproduce:

  $ ssh-keyscan github.com >test_known_hosts
  $ chmod 741 test_known_hosts
  $ ssh-keygen -R github.com -f test_known_hosts
  $ stat test_known_hosts
  ...
  Access: (0600/-rw---) ...

  Expected behavior: file permissions remain unchanged (mode 0741 in
  this example).

  $ lsb_release -rd
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04

  $ apt-cache policy openssh-client
  openssh-client:
    Installed: 1:7.6p1-4ubuntu0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1966591/+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 1966591] Re: ssh-keygen -R changes known_hosts file permissions (mode)

[Brian Murray]

Hello Evgeny, or anyone else affected,

Accepted openssh into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.2p1-4ubuntu0.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-
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: openssh (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

** Changed in: openssh (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  ssh-keygen -R changes known_hosts file permissions (mode)

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Impish:
  Fix Released
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  When using "ssh-keygen -R" to remove a host from "known_hosts" the
  command changes permissions on the file.  This can cause problems
  particularly when used on the global "known_hosts" file
  (/etc/ssh/ssh_known_hosts), because then only root can read it.
  Programs running non-interactively as non-root users suddenly fail to
  SSH and it's not immediately obvious why.

  [Test Plan]

  The problem happens on Bionic and Focal.

  $ lxc launch ubuntu-daily:focal openssh-bug1966591
  $ lxc shell openssh-bug1966591
  # ssh-keyscan github.com > test_known_hosts
  # chmod 644 test_known_hosts
  # ssh-keygen -R github.com -f test_known_hosts
  # stat test_known_hosts
  ...
  Access: (0600/-rw---) ...
  ...

  [Where problems could occur]

  The upstream patch is very simple and it is unlikely that it will
  cause any regressions.  An indirect problem that could occur is that
  users might expect to see a more strict set of permissions on a
  "known_hosts" file after using "ssh-keygen -R", but arguably this is
  not defined behaviour and should not be relied upon.  Of course, there
  is always a (very) small risk of introducing problems when rebuilding
  packages using newer versions of its dependencies (especially on
  Bionic, because it's older).

  [Original Description]

  When I use ssh-keygen -R to remove a host from known_hosts it changes
  permissions on the file. This causes problems particularly when used
  on the global known hosts file (/etc/ssh/ssh_known_hosts), because
  then only root can read it. Programs running non-interactively as non-
  root users suddenly fail to SSH and it's not immediately obvious why.

  To reproduce:

  $ ssh-keyscan github.com >test_known_hosts
  $ chmod 741 test_known_hosts
  $ ssh-keygen -R github.com -f test_known_hosts
  $ stat test_known_hosts
  ...
  Access: (0600/-rw---) ...

  Expected behavior: file permissions remain unchanged (mode 0741 in
  this example).

  $ lsb_release -rd
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04

  $ apt-cache policy openssh-client
  openssh-client:
    Installed: 1:7.6p1-4ubuntu0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1966591/+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 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft

[Brian Murray]

Hello Andrea, or anyone else affected,

Accepted iptables into impish-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iptables/1.8.7-1ubuntu2.1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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: iptables (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  Fix Released
Status in iptables source package in Impish:
  Fix Committed
Status in iptables source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  [Test case]

  tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel
  source code.

  [Fix]

  Apply iptables upstream commit:

  5f1fcace ("iptables-nft: fix -Z option")

  In this way also with iptables-nft the counters are reported
  correctly.

  [Regression potential]

  We may require other upstream commits now that the -Z option is
  working properly with iptables-nft.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1949603/+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 1955997] Re: The airplane hotkey has no function on a HP platform

[Brian Murray]

Please add some verification details in addition to changing the tag
from v-needed to v-done. I'm setting this back to v-needed until a
comment is made about the verification testing that was performed.

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

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  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 Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1967965] Re: "Other problem" and "Display" options are swapped

[Brian Murray]

** Tags added: rls-kk-incoming

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

Title:
  "Other problem" and "Display" options are swapped

Status in apport package in Ubuntu:
  New

Bug description:
  When attempting to report
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was
  unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`.
  However doing so gave me a menu with unrelated option (as expected)
  and an "Other problem..." option. I assumed this was for generic other
  bugs, as I think is reasonable; however, it brings me to a menu that
  only makes sense for display-related bugs. I think this text should be
  changed to note that; perhaps "Other display problem...".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 
13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash
   640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 
13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash
  CurrentDesktop: KDE
  Date: Tue Apr  5 19:58:56 2022
  InstallationDate: Installed on 2022-03-30 (6 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967965/+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 1968412] Re: When trying to open the program it says that i need to be in a special group to use it

[Brian Murray]

This may be a duplicate of bug 1965439.

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

Title:
  When trying to open the program it says that i need to be in a special
  group to use it

Status in software-properties package in Ubuntu:
  New

Bug description:
  Version: 0.99.22
  Kubuntu version 22.04
  I expected it to open up the software properties without any errors.
  It said that i need to be in a special group (wheel) to use it.
  It says the password is incorrect even though i use this password to log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-qt 0.99.22
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sat Apr  9 11:59:59 2022
  InstallationDate: Installed on 2022-04-09 (0 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968412/+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 1871538] Please test proposed package

[Brian Murray]

Hello Christian, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Committed
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Mul

[Touch-packages] [Bug 1962038] Re: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

[Brian Murray]

Hello Steve, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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 removed: verification-done-impish
** Tags added: verification-needed-impish

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

Title:
  wrong sysrq value in /usr/lib/sysctl.d/50-default.conf

Status in procps package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in procps source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  Fix Committed
Status in procps source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  I've just learned that systemd is setting kernel.sysrq to 16 in
  /usr/lib/sysctl.d/50-default.conf.  This is inconsistent with
  /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176
  by default.  systemd should drop its setting to defer to the file that
  we have been carrying in procps for a very long time.

  Therefore, users can only sync their storage but not do any other
  actions using the magic sysrq key.

  [Test Plan]

  $ sysctl kernel.sysrq
  => This should show "kernel.sysrq = 176" as set by 
/etc/sysctl.d/10-magic-sysrq.conf
  $ sysctl net.ipv4.conf.all.rp_filter
  => This should show "net.ipv4.conf.all.rp_filter=2" as set by 
/etc/sysctl.d/10-network-security.conf

  [Where problems could occur]

   * This patch changes systemd's sysctl configuration in /lib/sysctl.d/*.conf
   * If something is broken it could fail to apply any of systemd's sysctl 
configuration, but Ubuntu's defaults from /etc/sysctl.d/*.conf would still be 
in place.

  [Other Info]
   
   * None

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1962038/+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 1955997] Re: The airplane hotkey has no function on a HP platform

[Brian Murray]

Hello jeremyszu, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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 removed: verification-done verification-done-impish
** Tags added: verification-needed verification-needed-impish

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  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 Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID

[Touch-packages] [Bug 1967576] Re: systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units

[Brian Murray]

Hello Nick, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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 Impish)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  systemd: autopkgtest: tests-in-lxd fails because of remaining snap
  .mount units

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  This build log provides an example of the problem:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz.

  During setup for tests-in-lxd, an attempt is made to purge snapd, but
  this fails:

  [ ... ]
  Purging configuration files for snapd (2.54.3+21.10.1ubuntu0.2) ...
  Stopping snap.lxd.activate.service
  Stopping unit snap.lxd.activate.service
  Waiting until unit snap.lxd.activate.service is stopped [attempt 1]
  snap.lxd.activate.service is stopped.
  Removing snap.lxd.activate.service
  Stopping snap.lxd.daemon.service
  Stopping unit snap.lxd.daemon.service
  Waiting until unit snap.lxd.daemon.service is stopped [attempt 1]
  snap.lxd.daemon.service is stopped.
  Removing snap.lxd.daemon.service
  Stopping snap.lxd.user-daemon.service
  Stopping unit snap.lxd.user-daemon.service
  Waiting until unit snap.lxd.user-daemon.service is stopped [attempt 1]
  snap.lxd.user-daemon.service is stopped.
  Removing snap.lxd.user-daemon.service
  Stopping snap-core20-1378.mount
  Stopping unit snap-core20-1378.mount
  Waiting until unit snap-core20-1378.mount is stopped [attempt 1]
  snap-core20-1378.mount is stopped.
  Removing snap core20 and revision 1378
  Removing snap-core20-1378.mount
  Stopping snap-lxd-22672.mount
  Stopping unit snap-lxd-22672.mount
  Waiting until unit snap-lxd-22672.mount is stopped [attempt 1]
  snap-lxd-22672.mount is stopped.
  Removing snap lxd and revision 22672
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/meminfo': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/stat': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/uptime': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/diskstats': 
Function not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/swaps': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/loadavg': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/slabinfo': 
Function not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpu0': Operation not 
permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpuidle': Operation 
not permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/uevent': Function 
not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/svm': Function not 
implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/hotplug': Operation 
not permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/offline': Function 
not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/present': Function 
not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/power': Operation 
not permitted
  rm: cannot remove 
'/var/snap/lxd

[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

[Brian Murray]

I sponsored this, thanks!

** Tags removed: rls-jj-incoming

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  Triaged
Status in dbus source package in Jammy:
  Triaged

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1966800] Re: systemd locks up due to incorrect handling of time zone changes

[Brian Murray]

** Tags added: rls-jj-incoming

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

Title:
  systemd locks up due to incorrect handling of time zone changes

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Fedora:
  Unknown

Bug description:
  Recently on systems in Ireland, systemd became unresponsive due the
  change from GMT to Irish Standard Time. This is due to Ireland being
  unique in having their standard time during the summer, unlike most
  regions.

  Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1941335
  Fixed by: 
https://github.com/systemd/systemd-stable/commit/a8b66ca9af811148b67ee952ab32748f88b8bba3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966800/+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 1965964] Re: an error has occurred while searching for drivers

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1964880
   software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'

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

Title:
  an error has occurred while searching for drivers

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  when going to additional drivers it says an error has occurred while
  searching for drivers. I am using Ubuntu 22.04.

  software-properties-gtk:
  Installed: 0.99.19

  
  
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:49:
 PyGIWarning: Handy was imported without specifying a version first. Use 
gi.require_version('Handy', '1') before import to ensure that the right version 
gets loaded.
from gi.repository import GObject, Gdk, Gtk, Gio, GLib, Handy
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1380, in detect_drivers
  self.devices = detect.system_device_drivers(self.apt_cache)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in 
system_device_drivers
  for pkg, pkginfo in system_driver_packages(apt_cache, sys_path,
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in 
system_driver_packages
  for p in packages_for_modalias(apt_cache, alias):
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in 
packages_for_modalias
  apt_cache_hash = hash(package.get_fullname() for package in 
apt_cache.packages)
  AttributeError: 'Cache' object has no attribute 'packages'

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 15:57:06 2022
  InstallationDate: Installed on 2022-03-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965964/+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 1965857] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1964880
   software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'

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

Title:
  software-properties-gtk crashed with AttributeError in
  packages_for_modalias(): 'Cache' object has no attribute 'packages'

Status in software-properties package in Ubuntu:
  New

Bug description:
  live patch not active

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 10:22:47 2022
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2020-04-25 (695 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=6
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 
3.10.1-0ubuntu2
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=6']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'
  UpgradeStatus: Upgraded to jammy on 2022-02-12 (37 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965857/+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 1965180] Re: apt-add-repository requires --login for private repos, breaking automated workflows

[Brian Murray]

** Changed in: software-properties (Ubuntu Jammy)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: software-properties (Ubuntu Jammy)
   Status: New => In Progress

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

Title:
  apt-add-repository requires --login for private repos, breaking
  automated workflows

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Jammy:
  In Progress

Bug description:
  On Focal, in an automated environment (such as a launchpad builder), a
  used can do the following workflow:

  curl
  "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x${FINGERPRINT}";
  --output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu focal main"

  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
  Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
  Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64 
Packages [3288 B] 
  Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main 
Translation-en [1892 B]  

  However, on Jammy, I get the following:

  
  curl "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x${FINGERPRINT}"; 
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu jammy main"

  Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105, 
in lpppa
  self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 
592, in __call__
  response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
429, in _request
  raise error
  lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
  Response headers:
  ---
  -content-encoding: gzip
  content-length: 91
  content-type: text/plain;charset=utf-8
  date: Wed, 16 Mar 2022 19:54:16 GMT
  server: gunicorn/19.8.1
  status: 404
  vary: Accept-Encoding
  x-powered-by: Zope (www.zope.org), Python (www.python.org)
  x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
  x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
  ---
  Response body:
  ---
  b"Object: , 
name: '$REPO'"
  ---

  
  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
  self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
  if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117, 
in description
  return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109, 
in lpppa
  raise ShortcutException(msg)
  softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa 
'$REPO/proposed' not found (use --login if private)

  Impish similarly breaks. Digging through changelogs, I see various
  entries in Impish forward, starting with version 0.99.0 where a
  refactor was done.

  using `--login` is not possible in an automated setup (such as a
  builder) as it starts an OAuth dance, which requires human
  interaction. this will break existing automation utilizing apt-add-
  repository for users when migrating to Jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965180/+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 1923052] Re: screen reader does not read ubiquity window

[Brian Murray]

** Changed in: ubiquity (Ubuntu Jammy)
Milestone: None => ubuntu-22.04

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

Title:
  screen reader does not read ubiquity window

Status in at-spi2-core package in Ubuntu:
  Incomplete
Status in orca package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Confirmed
Status in at-spi2-core source package in Jammy:
  Incomplete
Status in orca source package in Jammy:
  Incomplete
Status in ubiquity source package in Jammy:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run Ubuntu MATE 21.04 installation media
  2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info 
testcase by pressing ++ to activate screenreader with shown 
Ubiquity window, press  to select some button

  Expected result:
  * screen reader reads ubiquity window

  Actual result:
  * screen reader does not read ubiquity window

  Note: screen reader actually works, it reads other windows - for
  example the terminal opened by ++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  8 13:01:30 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+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 1923052] Re: screen reader does not read ubiquity window

[Brian Murray]

I also tested this with an Ubuntu 21.10 image and observed the same
behavior as with Jammy.

** Also affects: orca (Ubuntu Jammy)
   Importance: Undecided
   Status: Incomplete

** Also affects: ubiquity (Ubuntu Jammy)
   Importance: High
   Status: Confirmed

** Also affects: at-spi2-core (Ubuntu Jammy)
   Importance: Undecided
   Status: Incomplete

** Tags removed: rls-jj-incoming

** Tags added: fr-2159

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

Title:
  screen reader does not read ubiquity window

Status in at-spi2-core package in Ubuntu:
  Incomplete
Status in orca package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Confirmed
Status in at-spi2-core source package in Jammy:
  Incomplete
Status in orca source package in Jammy:
  Incomplete
Status in ubiquity source package in Jammy:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run Ubuntu MATE 21.04 installation media
  2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info 
testcase by pressing ++ to activate screenreader with shown 
Ubiquity window, press  to select some button

  Expected result:
  * screen reader reads ubiquity window

  Actual result:
  * screen reader does not read ubiquity window

  Note: screen reader actually works, it reads other windows - for
  example the terminal opened by ++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  8 13:01:30 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+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 1966416] Re: pam_faillock does not actually deny login after given number of failures

[Brian Murray]

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

** Tags removed: rls-jj-incoming

** Changed in: pam (Ubuntu Jammy)
   Importance: Undecided => High

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

Title:
  pam_faillock does not actually deny login after given number of
  failures

Status in pam package in Ubuntu:
  New
Status in pam source package in Jammy:
  New

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libpam-modules 1.4.0-11ubuntu1

  I just noticed that Ubuntu 22.04 changed from the old pam_tally2
  module to the more widespread pam_faillock one. \o/

  However, locking (denying logins) does not actually seem to work.
  According to pam_faillock(8) I changed the config like this:

  # diff -u /etc/pam.d/common-auth{.orig,}
  --- /etc/pam.d/common-auth.orig   2022-03-25 10:41:29.08800 +
  +++ /etc/pam.d/common-auth2022-03-25 10:48:48.913419254 +
  @@ -17,11 +17,11 @@
   auth [success=2 default=ignore]  pam_unix.so nullok
   auth [success=1 default=ignore]  pam_sss.so use_first_pass
   # here's the fallback if no module succeeds
  -auth requisite   pam_deny.so
  +auth [default=die] pam_faillock.so authfail
   # prime the stack with a positive return value if there isn't one already;
   # this avoids us returning an error just because nothing sets a success code
   # since the modules above will each just jump around
  -auth requiredpam_permit.so
  +auth sufficient pam_faillock.so authsucc
   # and here are more per-package modules (the "Additional" block)
   auth optionalpam_cap.so 
   # end of pam-auth-update config

  
  This config works fine on both Debian 11 and Debian testing, and it agrees 
with the example in the manpage -- so I don't think it's that broken.

  Start from a blank slate:

  # faillock  --user admin --reset
  # faillock  --user admin 
  admin:
  WhenType  Source   
Valid

  Now I log in as user "admin" with a wrong password four times (one
  more than the default "deny=3", just to make sure):

sshd[3841]: pam_unix(sshd:auth): authentication failure; logname= uid=0 
euid=0 tty=ssh ruser= rhost=172.27.0.2  user=admin
sshd[3841]: Failed password for admin from 172.27.0.2 port 39446 ssh2

  After the third time, I even see this in the journal:

sshd[3841]: Failed password for admin from 172.27.0.2 port 39446 ssh2
pam_faillock(sshd:auth): Consecutive login failures for user admin account 
temporarily locked
Failed password for admin from 172.27.0.2 port 39446 ssh2

  
  But if I then log in with the correct password, it succeeds:

   sshd[4492]: Accepted password for admin from 172.27.0.2 port 39450 ssh2
   sshd[4492]: pam_unix(sshd:session): session opened for user admin(uid=1000) 
by (uid=0)

  That's buggy -- "admin" should be denied access for ten minutes
  ("unlock_time = 600" in /etc/security/faillock.conf).

  It did record the failed logins alright:

  # faillock  --user admin 
  admin:
  WhenType  Source   
Valid
  2022-03-25 10:54:02 RHOST 172.27.0.2  
 V
  2022-03-25 10:54:27 RHOST 172.27.0.2  
 V
  2022-03-25 10:54:30 RHOST 172.27.0.2  
 V

  But the actual denial doesn't seem to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1966416/+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 1923052] Re: screen reader does not read ubiquity window

[Brian Murray]

I tested this following the instructions in test case 1309 and did not
hear the screen reader read the ubiquity window after choosing Try
Ubuntu. The screen reader was working though and happily read other
windows.

** Changed in: ubiquity (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  screen reader does not read ubiquity window

Status in at-spi2-core package in Ubuntu:
  Incomplete
Status in orca package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run Ubuntu MATE 21.04 installation media
  2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info 
testcase by pressing ++ to activate screenreader with shown 
Ubiquity window, press  to select some button

  Expected result:
  * screen reader reads ubiquity window

  Actual result:
  * screen reader does not read ubiquity window

  Note: screen reader actually works, it reads other windows - for
  example the terminal opened by ++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  8 13:01:30 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+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 1966381] Re: applications crash that never crashed under Ubuntu-20.04

[Brian Murray]

** Also affects: systemd (Ubuntu Jammy)
   Importance: High
   Status: New

** Tags removed: rls-jj-incoming

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

Title:
  applications crash that never crashed under Ubuntu-20.04

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

Bug description:
  Just now I was watching some video in Firefox. I popped over to
  another virtual workspace for a few minutes, and when I popped back to
  Firefox it had gone. The same thing had been happening all week (I
  installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and
  Thunderbird.

  This time instead of shrugging it off I looked in the logs, and found
  this

  Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed 
/user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope
 due to memory used (15940579328) / total (16153944064) and swap used 
(925564928) / total (1023406080) being more than 90.00%
  Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: 
systemd-oomd killed 298 process(es) in this unit.
  Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed 
/user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope
 due to memory used (15591993344) / total (16149745664) and swap used 
(927760384) / total (1023406080) being more than 90.00%
  Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: 
systemd-oomd killed 173 process(es) in this unit.

  I know it's saying those three entirely unrelated applications had
  suddenly decided to swallow all the RAM+swap on this laptop of mine -
  but the very same apps didn't act like that last week under
  Ubuntu-20.04, so I suspect something else is going on

  I can't say they hadn't swallowed all the RAM, but there is ZERO sign
  of a system on the verge of collapsing - everything has been screaming
  along just nicely - no sign of the "staggering" you normally get when
  the OS is heavily into swap.

  However, now that I look I see my 16G laptop only has 1G swap??? I
  just let the Ubuntu installer do it's defaults - but it used to auto-
  choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be
  related?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd-oomd 249.11-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 25 19:47:44 2022
  InstallationDate: Installed on 2022-03-13 (11 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 1967165] [NEW] package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Brian Hardenstein]

Public bug reported:

automated update

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
Uname: Linux 5.4.0-104-generic x86_64
NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal 
falcon_lsm_pinned_13207 falcon_lsm_pinned_13109 nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Mar 30 06:47:50 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2022-02-10 (48 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  automated update

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  Uname: Linux 5.4.0-104-generic x86_64
  NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal 
falcon_lsm_pinned_13207 falcon_lsm_pinned_13109 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 30 06:47:50 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-02-10 (48 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1967165/+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 1967014] Re: Lenovo Ideapad 3 screen brightness F keys not working...

[Brian Murray]

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

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

Title:
  Lenovo Ideapad 3 screen brightness F keys not working...

Status in systemd package in Ubuntu:
  New

Bug description:
  As the title says, the F keys the control screen brightness (F11/F12
  on the Lenovo Ideapad 3 15ITL05 laptop I have) don't work on Ubuntu
  21.10. All other special function keys (volume up/down, lock screen,
  airplane mode, etc...) and the screen brightness slider in the top
  right-hand corner work; it's just the brightness keys that are not
  working.

  I know I can just use the slider, but it's more convenient to use the
  F keys. I hope you are working on this for a future 21.10 update.

  Also, I originally installed 20.04 and upgraded to 21.10, but even on
  20.04, those keys weren't working, either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1967014/+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 1965661] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1964880
   software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'

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

Title:
  software-properties-gtk crashed with AttributeError in
  packages_for_modalias(): 'Cache' object has no attribute 'packages'

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  software-properties-gtk crashed with AttributeError in
  packages_for_modalias(): 'Cache' object has no attribute 'packages'

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 03:33:53 2022
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2022-03-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 
3.10.1-0ubuntu2
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965661/+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 1959047] Re: systemd ignores RootDirectory option in .service units

[Brian Murray]

Hello MegaBrutal, or anyone else affected,

Accepted lxd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxd/3.0.3-0ubuntu1~18.04.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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

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

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

** Changed in: lxd (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  systemd ignores RootDirectory option in .service units

Status in lxd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in lxd source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in systemd source package in Impish:
  Confirmed

Bug description:
  [Impact]

  Ubuntu carries a patch on top of systemd [a] to silence
  namespace set up failures. This is meant as a workaround
  for a bug in the LXD version shipped in Ubuntu 18.04.

  Masking namespace set up failures creates a false sense of
  security for the user/admin.

  As mentioned in comment #1, systemd upstream explains that silencing
  this kind of error is dangerous and should be avoided.

  Backporting the LXD fix [b] to Ubuntu 18.04 would allow namespaces
  to work inside containers. This is the goal of this SRU.

  Ultimately, once LXD in Ubuntu 18.04 includes the fix [b], it would
  be possible to drop the Ubuntu-specific patch for systemd [a]. This
  is however *not an immediate concern for this SRU*.

  [Test Plan]

  1) Create a 18.04 VM:
  $ lxc launch images:ubuntu/18.04 lp1959047 --vm
  $ sleep 30  # give it time to boot

  2) Install and initialize LXD in it:
  $ lxc exec lp1959047 -- apt-get update
  $ lxc exec lp1959047 -- apt-get install -y lxd
  $ lxc exec lp1959047 -- lxd init --auto

  3) Create a Jammy container and enable systemd debugging:
  $ lxc exec lp1959047 -- lxc init images:ubuntu/22.04 c1
  $ lxc exec lp1959047 -- lxc config set c1 raw.lxc 'lxc.init.cmd = /sbin/init 
systemd.log_level=debug'
  $ lxc exec lp1959047 -- lxc start c1

  4) Check if namespace set up failures are logged:
  $ lxc exec lp1959047 --  lxc exec c1 -- journalctl -b0 --grep 'Failed to set 
up namespace'
  Mar 24 23:29:19 c1 systemd[99]: systemd-udevd.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:19 c1 systemd[132]: systemd-networkd.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:19 c1 systemd[131]: systemd-logind.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:20 c1 systemd[136]: systemd-resolved.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:20 c1 systemd[128]: e2scrub_reap.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:23 c1 systemd[243]: systemd-hostnamed.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied

  If LXD in Ubuntu 18.04 has the patch, the "Failed to set up namespace"
  messages wouldn't be there.

  [Where problems could occur]

  The LXD fix changes the Apparmor profile used for containers. This essentially
  loosen the mount restrictions applied to containers.

  Weakening the Apparmor profile could make it easier for a process in the 
container
  to do damage that would have otherwise been blocked. On the other hand, this
  allows making use of namespaces/sandboxing inside the container.

  Upstream LXD has the fix since 2019 which make it less likely to run into
  problems with the backport.

  The backported fix was also tested manually to ensure

[Touch-packages] [Bug 1965830] Re: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float'

[Brian Murray]

** Changed in: apport (Ubuntu Jammy)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

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

Title:
  apport-kde crashed with   setGeometry(self, int, int, int, int) in
  ui_start_info_collection_progress(): argument 1 has unexpected type
  'float'

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Jammy:
  In Progress

Bug description:
  this crash did happen after i successfully submitted my last report.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: apport-kde 2.20.11-0ubuntu79
  ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27
  Uname: Linux 5.15.0-23-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon Mar 21 18:22:47 2022
  ExecutablePath: /usr/share/apport/apport-kde
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANG=de_DE.UTF-8
  Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 
3.10.1-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport-kde']
  PythonDetails: N/A
  SourcePackage: apport
  Title: apport-kde crashed with   setGeometry(self, int, int, int, int) in 
ui_start_info_collection_progress(): argument 1 has unexpected type 'float'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm games lpadmin plugdev sudo users vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1965830/+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 1966416] Re: pam_faillock does not actually deny login after given number of failures

[Brian Murray]

** Tags added: rls-jj-incoming

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

Title:
  pam_faillock does not actually deny login after given number of
  failures

Status in pam package in Ubuntu:
  New

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libpam-modules 1.4.0-11ubuntu1

  I just noticed that Ubuntu 22.04 changed from the old pam_tally2
  module to the more widespread pam_faillock one. \o/

  However, locking (denying logins) does not actually seem to work.
  According to pam_faillock(8) I changed the config like this:

  # diff -u /etc/pam.d/common-auth{.orig,}
  --- /etc/pam.d/common-auth.orig   2022-03-25 10:41:29.08800 +
  +++ /etc/pam.d/common-auth2022-03-25 10:48:48.913419254 +
  @@ -17,11 +17,11 @@
   auth [success=2 default=ignore]  pam_unix.so nullok
   auth [success=1 default=ignore]  pam_sss.so use_first_pass
   # here's the fallback if no module succeeds
  -auth requisite   pam_deny.so
  +auth [default=die] pam_faillock.so authfail
   # prime the stack with a positive return value if there isn't one already;
   # this avoids us returning an error just because nothing sets a success code
   # since the modules above will each just jump around
  -auth requiredpam_permit.so
  +auth sufficient pam_faillock.so authsucc
   # and here are more per-package modules (the "Additional" block)
   auth optionalpam_cap.so 
   # end of pam-auth-update config

  
  This config works fine on both Debian 11 and Debian testing, and it agrees 
with the example in the manpage -- so I don't think it's that broken.

  Start from a blank slate:

  # faillock  --user admin --reset
  # faillock  --user admin 
  admin:
  WhenType  Source   
Valid

  Now I log in as user "admin" with a wrong password four times (one
  more than the default "deny=3", just to make sure):

sshd[3841]: pam_unix(sshd:auth): authentication failure; logname= uid=0 
euid=0 tty=ssh ruser= rhost=172.27.0.2  user=admin
sshd[3841]: Failed password for admin from 172.27.0.2 port 39446 ssh2

  After the third time, I even see this in the journal:

sshd[3841]: Failed password for admin from 172.27.0.2 port 39446 ssh2
pam_faillock(sshd:auth): Consecutive login failures for user admin account 
temporarily locked
Failed password for admin from 172.27.0.2 port 39446 ssh2

  
  But if I then log in with the correct password, it succeeds:

   sshd[4492]: Accepted password for admin from 172.27.0.2 port 39450 ssh2
   sshd[4492]: pam_unix(sshd:session): session opened for user admin(uid=1000) 
by (uid=0)

  That's buggy -- "admin" should be denied access for ten minutes
  ("unlock_time = 600" in /etc/security/faillock.conf).

  It did record the failed logins alright:

  # faillock  --user admin 
  admin:
  WhenType  Source   
Valid
  2022-03-25 10:54:02 RHOST 172.27.0.2  
 V
  2022-03-25 10:54:27 RHOST 172.27.0.2  
 V
  2022-03-25 10:54:30 RHOST 172.27.0.2  
 V

  But the actual denial doesn't seem to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1966416/+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 1946388] Re: Journalctl -f --file some.journal causes coredump

[Brian Murray]

Hello Marko, 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.16 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/1946388

Title:
  Journalctl -f --file some.journal causes coredump

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

Bug description:
  [impact]

  journalctl -f --file FILE results in segfault

  [test case]

  $ journalctl -f --file $FILENAME

  [regression potential]

  journalctl segfault or failure to properly operate

  [scope]

  needed in focal

  fixed upstream in 2b6df46d21a at v246, so fixed already in h and later

  [original description]

  Focal latest systemd 245.

  Journalctl -f --file path/to/file.journal.  Will allways causes
  journalctl crash...

  The same doesnt happen on centos8 systemd 239... I couldnt test on any
  more systems atm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1946388/+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 1955997] Re: The airplane hotkey has no function on a HP platform

[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.16 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/1955997

Title:
  The airplane hotkey has no function on a HP platform

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 Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events

[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Brian Murray]

Hello Christian, 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.16 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: 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Committed
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  A

[Touch-packages] [Bug 1958284] Re: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec

[Brian Murray]

Hello Jean, 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.16 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/1958284

Title:
  shutdown hangs at "Waiting for process: ..." for 90s, ignoring
  DefaultTimeoutStopSec

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

Bug description:
  [Impact]

  The systemd shutdown sequence does not honor systemd-system.conf
  settings when waiting for remaining processes. This means that, for
  example, if a systemd service specifies KillMode=process and a process
  remaining from that service does not properly handle SIGTERM, then the
  remaining process will not be killed until after the compiled-in
  default value of DefaultTimeoutStopSec (90s), even if the user has
  changed the setting of DefaultTimeoutStopSec. In such cases, this
  impacts users by significantly increasing the time required for
  shutdown/reboot.

  [Test Plan]

  * Create a new script, /usr/local/bin/loop-ignore-sigterm:
```
#!/bin/bash
loop_forever() {
while true; do sleep 1; done
}

(
trap 'echo Ignoring SIGTERM...' SIGTERM
loop_forever
)

loop_forever
```

This script will spawn a subshell which will loop forever and ignore 
SIGTERM. This will force systemd to wait for the subprocess at 
reboot/shutdown, and eventually send SIGKILL after TimeoutStopSec 
(DefaultTimeoutStopSec in this case).

  * Make the script executable: 
$ chmod +x /usr/local/bin/loop-ignore-sigterm

  * Create a systemd service for this script. Add the following to 
/etc/systemd/system/loop-ignore-sigterm.service:
```
[Service]
KillMode=process
ExecStart=/usr/local/bin/loop-ignore-sigterm
```

  * Start the service:
$ systemctl start loop-ignore-sigterm.service

  * Edit /etc/systemd/system.conf, and uncomment the 
   'DefaultTimeoutStopSec=90s' line. Modify 90s to something much shorter, 
e.g. 20s.

  * Re-exec the daemon so this new default takes effect:
$ systemctl daemon-reexec

  * Reboot, and monitor the logs. Observe that systemd-shutdown will wait 
for the loop-ignore-sigterm process for 90s, instead of the 20s 
configured earlier.

  [Where problems could occur]

  The patch moves the reset_arguments() call to the end of main, which
  means reset_arguments() is no longer called before daemon re-execution
  (if that branch is taken). If anything in that code path relied on
  reset_arguments() being called before re-executing, those assumptions
  could be broken. Any such problems would potentially be seen during
  daemon re-execution, e.g. when calling systemctl daemon-reexec.

  [ Original Description ]

  With systemd v245 as shipped with 20.04, the shutdown sequence does
  not use the value of `DefaultTimeoutStopSec` to wait for remaining
  processes, it instead uses the compiled in default of 90s.

  This is most visible with services that use `KillMode=process`
  (docker, k8s, k3s, etc...), especially if the remaining processes do
  not handle `SIGTERM` or choose to ignore it.

  For example:
  ```
  [ OK ] Finished Reboot.
  [ OK ] Reached target Reboot.
  [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, 
containerd-shim, containerd-shim, fluent-bit

  --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower
  value ---

  ```

  The bug has been fixed upstream here:
  https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22

  Marc was kind enou

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

[Brian Murray]

Hello jeremyszu, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.4 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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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 Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  The airplane hotkey has no function on a HP platform

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 Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  ev

[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Brian Murray]

Hello Christian, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.4 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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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 Impish)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Committed
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update