[Touch-packages] [Bug 1973306] Re: packages freezes on authentification with Wayland

2022-09-14 Thread Launchpad Bug Tracker
[Expired for software-properties (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  packages freezes on authentification with Wayland

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  I want to report an issue which might well have been reported already,
  although i could not find it. A few weeks ago I switched from Ubuntu
  LTS 20.04 towards the LTS 22.04 with Wayland as default.

  I discovered that there is a sort of incompatibility between the
  software-properties-package and the Wayland protocol, which occurs
  systematically and never occurs when switching back to Xorg.

  When one tries to add or change a rule in ‘other software’ the
  application always freezes when the user is asked to authenticate. As
  soon a one cancels the authentification procedure it unfreezes almost
  immediately, but freezes again when the user retries to complete the
  adding or alteration procedure. As said, this error never occurs if
  the user switches back to an Xorg session.

  See screenshot: the window with the communication 'software & updates
  does not respond' and with the choice to close or to wait is hidden
  behind the authentification window.

  I am not really sure whether this bug has to be reported as a security
  issue, but certainly the software-properties-package is of utmost
  importance for a stable and secure OS.

  My system:

  OS: Ubuntu 22.04 LTS x86_64
  Kernel: 5.15.0-30-generic
  Uptime: 13 mins
  Packages: 1940 (dpkg), 17 (flatpak),
  Shell: bash 5.1.16
  Resolution: 1920x1080
  DE: GNOME 42.0
  WM: Mutter
  WM Theme: Adwaita
  Theme: Adwaita [GTK2/3]
  Icons: Numix [GTK2/3]
  Terminal: gnome-terminal
  CPU: Intel i7-10510U (8) @ 4.900GHz
  GPU: Intel CometLake-U GT2 [UHD Grap
  Memory: 2992MiB / 64007MiB

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


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


[Touch-packages] [Bug 1276322] Re: [enhancement] Mir lacks relative mouse support

2022-09-14 Thread Daniel van Vugt
** Changed in: mir (Ubuntu)
 Assignee: aalosman (aalosman) => (unassigned)

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

Title:
  [enhancement] Mir lacks relative mouse support

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Mir lacks relative mouse support, as well as a way to warp the mouse.
  This is a problem when it comes to SDL as quite a few games depend on
  these features.

  SDL bug report:
  https://bugzilla.libsdl.org/show_bug.cgi?id=2380

  This is the only thing that is blocking full SDL Mir support.

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


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


[Touch-packages] [Bug 1988870] Re: apport-autoreport.service fails: whoopsie.path is not enabled

2022-09-14 Thread satmandu
The Diagnostics option showed as "Automatic"... and then showed "Never"!

I flipped it to automatic, and now I see this:

systemctl status whoopsie.path
● whoopsie.path - Start whoopsie on modification of the /var/crash directory
 Loaded: loaded (/lib/systemd/system/whoopsie.path; enabled; preset: 
enabled)
 Active: active (waiting) since Wed 2022-09-14 22:18:25 EDT; 2min 5s ago
  Until: Wed 2022-09-14 22:18:25 EDT; 2min 5s ago
   Triggers: ● whoopsie.service

systemctl status apport-autoreport.service
× apport-autoreport.service - Process error reports when automatic reporting is 
enabled
 Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static)
 Active: failed (Result: exit-code) since Wed 2022-09-14 22:19:37 EDT; 2min 
18s ago
TriggeredBy: ● apport-autoreport.timer
 ● apport-autoreport.path
Process: 18585 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 20 
(code=exited, status=2)
   Main PID: 18585 (code=exited, status=2)
CPU: 17.854s

Sep 14 22:19:05 mbp113 whoopsie-upload-all[18585]: WARNING: hook failed for 
processing /var/crash/_opt_Signal_signal-desktop.1000.crash:
Sep 14 22:19:07 mbp113 whoopsie-upload-all[18585]: INFO:root:Marking 
/var/crash/_opt_Signal_signal-desktop.1000.crash for whoopsie upload
Sep 14 22:19:07 mbp113 whoopsie-upload-all[18585]: INFO:root:Waiting for 
whoopsie to upload reports (timeout: 20 s)
Sep 14 22:19:07 mbp113 whoopsie-upload-all[18585]: INFO:root:  missing 
(remaining: 20 s): /var/crash/_usr_libexec_goa-daemon.1000.uploaded 
/var/crash/_opt_Signal_signal-desktop.1000.uploaded
Sep 14 22:19:17 mbp113 whoopsie-upload-all[18585]: INFO:root:  missing 
(remaining: 10 s): /var/crash/_opt_Signal_signal-desktop.1000.uploaded
Sep 14 22:19:27 mbp113 whoopsie-upload-all[18585]: INFO:root:  missing 
(remaining: 0 s): /var/crash/_opt_Signal_signal-desktop.1000.uploaded
Sep 14 22:19:37 mbp113 systemd[1]: apport-autoreport.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
Sep 14 22:19:37 mbp113 systemd[1]: apport-autoreport.service: Failed with 
result 'exit-code'.
Sep 14 22:19:37 mbp113 systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.
Sep 14 22:19:37 mbp113 systemd[1]: apport-autoreport.service: Consumed 17.854s 
CPU time.

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

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

Status in apport package in Ubuntu:
  Invalid

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.23.0-0ubuntu1
  Uname: Linux 6.0.0-rc4 x86_64
  NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 20795) Tue Sep  6 14:26:35 2022: called for pid 3732, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 20795) Tue Sep  6 14:26:35 2022: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
   ERROR: apport (pid 20795) Tue Sep  6 14:26:36 2022: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 20795) Tue Sep  6 14:26:46 2022: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashReports:
   640:1000:123:43075180:2022-09-06 14:26:45.388720512 -0400:2022-09-06 
14:27:48.608538333 -0400:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:123:8681261:2022-08-29 22:32:29.231918756 -0400:2022-08-29 
20:57:41.939131333 -0400:/var/crash/_usr_libexec_goa-daemon.1000.crash
   640:1000:

[Touch-packages] [Bug 1988870] Re: apport-autoreport.service fails: whoopsie.path is not enabled

2022-09-14 Thread satmandu
ls /var/crash/
_opt_Signal_signal-desktop.1000.crash   _usr_bin_gnome-shell.1000.crash   
_usr_bin_gnome-shell.1000.uploaded  _usr_libexec_goa-daemon.1000.upload
_opt_Signal_signal-desktop.1000.upload  _usr_bin_gnome-shell.1000.upload  
_usr_libexec_goa-daemon.1000.crash  _usr_libexec_goa-daemon.1000.uploaded

I guess it is working now...

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

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

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

Status in apport package in Ubuntu:
  Invalid

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

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

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

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

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


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


[Touch-packages] [Bug 1276322] Re: [enhancement] Mir lacks relative mouse support

2022-09-14 Thread aalosman
** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => aalosman (aalosman)

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

Title:
  [enhancement] Mir lacks relative mouse support

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Mir lacks relative mouse support, as well as a way to warp the mouse.
  This is a problem when it comes to SDL as quite a few games depend on
  these features.

  SDL bug report:
  https://bugzilla.libsdl.org/show_bug.cgi?id=2380

  This is the only thing that is blocking full SDL Mir support.

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


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


[Touch-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-09-14 Thread Seth Tanner
We're seeing the same behavior with Dell Precision 3600 series desktops and HID 
Global OMNIKEY 3x21 Smart Card Readers
We did not encounter the issue with 18.04 or 20.04, only in 22.04.
sudo systemctl enable pcscd.socket
does not seem to resolve the issue for us
sudo systemctl start pcscd.service
must be run after every reboot, we haven't seen any solution that persists a 
reboot.

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions


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


[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files

2022-09-14 Thread Jeremy Bicha
This bug **is** the tracker bug for the issue we believe was triggered
by libcanberra.

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

Title:
  Evolution not deleting autosave files

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid
Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xx ("xx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

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


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


[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files

2022-09-14 Thread Lindsay
Can you cite the bug report on the libcanberra package which relates to
this issue? There are LOTS of them.

FWIW, the only component of the several components of the evolution
suite which EXPLICITLY depends on libcanberra (ldd |grep canberra)
is /usr/libexec/evolution-data-server/evolution-alarm-notify. Disabling
the loading of this module by renaming it does NOT fix the problem, so
if the problem is indeed in libcanberra then it must be used implicitly
by some other part of the suite.

 or else something much more esoteric is going on :)

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

Title:
  Evolution not deleting autosave files

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid
Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xx ("xx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

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


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


[Touch-packages] [Bug 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic

2022-09-14 Thread Launchpad Bug Tracker
This bug was fixed in the package poppler - 0.62.0-2ubuntu2.14

---
poppler (0.62.0-2ubuntu2.14) bionic-security; urgency=medium

  * SECURITY REGRESSION: Adding missing install header
- debian/patches/0001-Install-goo-GooCheckedOps.h.patch:
  this add goo/GooCheckedOps.h to the CMakeLists.txt in order
  to it be distributed in the libpoppler-private-dev that was
  missing in the previous fix for CVE-2022-38784. (LP: #1989515)

 -- Leonidas Da Silva Barbosa   Wed, 14 Sep
2022 13:46:18 -0300

** Changed in: poppler (Ubuntu)
   Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-38784

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

Title:
  "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu
  Bionic

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on
  Ubuntu Bionic but "goo/gmem.h" still has the statement `#include
  "GooCheckedOps.h"`. As a result, a compile error will happen when
  compiling code that uses poppler:

  /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h:
  No such file or directory

  I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the
  previous version) installed. I confirmed that "goo/gmem.h" doesn't
  have the `#include "GooCheckedOps.h"` statement.

  I found this issue when I was compiling gdal on my Docker container.
  The Docker container was installed the problematic version
  0.62.0-2ubuntu2.13 and I ran into the "No such file or directory"
  error.

  I compiled on both Amd64 and AArch64 and I ran into the same error on
  both platforms.

  By reading the diff between 2.12 and 2.13
  
(https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz),
  the patch looks quite right. But when I examined the contents of the
  built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h".

  Kind of weird, because the problem seems to be caused by applying
  "CVE-2022-38784-pre.patch" in half: the first part that creates
  "goo/GooCheckedOps.h" was not applied during the build process and the
  second part that modifies "goo/gmem.h" was applied.

  Any thoughts? Ideas?

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


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


[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

2022-09-14 Thread Hannu E K N
Oh, I DO have sound in the speakers, BT high def (A2DP) audio too...

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

2022-09-14 Thread Hannu E K N
$ lspci | grep -i audio
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller 
(rev a1)

*** Is there REALLY Realtek audio hardware in here too? 
*** or just a partly initialized driver due to the missing hardware?

Looks as that driver(?) in linux-modules-extra-(uname -r)...

$ apt-file find snd-hda-intel | grep $(uname -r)
linux-modules-extra-5.13.0-52-generic: 
/lib/modules/5.13.0-52-generic/kernel/sound/pci/hda/snd-hda-intel.ko

$ apt-file find snd-hda-intel | wc -l
576

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeK

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

2022-09-14 Thread Hannu E K N
$ cat /sys/class/sound/hwC0D0/vendor_name
Realtek

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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


[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

2022-09-14 Thread Hannu E K N
Hmm...

$ cat /sys/class/sound/hwC0D0/chip_name
ALC294

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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


[Touch-packages] [Bug 1989381] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to install/upgrade: o subprocesso instalado, do pacote linux-firmware, o script post-installation retor

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

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

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

** Tags added: no-boot-space

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

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

Status in initramfs-tools package in Ubuntu:
  Invalid

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1989381/+subscriptions


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


[Touch-packages] [Bug 1989618] [NEW] [Feature Request] Include support for LACP bonds in initramfs

2022-09-14 Thread Fabio Augusto Miranda Martins
Public bug reported:

Feature Request:

When installing a system over the network using live installer
(subiquity), you can use the kernel cmdline option ip= [1] to provide
the network configuration.

In certain situations, it would be ideal to be able to configure a lacp
bond during this process. Sometimes the network ports on the switch are
configured with lacp bond (802.3ad) and the switch won't let an
interface be brought up unless it sends lacpdus.

I've discussed this through a subiquity bug [2] and it was mentioned
that there doesn't seem to be any support in our initramfs for LACP
bonds [3]. It was requested for a new bug to be filed at the initramfs-
tools project for such functionality to get included.

I don't have any use case at the moment, but I've received this request
in the past when the customer was still using debian installer. For
debian-installer this was once discussed via a debian bug [4] and a
patch was proposed [5], but this was never accepted / merged.

Considering that Tte new installer is an _entirely_ different codebase
than d-i, the lacp support would have to come from the initramfs.


[1] 
ip=:
[2] https://bugs.launchpad.net/subiquity/+bug/1988480
[3] https://bugs.launchpad.net/subiquity/+bug/1988480/comments/17
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611250
[5] 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=611250;filename=bonding_v2.patch;msg=39

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [Feature Request] Include support for LACP bonds in initramfs

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Feature Request:

  When installing a system over the network using live installer
  (subiquity), you can use the kernel cmdline option ip= [1] to provide
  the network configuration.

  In certain situations, it would be ideal to be able to configure a
  lacp bond during this process. Sometimes the network ports on the
  switch are configured with lacp bond (802.3ad) and the switch won't
  let an interface be brought up unless it sends lacpdus.

  I've discussed this through a subiquity bug [2] and it was mentioned
  that there doesn't seem to be any support in our initramfs for LACP
  bonds [3]. It was requested for a new bug to be filed at the
  initramfs-tools project for such functionality to get included.

  I don't have any use case at the moment, but I've received this
  request in the past when the customer was still using debian
  installer. For debian-installer this was once discussed via a debian
  bug [4] and a patch was proposed [5], but this was never accepted /
  merged.

  Considering that Tte new installer is an _entirely_ different codebase
  than d-i, the lacp support would have to come from the initramfs.

  
  [1] 
ip=:
  [2] https://bugs.launchpad.net/subiquity/+bug/1988480
  [3] https://bugs.launchpad.net/subiquity/+bug/1988480/comments/17
  [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611250
  [5] 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=611250;filename=bonding_v2.patch;msg=39

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1989618/+subscriptions


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


[Touch-packages] [Bug 1889443] Re: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`

2022-09-14 Thread Brian Murray
** Changed in: apport (Ubuntu Bionic)
   Status: Confirmed => Triaged

** Changed in: apport (Ubuntu Focal)
   Status: Confirmed => Triaged

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

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

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

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

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

Title:
  "ValueError: ['separator'] has no binary content" when running
  `apport-unpack /var/crash/...`

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Triaged
Status in apport source package in Focal:
  Triaged
Status in apport source package in Jammy:
  Triaged

Bug description:
  The crash file I'm using is as-produced by the system (on groovy), and
  appears to have an empty value for separator:

  $ grep separator /var/crash/_usr_bin_neomutt.1000.crash
  separator:

  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 77, in 
  pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in 
extract_keys
  raise ValueError('%s has no binary content' %
  ValueError: ['separator'] has no binary content

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu42
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu42
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29 
12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash
   640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23 
10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash
   640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29 
12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash
  CurrentDesktop: i3
  Date: Wed Jul 29 12:22:54 2020
  InstallationDate: Installed on 2019-05-07 (448 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago)

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


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


[Touch-packages] [Bug 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible

2022-09-14 Thread Brian Murray
** Changed in: initramfs-tools (Ubuntu Hirsute)
   Status: Confirmed => Won't Fix

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: Confirmed => Triaged

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

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

Title:
  Missing all modules for usb nics in initrd which makes PXE boot
  impossible

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Triaged
Status in initramfs-tools source package in Hirsute:
  Won't Fix
Status in initramfs-tools source package in Impish:
  Won't Fix
Status in initramfs-tools source package in Jammy:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  initrd taken from the live iso for PXE boot does not contain USB NIC
  drivers which makes PXE installation/netboot impossible via usb.

  This is the case on 20.04 server iso (both hwe and normal
  kernel/initrd) and desktop iso.

  "kernel/drivers/net/usb" is empty and needs to be included in the
  initramfs build.

  As most modern thin laptops lack physical rj45 ethernet this is a big
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18
  Uname: Linux 5.8.0-64-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 15 16:47:45 2021
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+subscriptions


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


[Touch-packages] [Bug 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04

2022-09-14 Thread Brian Murray
The failing autopkgtests have been re-run and everything passed.

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

Title:
  Incomplete support for DT_RELR relocations on Ubuntu 22.04

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Jammy:
  Fix Committed
Status in binutils source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * The latest glibc uses DT_RELR relocations,
 but it turned out that the linker support is still incomplete,
 as of binutils-2.38-3ubuntu1 on Ubuntu 22.04.

   * It lacks the fix/commit 'PowerPC64 DT_RELR relative reloc
  addresses'.

   * As discussed at the binutils mailing list:
 https://sourceware.org/pipermail/binutils/2022-March/119921.html
 this fixes several (glibc) regressions (from 574 to 17).

   * Instead of stashing r_offset final address calculations in
 ppc64_elf_size_stubs for use by ppc64_elf_build_stubs,
 section/offset pairs need to be kept.

  [Test Plan]

   * Build and run the official (make) check:
 git clone git://sourceware.org/git/glibc.git
 mkdir build && cd build
 ../glibc/configure --prefix=/usr && make -j8 && make check

  [Where problems could occur]

   * In case relr_addr is not replaced everywhere it's deletion in
 elf64-ppc.c can cause problems, which will mainly occur at build time.

   * The relr section/offset array may lead to problems if the array is not
 properly handled or used.

   * The rewrite of append_relr_off may cause issues due to wrong allocs
 erroneous pointer arithmetic or array handling.

   * The entirely new sort_relr function may introduce new code issues
 or performance issues.

   * The adjustments of ppc64_elf_size_stubs and ppc64_elf_build_stubs to
 the new relr code could be done wrong
 in which case the linker support is still not working.

   * But the patch was discussed at the upstream mailing list:
 https://sourceware.org/pipermail/binutils/2022-March/thread.html#119921

   * and is limited to ppc, and even to file 'elf64-ppc.c'.
  __

  == Comment: #0 - Matheus Salgueiro Castanho  - 2022-06-09 
09:32:29 ==
  ---Problem Description---
  Latest glibc uses DT_RELR relocations, but linker support is incomplete as of 
binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated 
into the upstream 2.38 branch:

  PowerPC64 DT_RELR relative reloc addresses
  
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858

  As mentioned in the binutils mailing list when this patch was discussed, this 
fixes several glibc regressions:
  https://sourceware.org/pipermail/binutils/2022-March/119921.html

  Contact Information = Matheus Castanho/mscasta...@ibm.com

  ---uname output---
  N/A

  Machine Type = N/A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   git clone git://sourceware.org/git/glibc.git
  mkdir build && cd build
  ../glibc/configure --prefix=/usr && make -j8 && make check

  Userspace tool common name: binutils

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: binutils

  Userspace tool obtained from project website:  na

  *Additional Instructions for Matheus Castanho/mscasta...@ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1978129/+subscriptions


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


[Touch-packages] [Bug 1981385] Re: initrd lacks modules to mount boot image from http boot

2022-09-14 Thread Brian Murray
** Tags added: foundations-triage-discuss

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

Title:
  initrd lacks modules to mount boot image from http boot

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  If you use UEFI http boot to boot an image (rather than an EFI
  executable) and get all the way to a normal userspace, you can access
  the boot image as /dev/pmem0. But this is not accessible in the
  initrd; presumably some modules are missing. Dimitri added some
  modules that are clearly going to be necessary (kernel/drivers/nvdimm)
  in 0.140ubuntu14 and I added kernel/drivers/dax too in local
  experiments but this appears not to be enough to get it to appear.

  This is desirable because then you can just feed an installer ISO to a
  machine via http boot and the installer just works as normal (the
  speed and, uh, quality, of the implementation of HTTP in a given
  machine's firmware may mean this isn't always the best option but it
  would be nice if it worked in case someone's machine actually does
  this well).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981385/+subscriptions


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


[Touch-packages] [Bug 1973734] [pulseaudio/focal] verification still needed

2022-09-14 Thread Brian Murray
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1973734

Title:
  FTBFS on riscv64 in focal

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * FTBFS on riscv64 in focal in unittest of volume test
   * Disable that unit test, as later releases do not run unittests on riscv64, 
and it's better to have up to date pulseaudio on riscv64 (with many security 
fixes), even if it doesn't completely correctly work.

  [Test Plan]

   * autopkgtests pass
   * riscv64 build is successful

  [Where problems could occur]

   * volume-test probably indicates that one can't set volume correctly
  on riscv64

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


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


[Touch-packages] [Bug 1988870] Re: apport-autoreport.service fails: whoopsie.path is not enabled

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

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

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

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

Status in apport package in Ubuntu:
  Incomplete

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

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

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

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

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


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


[Touch-packages] [Bug 1871465] Autopkgtest regression report (openssh/1:8.2p1-4ubuntu0.6)

2022-09-14 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted openssh (1:8.2p1-4ubuntu0.6) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.44.1-1ubuntu1.1 (arm64, amd64, ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#openssh

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  ssh_config(5) contains outdated information

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

Bug description:
  [Impact]

  The problem here is straightforward. 
  The case is to fix manpages. They need to reflect a change done to the code 
some time ago. That problem might be annoying for users before being fixed. 

  Backport upstream fix to Focal
  Origin: 
  
https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636


  [Test Plan]

  Make a container for testing:

  First option:
  $ lxc launch images:ubuntu/bionic focal-test
  $ lxc shell focal-test

  Simply install the openssh package using ‘apt install’ and check both 
ssh_config.5 and sshd_config.5 files. You should be able to spot the ‘ssh_rsa’ 
in these files.
   

  
  [Where problems could occur]

  Any code change might change the behavior of the package in a specific
  situation and cause other errors.

  Next things which might cause regression are new dependencies which
  might not align and it is obvious the dependencies are upgraded and it
  might be a problem, but it is really unlikely.

  Even none of the rather generic cases above does apply here as we only
  change non-functional content in the form of the man page; Therefore
  the only risk is out of re-building the package which could pick up
  something from e.g. a changed toolchain.

  
  [Other Info]

  
  Fixing this is nice for the users, but OTOH very low severity and would cause 
a package download and update on almost every Ubuntu in the world. Therefore we 
will mark this as block-proposed and keep it in focal-proposed so that a later 
real update (security or functional) will pick this up from -proposed and then 
fix it in the field for real.

  original
  report---

  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:

   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates
   by certificate authorities (CAs).  The default is:

     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

   ssh(1) will not accept host certificates signed using algorithms
   other than those specified.

  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

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


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


[Touch-packages] [Bug 1989599] Re: Random auditd start failures on Ubuntu 20.04 EC2 AMIs

2022-09-14 Thread Alan Sparks
Found that I can limit the package install to just:
apt install auditd audispd-plugins -y

with the changes to audit.rules and auditd.conf, and the /etc/default/grub file.
I get random launch failures with the service failure and "no rules".

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

Title:
  Random auditd start failures on Ubuntu 20.04 EC2 AMIs

Status in audit package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  linux-image-aws 5.15.0.1019.23~20.04.11
  auditd 1:2.8.5-2ubuntu6

  
  I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs.  I 
have tested this with published AMIs ami-0123376e204addb71 and 
ami-00bb3d0b5b36e89b8.

  I am following a process that has worked up to June 20 2022.  The
  process installs and configures the audit package for CIS hardening.
  The process steps are:

  • Launch an instance as a base, I’ve used ami-0123376e204addb71 or 
ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs).
  • Installed the packages listed below.
  • Copied the “auditdconf” contents as /etc/audit/auditd.conf
  • Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules
  • Edit /etc/default/grub, and set: GRUB_CMDLINE_LINUX="audit=1 selinux=1 
audit_backlog_limit=8192"
  • Run: grub-mkconfig > /boot/grub/grub.cfg
  • Stopped the instance, and created an AMI.

  I then launch 10 or 14 instances of this AMI in us-west-2.  Most will
  come up with auditd service running, and all rules loaded.  Usually at
  least two come up broken for unknown reason, with the auditd service
  reporting an error I cannot understand:

  ● auditd.service - Security Auditing Service
   Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-09-14 15:08:14 UTC; 
22min ago
 Docs: man:auditd(8)
   https://github.com/linux-audit/audit-documentation
  Process: 357 ExecStart=/sbin/auditd (code=exited, status=1/FAILURE)

  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Starting Security Auditing 
Service...
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error receiving audit netlink 
packet (No buffer space available)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error setting audit daemon pid 
(No buffer space available)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Unable to set audit pid, exiting
  Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: Cannot daemonize (Success)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: The audit daemon is exiting.
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: The audit daemon is exiting.
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Control process 
exited, code=exited, status=1/FAILURE
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Failed with 
result 'exit-code'.
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Failed to start Security 
Auditing Service.

  When I launch the above, it is a launch of 10 or so instances from the
  same AMI, with the same parameters.  Matter of fact, the launch is
  done by requesting X number of instances during the EC2 instance
  launch

  I've been trying to solve this for some time, and I've found the only
  way I can make the instances always start correctly is to remove the
  kernel "audit_backlog_limit" setting entirely - no value for the
  parameter works correctly (tried 320, 8192, 16384, 32768).

  See attachments for the above mentioned files.
  Thanks.
  -Alan

  expected behavior is:
  * service loaded and active
  * "auditctl -l" shows list of loaded rules

  seen behavior:
  * service dead with errors shown above.
  * "auditctl -l" reports "No rules".

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


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


[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

2022-09-14 Thread Hannu E K N
--- audio in the output of lshw ---

   *-multimedia
description: Audio device
product: TU116 High Definition Audio Controller
vendor: NVIDIA Corporation
physical id: 0.1
bus info: pci@:01:00.1
version: a1
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:17 memory:a508-a5083fff
---

*-multimedia
 description: Audio device
 product: Cannon Lake PCH cAVS
 vendor: Intel Corporation
 physical id: 1f.3
 bus info: pci@:00:1f.3
 version: 10
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi bus_master cap_list
 configuration: driver=snd_hda_intel latency=32
 resources: irq:150 memory:a5418000-a541bfff 
memory:a510-a51f
---

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dm

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

2022-09-14 Thread Hannu E K N
--- seen in dmesg ---
[5.815777] Bluetooth: hci0: Firmware revision 0.1 build 26 week 11 2020
[5.881465] NET: Registered protocol family 38
[9.328954] wlo1: authenticate with 94:18:65:08:59:ae
[9.338666] wlo1: send auth to 94:18:65:08:59:ae (try 1/3)
[9.382307] wlo1: authenticated
[9.384831] wlo1: associate with 94:18:65:08:59:ae (try 1/3)
[9.389564] wlo1: RX AssocResp from 94:18:65:08:59:ae (capab=0x431 status=0 
aid=3)
[9.392938] wlo1: associated
[9.505267] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
[   64.717314] snd_hda_intel :00:1f.3: couldn't bind with audio component
[   64.772851] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[   64.772856] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   64.772858] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   64.772860] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   64.772862] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   64.772863] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
[   64.772865] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   65.227287] snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel 
HDMI/DP codec
[   65.231312] hdaudio hdaudioC0D2: Unable to configure, disabling
[   65.232125] input: HDA Intel PCH Headset Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input21
[   65.232353] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input22
[  481.066720] kauditd_printk_skb: 22 callbacks suppressed
[  481.066723] audit: type=1400 audit(1663175820.795:34): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=2107 
comm="cups-browsed" capability=23  capname="sys_nice"
[  482.476639] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit
[  482.476642] usb usb3: root hub lost power or was reset
[  482.476643] usb usb4: root hub lost power or was reset
[  482.598315] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[  482.687635] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
[  484.946351] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[  485.054903] rfkill: input handler disabled
[  491.657064] Bluetooth: RFCOMM TTY layer initialized
[  491.657070] Bluetooth: RFCOMM socket layer initialized
[  491.657073] Bluetooth: RFCOMM ver 1.11
[  491.886727] rfkill: input handler enabled
[  492.013259] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[  493.174837] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[  493.434596] rfkill: input handler disabled

--- end of dmsg ---
" autoconfig for ALC294" =>

$ sudo lshw | grep ALC294 | wc -l
0
$
---
https://www.google.com/search?q=ALC294+%2Bg731 -> notably "g731" doesn't seem 
to be present in the google-search for ALC294 

https://www.google.com/search?q=%2BALC294+%2Bg731 => no match on g731

Why is there an attempt to initialize this non-existant hardware?

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.

[Touch-packages] [Bug 1897932]

2022-09-14 Thread Nick Rosbrook
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.

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

Title:
  systemd-repart not packaged

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

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in their new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  * Attach (local) build-log showing the systemd-repart self-tests passing, as 
found in build-deb/meson-logs/testlog.txt
  * Attach autopkgtest logs showing the regression tests passing (especially 
TEST-58-REPART from "upstream-2" testsuite)
  * Test upgrade-path Jammy->Kinetic to make sure systemd-repart is properly 
replaced by Kinetic's "systemd" binary package

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy so that they can start adopting it in mkosi.

  Runtime behavior of existing components is not affected by the build
  config change.

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


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


[Touch-packages] [Bug 1979952]

2022-09-14 Thread Nick Rosbrook
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.

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

Title:
  Bind mount to NFS mount fails on Ubuntu 22.04

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

Bug description:
  [Impact]
  Some NFS setups that have worked on previous versions of Ubuntu are now 
broken. Specifically, when creating a bind mount, systemd will fail if the 
directory already exists on NFS.

  [Test Plan]
  This test plan requires an NFS server to be in place. The exact setup is not 
important, but for the purposes of this test plan we will assume the server 
exports /data, which contains a directory called home.

  * Make sure nfs-common is installed:

   $ apt install nfs-common -y

  * Check the NFS server exports using showmount:

   $ showmount -e $NFS_SERVER_IP
   Export list for $NFS_SERVER_IP:
   /data *

  * Add the appropriate entries to /etc/fstab. In this example, we will
  make /home2 a bind mount to /data/home:

   # /etc/fstab
   $NFS_SERVER_IP:/data /data nfs defaults,nfsvers=3 0 0
   /data/home /home2 none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0

  * Check systemctl status home2.mount. On an affected system, we should
  see a permission denied error:

   $ systemctl status home2.mount
   x home2.mount - /home2
Loaded: loaded (/etc/fstab; generated)
Active: failed (Result: resources)
 Where: /home2
  What: /data/home
  Docs: man:fstab(5)
man:systemd-fstab-generator(8)

   systemd[1]: home2.mount: Failed to make bind mount source '/data/home': 
Permission denied
   systemd[1]: home2.mount: Failed to run 'mount' task: Permission denied
   systemd[1]: home2.mount: Failed with result 'resources'.
   systemd[1]: Failed to mount /home2.

  * On a patched system, we expect /home2 to be mounted successfully.

  [Where problems could occur]
  The patch makes it so that systemd will not fail bind mounts immediately if 
creating the directory fails. Thus, any regressions would be seen during bind 
mounts with systemd. N.B. that this patch restores previous behavior in systemd.

  [Original Description]
  I have the following setup:
  - /data is an NFS mount.
  - /home is a bind mount to /data/home.

  Configured in /etc/fstab with these lines:

  $FILE_SERVER:/data /data nfs defaults 0 0
  /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0

  This has worked with the same configuration for me on at least Ubuntu 18.04 
and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted 
by systemd.
  So not only is /home not mounted after boot, but also when I run "sudo 
systemctl start home.mount", it fails.

  The journal entries are this:

  sudo[1316]:  wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; 
COMMAND=/usr/bin/systemctl start home.mount
  sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by 
wendler(uid=1000)
  systemd[1]: home.mount: Directory /home to mount over is not empty, mounting 
anyway.
  systemd[1]: home.mount: Failed to make bind mount source '/data/home': 
Permission denied
  systemd[1]: home.mount: Failed to run 'mount' task: Permission denied
  systemd[1]: home.mount: Failed with result 'resources'.
  systemd[1]: Failed to mount /home.

  However, when I run "sudo mount /home" it works.

  Now the weird thing is that after I have mounted /home manually once
  and unmounted it again, then "sudo systemctl start home.mount"
  suddenly also works! But of course only until the next reboot.

  And even if I just do "ls /data" once (either as root or as my user),
  it also makes "sudo systemctl start home.mount" start working!

  To be fully clear:

  - Booting the system (/home fails to mount)
  - sudo systemctl start home.mount  # fails
  - sudo ls /data  # shows correct output
  - sudo systemctl start home.mount  # works!

  Additional information:

  The NFS export for /data has root_squash set and if I remove this
  option, the bind mount of /home works as it should. However, both
  /data and /data/home have mode rwxr-xr-x, so root is able to enter and
  read these directories even despite root_squash.

  It is not a network or mount-order problem. Not only is the bind mount
  to /home correctly attempted after /data is mounted during boot,
  remember that the bind mount also fails when I try it with "sudo
  systemctl start home.mount" minutes afterwards.

  Versions (system is a recent installation with all updates applied):
  - Ubuntu 22.04
  - Linux 5.15.0-40-generic
  - systemd 249.11-0ubuntu3.3
  - util-linux 2.37.2-4ubuntu3

  This appears on both Ubuntu 22.04 machines that I have (a ha

[Touch-packages] [Bug 1981042]

2022-09-14 Thread Nick Rosbrook
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.

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

Title:
  /etc/localtime symlink not correctly handled when using /etc/writable

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

Bug description:
  [Impact]
  When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to 
/etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle 
this correctly when doing firstboot or using inotify to watch for changes to 
localtime.

  [Test Plan]
  This is somewhat hard to test, the following situations need to be reproduced:
  - On firstboot the timezone link will not be read correctly, it will with 
this change.
  - Starting a timer unit and then changing timezone will cause it not to occur 
at the correct time.

  [Where problems could occur]
  This could potentially break other users of localtime, however the change is 
similar to existing changes which have been in Ubuntu's version of systemd for 
some time. The change detects the /etc/writable case and if not should have the 
same existing behaviour.

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


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


[Touch-packages] [Bug 1975667]

2022-09-14 Thread Nick Rosbrook
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.

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

Title:
  systemd-resolved does not reset DNS server and search domain list
  properly after VPN disconnect

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

Bug description:
  [Impact]

  Networking components such as VPNs that rely on systemd-resolved's API
  to configure search domains may inadvertently leave the network
  configuration in a bad state. This is a result of a broken systemd-
  resolved API.

  [Test Plan]
  * On a jammy host, configure a couple search domains with resolvectl:

  $ resolvectl domain  search1.internal search2.internal
  $ resolvectl domain 

  * In any case, both domains should be displayed. Then, attempt to
  clear the configured domains:

  $ resolvectl domain  ""
  $ resolvectl domain 

  * On a patched system, the two domains should no longer be displayed.
  On an un-patched system, one of the domains will still be configured.

  [Where problems could occur]
  This patch touches the logic that configures search domains in 
systemd-resolved. If the patch caused regressions, it would be related to the 
set of configured search domains.

  [Original Description]

  Hi,
  in Ubuntu 21.10 I am facing a problem with DNS server list and search domain 
list is not properly reset back to the previous values after a VPN is 
disconnected. I reproduced this in Ubuntu 21.10 instance which was upgraded 
from the older version of Ubuntu as well as in Live USB Ubuntu 21.10 so it is 
not an "upgrade issue".

  I use this resolv.conf symlink:
  /etc/resolv.conf -> ../run/systemd/resolve/resolv.conf

  Actual behavior:
  VPN connect will add VPN's DNS servers and search domains into 
/etc/resolv.conf. When VPN is disconnected there are some of the VPN's DNS 
server and search domain entries left there, so it is not reset back properly.

  Desired behavior:
  VPN connect will add VPN's DNS servers and search domains into 
/etc/resolv.conf. When VPN is disconnected DNS servers and search domain list 
is restored to exactly the same state as was prior to the VPN connection.

  Steps for reproducing:
  1. Before VPN is connected this is the DNS server and search domain list in 
/etc/resolv.conf:

  nameserver 192.168.122.1
  search .

  2. Once the VPN is connected, we see there were VPN's DNS server and
  serach domain list entries added:

  nameserver 2xx.xx.xx.x0
  nameserver 2xx.xx.xx.x1
  nameserver 192.168.122.1
  search domain1.local domain2.internal domain3.internal

  3. After VPN disconnection, we see the DNS server and search domain
  list in /etc/resolv.conf is not restored to the state at point (1.)
  and some entries from VPN is being kept there:

  nameserver 2xx.xx.xx.x1
  nameserver 192.168.122.1
  search domain2.internal domain3.internal

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 25 06:06:05 2022
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.14.0-2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-

[Touch-packages] [Bug 1979951]

2022-09-14 Thread Nick Rosbrook
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.

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

Title:
  127.0.0.1/::1 removed from loopback interface if you configure extra
  IPs on lo (r104 regression/behaviour change)

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Committed
Status in netplan.io source package in Jammy:
  New
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Users who wish to configure additional addresses on lo may
  inadvertently remove the 127.0.0.1/8 address from the interface. And,
  because this only happens on the second invocation of `netplan apply`,
  it can create confusing breakages for users. Although this is not a
  recommended configuration, it was previously supported and the current
  behavior is a regression.

  [Test Plan]

  * Configure additional addresses on the lo interface. I am testing in
  a LXD container, so I added the following to /etc/netplan/10-lxc.yaml
  under `ethernets:`

  lo:
addresses: ["10.10.10.17/24","10.10.10.19/24"]

  * Apply the config, and then inspect the lo interface's addresses:

   $ netplan apply
   $ ip addr show dev lo

  * Observe that the 127.0.0.1/8 address is still present. Now, run the
  same commands again:

   $ netplan apply
   $ ip addr show dev lo

  * On an affected system, observe that the 127.0.0.1/8 address is now
  gone. On a patched system, the address should still be present.

  [Where problems could occur]

  The patch removes cases where systemd-networkd will drop foreign
  addresses from a managed link. If problems were to occur, it would be
  related to the addresses configured on a managed link.

  [Original Description]

  If you configure the loopback interface using netplan without listing
  the standard loopback addresses (127.0.0.1 / ::1) that are auto-
  configured on boot then they are removed by netplan in r104+ but were
  not in r103.

  Confusingly this only happens the second time "netplan apply" is
  invoked and not the first time.

  There is some argument this is not a valid configuration, however
  - It worked on r103 and broke in the r104 SRU for 20.04 and breaks on upgrade
  - Since it only occurs on the second "netplan apply" it is likely people will 
accidentally create a configuration that on first verification works but breaks 
later
  - Adding addresses to a loopback or dummy interface is a common need
  - There is no dummy interface support in Netplan
  - Removing the loopback IP doesn't immediately cause obvious breakage in an 
SSH session but causes all sorts of hard to diagnose issues with applications

  Thus I consider this a high priority regression because of the
  multiple ways this can break a system at an unexpected/unrelated time
  to when the original change was made.

  As a workaround you can add 127.0.0.1/::1 to the file and this seems
  to generally work and product almost the same configuration with the
  exception that "brd 127.255.255.255" is added to the "ip addr" output
  compared to the auto-created configuration. All of the different
  routing tables seem otherwise the tame.

  = Test Case =
  (1) Add IP configuration for lo to /etc/netplan/lo.yaml

  lo:
    match:
  name: lo
    addresses:
    - 10.10.10.17/24
    - 10.10.10.19/24

  (2) Run "netplan apply" and observe the "ip addr show dev lo" output. 
Expected: 127.0.0.1/::1 are still there.
  (3) Run "netplan apply" a second time and observe the "ip addr show dev lo" 
output. Expected: 127.0.0.1/::1 are now removed.
  (4) Repeat the same test under netplan r103. Expected: 127.0.0.1/::1 are 
still there in both cases.

  = Observations =

  I found this change of behaviour happens only in r104. It is suspected
  but not clear that this is due to the configuraiton diffing behaviour
  introduced in r104. It's not clear to me why it doesn't happen on the
  first "netplan apply".

  I also found a recent upstream systemd commit to prevent networkd removing 
127.0.0.1/::1 which solves this issue on r104 as well. It's possible this is a 
better fix to backport to solve this:
  
https://github.com/systemd/systemd/commit/b69bfa43052586cd6894c32d7d3d447195539ec5

  Reverting to r103 *or* running a newer systemd with that patch
  resolves the issue on 20.04 and 22.04 in my testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1979951/+subscriptions


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


[Touch-packages] [Bug 1981622]

2022-09-14 Thread Nick Rosbrook
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.

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

Title:
  mtd device must be supplied (device name is empty)

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

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

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


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


[Touch-packages] [Bug 1988078]

2022-09-14 Thread Nick Rosbrook
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.

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

Title:
  Please backport systemd-hwdb patches to support src:systemd-hwe tests

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

Bug description:
  [Impact]

  We plan to SRU src:systemd-hwe to Jammy[1] to provide an easier way to
  SRU HWE hwdb rules to Ubuntu. The src:systemd-hwe package contains a
  test script[2] to ensure that no redundant hwdb rules are added to the
  package, i.e. rules that are already present in src:systemd. This test
  requires patches to implement --root flag support for the `systemd-
  hwdb query` command[3]. These patches are already present in kinetic.

  Without these patches in Jammy, src:systemd-hwe would have to disable
  these tests, which are important to maintaining HWE hwdb rules in
  Ubuntu.

  [1] https://bugs.launchpad.net/ubuntu/+source/systemd-hwe/+bug/1983996
  [2] 
https://git.launchpad.net/~canonical-foundations/+git/systemd-hwe/tree/tests/hwdb-redundancy?h=main
  [3] https://github.com/systemd/systemd/pull/23518

  [Test plan]

  * Create a new directory for testing hwdb rule queries:

  $ mkdir -p fakeroot/etc/udev/hwdb.d

  * Add a new .hwdb file to override an existing rule. For example, I
  chose to override the last entry from
  /lib/udev/hdwb.d/60-keyboard.hwdb:

  $ tail -2 /lib/udev/hwdb.d/60-keyboard.hwdb > 
fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb
  $ sed -i 's/chromebook/reserved/g' fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb
  $ cat fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb
  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:*
   XKB_FIXED_MODEL=reserved

  * Create the hwdb.bin within fakeroot:

  $ systemd-hwdb update --root fakeroot
  $ ls fakeroot/etc/udev/hwdb.bin
  fakeroot/etc/udev/hwdb.bin

  * Finally, attempt to query this new hwdb.bin using systemd-hwdb
  query. On an unpatched system, we will see results from the system's
  hwdb.bin:

  $ systemd-hwdb query --root fakeroot 
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* | grep XKB_FIXED_MODEL
  XKB_FIXED_MODEL=chromebook

  ...and on a patched system we should see the overridden rule:

  $ systemd-hwdb query --root fakeroot 
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* | grep XKB_FIXED_MODEL
  XKB_FIXED_MODEL=reserved

  [Where problems could occur]
  The patches add support for the --root flag when calling systemd-hwdb query, 
thus changing the behavior of this command (previously, query would always load 
the system's hwdb.bin). It is unlikely that existing scripts try to use the 
--root flag with `systemd-hwdb query`, but if they did, this is where we would 
see problems.

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


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


[Touch-packages] [Bug 1982462]

2022-09-14 Thread Nick Rosbrook
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.

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

Title:
  Some modprobe loading services requested by the pstore service fail

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

Bug description:
  [Impact]

  It has been detected that some modprobe services fail on UC22 after
  the jammy upgrade  249.11-0ubuntu3.4:

  $ systemctl --system --no-ask-password --no-pager list-units --state=failed
  Failed units:
UNIT LOAD   ACTIVE SUBDESCRIPTION
  ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module 
chromeos_pstore
  ● modprobe@efi_pstore.service  loaded failed failed Load Kernel Module 
efi_pstore
  ● modprobe@mtdpstore.service   loaded failed failed Load Kernel Module 
mtdpstore
  ● modprobe@pstore_blk.service  loaded failed failed Load Kernel Module 
pstore_blk
  ● modprobe@pstore_zone.service loaded failed failed Load Kernel Module 
pstore_zone
  ● modprobe@ramoops.service loaded failed failed Load Kernel Module 
ramoops

  This happens because of some changes to systemd-pstore.service that
  now has:

  After=modprobe@efi_pstore.service modprobe@mtdpstore.service 
modprobe@chromeos_pstore.service modprobe@ramoops.service 
modprobe@pstore_zone.service modprobe@pstore_blk.service
  Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service 
modprobe@chromeos_pstore.service modprobe@ramoops.service 
modprobe@pstore_zone.service modprobe@pstore_blk.service

  This causes too many tries of the modprobe services, that fail in the
  end with

  Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service:
  Start request repeated too quickly.

  Although we have seen this only on UC22, it potentially can affect
  classic systems as well, as systemd-pstore.service is re-tried there a
  few times too. See https://github.com/snapcore/core-base/issues/72 for
  more details.

  A fix for this is available upstream:
  
https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1

  [Test Plan]

  Start the device and check that there is no modprobe-pstore related
  failed service. This is racy, so a few tries will be needed to make
  sure things are fine.

  [Where problems could occur]

  The modprobe services are usually dependencies from other services, so
  it should be fine if the retry behavior is controlled by those other
  services. Risk should be small. If something goes wrong we might see a
  lot of restarts for these services.

  [Other Info]

  Testing should happen on UC22 too.

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


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


[Touch-packages] [Bug 1989599] Re: Random auditd start failures on Ubuntu 20.04 EC2 AMIs

2022-09-14 Thread Alan Sparks
** Attachment removed: "packages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+attachment/5615835/+files/packages.txt

** Attachment added: "packages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+attachment/5615864/+files/packages.txt

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

Title:
  Random auditd start failures on Ubuntu 20.04 EC2 AMIs

Status in audit package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  linux-image-aws 5.15.0.1019.23~20.04.11
  auditd 1:2.8.5-2ubuntu6

  
  I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs.  I 
have tested this with published AMIs ami-0123376e204addb71 and 
ami-00bb3d0b5b36e89b8.

  I am following a process that has worked up to June 20 2022.  The
  process installs and configures the audit package for CIS hardening.
  The process steps are:

  • Launch an instance as a base, I’ve used ami-0123376e204addb71 or 
ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs).
  • Installed the packages listed below.
  • Copied the “auditdconf” contents as /etc/audit/auditd.conf
  • Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules
  • Edit /etc/default/grub, and set: GRUB_CMDLINE_LINUX="audit=1 selinux=1 
audit_backlog_limit=8192"
  • Run: grub-mkconfig > /boot/grub/grub.cfg
  • Stopped the instance, and created an AMI.

  I then launch 10 or 14 instances of this AMI in us-west-2.  Most will
  come up with auditd service running, and all rules loaded.  Usually at
  least two come up broken for unknown reason, with the auditd service
  reporting an error I cannot understand:

  ● auditd.service - Security Auditing Service
   Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-09-14 15:08:14 UTC; 
22min ago
 Docs: man:auditd(8)
   https://github.com/linux-audit/audit-documentation
  Process: 357 ExecStart=/sbin/auditd (code=exited, status=1/FAILURE)

  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Starting Security Auditing 
Service...
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error receiving audit netlink 
packet (No buffer space available)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error setting audit daemon pid 
(No buffer space available)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Unable to set audit pid, exiting
  Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: Cannot daemonize (Success)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: The audit daemon is exiting.
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: The audit daemon is exiting.
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Control process 
exited, code=exited, status=1/FAILURE
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Failed with 
result 'exit-code'.
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Failed to start Security 
Auditing Service.

  When I launch the above, it is a launch of 10 or so instances from the
  same AMI, with the same parameters.  Matter of fact, the launch is
  done by requesting X number of instances during the EC2 instance
  launch

  I've been trying to solve this for some time, and I've found the only
  way I can make the instances always start correctly is to remove the
  kernel "audit_backlog_limit" setting entirely - no value for the
  parameter works correctly (tried 320, 8192, 16384, 32768).

  See attachments for the above mentioned files.
  Thanks.
  -Alan

  expected behavior is:
  * service loaded and active
  * "auditctl -l" shows list of loaded rules

  seen behavior:
  * service dead with errors shown above.
  * "auditctl -l" reports "No rules".

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


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


[Touch-packages] [Bug 1988994]

2022-09-14 Thread Nick Rosbrook
The autopkgtest regressions for systemd 249.11-0ubuntu3.6 in jammy-
proposed were all resolved with retries.

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

Title:
  TEST-58-REPART autopkgtest failure on ppc64el

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

Bug description:
  [Impact]

  With systemd 249.11-0ubuntu3.5 in jammy-proposed, which enables
  systemd-repart, the TEST-58-REPART fails on ppc64el:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  jammy/jammy/ppc64el/s/systemd/20220906_165335_6dd88@/log.gz.

  After trying to cherry-pick upstream commits, including [1], the test
  is still failing on ppc64el. This may be a testbed issue, and for now
  it seems the best course is to skip the test.

  [Test Plan]

  This fix is verified by TEST-58-REPART being skipped on ppc64el.

  [Where problems could occur]

  If we messed up the denylist usage, the test would not be skipped, or
  a different one would be.

  [1] https://github.com/systemd/systemd/commit/8e65d93e85f06e3f2

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


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


[Touch-packages] [Bug 1989467] Re: Several autopkgtest failures on Ubuntu 22.04 and older

2022-09-14 Thread Benjamin Drung
** Description changed:

- All autopkgtest fail on Ubuntu 22.04 (jammy) and older:
- https://autopkgtest.ubuntu.com/packages/apport
+ [Impact]
+ 
+ All autopkgtest fail on Ubuntu 22.04 (jammy) and older: 
https://autopkgtest.ubuntu.com/packages/apport
+ This leads to not detecting regressions from security updates.
+ 
+ [Test Plan]
+ 
+ Check that the autopkgtest succeed all architectures (except for i386).
+ 
+ [Where problems could occur]
+ 
+ The test cases are only part of the apport source package and are not
+ copied in any binary packages. Changes to the test will only affect the
+ package build and test execution.
+ 
+ [Details]
  
  Following test cases fail:
  
  * backend_apt_dpkg:
  ** test_get_dependencies (armhf)
  ** test_get_source_tree_sandbox (arm64, armhf, ppc64el)
  ** test_install_old_packages (arm64, armhf, ppc64el)
  ** test_install_package_from_a_ppa (arm64, armhf, ppc64el)
  ** test_install_packages_dependencies (arm64, armhf, ppc64el)
  ** test_install_packages_from_launchpad (arm64, armhf, ppc64el)
  ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el)
  ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el)
  ** test_install_packages_unversioned (arm64, armhf, ppc64el)
  ** test_install_packages_versioned (arm64, armhf, ppc64el)
  * hookutils:
  ** test_module_license_evaluation (armhf)
  * python_crashes:
  ** test_dbus_service_timeout_running (armhf)
  ** test_dbus_service_unknown_wrongbus_notrunning (armhf)
  * report:
  ** test_add_gdb_info_abort (armhf)
  ** test_add_gdb_info_script (armhf)
  ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x)
  * signal_crashes:
  ** test_core_dump_packaged (armhf, ppc64el, s390x)
  ** test_core_dump_unpackaged (armhf)
  ** test_core_file_injection (armhf)
  ** test_crash_system_slice (amd64, ppc64el, s390x)
  ** test_empty_core_dump (follow-up failure for test_crash_system_slice)
  ** test_flood_limit (follow-up failure for test_crash_system_slice)
  ** test_ignore (follow-up failure for test_crash_system_slice)
  ** test_ignore_sigquit (follow-up failure for test_crash_system_slice)
  * ui:
  ** test_run_crash_kernel (arm64, s390x)
  ** test_run_update_report_different_binary_source (armhf)
  ** test_run_report_bug_kernel_thread (armhf)
  * ui_gtk:
  ** test_kerneloops_nodetails (armhf)

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

Title:
  Several autopkgtest failures on Ubuntu 22.04 and older

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Triaged
Status in apport source package in Jammy:
  Triaged

Bug description:
  [Impact]

  All autopkgtest fail on Ubuntu 22.04 (jammy) and older: 
https://autopkgtest.ubuntu.com/packages/apport
  This leads to not detecting regressions from security updates.

  [Test Plan]

  Check that the autopkgtest succeed all architectures (except for
  i386).

  [Where problems could occur]

  The test cases are only part of the apport source package and are not
  copied in any binary packages. Changes to the test will only affect
  the package build and test execution.

  [Details]

  Following test cases fail:

  * backend_apt_dpkg:
  ** test_get_dependencies (armhf)
  ** test_get_source_tree_sandbox (arm64, armhf, ppc64el)
  ** test_install_old_packages (arm64, armhf, ppc64el)
  ** test_install_package_from_a_ppa (arm64, armhf, ppc64el)
  ** test_install_packages_dependencies (arm64, armhf, ppc64el)
  ** test_install_packages_from_launchpad (arm64, armhf, ppc64el)
  ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el)
  ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el)
  ** test_install_packages_unversioned (arm64, armhf, ppc64el)
  ** test_install_packages_versioned (arm64, armhf, ppc64el)
  * hookutils:
  ** test_module_license_evaluation (armhf)
  * python_crashes:
  ** test_dbus_service_timeout_running (armhf)
  ** test_dbus_service_unknown_wrongbus_notrunning (armhf)
  * report:
  ** test_add_gdb_info_abort (armhf)
  ** test_add_gdb_info_script (armhf)
  ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x)
  * signal_crashes:
  ** test_core_dump_packaged (armhf, ppc64el, s390x)
  ** test_core_dump_unpackaged (armhf)
  ** test_core_file_injection (armhf)
  ** test_crash_system_slice (amd64, ppc64el, s390x)
  ** test_empty_core_dump (follow-up failure for test_crash_system_slice)
  ** test_flood_limit (follow-up failure for test_crash_system_slice)
  ** test_ignore (follow-up failure for test_crash_system_slice)
  ** test_ignore_sigquit (follow-up failure for test_crash_system_slice)
  * ui:
  ** test_run_crash_kernel (arm64, s390x)
  ** test_run_update_report_different_binary_source (armhf)
  ** test_run_report_bug_kernel_thread (armhf)
  * ui_gtk:
  ** test_kerneloops_nodetails (armhf)

To manage notifications about this bug go 

[Touch-packages] [Bug 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic

2022-09-14 Thread Leonidas S. Barbosa
Ok, i did find the issue  -Thanks Security folks - and I'm issuing a
security regression update.

Thanks.

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

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

Title:
  "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu
  Bionic

Status in poppler package in Ubuntu:
  In Progress

Bug description:
  Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on
  Ubuntu Bionic but "goo/gmem.h" still has the statement `#include
  "GooCheckedOps.h"`. As a result, a compile error will happen when
  compiling code that uses poppler:

  /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h:
  No such file or directory

  I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the
  previous version) installed. I confirmed that "goo/gmem.h" doesn't
  have the `#include "GooCheckedOps.h"` statement.

  I found this issue when I was compiling gdal on my Docker container.
  The Docker container was installed the problematic version
  0.62.0-2ubuntu2.13 and I ran into the "No such file or directory"
  error.

  I compiled on both Amd64 and AArch64 and I ran into the same error on
  both platforms.

  By reading the diff between 2.12 and 2.13
  
(https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz),
  the patch looks quite right. But when I examined the contents of the
  built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h".

  Kind of weird, because the problem seems to be caused by applying
  "CVE-2022-38784-pre.patch" in half: the first part that creates
  "goo/GooCheckedOps.h" was not applied during the build process and the
  second part that modifies "goo/gmem.h" was applied.

  Any thoughts? Ideas?

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


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


[Touch-packages] [Bug 1989602] [NEW] Delay in updating charge status in Ubuntu 22.04 LTS

2022-09-14 Thread John D
Public bug reported:

I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS.
When plugging in the charger, the current charge status in the top bar and 
Settings shows 'Not Charging' for a few minutes and then shows that the system 
is charging normally.

When unplugging the charger the same happens; the charge status shows
'Not Charging' for a few minutes, and then shows the correct charge
status.

Normally, the change in power status should be instantaneous.
In short, there is a delay in the OS in showing the current charge status.

Upon further research, it was found that the 'upower' service is to blame; it 
polls every two minutes(i.e., it refreshes the charge status every two 
minutes); causing a delay in charge status.
This is further compounded by the fact that restarting upower service, or the 
system as a whole makes the system to show the correct charge status.

However, I did not have this problem on another system, a HP Pavilion x360 
14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS.
There, the power status behaves normally with no delays whatsoever.

Please look into this issue and fix this bug as soon as possible.
One suggestion would be to increase the polling frequency of upower from 2 
mins. to something lesser, so that the charge status shows correctly.

upower version:
UPower client version 0.99.17
UPower daemon version 0.99.17

OS:
Description:Ubuntu 22.04.1 LTS
Release:22.04
Kernel: Linux 5.15.0-47-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: upower 0.99.17-1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 14 20:41:16 2022
InstallationDate: Installed on 2022-09-12 (1 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Delay in updating charge status in Ubuntu 22.04 LTS

Status in upower package in Ubuntu:
  New

Bug description:
  I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS.
  When plugging in the charger, the current charge status in the top bar and 
Settings shows 'Not Charging' for a few minutes and then shows that the system 
is charging normally.

  When unplugging the charger the same happens; the charge status shows
  'Not Charging' for a few minutes, and then shows the correct charge
  status.

  Normally, the change in power status should be instantaneous.
  In short, there is a delay in the OS in showing the current charge status.

  Upon further research, it was found that the 'upower' service is to blame; it 
polls every two minutes(i.e., it refreshes the charge status every two 
minutes); causing a delay in charge status.
  This is further compounded by the fact that restarting upower service, or the 
system as a whole makes the system to show the correct charge status.

  However, I did not have this problem on another system, a HP Pavilion x360 
14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS.
  There, the power status behaves normally with no delays whatsoever.

  Please look into this issue and fix this bug as soon as possible.
  One suggestion would be to increase the polling frequency of upower from 2 
mins. to something lesser, so that the charge status shows correctly.

  upower version:
  UPower client version 0.99.17
  UPower daemon version 0.99.17

  OS:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  Kernel: Linux 5.15.0-47-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: upower 0.99.17-1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 14 20:41:16 2022
  InstallationDate: Installed on 2022-09-12 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1958055] Autopkgtest regression report (sudo/1.9.9-1ubuntu2.1)

2022-09-14 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted sudo (1.9.9-1ubuntu2.1) for jammy have 
finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.48.2-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#sudo

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  sudo apport-kde is in a different design (stripped
  XDG_CURRENT_DESKTOP)

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

Bug description:
  [Impact]

  Running ubuntu-bug as normal user has the correct theme (see
  screenshots attached to bug #1881640), but running "sudo ubuntu-bug"
  has a different, non-matching theme (see attached screenshot). This
  applies to all Qt applications.

  [Test Plan]

  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):

  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.

  Same result with KDE:

  1. Use kubuntu-22.04-desktop-amd64.iso
  2. Run ubuntu-bug -f
  3. Run: sudo ubuntu-bug -f

  [Where problems could occur]
  Passing through an additional environment variable could lead to an undesired 
side effect (if an application expect it not be be set when run as root). Since 
this environment variable changes the code paths, it could reveal Qt bugs 
related to running as root. 

  [Analysis]

  Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme,
  but XDG_CURRENT_DESKTOP is not in the list of environment variables to
  preserve (and not in env_keep in /etc/sudoers).

  On other other hand, sudo preserves the DISPLAY environment variable:

  $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)'
  XAUTHORITY=/run/user/1000/gdm/Xauthority
  DISPLAY=:0
  MAIL=/var/mail/root
  LOGNAME=root
  USER=root
  HOME=/root
  SHELL=/bin/bash

  [Workaround]

  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde
  -f

  [Other Info]

  This changes was accepted upstream: https://github.com/sudo-
  project/sudo/pull/165

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  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/sudo/+bug/1958055/+subscriptions


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


[Touch-packages] [Bug 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic

2022-09-14 Thread Leonidas S. Barbosa
Hi,

Could you please provide with any steps in how to reproduce it?

Thanks!

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

Title:
  "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu
  Bionic

Status in poppler package in Ubuntu:
  New

Bug description:
  Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on
  Ubuntu Bionic but "goo/gmem.h" still has the statement `#include
  "GooCheckedOps.h"`. As a result, a compile error will happen when
  compiling code that uses poppler:

  /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h:
  No such file or directory

  I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the
  previous version) installed. I confirmed that "goo/gmem.h" doesn't
  have the `#include "GooCheckedOps.h"` statement.

  I found this issue when I was compiling gdal on my Docker container.
  The Docker container was installed the problematic version
  0.62.0-2ubuntu2.13 and I ran into the "No such file or directory"
  error.

  I compiled on both Amd64 and AArch64 and I ran into the same error on
  both platforms.

  By reading the diff between 2.12 and 2.13
  
(https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz),
  the patch looks quite right. But when I examined the contents of the
  built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h".

  Kind of weird, because the problem seems to be caused by applying
  "CVE-2022-38784-pre.patch" in half: the first part that creates
  "goo/GooCheckedOps.h" was not applied during the build process and the
  second part that modifies "goo/gmem.h" was applied.

  Any thoughts? Ideas?

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


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


[Touch-packages] [Bug 1989599] Re: Random auditd start failures on Ubuntu 20.04 EC2 AMIs

2022-09-14 Thread Alan Sparks
** Attachment added: "packages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+attachment/5615835/+files/packages.txt

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

Title:
  Random auditd start failures on Ubuntu 20.04 EC2 AMIs

Status in audit package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  linux-image-aws 5.15.0.1019.23~20.04.11
  auditd 1:2.8.5-2ubuntu6

  
  I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs.  I 
have tested this with published AMIs ami-0123376e204addb71 and 
ami-00bb3d0b5b36e89b8.

  I am following a process that has worked up to June 20 2022.  The
  process installs and configures the audit package for CIS hardening.
  The process steps are:

  • Launch an instance as a base, I’ve used ami-0123376e204addb71 or 
ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs).
  • Installed the packages listed below.
  • Copied the “auditdconf” contents as /etc/audit/auditd.conf
  • Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules
  • Edit /etc/default/grub, and set: GRUB_CMDLINE_LINUX="audit=1 selinux=1 
audit_backlog_limit=8192"
  • Run: grub-mkconfig > /boot/grub/grub.cfg
  • Stopped the instance, and created an AMI.

  I then launch 10 or 14 instances of this AMI in us-west-2.  Most will
  come up with auditd service running, and all rules loaded.  Usually at
  least two come up broken for unknown reason, with the auditd service
  reporting an error I cannot understand:

  ● auditd.service - Security Auditing Service
   Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-09-14 15:08:14 UTC; 
22min ago
 Docs: man:auditd(8)
   https://github.com/linux-audit/audit-documentation
  Process: 357 ExecStart=/sbin/auditd (code=exited, status=1/FAILURE)

  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Starting Security Auditing 
Service...
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error receiving audit netlink 
packet (No buffer space available)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error setting audit daemon pid 
(No buffer space available)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Unable to set audit pid, exiting
  Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: Cannot daemonize (Success)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: The audit daemon is exiting.
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: The audit daemon is exiting.
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Control process 
exited, code=exited, status=1/FAILURE
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Failed with 
result 'exit-code'.
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Failed to start Security 
Auditing Service.

  When I launch the above, it is a launch of 10 or so instances from the
  same AMI, with the same parameters.  Matter of fact, the launch is
  done by requesting X number of instances during the EC2 instance
  launch

  I've been trying to solve this for some time, and I've found the only
  way I can make the instances always start correctly is to remove the
  kernel "audit_backlog_limit" setting entirely - no value for the
  parameter works correctly (tried 320, 8192, 16384, 32768).

  See attachments for the above mentioned files.
  Thanks.
  -Alan

  expected behavior is:
  * service loaded and active
  * "auditctl -l" shows list of loaded rules

  seen behavior:
  * service dead with errors shown above.
  * "auditctl -l" reports "No rules".

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


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


[Touch-packages] [Bug 1989365] Re: test_omit_all_processes_except_one is racy and fails sometimes

2022-09-14 Thread Benjamin Drung
Fix committed upstream:
https://github.com/canonical/apport/commit/bb7cd6f08d16749c501ef893d5056a20a82346fd

** Changed in: apport
   Status: New => Fix Committed

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

Title:
  test_omit_all_processes_except_one is racy and fails sometimes

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The test case test_omit_all_processes_except_one is racy and fails
  sometimes:

  ```
  test_omit_all_processes_except_one 
(tests.system.test_unkillable_shutdown.TestUnkillableShutdown)
  unkillable_shutdown will write exactly one report. ... Running as unit: 
run-r0b0d3fe87473410c9eb61a5ae4635938.service
  FAIL
  ==
  FAIL: test_omit_all_processes_except_one 
(tests.system.test_unkillable_shutdown.TestUnkillableShutdown)
  unkillable_shutdown will write exactly one report.
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.JJoBfX/autopkgtest_tmp/tests/system/test_unkillable_shutdown.py",
 line 96, in test_omit_all_processes_except_one
  pid = self._launch_process_with_different_session_id(existing_pids)
File 
"/tmp/autopkgtest.JJoBfX/autopkgtest_tmp/tests/system/test_unkillable_shutdown.py",
 line 90, in _launch_process_with_different_session_id
  self.assertEqual(len(test_executable_pids), 1, test_executable_pids)
  AssertionError: 0 != 1 : set()

  --
  ```

  autopkgtest log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  kinetic/kinetic/amd64/a/apport/20220912_055849_5f03e@/log.gz

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


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


[Touch-packages] [Bug 1989599] Re: Random auditd start failures on Ubuntu 20.04 EC2 AMIs

2022-09-14 Thread Alan Sparks
** Attachment added: "auditconf.x86_64"
   
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+attachment/5615836/+files/auditconf.x86_64

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

Title:
  Random auditd start failures on Ubuntu 20.04 EC2 AMIs

Status in audit package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  linux-image-aws 5.15.0.1019.23~20.04.11
  auditd 1:2.8.5-2ubuntu6

  
  I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs.  I 
have tested this with published AMIs ami-0123376e204addb71 and 
ami-00bb3d0b5b36e89b8.

  I am following a process that has worked up to June 20 2022.  The
  process installs and configures the audit package for CIS hardening.
  The process steps are:

  • Launch an instance as a base, I’ve used ami-0123376e204addb71 or 
ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs).
  • Installed the packages listed below.
  • Copied the “auditdconf” contents as /etc/audit/auditd.conf
  • Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules
  • Edit /etc/default/grub, and set: GRUB_CMDLINE_LINUX="audit=1 selinux=1 
audit_backlog_limit=8192"
  • Run: grub-mkconfig > /boot/grub/grub.cfg
  • Stopped the instance, and created an AMI.

  I then launch 10 or 14 instances of this AMI in us-west-2.  Most will
  come up with auditd service running, and all rules loaded.  Usually at
  least two come up broken for unknown reason, with the auditd service
  reporting an error I cannot understand:

  ● auditd.service - Security Auditing Service
   Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-09-14 15:08:14 UTC; 
22min ago
 Docs: man:auditd(8)
   https://github.com/linux-audit/audit-documentation
  Process: 357 ExecStart=/sbin/auditd (code=exited, status=1/FAILURE)

  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Starting Security Auditing 
Service...
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error receiving audit netlink 
packet (No buffer space available)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error setting audit daemon pid 
(No buffer space available)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Unable to set audit pid, exiting
  Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: Cannot daemonize (Success)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: The audit daemon is exiting.
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: The audit daemon is exiting.
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Control process 
exited, code=exited, status=1/FAILURE
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Failed with 
result 'exit-code'.
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Failed to start Security 
Auditing Service.

  When I launch the above, it is a launch of 10 or so instances from the
  same AMI, with the same parameters.  Matter of fact, the launch is
  done by requesting X number of instances during the EC2 instance
  launch

  I've been trying to solve this for some time, and I've found the only
  way I can make the instances always start correctly is to remove the
  kernel "audit_backlog_limit" setting entirely - no value for the
  parameter works correctly (tried 320, 8192, 16384, 32768).

  See attachments for the above mentioned files.
  Thanks.
  -Alan

  expected behavior is:
  * service loaded and active
  * "auditctl -l" shows list of loaded rules

  seen behavior:
  * service dead with errors shown above.
  * "auditctl -l" reports "No rules".

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


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


[Touch-packages] [Bug 1989599] [NEW] Random auditd start failures on Ubuntu 20.04 EC2 AMIs

2022-09-14 Thread Alan Sparks
Public bug reported:

Description:Ubuntu 20.04.5 LTS
Release:20.04

linux-image-aws 5.15.0.1019.23~20.04.11
auditd 1:2.8.5-2ubuntu6


I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs.  I 
have tested this with published AMIs ami-0123376e204addb71 and 
ami-00bb3d0b5b36e89b8.

I am following a process that has worked up to June 20 2022.  The
process installs and configures the audit package for CIS hardening.
The process steps are:

•   Launch an instance as a base, I’ve used ami-0123376e204addb71 or 
ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs).
•   Installed the packages listed below.
•   Copied the “auditdconf” contents as /etc/audit/auditd.conf
•   Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules
•   Edit /etc/default/grub, and set: GRUB_CMDLINE_LINUX="audit=1 selinux=1 
audit_backlog_limit=8192"
•   Run: grub-mkconfig > /boot/grub/grub.cfg
•   Stopped the instance, and created an AMI.

I then launch 10 or 14 instances of this AMI in us-west-2.  Most will
come up with auditd service running, and all rules loaded.  Usually at
least two come up broken for unknown reason, with the auditd service
reporting an error I cannot understand:

● auditd.service - Security Auditing Service
 Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Wed 2022-09-14 15:08:14 UTC; 
22min ago
   Docs: man:auditd(8)
 https://github.com/linux-audit/audit-documentation
Process: 357 ExecStart=/sbin/auditd (code=exited, status=1/FAILURE)

Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Starting Security Auditing 
Service...
Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error receiving audit netlink 
packet (No buffer space available)
Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error setting audit daemon pid 
(No buffer space available)
Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Unable to set audit pid, exiting
Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: Cannot daemonize (Success)
Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: The audit daemon is exiting.
Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: The audit daemon is exiting.
Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Control process 
exited, code=exited, status=1/FAILURE
Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Failed with result 
'exit-code'.
Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Failed to start Security Auditing 
Service.

When I launch the above, it is a launch of 10 or so instances from the
same AMI, with the same parameters.  Matter of fact, the launch is done
by requesting X number of instances during the EC2 instance launch

I've been trying to solve this for some time, and I've found the only
way I can make the instances always start correctly is to remove the
kernel "audit_backlog_limit" setting entirely - no value for the
parameter works correctly (tried 320, 8192, 16384, 32768).

See attachments for the above mentioned files.
Thanks.
-Alan

expected behavior is:
* service loaded and active
* "auditctl -l" shows list of loaded rules

seen behavior:
* service dead with errors shown above.
* "auditctl -l" reports "No rules".

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

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

Title:
  Random auditd start failures on Ubuntu 20.04 EC2 AMIs

Status in audit package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  linux-image-aws 5.15.0.1019.23~20.04.11
  auditd 1:2.8.5-2ubuntu6

  
  I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs.  I 
have tested this with published AMIs ami-0123376e204addb71 and 
ami-00bb3d0b5b36e89b8.

  I am following a process that has worked up to June 20 2022.  The
  process installs and configures the audit package for CIS hardening.
  The process steps are:

  • Launch an instance as a base, I’ve used ami-0123376e204addb71 or 
ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs).
  • Installed the packages listed below.
  • Copied the “auditdconf” contents as /etc/audit/auditd.conf
  • Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules
  • Edit /etc/default/grub, and set: GRUB_CMDLINE_LINUX="audit=1 selinux=1 
audit_backlog_limit=8192"
  • Run: grub-mkconfig > /boot/grub/grub.cfg
  • Stopped the instance, and created an AMI.

  I then launch 10 or 14 instances of this AMI in us-west-2.  Most will
  come up with auditd service running, and all rules loaded.  Usually at
  least two come up broken for unknown reason, with the auditd service
  reporting an error I cannot understand:

  ● auditd.service - Security Auditing Service
   Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enable

[Touch-packages] [Bug 1989599] Re: Random auditd start failures on Ubuntu 20.04 EC2 AMIs

2022-09-14 Thread Alan Sparks
** Attachment added: "auditrules.x86_64"
   
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+attachment/5615834/+files/auditrules.x86_64

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

Title:
  Random auditd start failures on Ubuntu 20.04 EC2 AMIs

Status in audit package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  linux-image-aws 5.15.0.1019.23~20.04.11
  auditd 1:2.8.5-2ubuntu6

  
  I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs.  I 
have tested this with published AMIs ami-0123376e204addb71 and 
ami-00bb3d0b5b36e89b8.

  I am following a process that has worked up to June 20 2022.  The
  process installs and configures the audit package for CIS hardening.
  The process steps are:

  • Launch an instance as a base, I’ve used ami-0123376e204addb71 or 
ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs).
  • Installed the packages listed below.
  • Copied the “auditdconf” contents as /etc/audit/auditd.conf
  • Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules
  • Edit /etc/default/grub, and set: GRUB_CMDLINE_LINUX="audit=1 selinux=1 
audit_backlog_limit=8192"
  • Run: grub-mkconfig > /boot/grub/grub.cfg
  • Stopped the instance, and created an AMI.

  I then launch 10 or 14 instances of this AMI in us-west-2.  Most will
  come up with auditd service running, and all rules loaded.  Usually at
  least two come up broken for unknown reason, with the auditd service
  reporting an error I cannot understand:

  ● auditd.service - Security Auditing Service
   Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-09-14 15:08:14 UTC; 
22min ago
 Docs: man:auditd(8)
   https://github.com/linux-audit/audit-documentation
  Process: 357 ExecStart=/sbin/auditd (code=exited, status=1/FAILURE)

  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Starting Security Auditing 
Service...
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error receiving audit netlink 
packet (No buffer space available)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error setting audit daemon pid 
(No buffer space available)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Unable to set audit pid, exiting
  Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: Cannot daemonize (Success)
  Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: The audit daemon is exiting.
  Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: The audit daemon is exiting.
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Control process 
exited, code=exited, status=1/FAILURE
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Failed with 
result 'exit-code'.
  Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Failed to start Security 
Auditing Service.

  When I launch the above, it is a launch of 10 or so instances from the
  same AMI, with the same parameters.  Matter of fact, the launch is
  done by requesting X number of instances during the EC2 instance
  launch

  I've been trying to solve this for some time, and I've found the only
  way I can make the instances always start correctly is to remove the
  kernel "audit_backlog_limit" setting entirely - no value for the
  parameter works correctly (tried 320, 8192, 16384, 32768).

  See attachments for the above mentioned files.
  Thanks.
  -Alan

  expected behavior is:
  * service loaded and active
  * "auditctl -l" shows list of loaded rules

  seen behavior:
  * service dead with errors shown above.
  * "auditctl -l" reports "No rules".

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


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


[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged

2022-09-14 Thread Nick Rosbrook
I have verified that systemd-repart is available in jammy-proposed, and
that the upgrade path to kinetic works as expected:

root@jammy:~# apt-cache policy systemd-repart
systemd-repart:
  Installed: 249.11-0ubuntu3.6
  Candidate: 249.11-0ubuntu3.6
  Version table:
 *** 249.11-0ubuntu3.6 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
root@jammy:~# do-release-upgrade -d
[ upgrade... ]
[ reboot...  ]

root@jammy:~# lsb_release -cs
kinetic
root@jammy:~# apt-cache policy systemd-repart
systemd-repart:
  Installed: (none)
  Candidate: (none)
  Version table:
root@jammy:~# apt-cache policy systemd
systemd:
  Installed: 251.4-1ubuntu4
  Candidate: 251.4-1ubuntu4
  Version table:
 *** 251.4-1ubuntu4 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status
root@jammy:~# dpkg -S /bin/systemd-repart 
systemd: /bin/systemd-repart


** Tags removed: rls-jj-incoming verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

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

Title:
  systemd-repart not packaged

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

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in their new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  * Attach (local) build-log showing the systemd-repart self-tests passing, as 
found in build-deb/meson-logs/testlog.txt
  * Attach autopkgtest logs showing the regression tests passing (especially 
TEST-58-REPART from "upstream-2" testsuite)
  * Test upgrade-path Jammy->Kinetic to make sure systemd-repart is properly 
replaced by Kinetic's "systemd" binary package

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy so that they can start adopting it in mkosi.

  Runtime behavior of existing components is not affected by the build
  config change.

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


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


[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

2022-09-14 Thread Robie Basak
Hello iBug, 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.6 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: Triaged => 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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1871465

Title:
  ssh_config(5) contains outdated information

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

Bug description:
  [Impact]

  The problem here is straightforward. 
  The case is to fix manpages. They need to reflect a change done to the code 
some time ago. That problem might be annoying for users before being fixed. 

  Backport upstream fix to Focal
  Origin: 
  
https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636


  [Test Plan]

  Make a container for testing:

  First option:
  $ lxc launch images:ubuntu/bionic focal-test
  $ lxc shell focal-test

  Simply install the openssh package using ‘apt install’ and check both 
ssh_config.5 and sshd_config.5 files. You should be able to spot the ‘ssh_rsa’ 
in these files.
   

  
  [Where problems could occur]

  Any code change might change the behavior of the package in a specific
  situation and cause other errors.

  Next things which might cause regression are new dependencies which
  might not align and it is obvious the dependencies are upgraded and it
  might be a problem, but it is really unlikely.

  Even none of the rather generic cases above does apply here as we only
  change non-functional content in the form of the man page; Therefore
  the only risk is out of re-building the package which could pick up
  something from e.g. a changed toolchain.

  
  [Other Info]

  
  Fixing this is nice for the users, but OTOH very low severity and would cause 
a package download and update on almost every Ubuntu in the world. Therefore we 
will mark this as block-proposed and keep it in focal-proposed so that a later 
real update (security or functional) will pick this up from -proposed and then 
fix it in the field for real.

  original
  report---

  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:

   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates
   by certificate authorities (CAs).  The default is:

     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

   ssh(1) will not accept host certificates signed using algorithms
   other than those specified.

  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

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


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


[Touch-packages] [Bug 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic

2022-09-14 Thread Sebastien Bacher
** Changed in: poppler (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu
  Bionic

Status in poppler package in Ubuntu:
  New

Bug description:
  Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on
  Ubuntu Bionic but "goo/gmem.h" still has the statement `#include
  "GooCheckedOps.h"`. As a result, a compile error will happen when
  compiling code that uses poppler:

  /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h:
  No such file or directory

  I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the
  previous version) installed. I confirmed that "goo/gmem.h" doesn't
  have the `#include "GooCheckedOps.h"` statement.

  I found this issue when I was compiling gdal on my Docker container.
  The Docker container was installed the problematic version
  0.62.0-2ubuntu2.13 and I ran into the "No such file or directory"
  error.

  I compiled on both Amd64 and AArch64 and I ran into the same error on
  both platforms.

  By reading the diff between 2.12 and 2.13
  
(https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz),
  the patch looks quite right. But when I examined the contents of the
  built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h".

  Kind of weird, because the problem seems to be caused by applying
  "CVE-2022-38784-pre.patch" in half: the first part that creates
  "goo/GooCheckedOps.h" was not applied during the build process and the
  second part that modifies "goo/gmem.h" was applied.

  Any thoughts? Ideas?

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


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


[Touch-packages] [Bug 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

2022-09-14 Thread Sebastien Bacher
The description of the patch explains why the current behavior is buggy
and not just different in a way users would be relying on the difference
of behavior. It's not that it works differently, it is that it reports
wrong information.

The patch didn't apply directly so I've adapted it and verified that a
build of the package with it  matched the new expected behavior before
uploading.

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  Incomplete

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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


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


[Touch-packages] [Bug 1989371] Re: test_crash_setuid_unpackaged fails with psutil.NoSuchProcess: process no longer exists

2022-09-14 Thread Benjamin Drung
Proposed fix: https://github.com/canonical/apport/pull/4

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

Title:
  test_crash_setuid_unpackaged fails with psutil.NoSuchProcess: process
  no longer exists

Status in Apport:
  New
Status in apport package in Ubuntu:
  Triaged

Bug description:
  test_crash_setuid_unpackaged is racy and rarely fails with:

  ==
  ERROR: test_crash_setuid_unpackaged (tests.integration.test_signal_crashes.T)
  report generation for unpackaged setuid program
  --
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/psutil/_pslinux.py", line 1661, in 
wrapper
  return fun(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/psutil/_pslinux.py", line 1782, in 
cmdline
  data = f.read()
  ProcessLookupError: [Errno 3] No such process

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/tmp/autopkgtest.ukiC2X/autopkgtest_tmp/tests/integration/test_signal_crashes.py",
 line 746, in test_crash_setuid_unpackaged
  self.do_crash(
File 
"/tmp/autopkgtest.ukiC2X/autopkgtest_tmp/tests/integration/test_signal_crashes.py",
 line 918, in do_crash
  command_process = self.wait_for_gdb_child_process(
File 
"/tmp/autopkgtest.ukiC2X/autopkgtest_tmp/tests/integration/test_signal_crashes.py",
 line 1088, in wait_for_gdb_child_process
  cmdline = process.cmdline()
File "/usr/lib/python3/dist-packages/psutil/__init__.py", line 684, in 
cmdline
  return self._proc.cmdline()
File "/usr/lib/python3/dist-packages/psutil/_pslinux.py", line 1665, in 
wrapper
  raise NoSuchProcess(self.pid, self._name)
  psutil.NoSuchProcess: process no longer exists (pid=3767)

  --

  Failing autopkgtest:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  kinetic/kinetic/arm64/a/apport/20220825_140850_23979@/log.gz

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


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


[Touch-packages] [Bug 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

2022-09-14 Thread Robie Basak
I'm not doubting that the revert was correct for upstream. But we have a
different context in a stable release, where users may be relying on
behaviours that upstream are at liberty to change in their main
development branch, but we are not in our stable releases. Further, we
can't just assume that what is correct for them in their code base is
correct for us to cherry-pick to our stable release that holds a
previous version of the code base. Somebody needs to spend time to
ensure this is safe.

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  Incomplete

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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


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


[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say so

2022-09-14 Thread Brian Foster
Yeah, I was confused by this at first too.  Here's a hint, try "apt-mark
showhold":

   $ apt-mark showhold
   $ 

If nothing is printed (as above), then the "issue" PRESUMABLY isn't
local to your system; ergo, the cause is PROBABLY at the server, such as
a phased update.  Relax.  It will probably sort itself out in a few
days.  (This hint is from https://askubuntu.com/questions/640986/how-to-
get-a-list-of-installed-packages-held-back-from-upgrade "How to get a
list of installed packages held back from upgrade?" (APT, etc., experts
can please correct).)

As per above (#3), whilst the reason isn't stored, that does not mean
apt(8)'s message cannot be improved.  For example, instead of the
current:

   The following packages have been kept back:
  PKG...

better might be something like:

   The following packages have been kept back:
  PKG...
   Some or all of those packages may be deliberately "on hold" on the server;
   please see manual page XXX(N) for information.

with (obviously) appropriate text in the manual page.  (Exactly which
man page is left to the experts.)

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

Title:
  When apt keeps back packages due to phased updates, it should say so

Status in apt package in Ubuntu:
  New

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

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


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


[Touch-packages] [Bug 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)

2022-09-14 Thread Robie Basak
Hello Kangarooo, or anyone else affected,

Accepted sudo into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sudo/1.9.9-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-
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: sudo (Ubuntu Jammy)
   Status: Triaged => 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 sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1958055

Title:
  sudo apport-kde is in a different design (stripped
  XDG_CURRENT_DESKTOP)

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

Bug description:
  [Impact]

  Running ubuntu-bug as normal user has the correct theme (see
  screenshots attached to bug #1881640), but running "sudo ubuntu-bug"
  has a different, non-matching theme (see attached screenshot). This
  applies to all Qt applications.

  [Test Plan]

  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):

  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.

  Same result with KDE:

  1. Use kubuntu-22.04-desktop-amd64.iso
  2. Run ubuntu-bug -f
  3. Run: sudo ubuntu-bug -f

  [Where problems could occur]
  Passing through an additional environment variable could lead to an undesired 
side effect (if an application expect it not be be set when run as root). Since 
this environment variable changes the code paths, it could reveal Qt bugs 
related to running as root. 

  [Analysis]

  Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme,
  but XDG_CURRENT_DESKTOP is not in the list of environment variables to
  preserve (and not in env_keep in /etc/sudoers).

  On other other hand, sudo preserves the DISPLAY environment variable:

  $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)'
  XAUTHORITY=/run/user/1000/gdm/Xauthority
  DISPLAY=:0
  MAIL=/var/mail/root
  LOGNAME=root
  USER=root
  HOME=/root
  SHELL=/bin/bash

  [Workaround]

  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde
  -f

  [Other Info]

  This changes was accepted upstream: https://github.com/sudo-
  project/sudo/pull/165

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  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/sudo/+bug/1958055/+subscriptions


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


[Touch-packages] [Bug 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

2022-09-14 Thread Sebastien Bacher
@Robie, the patch description has details on the change. The github
report also discuss why the patch was broken and not just doing what is
intended and why the revert is right.

I'm not involved in iputils and will not be able to provide more
information that was in there. Note that the revert is part of 22.04.

I was mostly trying to help landing a fix we were getting request on.
I'm fine updating the testcase if that's enough to unblock the SRU but
otherwise please reject my upload, I'm not wanting to spend the time
needed to prove that upstream can be trusted on that one.

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  Incomplete

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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


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


[Touch-packages] [Bug 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

2022-09-14 Thread Robie Basak
This is definitely a bug that we want to fix in Focal. But is this
particular code change the correct way to do it?

Won't reverting this commit regress the fix that was introduced by the
commit in the first place? I think this needs a proper analysis of the
possible implications for unaffected users, please, rather than just
blindly cherry-picking the revert from upstream.

I think maybe bug 1551020 would be reintroduced by this upload, for
example?

The test plan should also include verifying regular use cases that might
be impacted by this code change are not regressed, not just that this
particular bug is fixed.

** Changed in: iputils (Ubuntu Focal)
   Status: Fix Committed => Incomplete

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  Incomplete

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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


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


[Touch-packages] [Bug 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

2022-09-14 Thread Andreas Hasenack
I checked that jammy and later indeed has the same commit reverted.

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  Incomplete

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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


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


[Touch-packages] [Bug 1551020] Re: IpUtils Ping can be in wait forever

2022-09-14 Thread Andreas Hasenack
Upstream bug: https://github.com/iputils/iputils/pull/67

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

Title:
  IpUtils Ping can be in wait forever

Status in iputils package in Ubuntu:
  Expired

Bug description:
  Ping is using round trip time from previous incoming echo response
  packet to determine max waittime for next packet, but the validation
  of the value read from incoming echo response packet is poor. It only
  checks for non-negative values.

  To reproduce the Bug: 
  Step 1: Apply the following diff to the Ping command- (this simulates the 
condition that triptime value read from incoming echo response was some 
arbitrary large value)-
  diff -r iputils/ping_common.c iputils_ping_hang_repro/ping_common.c
  709c709,711
  <   triptime = tv->tv_sec * 100 + tv->tv_usec;
  ---
  >   /*SNAP: To repro Ping hang, set this value to some large long 
value. Since this is read from */
  >   /*  incoming echo reply and not validated for 0 or too 
large, this will cause hang/long wait.
  >   /* triptime = tv->tv_sec * 100 + tv->tv_usec; */
  >   triptime = 1000123456789;
  /tmp/diff.out (END)

  Step 2: Run the following ping command targeted at a host that is at
  first successfully replying to the Ping echo requests, but at some
  point during the execution (before the last ping echo request) take
  the target offline(to trigger the waittime).  This will cause Ping to
  set the waittime to tmax which is 2 X the max RTT which we just set to
  a very large value.

  sudo ./ping -c 10 -i 0.5 $TARGET_IP > /tmp/out.log

  
  AS A RESULT,

  1. The Ping will keep running for a few hundred years, no big deal. In
  strace there will be a periodic recvmsg to check for response every
  few ms, something like this-

  Process 11373 attached - interrupt to quit
  ...
  recvmsg(3, 0x7ffed06dc650, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(3, 0x7ffed06dc650, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(3, 0x7ffed06dc650, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  ...

  2. In the /proc/timer_list file I see a large value for the process' timer-
  ...
   #14: <>, it_real_fn, S:01, hrtimer_start, ping/11373
   # expires at 611433835413-611433835413 nsecs [in 2000179546163581 to 
2000179546163581 nsecs]
  ...

  So we can see that when a large timeval is read from the echo
  response, it is not validated.

  Possible causes for invalid timeval values could be:
  Malicious destination, buggy OS, Malformed packets, interference with echo 
response belonging to "traceroute" command but had the same ID and Seq No.

  Impact-
  Ping runs forever.

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


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


[Touch-packages] [Bug 1989467] Re: Several autopkgtest failures on Ubuntu 22.04 and older

2022-09-14 Thread Benjamin Drung
** Description changed:

  All autopkgtest fail on Ubuntu 22.04 (jammy) and older:
  https://autopkgtest.ubuntu.com/packages/apport
  
  Following test cases fail:
  
  * backend_apt_dpkg:
  ** test_get_dependencies (armhf)
  ** test_get_source_tree_sandbox (arm64, armhf, ppc64el)
  ** test_install_old_packages (arm64, armhf, ppc64el)
  ** test_install_package_from_a_ppa (arm64, armhf, ppc64el)
  ** test_install_packages_dependencies (arm64, armhf, ppc64el)
  ** test_install_packages_from_launchpad (arm64, armhf, ppc64el)
  ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el)
  ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el)
  ** test_install_packages_unversioned (arm64, armhf, ppc64el)
  ** test_install_packages_versioned (arm64, armhf, ppc64el)
  * hookutils:
  ** test_module_license_evaluation (armhf)
  * python_crashes:
  ** test_dbus_service_timeout_running (armhf)
  ** test_dbus_service_unknown_wrongbus_notrunning (armhf)
  * report:
  ** test_add_gdb_info_abort (armhf)
  ** test_add_gdb_info_script (armhf)
  ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x)
  * signal_crashes:
  ** test_core_dump_packaged (armhf, ppc64el, s390x)
  ** test_core_dump_unpackaged (armhf)
  ** test_core_file_injection (armhf)
  ** test_crash_system_slice (amd64, ppc64el, s390x)
  ** test_empty_core_dump (follow-up failure for test_crash_system_slice)
  ** test_flood_limit (follow-up failure for test_crash_system_slice)
  ** test_ignore (follow-up failure for test_crash_system_slice)
  ** test_ignore_sigquit (follow-up failure for test_crash_system_slice)
  * ui:
  ** test_run_crash_kernel (arm64, s390x)
+ * ui_gtk:
+ ** test_kerneloops_nodetails (armhf)

** Description changed:

  All autopkgtest fail on Ubuntu 22.04 (jammy) and older:
  https://autopkgtest.ubuntu.com/packages/apport
  
  Following test cases fail:
  
  * backend_apt_dpkg:
  ** test_get_dependencies (armhf)
  ** test_get_source_tree_sandbox (arm64, armhf, ppc64el)
  ** test_install_old_packages (arm64, armhf, ppc64el)
  ** test_install_package_from_a_ppa (arm64, armhf, ppc64el)
  ** test_install_packages_dependencies (arm64, armhf, ppc64el)
  ** test_install_packages_from_launchpad (arm64, armhf, ppc64el)
  ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el)
  ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el)
  ** test_install_packages_unversioned (arm64, armhf, ppc64el)
  ** test_install_packages_versioned (arm64, armhf, ppc64el)
  * hookutils:
  ** test_module_license_evaluation (armhf)
  * python_crashes:
  ** test_dbus_service_timeout_running (armhf)
  ** test_dbus_service_unknown_wrongbus_notrunning (armhf)
  * report:
  ** test_add_gdb_info_abort (armhf)
  ** test_add_gdb_info_script (armhf)
  ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x)
  * signal_crashes:
  ** test_core_dump_packaged (armhf, ppc64el, s390x)
  ** test_core_dump_unpackaged (armhf)
  ** test_core_file_injection (armhf)
  ** test_crash_system_slice (amd64, ppc64el, s390x)
  ** test_empty_core_dump (follow-up failure for test_crash_system_slice)
  ** test_flood_limit (follow-up failure for test_crash_system_slice)
  ** test_ignore (follow-up failure for test_crash_system_slice)
  ** test_ignore_sigquit (follow-up failure for test_crash_system_slice)
  * ui:
  ** test_run_crash_kernel (arm64, s390x)
+ ** test_run_report_bug_kernel_thread (armhf)
  * ui_gtk:
  ** test_kerneloops_nodetails (armhf)

** Description changed:

  All autopkgtest fail on Ubuntu 22.04 (jammy) and older:
  https://autopkgtest.ubuntu.com/packages/apport
  
  Following test cases fail:
  
  * backend_apt_dpkg:
  ** test_get_dependencies (armhf)
  ** test_get_source_tree_sandbox (arm64, armhf, ppc64el)
  ** test_install_old_packages (arm64, armhf, ppc64el)
  ** test_install_package_from_a_ppa (arm64, armhf, ppc64el)
  ** test_install_packages_dependencies (arm64, armhf, ppc64el)
  ** test_install_packages_from_launchpad (arm64, armhf, ppc64el)
  ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el)
  ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el)
  ** test_install_packages_unversioned (arm64, armhf, ppc64el)
  ** test_install_packages_versioned (arm64, armhf, ppc64el)
  * hookutils:
  ** test_module_license_evaluation (armhf)
  * python_crashes:
  ** test_dbus_service_timeout_running (armhf)
  ** test_dbus_service_unknown_wrongbus_notrunning (armhf)
  * report:
  ** test_add_gdb_info_abort (armhf)
  ** test_add_gdb_info_script (armhf)
  ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x)
  * signal_crashes:
  ** test_core_dump_packaged (armhf, ppc64el, s390x)
  ** test_core_dump_unpackaged (armhf)
  ** test_core_file_injection (armhf)
  ** test_crash_system_slice (amd64, ppc64el, s390x)
  ** test_empty_core_dump (follow-up failure for test_crash_system_slice)
  ** test_flood_limit (follow-up failure for test_crash_system_slice)
  ** test_ignore (follo

[Touch-packages] [Bug 1989572] Re: libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0

2022-09-14 Thread Juan Navarro
** Description changed:

  This maybe has to be reassigned to affect 'ddeb-retriever', but the web
  form doesn't allow setting it as package for reporting.
  
  'libglib2.0-0' was updated in the bionic-updates repository, but
  'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs
  repository:
  
- # apt-cache policy libglib2.0-0 
- libglib2.0-0:
-   Installed: 2.56.4-0ubuntu0.18.04.9
-   Candidate: 2.56.4-0ubuntu0.18.04.9
-   Version table:
-  *** 2.56.4-0ubuntu0.18.04.9 500
- 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
- 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  2.56.1-2ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ # apt-cache policy libglib2.0-0
+ libglib2.0-0:
+   Installed: 2.56.4-0ubuntu0.18.04.9
+   Candidate: 2.56.4-0ubuntu0.18.04.9
+   Version table:
+  *** 2.56.4-0ubuntu0.18.04.9 500
+ 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
+ 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  2.56.1-2ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
- # apt-cache policy libglib2.0-0-dbgsym
- libglib2.0-0-dbgsym:
-   Installed: (none)
-   Candidate: 2.56.1-2ubuntu1
-   Version table:
-  2.56.1-2ubuntu1 500
- 500 http://ddebs.ubuntu.com bionic/main amd64 Packages
+ # apt-cache policy libglib2.0-0-dbgsym
+ libglib2.0-0-dbgsym:
+   Installed: (none)
+   Candidate: 2.56.1-2ubuntu1
+   Version table:
+  2.56.1-2ubuntu1 500
+ 500 http://ddebs.ubuntu.com bionic/main amd64 Packages
  
  Due to this, the package 'libglib2.0-0-dbgsym' is not installable with
  apt-get:
  
- # apt-get update && apt-get install libglib2.0-0-dbgsym
- [...]
- The following packages have unmet dependencies:
-  libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 
2.56.4-0ubuntu0.18.04.9 is to be installed
- E: Unable to correct problems, you have held broken packages.
+ # apt-get update && apt-get install libglib2.0-0-dbgsym
+ [...]
+ The following packages have unmet dependencies:
+  libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 
2.56.4-0ubuntu0.18.04.9 is to be installed
+ E: Unable to correct problems, you have held broken packages.
  
  Using `--force-yes` or `--allow-downgrades` does not make any
  difference.
  
  These are the ddebs repositories in use:
  
- # cat /etc/apt/sources.list.d/ddebs.list
- deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
- deb http://ddebs.ubuntu.com bionic-updates main restricted universe 
multiverse
- deb http://ddebs.ubuntu.com bionic-proposed main restricted universe 
multiverse
+ # cat /etc/apt/sources.list.d/ddebs.list
+ deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
+ deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse
+ deb http://ddebs.ubuntu.com bionic-proposed main restricted universe 
multiverse
  
  System is Ubuntu 18.04 Bionic:
  
- # lsb_release -rd
- Description:Ubuntu 18.04.6 LTS
- Release:18.04
+ # lsb_release -rd
+ Description:Ubuntu 18.04.6 LTS
+ Release:18.04

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

Title:
  libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  This maybe has to be reassigned to affect 'ddeb-retriever', but the
  web form doesn't allow setting it as package for reporting.

  'libglib2.0-0' was updated in the bionic-updates repository, but
  'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs
  repository:

  # apt-cache policy libglib2.0-0
  libglib2.0-0:
    Installed: 2.56.4-0ubuntu0.18.04.9
    Candidate: 2.56.4-0ubuntu0.18.04.9
    Version table:
   *** 2.56.4-0ubuntu0.18.04.9 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.56.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  # apt-cache policy libglib2.0-0-dbgsym
  libglib2.0-0-dbgsym:
    Installed: (none)
    Candidate: 2.56.1-2ubuntu1
    Version table:
   2.56.1-2ubuntu1 500
  500 http://ddebs.ubuntu.com bionic/main amd64 Packages

  Due to this, the package 'libglib2.0-0-dbgsym' is not installable with
  apt-get:

  # apt-get update && apt-get install libglib2.0-0-dbgsym
  [...]
  The following packages have unmet dependencies:
   libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56

[Touch-packages] [Bug 1971901]

2022-09-14 Thread Alexandre Julliard
*** Bug 53675 has been marked as a duplicate of this bug. ***

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

Title:
  dlltool uses non-unique temp filenames

Status in binutils:
  Fix Released
Status in Wine:
  Won't Fix
Status in binutils package in Ubuntu:
  Confirmed
Status in binutils-mingw-w64 package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

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

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

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

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

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

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

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


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


[Touch-packages] [Bug 1989572] [NEW] libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0

2022-09-14 Thread Juan Navarro
Public bug reported:

This maybe has to be reassigned to affect 'ddeb-retriever', but the web
form doesn't allow setting it as package for reporting.

'libglib2.0-0' was updated in the bionic-updates repository, but
'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs
repository:

# apt-cache policy libglib2.0-0 
libglib2.0-0:
  Installed: 2.56.4-0ubuntu0.18.04.9
  Candidate: 2.56.4-0ubuntu0.18.04.9
  Version table:
 *** 2.56.4-0ubuntu0.18.04.9 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 2.56.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

# apt-cache policy libglib2.0-0-dbgsym
libglib2.0-0-dbgsym:
  Installed: (none)
  Candidate: 2.56.1-2ubuntu1
  Version table:
 2.56.1-2ubuntu1 500
500 http://ddebs.ubuntu.com bionic/main amd64 Packages

Due to this, the package 'libglib2.0-0-dbgsym' is not installable with
apt-get:

# apt-get update && apt-get install libglib2.0-0-dbgsym
[...]
The following packages have unmet dependencies:
 libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 
2.56.4-0ubuntu0.18.04.9 is to be installed
E: Unable to correct problems, you have held broken packages.

Using `--force-yes` or `--allow-downgrades` does not make any
difference.

These are the ddebs repositories in use:

# cat /etc/apt/sources.list.d/ddebs.list
deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
deb http://ddebs.ubuntu.com bionic-updates main restricted universe 
multiverse
deb http://ddebs.ubuntu.com bionic-proposed main restricted universe 
multiverse

System is Ubuntu 18.04 Bionic:

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

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic

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

Title:
  libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  This maybe has to be reassigned to affect 'ddeb-retriever', but the
  web form doesn't allow setting it as package for reporting.

  'libglib2.0-0' was updated in the bionic-updates repository, but
  'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs
  repository:

  # apt-cache policy libglib2.0-0 
  libglib2.0-0:
Installed: 2.56.4-0ubuntu0.18.04.9
Candidate: 2.56.4-0ubuntu0.18.04.9
Version table:
   *** 2.56.4-0ubuntu0.18.04.9 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.56.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  # apt-cache policy libglib2.0-0-dbgsym
  libglib2.0-0-dbgsym:
Installed: (none)
Candidate: 2.56.1-2ubuntu1
Version table:
   2.56.1-2ubuntu1 500
  500 http://ddebs.ubuntu.com bionic/main amd64 Packages

  Due to this, the package 'libglib2.0-0-dbgsym' is not installable with
  apt-get:

  # apt-get update && apt-get install libglib2.0-0-dbgsym
  [...]
  The following packages have unmet dependencies:
   libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 
2.56.4-0ubuntu0.18.04.9 is to be installed
  E: Unable to correct problems, you have held broken packages.

  Using `--force-yes` or `--allow-downgrades` does not make any
  difference.

  These are the ddebs repositories in use:

  # cat /etc/apt/sources.list.d/ddebs.list
  deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
  deb http://ddebs.ubuntu.com bionic-updates main restricted universe 
multiverse
  deb http://ddebs.ubuntu.com bionic-proposed main restricted universe 
multiverse

  System is Ubuntu 18.04 Bionic:

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1989572/+subscriptions


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


[Touch-packages] [Bug 1989365] Re: test_omit_all_processes_except_one is racy and fails sometimes

2022-09-14 Thread Benjamin Drung
Proposed fix: https://github.com/canonical/apport/pull/3

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

Title:
  test_omit_all_processes_except_one is racy and fails sometimes

Status in Apport:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The test case test_omit_all_processes_except_one is racy and fails
  sometimes:

  ```
  test_omit_all_processes_except_one 
(tests.system.test_unkillable_shutdown.TestUnkillableShutdown)
  unkillable_shutdown will write exactly one report. ... Running as unit: 
run-r0b0d3fe87473410c9eb61a5ae4635938.service
  FAIL
  ==
  FAIL: test_omit_all_processes_except_one 
(tests.system.test_unkillable_shutdown.TestUnkillableShutdown)
  unkillable_shutdown will write exactly one report.
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.JJoBfX/autopkgtest_tmp/tests/system/test_unkillable_shutdown.py",
 line 96, in test_omit_all_processes_except_one
  pid = self._launch_process_with_different_session_id(existing_pids)
File 
"/tmp/autopkgtest.JJoBfX/autopkgtest_tmp/tests/system/test_unkillable_shutdown.py",
 line 90, in _launch_process_with_different_session_id
  self.assertEqual(len(test_executable_pids), 1, test_executable_pids)
  AssertionError: 0 != 1 : set()

  --
  ```

  autopkgtest log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  kinetic/kinetic/amd64/a/apport/20220912_055849_5f03e@/log.gz

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


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


[Touch-packages] [Bug 1989457] Re: Enable riscv64 build

2022-09-14 Thread Heinrich Schuchardt
@enr0n and @brian-murray suggested that this change should go through
the feature freeze exception process.

**Description of the proposed changes**

With the change packages systemd-boot and systemd-boot-efi will be first
time built for the riscv64 architecture. No changes will occur for any
other architecture.

**Rationale for the exception**

systemd-boot-efi is used to implement Ubuntu Core based gadgets. To
provide these on riscv64 the packages should be built for this
architecture.

**Additional information**

As these are new packages for the riscv64 archtitecture we do not have a
regression risk.

The packages are not preinstalled by any Kinetics image but have to be
installed manually.


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

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

Title:
  Enable riscv64 build

Status in systemd package in Ubuntu:
  New

Bug description:
  The upstream source supports building systemd-boot for the riscv64
  architecture. We just haven't enabled it yet in debian/control.

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


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


[Touch-packages] [Bug 1895664] Re: evince can't start local installation of vivaldi browser

2022-09-14 Thread Marian Rainer-Harbach
@seb128: Vivaldi is the spiritual successor of Opera. Opera _is_
included in /etc/apparmor.d/abstractions/ubuntu-browsers, so Vivaldi
should be as well.

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

Title:
  evince can't start local installation of vivaldi browser

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Invalid

Bug description:
  evince 3.28.4-0ubuntu1.2 running on bionic.  I cannot call the
  vivaldi-browser by clicking on a link.  Instead an error is shown
  "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission
  denied)".  Some lines from syslog:

  Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 
audit(1600172908.761:241): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 
audit(1600172909.393:242): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 
audit(1600172909.585:243): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 
audit(1600172909.617:244): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 
audit(1600172933.841:256): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

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


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


[Touch-packages] [Bug 1895664] Re: evince can't start local installation of vivaldi browser

2022-09-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  evince can't start local installation of vivaldi browser

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Invalid

Bug description:
  evince 3.28.4-0ubuntu1.2 running on bionic.  I cannot call the
  vivaldi-browser by clicking on a link.  Instead an error is shown
  "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission
  denied)".  Some lines from syslog:

  Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 
audit(1600172908.761:241): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 
audit(1600172909.393:242): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 
audit(1600172909.585:243): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 
audit(1600172909.617:244): apparmor="DENIED" operation="create" 
profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" 
family="netlink" sock_type="raw" protocol=0 requested_mask="create" 
denied_mask="create"
  Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 
audit(1600172933.841:256): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

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


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


[Touch-packages] [Bug 1989545] [NEW] ubuntu-bug fails when run via remote SSH login

2022-09-14 Thread Ian! D. Allen
Public bug reported:

I'm running Ubuntu 20.04 on my desktop.  I SSH into my laptop running
22.04:

desktop$ ssh laptop
laptop$ sudo -sE
laptop#

If I now run most any X11 client applications (e.g. xload, xterm)
using this laptop SSH command line, they correctly open windows on my
desktop X11 display, not on my laptop, using the DISPLAY variable set
to localhost:10.0.  But ubuntu-bug does not do this when I run it on
the laptop:

laptop# ubuntu-bug /etc/network/if-up.d/resolved

At this point, the laptop display incorrectly has the apport X11 window
open.  The apport window does not open on my desktop, like any other
X11 application would.  It appears to ignore my DISPLAY variable.

If I go over to the laptop and try to continue with the bug report,
everything falls apart when it tries to start up a web browser.  I get
all these error messages on my SSH terminal screen:

update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): not a directory
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib": permission denied
/home/username/Music was removed, reassigning MUSIC to homedir
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
Error: cannot open display: localhost:10.0
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.

If ubuntu-bug cannot work over SSH with DISPLAY=localhost:10.0, it should
detect this and not even try.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.1
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 14 02:33:18 2022
InstallationDate: Installed on 2020-09-08 (735 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to jammy on 2022-04-04 (162 days ago)

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


** Tags: amd64 apport-bug jammy third-party-packages wayland-session

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

Title:
  ubuntu-bug fails when run via remote SSH login

Status in apport package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 20.04 on my desktop.  I SSH into my laptop running
  22.04:

  desktop$ ssh laptop
  laptop$ sudo -sE
  laptop#

  If I now run most any X11 client applications (e.g. xload, xterm)
  using this laptop SSH command line, they correctly open windows on my
  desktop X11 display, not on my laptop, using the DISPLAY variable set
  to localhost:10.0.  But ubuntu-bug does not do this when I run it on
  the laptop:

  laptop# ubuntu-bug /etc/network/if-up.d/resolved

  At this point, the laptop display incorrectly has the apport X11 window
  open.  The apport window does not open on my desktop, like any other
  X11 application would.  It appears to ignore my DISPLAY variable.

  If I go over to the laptop and try to continue with the bug report,
  everything falls apart when it tries to start up a web browser.  I get
  all these error messages on my SSH terminal screen:

  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): not a directory
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib": permission denied
  /home/username/Music was removed, reassigning MUSIC to homedir
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.
  Error: cannot open display: localhost:10.0
  X11 connection rejected because of