[Touch-packages] [Bug 1597017] Re: mount rules grant excessive permissions

[Andrew Killen]

@Simon, thank you for the link, that also clarifies Steve's comment
(https://bugs.launchpad.net/apparmor/+bug/1597017/comments/25) earlier
in this thread which I didn't interpret appropriately during first read
through. Based on the linked thread the plan was to publish to the
security repository last week, but I have my questions answered and will
sit tight until that takes place. Appreciate your help!

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

Title:
  mount rules grant excessive permissions

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * The mount rules in apparmor grant excessive permissions.
 See Original Report below.

  [Test Plan]

   * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
 See comment 26 for context.

  [Other Info]

  SRU Team; the packages for focal-proposed and jammy-proposed are
  intended as security updates prepared by the Ubuntu Security team (and
  have built in a ppa with only the security pockets enabled). However,
  because the fix makes mount rules in apparmor policy be treated more
  restrictively than they were prior to this update, we would like these
  packages to gain more widespread testing.

  [Risk of Regression]

  The update for this issue causes the apparmor parser, the tool that
  translates written policy into the enforcement data structures used by
  the kernel, to generate more strict policy for mount rules, like the
  example below. They are not common in apparmor policy generally, but
  can appear in policies written for container managers to restrict
  containers, and thus can potentially break container startup.

  The packages prepared for focal-proposed and jammy-proposed have
  tested with the versions of snapd, lxc, libvirt, and docker in the
  ubuntu archive, but container managers outside of the ubuntu archive
  may run into issues, hence the need for testing and policy
  adjustments.

  Original Report:

  The rule
    mount options=(rw,make-slave) -> **,

  ends up allowing
    mount -t proc proc /mnt

  which it shouldn't as it should be restricted to commands with a make-
  slave flag

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


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

[Touch-packages] [Bug 1597017] Re: mount rules grant excessive permissions

[Andrew Killen]

I am running Focal Fossa and noticed that AppArmor was vulnerable
(CVE-2016-1585). My automatic upgrade attempts were not upgrading from
the vulnerable version 2.13.3-7ubuntu5.3build2 to the latest version
2.13.3-7ubuntu5.4. When investigating further it is because my systems
are configured to only pull updates out of the security repository,
which does not include this update.

I posted a question in the general AppArmor area and it was suggested to
bring this up in this specific bug thread. The thought is that the
version released around this bug should be included in the security
repository, not just the update repository. If this is indeed an issue,
the same can be said for the jammy releases as well.

Link to my question:
https://answers.launchpad.net/ubuntu/+source/apparmor/+question/818906

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

Title:
  mount rules grant excessive permissions

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * The mount rules in apparmor grant excessive permissions.
 See Original Report below.

  [Test Plan]

   * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
 See comment 26 for context.

  [Other Info]

  SRU Team; the packages for focal-proposed and jammy-proposed are
  intended as security updates prepared by the Ubuntu Security team (and
  have built in a ppa with only the security pockets enabled). However,
  because the fix makes mount rules in apparmor policy be treated more
  restrictively than they were prior to this update, we would like these
  packages to gain more widespread testing.

  [Risk of Regression]

  The update for this issue causes the apparmor parser, the tool that
  translates written policy into the enforcement data structures used by
  the kernel, to generate more strict policy for mount rules, like the
  example below. They are not common in apparmor policy generally, but
  can appear in policies written for container managers to restrict
  containers, and thus can potentially break container startup.

  The packages prepared for focal-proposed and jammy-proposed have
  tested with the versions of snapd, lxc, libvirt, and docker in the
  ubuntu archive, but container managers outside of the ubuntu archive
  may run into issues, hence the need for testing and policy
  adjustments.

  Original Report:

  The rule
    mount options=(rw,make-slave) -> **,

  ends up allowing
    mount -t proc proc /mnt

  which it shouldn't as it should be restricted to commands with a make-
  slave flag

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


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

[Touch-packages] [Bug 2081052] [NEW] audio

[Dave Andrew]

Public bug reported:

i get sound through speakers for about 30 seconds and then sound cuts
off.sound through a headset is ok

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu10
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:dave   1388 F pipewire
 /dev/snd/controlC0:  dave   1396 F wireplumber
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Sep 18 11:23:05 2024
InstallationDate: Installed on 2020-02-07 (1685 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: RM Education RM
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
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: Upgraded to noble on 2024-09-18 (0 days ago)
dmi.bios.date: 04/20/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 202
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: RM MOBILE ONE 310
dmi.board.vendor: RM Education
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: RM Education
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr202:bd04/20/2011:br4.6:svnRMEducation:pnRM:pvr1.0:rvnRMEducation:rnRMMOBILEONE310:rvr1.0:cvnRMEducation:ct10:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: PEGA Family
dmi.product.name: RM
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: RM Education
mtime.conffile..etc.init.d.apport: 2024-07-22T15:59:07

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


** Tags: amd64 apport-bug noble

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

Title:
  audio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  i get sound through speakers for about 30 seconds and then sound cuts
  off.sound through a headset is ok

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu10
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:dave   1388 F pipewire
   /dev/snd/controlC0:  dave   1396 F wireplumber
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 18 11:23:05 2024
  InstallationDate: Installed on 2020-02-07 (1685 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: RM Education RM
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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: Upgraded to noble on 2024-09-18 (0 days ago)
  dmi.bios.date: 04/20/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 202
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RM MOBILE ONE 310
  dmi.board.vendor: RM Education
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: RM Education
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr202:bd04/20/2011:br4.6:svnRMEducation:pnRM:pvr1.0:rvnRMEducation:rnRMMOBILEONE310:rvr1.0:cvnRMEducation:ct10:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: RM
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: RM Education
  mtime.conffile..etc.init.d.apport: 2024-07-22T15:59:07

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


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

[Touch-packages] [Bug 2073776] Re: nsswitch.conf "passwd" entry misses "systemd", breaking DynamicUser=yes systemd units

[Andrew Martin]

Yes, I had changed it with ansible

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

Title:
  nsswitch.conf "passwd" entry misses "systemd", breaking
  DynamicUser=yes systemd units

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The 321-1~bpo22.04.1 version of cockpit-ws calls the cockpit user 
"cockpit-wsinstance":
  $ cat usr/lib/sysusers.d/cockpit-wsinstance.conf
  u cockpit-wsinstance - "User for cockpit-ws instances" -

  However the following systemd files still reference the old "cockpit-ws" 
username, so the service fails to start:
  $ grep -r cockpit-ws$ lib/systemd/system
  lib/systemd/system/cockpit-ws-user.service:Description=Dynamic user for 
cockpit-ws
  lib/systemd/system/cockpit-ws-user.service:User=cockpit-ws
  lib/systemd/system/cockpit-ws-user.service:Group=cockpit-ws
  lib/systemd/system/cockpit-wsinstance-https@.socket:SocketUser=cockpit-ws
  
lib/systemd/system/cockpit-wsinstance-https-factory.socket:SocketUser=cockpit-ws
  lib/systemd/system/cockpit.service:User=cockpit-ws
  lib/systemd/system/cockpit.service:Group=cockpit-ws
  lib/systemd/system/cockpit-wsinstance-http.socket:SocketUser=cockpit-ws

  Can these systemd files be updated to use the new username? Thanks!

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


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

[Touch-packages] [Bug 2018425] Re: apt install ubuntu-desktop takes forever

[Andrew N]

Hi, I’ve run into this issue many times and today tracked down the cause
to this open bug: https://bugs.launchpad.net/netplan/+bug/1999178

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

Title:
  apt install ubuntu-desktop takes forever

Status in subiquity:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Install server 23.04 to take advantage of flexible disk
  partitioning/raid. While installing desktop over the installed server
  (apt install ubuntu-desktop) it proceeds normally about 40% of the way
  but after that it slows down tremendously, hanging for minutes in
  between packages. It eventually (after several hours) completes
  without error.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  3 11:41:00 2023
  InstallationDate: Installed on 2023-04-29 (3 days ago)
  InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 
(20230415)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2052722] [NEW] systemd should package libnss-myhostname

[Andrew Lutomirski]

Public bug reported:

Ubuntu generally decided not to use libnss-myhostname in 2014, due to:

https://bugs.launchpad.net/ubuntu/+source/libnss-
myhostname/+bug/1162478/comments/6

which says "I don't agree that libnss-myhostname is a technically sound
approach, *period*; it works at cross-purposes to the existing Debian
handling of the hostname being resolved to 127.0.1.1 via /etc/hosts.
There should be a plan for aligning these, across *all* systems, not
just desktop systems."

While this may well have made sense in 2014, I think it's no longer the
right decision in light of widespread adoption of containers.  Container
managers (Docker, Podman, systemd-nspawm, etc) generally set the
container's hostname from _outside_ the container, either by bind-
mounting over /etc/hostname or by simply not having /etc/hostname.  In
either case, the hostname of the container cannot be reliably predicted
based on the contents of the container image, and editing /etc/hosts
inside the container to make the hostname resolvable is fragile at best.

While other solutions exist (arranging for the container manager to make
sure that the container's hostname is resolvable from inside the
container), libnss-myhostname offers users a straightforward way to
allow the container's hostname to be resolved.

Please reconsider packaging it.  Debian packages libnss-myhostname.

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

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

Title:
  systemd should package libnss-myhostname

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu generally decided not to use libnss-myhostname in 2014, due to:

  https://bugs.launchpad.net/ubuntu/+source/libnss-
  myhostname/+bug/1162478/comments/6

  which says "I don't agree that libnss-myhostname is a technically
  sound approach, *period*; it works at cross-purposes to the existing
  Debian handling of the hostname being resolved to 127.0.1.1 via
  /etc/hosts. There should be a plan for aligning these, across *all*
  systems, not just desktop systems."

  While this may well have made sense in 2014, I think it's no longer
  the right decision in light of widespread adoption of containers.
  Container managers (Docker, Podman, systemd-nspawm, etc) generally set
  the container's hostname from _outside_ the container, either by bind-
  mounting over /etc/hostname or by simply not having /etc/hostname.  In
  either case, the hostname of the container cannot be reliably
  predicted based on the contents of the container image, and editing
  /etc/hosts inside the container to make the hostname resolvable is
  fragile at best.

  While other solutions exist (arranging for the container manager to
  make sure that the container's hostname is resolvable from inside the
  container), libnss-myhostname offers users a straightforward way to
  allow the container's hostname to be resolved.

  Please reconsider packaging it.  Debian packages libnss-myhostname.

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


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

[Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when preconfiguring packages

[Andrew J. Caines]

This system has remained substantially vanilla since the original
install - 18.04 if I remember correctly - with only LTS upgrades and I
have certainly made no local changes to the packaging tools.

$ which apt-extracttemplates
/usr/bin/apt-extracttemplates
$ debsums -s apt-utils
$

That is to say that there was no output and debsums returned an exit
code of 0.

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

Title:
  Open3.pm tries to run code in /tmp when preconfiguring packages

Status in debconf package in Ubuntu:
  New

Bug description:
  During update of ubuntu-drivers-common:

Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
  open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  /tmp is mounted with noexec because running code from /tmp has been a
  vulnerability vector for several decades, hence reporting this as a
  vulnerability in perl-base.

  This error did not appear to prevent the update of ubuntu-drivers-
  common and "dpkg --verify ubuntu-drivers-common" returns 0.

  
___

  Attempting to use the package search on this form by clicking the 🔍
  created a modal in which there is an error

Sorry, something went wrong with your search. We've recorded what
  happened, and we'll fix it as soon as possible. (Error ID:
  OOPS-c80f71590b02908a1187b9f743c53eac)

  which is repeated with any attempt to search for a package.

  
___

  Submitting this form gives an error

"perl-base" does not exist in Ubuntu. Please choose a different
  package. If you're unsure, please select "I don't know"

$ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
$ dpkg -l perl-base
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description

+++-==-=--=>
ii  perl-base  5.34.0-3ubuntu1.2 amd64minimal Perl system

  Looks like a package to me. Nevertheless, using "Did you mean..."
  offers "perl".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: perl-base 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3
  Uname: Linux 6.5.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 10:08:48 2023
  InstallationDate: Installed on 2016-04-23 (2763 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=rxvt
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: perl
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (453 days ago)

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


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

[Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when preconfiguring packages

[Andrew J. Caines]

$ readlink -f /var/cache/debconf/tmp.ci
/var/cache/debconf/tmp.ci

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

Title:
  Open3.pm tries to run code in /tmp when preconfiguring packages

Status in debconf package in Ubuntu:
  Incomplete

Bug description:
  During update of ubuntu-drivers-common:

Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
  open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  /tmp is mounted with noexec because running code from /tmp has been a
  vulnerability vector for several decades, hence reporting this as a
  vulnerability in perl-base.

  This error did not appear to prevent the update of ubuntu-drivers-
  common and "dpkg --verify ubuntu-drivers-common" returns 0.

  
___

  Attempting to use the package search on this form by clicking the 🔍
  created a modal in which there is an error

Sorry, something went wrong with your search. We've recorded what
  happened, and we'll fix it as soon as possible. (Error ID:
  OOPS-c80f71590b02908a1187b9f743c53eac)

  which is repeated with any attempt to search for a package.

  
___

  Submitting this form gives an error

"perl-base" does not exist in Ubuntu. Please choose a different
  package. If you're unsure, please select "I don't know"

$ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
$ dpkg -l perl-base
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description

+++-==-=--=>
ii  perl-base  5.34.0-3ubuntu1.2 amd64minimal Perl system

  Looks like a package to me. Nevertheless, using "Did you mean..."
  offers "perl".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: perl-base 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3
  Uname: Linux 6.5.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 10:08:48 2023
  InstallationDate: Installed on 2016-04-23 (2763 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=rxvt
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: perl
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (453 days ago)

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


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

[Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when preconfiguring packages

[Andrew J. Caines]

Attributing the bug to debconf and setting status to New following
advice while (mis)attributed to perl.

** Package changed: perl (Ubuntu) => debconf (Ubuntu)

** Changed in: debconf (Ubuntu)
   Status: Invalid => New

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

Title:
  Open3.pm tries to run code in /tmp when preconfiguring packages

Status in debconf package in Ubuntu:
  New

Bug description:
  During update of ubuntu-drivers-common:

Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
  open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  /tmp is mounted with noexec because running code from /tmp has been a
  vulnerability vector for several decades, hence reporting this as a
  vulnerability in perl-base.

  This error did not appear to prevent the update of ubuntu-drivers-
  common and "dpkg --verify ubuntu-drivers-common" returns 0.

  
___

  Attempting to use the package search on this form by clicking the 🔍
  created a modal in which there is an error

Sorry, something went wrong with your search. We've recorded what
  happened, and we'll fix it as soon as possible. (Error ID:
  OOPS-c80f71590b02908a1187b9f743c53eac)

  which is repeated with any attempt to search for a package.

  
___

  Submitting this form gives an error

"perl-base" does not exist in Ubuntu. Please choose a different
  package. If you're unsure, please select "I don't know"

$ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
$ dpkg -l perl-base
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description

+++-==-=--=>
ii  perl-base  5.34.0-3ubuntu1.2 amd64minimal Perl system

  Looks like a package to me. Nevertheless, using "Did you mean..."
  offers "perl".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: perl-base 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3
  Uname: Linux 6.5.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 10:08:48 2023
  InstallationDate: Installed on 2016-04-23 (2763 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=rxvt
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: perl
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (453 days ago)

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


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

[Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

[Andrew J. Caines]

Caught the error again, again while running in Software Updater, but I
captured the output from the beginning. There were only four related
packages being updated.

Preconfiguring packages ...
Can't exec "/tmp/cryptsetup-initramfs.config.UaZ02N": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/cryptsetup-initramfs.config.UaZ02N configure 
2:2.4.3-1ubuntu1.1 failed: Permission denied at 
/usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/cryptsetup-initramfs.config.dTuBRN": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/cryptsetup-initramfs.config.dTuBRN configure 
2:2.4.3-1ubuntu1.1 failed: Permission denied at 
/usr/share/perl5/Debconf/ConfModule.pm line 59.
(Reading database ... 247176 files and directories currently installed.)
Preparing to unpack .../libcryptsetup12_2%3a2.4.3-1ubuntu1.2_amd64.deb ...
Unpacking libcryptsetup12:amd64 (2:2.4.3-1ubuntu1.2) over (2:2.4.3-1ubuntu1.1) 
...
Preparing to unpack .../cryptsetup-initramfs_2%3a2.4.3-1ubuntu1.2_all.deb ...
Unpacking cryptsetup-initramfs (2:2.4.3-1ubuntu1.2) over (2:2.4.3-1ubuntu1.1) 
...
Preparing to unpack .../cryptsetup-bin_2%3a2.4.3-1ubuntu1.2_amd64.deb ...
Unpacking cryptsetup-bin (2:2.4.3-1ubuntu1.2) over (2:2.4.3-1ubuntu1.1) ...
Preparing to unpack .../cryptsetup_2%3a2.4.3-1ubuntu1.2_amd64.deb ...
Unpacking cryptsetup (2:2.4.3-1ubuntu1.2) over (2:2.4.3-1ubuntu1.1) ...
Setting up libcryptsetup12:amd64 (2:2.4.3-1ubuntu1.2) ...
Setting up cryptsetup-bin (2:2.4.3-1ubuntu1.2) ...
Setting up cryptsetup (2:2.4.3-1ubuntu1.2) ...
Setting up cryptsetup-initramfs (2:2.4.3-1ubuntu1.2) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for libc-bin (2.35-0ubuntu3.5) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for initramfs-tools (0.140ubuntu13.4) ...
update-initramfs: Generating /boot/initrd.img-6.5.0-1009-oem
...

Since ConfModule.pm is part of debconf, the errors occur during
"Preconfiguring packages" and earlier speculation, I will presume to
attribute this bug to debconf and update the title accordingly.

** Summary changed:

- Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common
+ Open3.pm tries to run code in /tmp when preconfiguring packages

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

Title:
  Open3.pm tries to run code in /tmp when preconfiguring packages

Status in debconf package in Ubuntu:
  New

Bug description:
  During update of ubuntu-drivers-common:

Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
  open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  /tmp is mounted with noexec because running code from /tmp has been a
  vulnerability vector for several decades, hence reporting this as a
  vulnerability in perl-base.

  This error did not appear to prevent the update of ubuntu-drivers-
  common and "dpkg --verify ubuntu-drivers-common" returns 0.

  
___

  Attempting to use the package search on this form by clicking the 🔍
  created a modal in which there is an error

Sorry, something went wrong with your search. We've recorded what
  happened, and we'll fix it as soon as possible. (Error ID:
  OOPS-c80f71590b02908a1187b9f743c53eac)

  which is repeated with any attempt to search for a package.

  
___

  Submitting this form gives an error

"perl-base" does not exist in Ubuntu. Please choose a different
  package. If you're unsure, please select "I don't know"

$ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
$ dpkg -l perl-base
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description

+++-==-=--=>
ii  perl-base  5.34.0-3ubuntu1.2 amd64

[Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

[Andrew J. Caines]

I will attempt to capture more details when I next observe the error so
that the correct package can be identified for this report.

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

Title:
  Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

Status in perl package in Ubuntu:
  Invalid

Bug description:
  During update of ubuntu-drivers-common:

Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
  open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  /tmp is mounted with noexec because running code from /tmp has been a
  vulnerability vector for several decades, hence reporting this as a
  vulnerability in perl-base.

  This error did not appear to prevent the update of ubuntu-drivers-
  common and "dpkg --verify ubuntu-drivers-common" returns 0.

  
___

  Attempting to use the package search on this form by clicking the 🔍
  created a modal in which there is an error

Sorry, something went wrong with your search. We've recorded what
  happened, and we'll fix it as soon as possible. (Error ID:
  OOPS-c80f71590b02908a1187b9f743c53eac)

  which is repeated with any attempt to search for a package.

  
___

  Submitting this form gives an error

"perl-base" does not exist in Ubuntu. Please choose a different
  package. If you're unsure, please select "I don't know"

$ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
$ dpkg -l perl-base
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description

+++-==-=--=>
ii  perl-base  5.34.0-3ubuntu1.2 amd64minimal Perl system

  Looks like a package to me. Nevertheless, using "Did you mean..."
  offers "perl".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: perl-base 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3
  Uname: Linux 6.5.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 10:08:48 2023
  InstallationDate: Installed on 2016-04-23 (2763 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=rxvt
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: perl
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (453 days ago)

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


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

[Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

[Andrew J. Caines]

You are of course quite right that the risk associated with a file
created with a "random" six character case-insensitive alphanumeric
suffix and run a moment later is far smaller than more obviously risky
misuses of /tmp. Nevertheless the issue is not about evaluating the risk
of an adversary creating over forty-four milliard files or symlinks per
package in /tmp, or if the code checks for the presence of the file
before trying to create it (which I trust it does), or just how random
the suffix really is, or how many race conditions might exist, or any of
the other cases we've seen exploited over the decades, but that this is
even a matter to consider in late 2024.

Since you mention it specifically, creating the file with mode 600 will
(or certainly should) of course prevent the contents of the file from
being overwritten by another user between creation and execution.

I consider it uncontroversial to claim that a standard process for updating 
software on Ubuntu should not
1) involve creating executables (or files containing code to be executed) 
directly in /tmp and running them as root, and
2) result in errors when /tmp is mounted noexec, especially when they may 
indicate unhandled breakage.

I briefly observed more similar errors during an update earlier today,
but was not quick enough to capture more details before the Software
Updater output window disappeared; however I doubt those details
provided any more useful information.

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

Title:
  Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

Status in perl package in Ubuntu:
  Invalid

Bug description:
  During update of ubuntu-drivers-common:

Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
  open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  /tmp is mounted with noexec because running code from /tmp has been a
  vulnerability vector for several decades, hence reporting this as a
  vulnerability in perl-base.

  This error did not appear to prevent the update of ubuntu-drivers-
  common and "dpkg --verify ubuntu-drivers-common" returns 0.

  
___

  Attempting to use the package search on this form by clicking the 🔍
  created a modal in which there is an error

Sorry, something went wrong with your search. We've recorded what
  happened, and we'll fix it as soon as possible. (Error ID:
  OOPS-c80f71590b02908a1187b9f743c53eac)

  which is repeated with any attempt to search for a package.

  
___

  Submitting this form gives an error

"perl-base" does not exist in Ubuntu. Please choose a different
  package. If you're unsure, please select "I don't know"

$ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
$ dpkg -l perl-base
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description

+++-==-=--=>
ii  perl-base  5.34.0-3ubuntu1.2 amd64minimal Perl system

  Looks like a package to me. Nevertheless, using "Did you mean..."
  offers "perl".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: perl-base 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3
  Uname: Linux 6.5.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 10:08:48 2023
  InstallationDate: Installed on 2016-04-23 (2763 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=rxvt
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: perl
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (453 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2043711/+subscripti

[Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

[Andrew J. Caines]

@vorlon, Thank you for your considered response. I concur that this is
not a vulnerability in the Ubuntu perl package.

While I do not disagree with any of the points you make, the fact
remains that processes running as root created a file directly in /tmp
not using a safe *mktemp* process and later ran the code in that file.
The risks of doing this are sufficiently well understood, as the
preferable alternatives.

Given that that this quite vanilla Ubuntu system and that this behaviour
was only observed as a result of the reasonable and fairly common
configuration of mounting `/tmp` with *noexec* and did so while running
updates in a fully supported manner, i.e. with *Software Updater*, this
remains a bug with a directly associated security risk. That is to say -
as you expressed it - this comes from an Ubuntu package, though I don't
know which.

Do you recommend that I do anything other than change the Package to
"debconf" and Status to "New"?


@juliank, *apt-utils* is installed.

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

Title:
  Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

Status in perl package in Ubuntu:
  Invalid

Bug description:
  During update of ubuntu-drivers-common:

Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
  open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  /tmp is mounted with noexec because running code from /tmp has been a
  vulnerability vector for several decades, hence reporting this as a
  vulnerability in perl-base.

  This error did not appear to prevent the update of ubuntu-drivers-
  common and "dpkg --verify ubuntu-drivers-common" returns 0.

  
___

  Attempting to use the package search on this form by clicking the 🔍
  created a modal in which there is an error

Sorry, something went wrong with your search. We've recorded what
  happened, and we'll fix it as soon as possible. (Error ID:
  OOPS-c80f71590b02908a1187b9f743c53eac)

  which is repeated with any attempt to search for a package.

  
___

  Submitting this form gives an error

"perl-base" does not exist in Ubuntu. Please choose a different
  package. If you're unsure, please select "I don't know"

$ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
$ dpkg -l perl-base
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description

+++-==-=--=>
ii  perl-base  5.34.0-3ubuntu1.2 amd64minimal Perl system

  Looks like a package to me. Nevertheless, using "Did you mean..."
  offers "perl".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: perl-base 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3
  Uname: Linux 6.5.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 10:08:48 2023
  InstallationDate: Installed on 2016-04-23 (2763 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=rxvt
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: perl
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (453 days ago)

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


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

[Touch-packages] [Bug 2038610] [NEW] package linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Andrew Adams]

Public bug reported:

System crashed when installing update

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Oct  6 06:44:43 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2023-09-22 (13 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.10
SourcePackage: initramfs-tools
Title: package linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  System crashed when installing update

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Oct  6 06:44:43 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-09-22 (13 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: initramfs-tools
  Title: package linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1957024] Re: pam-mkhomedir does not honor private home directories

[Andrew Lowther]

I created a patch that changes the behavior of the default mkhomedir
configuration to follow the "private home directories" proposal.  The
permissions on home directories created by pam_mkhomedir.so will be
consistent with the permissions on home directories created by `adduser`
and `useradd`.

** Patch added: "private_homedir.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1957024/+attachment/5705955/+files/private_homedir.patch

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

Title:
  pam-mkhomedir does not honor private home directories

Status in pam package in Ubuntu:
  New

Bug description:
  As reported in https://discourse.ubuntu.com/t/private-home-
  directories-for-ubuntu-21-04-onwards/19533/13:

  A common situation is to have a central set of users (e.g. in LDAP)
  and use pam_mkhomedir.so to create the home directory when the user
  first logs in.

  These changes do not cover this situation. The default configuration
  of pam_mkhomedir.so will result in a home directory created with 0755
  permissions.

  To make pam_mkhomedir.so create a home directory by default with
  permissions consistent with the other tools then a umask argument can
  be added to the pam_mkhomedir.so module in the file /usr/share/pam-
  configs/mkhomedir. I believe this would have to be done before
  enabling the module. The file is part of the libpam-modules package.

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


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

[Touch-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

[andrew]

Same issue on Razer Blade 16. Please help

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

Re: [Touch-packages] [Bug 2023436] Re: Icons are showing as no entry signs

[Andrew Perry]

Correction, I ran:
sudo /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
--update-cache.

I rebooted and all the icons are loading correctly, thank you!

I am also applying the driver change which will hopefully resolve my screen
issue. If not I will raise a separate bug.

I've been putting up with this annoyance for months, thank you for helping
me get rid of this problem!

Kind regards,
Andrew

On Mon, 12 Jun 2023 at 19:57, Andrew Perry  wrote:

> I did some googling and fixed the gnome control centre  issue by running:
> sudo /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
>
> Lots of other images aren't loading yet but I'll restart and see if that
> addresses it
>
> On Mon, 12 Jun 2023 at 19:37, Andrew Perry  wrote:
>
>> This is the output:
>>
>> (gnome-control-center:9103): Gtk-WARNING **: 19:35:37.672: Could not load
>> a pixbuf from /com/ubuntu/themes/Yaru-dark/3.0/assets/bullet-symbolic.svg.
>> This may indicate that pixbuf loaders or the mime database could not be
>> found.
>>
>> On Mon, 12 Jun 2023 at 09:31, Andrew Perry  wrote:
>>
>>> Thanks for the replies, you're right about it being a different bug.
>>> Should have known better. Will post the results of the command for this bug
>>> tonight.
>>>
>>> Kind regards,
>>> Andrew
>>>
>>> On Mon, 12 Jun 2023, 08:45 Daniel van Vugt, <2023...@bugs.launchpad.net>
>>> wrote:
>>>
>>>> The black screen issue you mention should be discussed elsewhere because
>>>> each bug should only cover a single topic. But that's likely to be
>>>> caused by the open source 'nouveau' driver. So please open the
>>>> 'Additional Drivers' app to install a supported NVIDIA driver to avoid
>>>> that.
>>>>
>>>> --
>>>> You received this bug notification because you are subscribed to the bug
>>>> report.
>>>> https://bugs.launchpad.net/bugs/2023436
>>>>
>>>> Title:
>>>>   Icons are showing as no entry signs
>>>>
>>>> Status in gtk+3.0 package in Ubuntu:
>>>>   Incomplete
>>>>
>>>> Bug description:
>>>>   I have tried looking in various places to see why icons aren't showing
>>>>   properly. Checked loads of log messages. Located the icons on the
>>>>   filesystem but for some reason the icons aren't loading. It is
>>>>   intermittent, for example sometimes the battery symbol shows and
>>>>   sometimes it doesn't.
>>>>
>>>>   A bigger problem is that sometimes the screen goes black but the
>>>>   laptop is still on, the keyboard is still responding but it's
>>>>   impossible to use. Sometimes this happens a few times in an hour.
>>>>   Sometimes it can be days between using it.
>>>>
>>>>   This is making my laptop pretty unusable. If there is anything I can
>>>>   do to investigate this further then please shout, happy to run all the
>>>>   commands and provide all the logs. I've attached a screenshot showing
>>>>   the issue in the settings panel but that isn't the only place this is
>>>>   happening.
>>>>
>>>>   ProblemType: Bug
>>>>   DistroRelease: Ubuntu 22.04
>>>>   Package: xorg 1:7.7+23ubuntu2
>>>>   ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
>>>>   Uname: Linux 5.19.0-43-generic x86_64
>>>>   ApportVersion: 2.20.11-0ubuntu82.5
>>>>   Architecture: amd64
>>>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>>>   CasperMD5CheckResult: unknown
>>>>   CompositorRunning: None
>>>>   CurrentDesktop: ubuntu:GNOME
>>>>   Date: Sat Jun 10 10:17:48 2023
>>>>   DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed,
>>>> re-reading
>>>>   DistroCodename: jammy
>>>>   DistroVariant: ubuntu
>>>>   ExtraDebuggingInterest: Yes, including running git bisection searches
>>>>   GraphicsCard:
>>>>Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev
>>>> 05) (prog-if 00 [VGA controller])
>>>>  Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d]
>>>>  Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d]
>>>>   InstallationDate: Installed on 2020-07-31 (1043 days ago)
>>>>   InstallationMedia: Ubun

Re: [Touch-packages] [Bug 2023436] Re: Icons are showing as no entry signs

[Andrew Perry]

I did some googling and fixed the gnome control centre  issue by running:
sudo /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders

Lots of other images aren't loading yet but I'll restart and see if that
addresses it

On Mon, 12 Jun 2023 at 19:37, Andrew Perry  wrote:

> This is the output:
>
> (gnome-control-center:9103): Gtk-WARNING **: 19:35:37.672: Could not load
> a pixbuf from /com/ubuntu/themes/Yaru-dark/3.0/assets/bullet-symbolic.svg.
> This may indicate that pixbuf loaders or the mime database could not be
> found.
>
> On Mon, 12 Jun 2023 at 09:31, Andrew Perry  wrote:
>
>> Thanks for the replies, you're right about it being a different bug.
>> Should have known better. Will post the results of the command for this bug
>> tonight.
>>
>> Kind regards,
>> Andrew
>>
>> On Mon, 12 Jun 2023, 08:45 Daniel van Vugt, <2023...@bugs.launchpad.net>
>> wrote:
>>
>>> The black screen issue you mention should be discussed elsewhere because
>>> each bug should only cover a single topic. But that's likely to be
>>> caused by the open source 'nouveau' driver. So please open the
>>> 'Additional Drivers' app to install a supported NVIDIA driver to avoid
>>> that.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/2023436
>>>
>>> Title:
>>>   Icons are showing as no entry signs
>>>
>>> Status in gtk+3.0 package in Ubuntu:
>>>   Incomplete
>>>
>>> Bug description:
>>>   I have tried looking in various places to see why icons aren't showing
>>>   properly. Checked loads of log messages. Located the icons on the
>>>   filesystem but for some reason the icons aren't loading. It is
>>>   intermittent, for example sometimes the battery symbol shows and
>>>   sometimes it doesn't.
>>>
>>>   A bigger problem is that sometimes the screen goes black but the
>>>   laptop is still on, the keyboard is still responding but it's
>>>   impossible to use. Sometimes this happens a few times in an hour.
>>>   Sometimes it can be days between using it.
>>>
>>>   This is making my laptop pretty unusable. If there is anything I can
>>>   do to investigate this further then please shout, happy to run all the
>>>   commands and provide all the logs. I've attached a screenshot showing
>>>   the issue in the settings panel but that isn't the only place this is
>>>   happening.
>>>
>>>   ProblemType: Bug
>>>   DistroRelease: Ubuntu 22.04
>>>   Package: xorg 1:7.7+23ubuntu2
>>>   ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
>>>   Uname: Linux 5.19.0-43-generic x86_64
>>>   ApportVersion: 2.20.11-0ubuntu82.5
>>>   Architecture: amd64
>>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>>   CasperMD5CheckResult: unknown
>>>   CompositorRunning: None
>>>   CurrentDesktop: ubuntu:GNOME
>>>   Date: Sat Jun 10 10:17:48 2023
>>>   DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed,
>>> re-reading
>>>   DistroCodename: jammy
>>>   DistroVariant: ubuntu
>>>   ExtraDebuggingInterest: Yes, including running git bisection searches
>>>   GraphicsCard:
>>>Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05)
>>> (prog-if 00 [VGA controller])
>>>  Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d]
>>>  Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d]
>>>   InstallationDate: Installed on 2020-07-31 (1043 days ago)
>>>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>>> (20200423)
>>>   MachineType: Dell Inc. XPS 15 9500
>>>   ProcEnviron:
>>>LANGUAGE=en_GB:en
>>>PATH=(custom, no user)
>>>XDG_RUNTIME_DIR=
>>>LANG=en_GB.UTF-8
>>>SHELL=/bin/bash
>>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic
>>> root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7
>>>   SourcePackage: xorg
>>>   Symptom: display
>>>   UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago)
>>>   dmi.bios.date: 03/16/2023
>>>   dmi.bios.release: 1.22
>>>   dmi.bios.vendor: Dell Inc.
>>>   dmi.bios.version: 1.22.0
>>>   dmi.board.name: 05XYW7
&g

Re: [Touch-packages] [Bug 2023436] Re: Icons are showing as no entry signs

[Andrew Perry]

This is the output:

(gnome-control-center:9103): Gtk-WARNING **: 19:35:37.672: Could not load a
pixbuf from /com/ubuntu/themes/Yaru-dark/3.0/assets/bullet-symbolic.svg.
This may indicate that pixbuf loaders or the mime database could not be
found.

On Mon, 12 Jun 2023 at 09:31, Andrew Perry  wrote:

> Thanks for the replies, you're right about it being a different bug.
> Should have known better. Will post the results of the command for this bug
> tonight.
>
> Kind regards,
> Andrew
>
> On Mon, 12 Jun 2023, 08:45 Daniel van Vugt, <2023...@bugs.launchpad.net>
> wrote:
>
>> The black screen issue you mention should be discussed elsewhere because
>> each bug should only cover a single topic. But that's likely to be
>> caused by the open source 'nouveau' driver. So please open the
>> 'Additional Drivers' app to install a supported NVIDIA driver to avoid
>> that.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/2023436
>>
>> Title:
>>   Icons are showing as no entry signs
>>
>> Status in gtk+3.0 package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   I have tried looking in various places to see why icons aren't showing
>>   properly. Checked loads of log messages. Located the icons on the
>>   filesystem but for some reason the icons aren't loading. It is
>>   intermittent, for example sometimes the battery symbol shows and
>>   sometimes it doesn't.
>>
>>   A bigger problem is that sometimes the screen goes black but the
>>   laptop is still on, the keyboard is still responding but it's
>>   impossible to use. Sometimes this happens a few times in an hour.
>>   Sometimes it can be days between using it.
>>
>>   This is making my laptop pretty unusable. If there is anything I can
>>   do to investigate this further then please shout, happy to run all the
>>   commands and provide all the logs. I've attached a screenshot showing
>>   the issue in the settings panel but that isn't the only place this is
>>   happening.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 22.04
>>   Package: xorg 1:7.7+23ubuntu2
>>   ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
>>   Uname: Linux 5.19.0-43-generic x86_64
>>   ApportVersion: 2.20.11-0ubuntu82.5
>>   Architecture: amd64
>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>   CasperMD5CheckResult: unknown
>>   CompositorRunning: None
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Sat Jun 10 10:17:48 2023
>>   DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed,
>> re-reading
>>   DistroCodename: jammy
>>   DistroVariant: ubuntu
>>   ExtraDebuggingInterest: Yes, including running git bisection searches
>>   GraphicsCard:
>>Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05)
>> (prog-if 00 [VGA controller])
>>  Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d]
>>  Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d]
>>   InstallationDate: Installed on 2020-07-31 (1043 days ago)
>>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>> (20200423)
>>   MachineType: Dell Inc. XPS 15 9500
>>   ProcEnviron:
>>LANGUAGE=en_GB:en
>>PATH=(custom, no user)
>>XDG_RUNTIME_DIR=
>>LANG=en_GB.UTF-8
>>SHELL=/bin/bash
>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic
>> root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7
>>   SourcePackage: xorg
>>   Symptom: display
>>   UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago)
>>   dmi.bios.date: 03/16/2023
>>   dmi.bios.release: 1.22
>>   dmi.bios.vendor: Dell Inc.
>>   dmi.bios.version: 1.22.0
>>   dmi.board.name: 05XYW7
>>   dmi.board.vendor: Dell Inc.
>>   dmi.board.version: A00
>>   dmi.chassis.type: 10
>>   dmi.chassis.vendor: Dell Inc.
>>   dmi.modalias:
>> dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D:
>>   dmi.product.family: XPS
>>   dmi.product.name: XPS 15 9500
>>   dmi.product.sku: 097D
>>   dmi.sys.vendor: Dell Inc.
>>   version.compiz: compiz N/A
>>   version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
>>   version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
>>   version.libgl1-mesa-glx: libgl1-mesa-g

Re: [Touch-packages] [Bug 2023436] Re: Icons are showing as no entry signs

[Andrew Perry]

Thanks for the replies, you're right about it being a different bug. Should
have known better. Will post the results of the command for this bug
tonight.

Kind regards,
Andrew

On Mon, 12 Jun 2023, 08:45 Daniel van Vugt, <2023...@bugs.launchpad.net>
wrote:

> The black screen issue you mention should be discussed elsewhere because
> each bug should only cover a single topic. But that's likely to be
> caused by the open source 'nouveau' driver. So please open the
> 'Additional Drivers' app to install a supported NVIDIA driver to avoid
> that.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2023436
>
> Title:
>   Icons are showing as no entry signs
>
> Status in gtk+3.0 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have tried looking in various places to see why icons aren't showing
>   properly. Checked loads of log messages. Located the icons on the
>   filesystem but for some reason the icons aren't loading. It is
>   intermittent, for example sometimes the battery symbol shows and
>   sometimes it doesn't.
>
>   A bigger problem is that sometimes the screen goes black but the
>   laptop is still on, the keyboard is still responding but it's
>   impossible to use. Sometimes this happens a few times in an hour.
>   Sometimes it can be days between using it.
>
>   This is making my laptop pretty unusable. If there is anything I can
>   do to investigate this further then please shout, happy to run all the
>   commands and provide all the logs. I've attached a screenshot showing
>   the issue in the settings panel but that isn't the only place this is
>   happening.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: xorg 1:7.7+23ubuntu2
>   ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
>   Uname: Linux 5.19.0-43-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.5
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: unknown
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Jun 10 10:17:48 2023
>   DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed,
> re-reading
>   DistroCodename: jammy
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, including running git bisection searches
>   GraphicsCard:
>Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05)
> (prog-if 00 [VGA controller])
>  Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d]
>  Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d]
>   InstallationDate: Installed on 2020-07-31 (1043 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: Dell Inc. XPS 15 9500
>   ProcEnviron:
>LANGUAGE=en_GB:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_GB.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic
> root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago)
>   dmi.bios.date: 03/16/2023
>   dmi.bios.release: 1.22
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.22.0
>   dmi.board.name: 05XYW7
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D:
>   dmi.product.family: XPS
>   dmi.product.name: XPS 15 9500
>   dmi.product.sku: 097D
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20210115-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.17-2build1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2023436/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed

[Touch-packages] [Bug 2020030] [NEW] System 76 Lemur Pro - Light Display Manager failed on boot

[Andrew Barge]

Public bug reported:

I have executed a ubuntu-bug lightdm as requested here:
https://discourse.ubuntubudgie.org/t/failed-to-start-light-display-manager/6709

In my case I did nano /etc/systemd/system/display-manager.service and
double checked Restart=Always was on (it was) and added RestartSec=0.5.
So far it’s booting every single time without issue.

It might be better to  include that in the config by default so less
people run into this issue.  Most of the people who were addressing this
ended up reinstalling Ubuntu Budgie and this fix can avoid that issue
entirely.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: lightdm 1.30.0-0ubuntu5 [modified: lib/systemd/system/lightdm.service]
Uname: Linux 6.2.6-76060206-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Wed May 17 21:50:52 2023
InstallationDate: Installed on 2022-09-21 (239 days ago)
InstallationMedia: Ubuntu-Budgie 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
LightdmConfig:
 [Seat:*]
 greeter-session=slick-greeter
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy third-party-packages

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

Title:
  System 76 Lemur Pro - Light Display Manager failed on boot

Status in lightdm package in Ubuntu:
  New

Bug description:
  I have executed a ubuntu-bug lightdm as requested here:
  
https://discourse.ubuntubudgie.org/t/failed-to-start-light-display-manager/6709

  In my case I did nano /etc/systemd/system/display-manager.service and
  double checked Restart=Always was on (it was) and added
  RestartSec=0.5. So far it’s booting every single time without issue.

  It might be better to  include that in the config by default so less
  people run into this issue.  Most of the people who were addressing
  this ended up reinstalling Ubuntu Budgie and this fix can avoid that
  issue entirely.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: lightdm 1.30.0-0ubuntu5 [modified: 
lib/systemd/system/lightdm.service]
  Uname: Linux 6.2.6-76060206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Wed May 17 21:50:52 2023
  InstallationDate: Installed on 2022-09-21 (239 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809.1)
  LightdmConfig:
   [Seat:*]
   greeter-session=slick-greeter
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1899218] Re: Incorrect warning from apparmor_parser on force complained profiles

[Andrew Lentvorski]

Also confirm.  I'm seeing the same error on an "apt upgrade":


Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing 
complain mode
Warning from /etc/apparmor.d (/etc/apparmor.d/usr.sbin.sssd line 60): Caching 
disabled for: 'usr.sbin.sssd' due to force complain
Setting up docker-buildx-plugin (0.10.4-1~ubuntu.22.04~jammy) ...
Setting up libsnmp40:amd64 (5.9.1+dfsg-1ubuntu2.6) ...

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

Title:
  Incorrect warning from apparmor_parser on force complained profiles

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  apparmor_parser on a force complained profile produces an incorrect
  warning message:

  $ sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd
  Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing 
complain mode
  Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd 
line 54): Warning failed to create cache: usr.sbin.sssd

  Even though not generating the cache at all is expected, the warning
  should describe caching is disabled for force complained profiles
  instead of failure to create it.

  $ lsb_release -rd
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10

  $ apt-cache policy apparmor
  apparmor:
    Installed: 3.0.0~beta1-0ubuntu6
    Candidate: 3.0.0~beta1-0ubuntu6
    Version table:
   *** 3.0.0~beta1-0ubuntu6 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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


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

[Touch-packages] [Bug 2009684] [NEW] package libgl1-mesa-dri 22.2.5-0ubuntu0.1 [modified: usr/share/drirc.d/00-mesa-defaults.conf] failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux

[Andrew]

Public bug reported:

apt dist-upgrade crashed

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1 [modified: 
usr/share/drirc.d/00-mesa-defaults.conf]
ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.85.12  Sat Jan 28 02:10:06 
UTC 2023
 GCC version:
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
Date: Wed Mar  8 12:48:25 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', 
which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
GraphicsCard:
 NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] [10de:2488] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Palit Microsystems Inc. GA104 [GeForce RTX 3070 Lite Hash Rate] 
[1569:f280]
InstallationDate: Installed on 2023-03-08 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: Micro-Star International Co., Ltd. MS-7D28
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=8a4a53bf-0539-4847-80b7-e688eea77975 ro quiet nomodeset
Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.20ubuntu2
 apt  2.5.6
SourcePackage: mesa
Title: package libgl1-mesa-dri 22.2.5-0ubuntu0.1 [modified: 
usr/share/drirc.d/00-mesa-defaults.conf] failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package 
libgl1-amber-dri:amd64 21.3.7-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/07/2022
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.90
dmi.board.asset.tag: Default string
dmi.board.name: MEG Z690 UNIFY (MS-7D28)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.90:bd11/07/2022:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D28:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ690UNIFY(MS-7D28):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7D28
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-package lunar single-occurrence ubuntu

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

Title:
  package libgl1-mesa-dri 22.2.5-0ubuntu0.1 [modified:
  usr/share/drirc.d/00-mesa-defaults.conf] failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which
  is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1

Status in mesa package in Ubuntu:
  New

Bug description:
  apt dist-upgrade crashed

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1 [modified: 
usr/share/drirc.d/00-mesa-defaults.conf]
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidi

[Touch-packages] [Bug 2006636] [NEW] Many Cyan Lines Cover Computer Screen

[Andrew Rossman]

Public bug reported:

bunch of cyan lines appearing on my screen rapidly, pretty sure its a
hardware issue but want to make sure the graphics drivers are up to
date.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb  8 13:34:44 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
InstallationDate: Installed on 2023-02-06 (2 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Dell Inc. Inspiron 5521
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0K08H3
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A07
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA:
dmi.product.family: 103C_5335KV
dmi.product.name: Inspiron 5521
dmi.product.sku: xxx123x#ABA
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  Many Cyan Lines Cover Computer Screen

Status in xorg package in Ubuntu:
  New

Bug description:
  bunch of cyan lines appearing on my screen rapidly, pretty sure its a
  hardware issue but want to make sure the graphics drivers are up to
  date.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  8 13:34:44 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
  InstallationDate: Installed on 2023-02-06 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. Inspiron 5521
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0K08H3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 5521
  dmi.product.sku: xxx123x#ABA
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubun

[Touch-packages] [Bug 2005112] [NEW] lvs --sort=devices does not sort properly

[andrew bezella]

Public bug reported:

Description:Ubuntu 22.04.1 LTS
Release:22.04

lvm2:
  Installed: 2.03.11-2.1ubuntu4
  Candidate: 2.03.11-2.1ubuntu4
  Version table:
 *** 2.03.11-2.1ubuntu4 500
500 http://apt-mirror.us.archive.org/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

expected output:
  Path   Devices  
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_meta /dev/md3(0)  
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_data /dev/md4(24576)  
  /dev/xenvg/577f8216-dc41-4a88-971c-f27e786325cf.disk0  /dev/md5(0)  
  /dev/archivevg/lvol0   /dev/md6(0)  
  /dev/archivevg/lvol1   /dev/md6(943719) 
  /dev/xenvg/2e63d553-8a4c-42c2-8b63-04589582cb66.disk0  /dev/md7(2048)   
  /dev/xenvg/4b754245-b9fb-4c74-baf5-6c660b133e62.disk0  /dev/md7(4096)   
  /dev/vg0/lvol0 /dev/md9(0)  
  /dev/vg0/lvol1 /dev/md11(0) 
  /dev/vg0/lvol2 /dev/md11(471860)

actual output is incorrect and inconsistent, apparently varying w/list of 
fields to display:
% sudo lvs -o lv_path,devices --sort=devices
  Path   Devices  
  /dev/archivevg/lvol0   /dev/md6(0)  
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_data /dev/md4(24576)  
  /dev/vg0/lvol1 /dev/md11(0) 
  /dev/xenvg/2e63d553-8a4c-42c2-8b63-04589582cb66.disk0  /dev/md7(2048)   
  /dev/xenvg/577f8216-dc41-4a88-971c-f27e786325cf.disk0  /dev/md5(0)  
  /dev/archivevg/lvol1   /dev/md6(943719) 
  /dev/vg0/lvol2 /dev/md11(471860)
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_meta /dev/md3(0)  
  /dev/xenvg/4b754245-b9fb-4c74-baf5-6c660b133e62.disk0  /dev/md7(4096)   
  /dev/vg0/lvol0 /dev/md9(0)
% sudo lvs -o lv_path,lv_size,devices --sort=devices
  Path   LSize   Devices
  
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_meta 128.00m 
/dev/md3(0)  
  /dev/vg0/lvol1   1.80t 
/dev/md11(0) 
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_data  16.00g 
/dev/md4(24576)  
  /dev/archivevg/lvol1 3.60t 
/dev/md6(943719) 
  /dev/vg0/lvol0   7.13t 
/dev/md9(0)  
  /dev/xenvg/577f8216-dc41-4a88-971c-f27e786325cf.disk01.80t 
/dev/md5(0)  
  /dev/archivevg/lvol0 3.60t 
/dev/md6(0)  
  /dev/xenvg/4b754245-b9fb-4c74-baf5-6c660b133e62.disk0   16.00g 
/dev/md7(4096)   
  /dev/vg0/lvol2 128.00g 
/dev/md11(471860)
  /dev/xenvg/2e63d553-8a4c-42c2-8b63-04589582cb66.disk08.00g 
/dev/md7(2048)

if memory serves, this worked as expected in xenial/16.04.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: lvm2 2.03.11-2.1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Feb  3 14:48:50 2023
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: lvm2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.lvm.lvm.conf: [modified]
mtime.conffile..etc.lvm.lvm.conf: 2023-02-02T13:01:26.465746

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


** Tags: amd64 apport-bug jammy

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

Title:
  lvs --sort=devices does not sort properly

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  lvm2:
Installed: 2.03.11-2.1ubuntu4
Candidate: 2.03.11-2.1ubuntu4
Version table:
   *** 2.03.11-2.1ubuntu4 500
  500 http://apt-mirror.us.archive.org/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  expected output:
Path   Devices  
/dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_meta /dev/md3(0)  
/dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_data /dev/md4(24576)  
/dev/xenvg/577f8216-dc41-4a88-971c-f27e786325cf.disk0  /dev/md5(0)  
/dev/archivevg/lvol0   /dev/md6(0)  
/dev/arc

[Touch-packages] [Bug 1955804] Re: make and make test fail

[Andrew G. Morgan]

Confused about this bug.

The first entry refers to Go package compilation failing for
libcap-2.32. It is not clear which version of golang is installed, but
the whole module support for Go has changed substantially since
libcap-2.32 was new. Modern golang does not work with that old version
of libcap. Please try libcap-2.66. A walk through of using it is
documented here:

https://sites.google.com/site/fullycapable/getting-started-with-go

The second comment in this bug has nothing to do with Go, but refers to
trying to build libcap-2.24 (which is yet older). The failure mode there
is because libattr is not installed on your system.

FWIW the need for `-lattr` was removed in libcap-2.25 via this commit.

https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=85f38a573fc47472ab792e813b6f6b6f0b1df112

Again the current libcap release is 2.66.

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

Title:
  make and make test fail

Status in libcap2 package in Ubuntu:
  New

Bug description:
  Hello,

  
  make and make test fail like the printscreen following : 

  CGO_LDFLAGS_ALLOW="-Wl,-wrap,.+" 
CGO_CFLAGS="-I/home/ubuntu/programs/libcap-2.32/libcap/include" 
CGO_LDFLAGS="-L/home/ubuntu/programs/libcap-2.32/libcap" 
GOPATH="/home/ubuntu/programs/libcap-2.32/go" go install libcap/psx
  go install: version is required when current directory is not in a module
Try 'go install libcap/psx@latest' to install the latest version
  make[1]: *** [Makefile:37 : pkg/linux_amd64/libcap/psx.a] Erreur 1
  make[1] : on quitte le répertoire « /home/ubuntu/programs/libcap-2.32/go »
  make: *** [Makefile:13 : all] Erreur 2
  root@ubuntu-ThinkPad-X250:/home/ubuntu/programs/libcap-2.32# go install 
libcap/psx@latest
  go install: libcap/psx@latest: malformed module path "libcap/psx": missing 
dot in first path element
  root@ubuntu-ThinkPad-X250:/home/ubuntu/programs/libcap-2.32# 

  thank you in advance to help myself fully install your program,

  Regards.

  
  Dorian ROSSE.

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


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

[Touch-packages] [Bug 1899103] Re: libpam-cap causes PAM applications to crash

[Andrew G. Morgan]

Had not heard about this specifically before. Some bug fixes to
pam_cap.so found by static analysis:

https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=954a5ce4fdf195e062909f2c921d8f915d2905b9

https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=552db8f4116df3fad4e4ebf90a9a05a77b9486fd

Perhaps they address this problem? The more recent of these two appeared
in libcap-2.50.

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

Title:
  libpam-cap causes PAM applications to crash

Status in libcap2 package in Ubuntu:
  Confirmed

Bug description:
  Install ocserv and setup for PAM authentication. On second connection,
  ocserv crashes due to a double free in PAM.

  Repro steps:
  1. Create Dockerfile that installs ocserv + libpam-cap
  ```
  FROM ubuntu:20.04

  RUN apt update && apt install -y ocserv libpam-cap && apt autoremove
  && apt clean

  COPY server-cert.pem /etc/ssl/ocserv_test.cert
  COPY server-key.pem /etc/ssl/ocserv_test.key
  COPY ca-cert.pem /etc/ssl/certs/ssl-cert-snakeoil.pem
  COPY ocserv.conf /etc/ocserv/ocserv.conf

  RUN useradd test
  RUN echo "test\ntest" | passwd test

  ENV MALLOC_CHECK_=3
  CMD ocserv -f -d 1
  ```

  2. Build container:
  ```
  sudo docker build -t ocserv:20.04 .
  ```

  3. Launch container:
  ```
  docker run -p 443:443/tcp -p 443:443/udp -it --rm --device /dev/net/tun 
--cap-add net_admin ocserv:20.04
  ```

  4. From another console, connect / disconnect:
  ```
  while true; do echo test | openconnect https://localhost -u test 
--passwd-on-stdin --servercert 
pin-sha256:qBLVTyoXiFdn+0pW+eSGqnVCEnMbLigVf5vAl1ZewW4= --background && sleep 2 
&& pkill openconnect && sleep 2;done
  ```

  5. ocserv crashes:
  free(): invalid pointer
  ocserv[8]: main: main-sec-mod-cmd.c:106: command socket for sec-mod closed
  ocserv[8]: main: main.c:1179: error in command from sec-mod
  ocserv[8]: main: termination request received; waiting for children to die

  For more details see:
  https://gitlab.com/openconnect/ocserv/-/issues/361

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


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

[Touch-packages] [Bug 1704416] Re: CAP_AUDIT_READ is not supported on Xenial

[Andrew G. Morgan]

This was fixed upstream in libcap-2.25 :

https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=9c3d89fbb9d819ade80b544f8a35f7b90c07cd14

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

Title:
  CAP_AUDIT_READ is not supported on Xenial

Status in libcap2 package in Ubuntu:
  New

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

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

  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

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

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

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

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


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

[Touch-packages] [Bug 1955804] Re: make and make test fail

[Andrew G. Morgan]

Is this still a problem with libcap-2.66 ?

https://git.kernel.org/pub/scm/libs/libcap/libcap.git/

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

Title:
  make and make test fail

Status in libcap2 package in Ubuntu:
  New

Bug description:
  Hello,

  
  make and make test fail like the printscreen following : 

  CGO_LDFLAGS_ALLOW="-Wl,-wrap,.+" 
CGO_CFLAGS="-I/home/ubuntu/programs/libcap-2.32/libcap/include" 
CGO_LDFLAGS="-L/home/ubuntu/programs/libcap-2.32/libcap" 
GOPATH="/home/ubuntu/programs/libcap-2.32/go" go install libcap/psx
  go install: version is required when current directory is not in a module
Try 'go install libcap/psx@latest' to install the latest version
  make[1]: *** [Makefile:37 : pkg/linux_amd64/libcap/psx.a] Erreur 1
  make[1] : on quitte le répertoire « /home/ubuntu/programs/libcap-2.32/go »
  make: *** [Makefile:13 : all] Erreur 2
  root@ubuntu-ThinkPad-X250:/home/ubuntu/programs/libcap-2.32# go install 
libcap/psx@latest
  go install: libcap/psx@latest: malformed module path "libcap/psx": missing 
dot in first path element
  root@ubuntu-ThinkPad-X250:/home/ubuntu/programs/libcap-2.32# 

  thank you in advance to help myself fully install your program,

  Regards.

  
  Dorian ROSSE.

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


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

[Touch-packages] [Bug 1700814] Re: Default capability of cap_setfcap+i should be set on setcap

[Andrew G. Morgan]

FWIW This used to be the default inside the libcap build tree, but the problems 
with the container defaults (eventually fixed with 
https://github.com/moby/moby/security/advisories/GHSA-2mm7-x5h6-5pvq
 ) changed my position on this:

https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=2b5f5635be6131d7e89b4c6244b29f32ebd163c1

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

Title:
  Default capability of cap_setfcap+i should be set on setcap

Status in libcap2 package in Ubuntu:
  New

Bug description:
  If I grant a user (via pam_cap) cap_setfcap+i, I would then expect
  them to be able to use setcap without sudo. setcap is not provided
  with any default file capabilities however, so either the user has to
  sudo, or I have to grant the setfcap capability to setcap with setcap.

  In my mind, it would be reasonable to grant setfcap+i to setcap by
  default on installation.

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


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

[Touch-packages] [Bug 1981488] [NEW] presistent reoccuring error message: wrapper-2.0

[Andrew Cochrane]

Public bug reported:

After an update there is a reoccuring system message saying there is an
error in wrapper-2.0 it doesn't seem to affect any of my processes,
except it steals cursor focus when it occurs.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-common-470 470.129.06-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-52-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jul 12 14:43:28 2022
ErrorMessage: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
InstallationDate: Installed on 2021-04-06 (462 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: initramfs-tools
Title: package nvidia-kernel-common-470 470.129.06-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  presistent reoccuring error message: wrapper-2.0

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After an update there is a reoccuring system message saying there is
  an error in wrapper-2.0 it doesn't seem to affect any of my processes,
  except it steals cursor focus when it occurs.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-common-470 470.129.06-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jul 12 14:43:28 2022
  ErrorMessage: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-04-06 (462 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package nvidia-kernel-common-470 470.129.06-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1964763] Re: QtChooser doesn't support qt6

[Andrew Hayzen]

I was going to request this change into Debian as well, but appears that
has already been attempted and was rejected due to "qtchooser is dead
upstream". https://salsa.debian.org/qt-kde-
team/qt/qtchooser/-/merge_requests/2

I wonder if the situation can be improved though as if you are trying to
use Qt 6 tooling in a container image then you need workarounds :-/

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

Title:
  QtChooser doesn't support qt6

Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  qtchooser doesn't run qt6 applications because it doesn't have a
  qt6.conf/6.conf file yet.

  In order to work, it must have two files `/usr/lib/x86_64-linux-
  gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux-
  gnu/qtchooser/6.conf` with this content:

  
  ```
  /usr/lib/qt6/bin
  /usr/lib/x86_64-linux-gnu
  ```

  Without it, lupdate, lrelease, and any other qt6 tools show this
  error: `could not find a Qt installation of ''`

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


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

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

[Andrew Ruthven]

Public bug reported:

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

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

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

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

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

Cheers,
Andrew

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

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

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

Status in cron package in Ubuntu:
  New

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

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

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

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

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

  Cheers,
  Andrew

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


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

[Touch-packages] [Bug 1956243] Re: Ping give socket error initially if IPv6 is disabled

[Andrew Welham]

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

Title:
  Ping give socket  error initially if IPv6 is disabled

Status in iputils package in Ubuntu:
  New

Bug description:
  With IpV6 enabled everything works well. However if you disable ipv6 by 
editing /etc/default/grub with the following entry
  GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
   then when you ping there is an initial socket error 

  ping localhost
  ping: socket: Address family not supported by protocol
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms

  
  however ping -4 works

  ping -4 localhost
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms

  so it looks like ping is trying ipv6 first and not detecting that its
  disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: iputils-ping 3:20210202-1build1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Jan  3 17:42:07 2022
  InstallationDate: Installed on 2022-01-03 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211029)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1961425] Re: 22.04: FTBFS due to test failure

[Andrew Cloke]

As 0.8.0-2ubuntu2 has fixed the build issue, marking this bug as "Fix Released".
Please feel free to revert if the issue is persisting.

** Changed in: capnproto (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: ubuntu-power-systems
   Status: New => Fix Released

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

Title:
  22.04: FTBFS due to test failure

Status in The Ubuntu-power-systems project:
  Fix Released
Status in capnproto package in Ubuntu:
  Fix Released

Bug description:
  Hi,
  capnproto 0.8.0-2ubuntu1 fails on ppc64el : 
  
https://launchpad.net/ubuntu/+source/capnproto/0.8.0-2ubuntu1/+build/23090234/+files/buildlog_ubuntu-jammy-ppc64el.capnproto_0.8.0-2ubuntu1_BUILDING.txt.gz

  Lowering optimization (O3->O2) level makes the failing test pass, for
  instance adding 

  export DEB_CXXFLAGS_MAINT_APPEND=-O1
  export DEB_CXXFLAGS_MAINT_STRIP=-O3

  in debian/rules.

  For the time being that can be the way to go as 0.9.1-2 from Debian 
Experimental
  builds fine on Jammy by default with O3.

  F.

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


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

[Touch-packages] [Bug 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

https://github.com/OSGeo/gdal/issues/5324 is a result of this and the
upstream https://github.com/libexpat/libexpat/issues/501

** Bug watch added: github.com/OSGeo/gdal/issues #5324
   https://github.com/OSGeo/gdal/issues/5324

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

Title:
  `libexpat1-dev` CMake configuration error

Status in Expat:
  Unknown
Status in expat package in Ubuntu:
  Confirmed

Bug description:
  Using the package provided by Ubuntu Impish results in the following
  CMake configuration error when trying to build OpenColorIO:

  ```
  […]
  CMake Error in src/OpenColorIO/CMakeLists.txt:
    Imported target "expat::expat" includes non-existent path

  "/usr/lib/include"

    in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

    * The path was deleted, renamed, or moved to another location.

    * An install or uninstall procedure did not complete successfully.

    * The installation package was faulty and references files it does not
    provide.
  […]
  ```

  This wasn't an issue in Ubuntu Hirsute as far as I can recall and is
  not an issue when using the ASWF-provided packages — CMake flag
  `-DOCIO_INSTALL_EXT_PACKAGES=ALL`. A patch is attached that allows
  OpenColorIO to build using system-provided packages.

  Further information in the related ticket in the OpenColorIO
  repository:
  
https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1415#issuecomment-1003826550

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


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

[Touch-packages] [Bug 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

** Bug watch added: github.com/libexpat/libexpat/issues #501
   https://github.com/libexpat/libexpat/issues/501

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

Title:
  `libexpat1-dev` CMake configuration error

Status in Expat:
  Unknown
Status in expat package in Ubuntu:
  Confirmed

Bug description:
  Using the package provided by Ubuntu Impish results in the following
  CMake configuration error when trying to build OpenColorIO:

  ```
  […]
  CMake Error in src/OpenColorIO/CMakeLists.txt:
    Imported target "expat::expat" includes non-existent path

  "/usr/lib/include"

    in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

    * The path was deleted, renamed, or moved to another location.

    * An install or uninstall procedure did not complete successfully.

    * The installation package was faulty and references files it does not
    provide.
  […]
  ```

  This wasn't an issue in Ubuntu Hirsute as far as I can recall and is
  not an issue when using the ASWF-provided packages — CMake flag
  `-DOCIO_INSTALL_EXT_PACKAGES=ALL`. A patch is attached that allows
  OpenColorIO to build using system-provided packages.

  Further information in the related ticket in the OpenColorIO
  repository:
  
https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1415#issuecomment-1003826550

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


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

[Touch-packages] [Bug 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

** Also affects: expat via
   https://github.com/libexpat/libexpat/issues/501
   Importance: Unknown
   Status: Unknown

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

Title:
  `libexpat1-dev` CMake configuration error

Status in Expat:
  Unknown
Status in expat package in Ubuntu:
  New

Bug description:
  Using the package provided by Ubuntu Impish results in the following
  CMake configuration error when trying to build OpenColorIO:

  ```
  […]
  CMake Error in src/OpenColorIO/CMakeLists.txt:
    Imported target "expat::expat" includes non-existent path

  "/usr/lib/include"

    in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

    * The path was deleted, renamed, or moved to another location.

    * An install or uninstall procedure did not complete successfully.

    * The installation package was faulty and references files it does not
    provide.
  […]
  ```

  This wasn't an issue in Ubuntu Hirsute as far as I can recall and is
  not an issue when using the ASWF-provided packages — CMake flag
  `-DOCIO_INSTALL_EXT_PACKAGES=ALL`. A patch is attached that allows
  OpenColorIO to build using system-provided packages.

  Further information in the related ticket in the OpenColorIO
  repository:
  
https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1415#issuecomment-1003826550

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


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

[Touch-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

[Andrew Platt]

Having a similar issue on my ASUS Zenbook UX434, also using the ALC294
as above, Kernel: 5.13.0-28-generic.

In my case after a reboot from my Windows 10 dual boot the audio out is
fine, but the microphone has very loud crackling which makes it
unusable. The problem isn't fixed by a reboot but after a full shutdown
and restart the problem seems to go away. Thanks to Hilikus for the
workaround!

Had an identical problem on Kubuntu 20.04 and now ZorinOS 16 - clearly
this issue isn't entirely fixed even with more recent kernel patches.

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  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.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  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/alsa-driver/+bug/1742852/+subscriptions


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

[Touch-packages] [Bug 1959512] [NEW] playing a video cause the video player to crash

[andrew g]

Public bug reported:

when attempting to play the vp8.webm file causes the Videos file to
crash

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgstreamer1.0-0 1.16.2-2
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 30 10:36:31 2022
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2022-01-30 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "vp8.webm"
   https://bugs.launchpad.net/bugs/1959512/+attachment/5558263/+files/vp8.webm

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

Title:
   playing a video cause the video player to crash

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  when attempting to play the vp8.webm file causes the Videos file to
  crash

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgstreamer1.0-0 1.16.2-2
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 30 10:36:31 2022
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2022-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1959512/+subscriptions


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

[Touch-packages] [Bug 1957024] Re: pam-mkhomedir does not honor private home directories

[Andrew Lowther]

Here is a demonstration as requested in Discourse.  These steps were run
on a stock image of Ubuntu Impish taken from https://cloud-
images.ubuntu.com/impish/current/.

Showing the inconsistent behavior of the default settings if the goal is
private home directories.  Both adduser and useradd create a home
directory that is private but pam_mkhomedir.so does not.

# enable pam_mkhomedir.so configuration
pam-auth-update --enable mkhomedir
# create a user with adduser that creates the home directory
adduser --disabled-password --gecos adduser homemadebyadduser
# create a user with useradd that creates the home directory
useradd --create-home homemadebyuseradd
# create a user with useradd that does *not* create the home directory so that 
pam_mkhomedir.so can create it
useradd --no-create-home homemadebymkhomedir
# trigger pam_mkhomedir.so to create the home directory
su - homemadebymkhomedir -c exit

The result is inconsistent permissions on the home directories.
root@ubuntu:~# ls -al /home
total 24
drwxr-xr-x  6 rootroot4096 Jan 11 03:27 .
drwxr-xr-x 19 rootroot4096 Jan 11 03:13 ..
drwxr-x---  2 homemadebyadduser   homemadebyadduser   4096 Jan 11 03:20 
homemadebyadduser
drwxr-xr-x  2 homemadebymkhomedir homemadebymkhomedir 4096 Jan 11 03:27 
homemadebymkhomedir
drwxr-x---  2 homemadebyuseradd   homemadebyuseradd   4096 Jan 11 03:23 
homemadebyuseradd
drwxr-x---  4 ubuntu  ubuntu  4096 Jan 11 03:15 ubuntu


Configuring pam_mkhomedir.so to be consistent with the other tools.

# update pam_mkhomedir.so configuration
sed -i -e "s/pam_mkhomedir.so$/pam_mkhomedir.so umask=0027/" 
/usr/share/pam-configs/mkhomedir
# enable mkhomedir again
pam-auth-update --enable mkhomedir
# create a user with useradd that does *not* create the home directory so that 
pam_mkhomedir.so can create it
useradd --no-create-home homemadebymkhomedirpatch
# trigger pam_mkhomedir.so to create the home directory
su - homemadebymkhomedirpatch -c exit

The result is the permissions are consistent with the other tools.
root@ubuntu:~# ls -l /home/
total 20
drwxr-x--- 2 homemadebyadduserhomemadebyadduser4096 Jan 11 
03:20 homemadebyadduser
drwxr-xr-x 2 homemadebymkhomedir  homemadebymkhomedir  4096 Jan 11 
03:27 homemadebymkhomedir
drwxr-x--- 2 homemadebymkhomedirpatch homemadebymkhomedirpatch 4096 Jan 11 
03:36 homemadebymkhomedirpatch
drwxr-x--- 2 homemadebyuseraddhomemadebyuseradd4096 Jan 11 
03:23 homemadebyuseradd
drwxr-x--- 4 ubuntu   ubuntu   4096 Jan 11 
03:15 ubuntu

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

Title:
  pam-mkhomedir does not honor private home directories

Status in pam package in Ubuntu:
  New

Bug description:
  As reported in https://discourse.ubuntu.com/t/private-home-
  directories-for-ubuntu-21-04-onwards/19533/13:

  A common situation is to have a central set of users (e.g. in LDAP)
  and use pam_mkhomedir.so to create the home directory when the user
  first logs in.

  These changes do not cover this situation. The default configuration
  of pam_mkhomedir.so will result in a home directory created with 0755
  permissions.

  To make pam_mkhomedir.so create a home directory by default with
  permissions consistent with the other tools then a umask argument can
  be added to the pam_mkhomedir.so module in the file /usr/share/pam-
  configs/mkhomedir. I believe this would have to be done before
  enabling the module. The file is part of the libpam-modules package.

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


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

[Touch-packages] [Bug 1956243] [NEW] Ping give socket error initially if IPv6 is disabled

[Andrew Welham]

Public bug reported:

With IpV6 enabled everything works well. However if you disable ipv6 by editing 
/etc/default/grub with the following entry
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
 then when you ping there is an initial socket error 

ping localhost
ping: socket: Address family not supported by protocol
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms


however ping -4 works

ping -4 localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms

so it looks like ping is trying ipv6 first and not detecting that its
disabled.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: iputils-ping 3:20210202-1build1
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Jan  3 17:42:07 2022
InstallationDate: Installed on 2022-01-03 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211029)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy third-party-packages uec-images

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

Title:
  Ping give socket  error initially if IPv6 is disabled

Status in iputils package in Ubuntu:
  New

Bug description:
  With IpV6 enabled everything works well. However if you disable ipv6 by 
editing /etc/default/grub with the following entry
  GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
   then when you ping there is an initial socket error 

  ping localhost
  ping: socket: Address family not supported by protocol
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms

  
  however ping -4 works

  ping -4 localhost
  PING localhost (127.0.0.1) 56(84) bytes of data.
  64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms
  64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms

  so it looks like ping is trying ipv6 first and not detecting that its
  disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: iputils-ping 3:20210202-1build1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Jan  3 17:42:07 2022
  InstallationDate: Installed on 2022-01-03 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211029)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1953116] [NEW] Mouse not staying powered

[Andrew]

Public bug reported:

Mouse receives power via USB when plugged in, immediately loses it.
Mouse on other devices, USB port provides power to other mice.

Manufacturer: Microsoft  
Model: Microsoft Ergonomic Mouse (Wired)
Connection: USB
Mechanism: Optical
Buttons: 4 Buttons + 1 Scrollwheel

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151
Uname: Linux 5.4.0-91-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  3 00:14:13 2021
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:0810]
InstallationDate: Installed on 2021-11-01 (32 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic 
root=UUID=e3adb636-cdf3-436a-8963-358dfa8e0a4e ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 05/15/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 0D65FD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0D65FD:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Mouse not staying powered

Status in xorg package in Ubuntu:
  New

Bug description:
  Mouse receives power via USB when plugged in, immediately loses it.
  Mouse on other devices, USB port provides power to other mice.

  Manufacturer: Microsoft  
  Model: Microsoft Ergonomic Mouse (Wired)
  Connection: USB
  Mechanism: Optical
  Buttons: 4 Buttons + 1 Scrollwheel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  3 00:14:13 2021
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2021-11-01 (32 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic 
root=UUID=e3adb636-cdf3-436a-8963-358dfa8e0a4e ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 0D65FD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0D65FD:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  versio

[Touch-packages] [Bug 1949909] Re: Bluetooth crashes on resume from suspend

[Andrew Marshall]

Hi, apologies if bluez is not the appropriate package. I have followed
the above instructions in an case.

1. No crash files present.

2. The following problems were reported on errors.ubuntu.com

https://errors.ubuntu.com/oops/feac943a-8847-11eb-9538-fa163ee63de6
https://errors.ubuntu.com/oops/7f383282-8841-11eb-9347-fa163e6cac46
https://errors.ubuntu.com/oops/414874ba-40fd-11e9-90bf-fa163e6cac46
https://errors.ubuntu.com/oops/6c93da58-3552-11e9-9eff-fa163e102db1

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

Title:
  Bluetooth crashes on resume from suspend

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Crash on resume from suspend. The following messages appear and the
  computer stops responding:

  ```
  [   26.227264] Bluetooth: hci0: Reading supported features failed (-16)
  [   26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask 
failed (-95)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  4 22:50:23 2021
  InstallationDate: Installed on 2021-09-16 (49 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1949909] [NEW] bluetooth crashes on resume from suspend

[Andrew Marshall]

Public bug reported:

Crash on resume from suspend. The following messages appear and the
computer stops responding:

```
[   26.227264] Bluetooth: hci0: Reading supported features failed (-16)
[   26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask 
failed (-95)
```

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez (not installed)
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  4 22:50:23 2021
InstallationDate: Installed on 2021-09-16 (49 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  bluetooth crashes on resume from suspend

Status in bluez package in Ubuntu:
  New

Bug description:
  Crash on resume from suspend. The following messages appear and the
  computer stops responding:

  ```
  [   26.227264] Bluetooth: hci0: Reading supported features failed (-16)
  [   26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask 
failed (-95)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  4 22:50:23 2021
  InstallationDate: Installed on 2021-09-16 (49 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1947526] [NEW] can't run associated docker-compose

[Andrew deVillier]

Public bug reported:

I can't seem to get apparmor to run at all, even sudo rm and sudo
restart in the /etc/init.d/apparmor

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apparmor 2.13.3-7ubuntu5.1
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 17 17:56:59 2021
InstallationDate: Installed on 2021-08-31 (47 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=ca77035a-d2b3-4803-a4e1-333e95d847fb ro quiet splash
SourcePackage: apparmor
Syslog:
 
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.abstractions.mysql: [deleted]
modified.conffile..etc.apparmor.parser.conf: [deleted]

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


** Tags: amd64 apport-bug focal

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

Title:
  can't run associated docker-compose

Status in apparmor package in Ubuntu:
  New

Bug description:
  I can't seem to get apparmor to run at all, even sudo rm and sudo
  restart in the /etc/init.d/apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu5.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 17 17:56:59 2021
  InstallationDate: Installed on 2021-08-31 (47 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=ca77035a-d2b3-4803-a4e1-333e95d847fb ro quiet splash
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.abstractions.mysql: [deleted]
  modified.conffile..etc.apparmor.parser.conf: [deleted]

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


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

[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

[Andrew Enderson]

While trouble shooting something else, I used the Driver Manager in
kubuntu System Settings (which uses Additional Drivers) to uninstall the
nvidia driver (nvidia-driver-390). After finishing the trouble shooting,
I attempted to reinstall the nvidia driver via Additional Drivers, and
I'm getting this error as well.

After seeing message #1, I also attempted to launched the Discover
package manager, and Discover is reporting the error as well: Cannot
refresh cache whilst offline.

I've recently run sudo apt update && sudo apt full-upgrade, so the
system appears to be up to date.

Distributor ID: Ubuntu
Description:Ubuntu Impish Indri (development branch)
Release:21.10
Codename:   impish

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


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

[Touch-packages] [Bug 1943312] Re: dependency problems of version 3.4.2-1ubuntu3

[Andrew]

It's already in repository

libffi8/impish-proposed 3.4.2-1ubuntu4 amd64 [can be updated from: 
3.4.2-1ubuntu3]
  Foreign Function Interface library runtime

libffi8ubuntu1/hirsute,impish 3.4~20200819gead65ca871-0ubuntu5 amd64
  Foreign Function Interface library runtime

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

Title:
  dependency problems of version 3.4.2-1ubuntu3

Status in libffi package in Ubuntu:
  Fix Released

Bug description:
  Have both libffi8ubuntu1:amd64 and libffi8ubuntu1:i386 installed
  previously. Got these after upgrading to 3.4.2-1ubuntu3

  dpkg: dependency problems prevent configuration of libffi8:amd64:
   libffi8:i386 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:amd64 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libffi8:i386:
   libffi8:amd64 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:i386 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:i386 (--configure):
   dependency problems - leaving unconfigured

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


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

[Touch-packages] [Bug 1943312] Re: dependency problems of version 3.4.2-1ubuntu3

[Andrew]

I'm newby in this. Can you write actions by steps?

for d in libffi8*.deb; do
  dpkg-deb -x $d $d.dir;
  dpkg-deb -e $d $d.dir/DEBIAN;
  sed -i 's/Breaks: libffi8ubuntu1/Breaks: libffi8ubuntu1 (<= 
3.4~20200819gead65ca871-0ubuntu5)/' $d/DEBIAN/control;
  dpkg-deb -b $d.dir $d;
done

Is it script?

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

Title:
  dependency problems of version 3.4.2-1ubuntu3

Status in libffi package in Ubuntu:
  Confirmed

Bug description:
  Have both libffi8ubuntu1:amd64 and libffi8ubuntu1:i386 installed
  previously. Got these after upgrading to 3.4.2-1ubuntu3

  dpkg: dependency problems prevent configuration of libffi8:amd64:
   libffi8:i386 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:amd64 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libffi8:i386:
   libffi8:amd64 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:i386 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:i386 (--configure):
   dependency problems - leaving unconfigured

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


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

[Touch-packages] [Bug 1943312] Re: dependency problems of version 3.4.2-1ubuntu3

[Andrew]

Replace Breaks: libffi8ubuntu1 with Breaks: libffi8ubuntu1 (<=
3.4~20200819gead65ca871-0ubuntu5) doesn't help. Bug still present.

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

Title:
  dependency problems of version 3.4.2-1ubuntu3

Status in libffi package in Ubuntu:
  Confirmed

Bug description:
  Have both libffi8ubuntu1:amd64 and libffi8ubuntu1:i386 installed
  previously. Got these after upgrading to 3.4.2-1ubuntu3

  dpkg: dependency problems prevent configuration of libffi8:amd64:
   libffi8:i386 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:amd64 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libffi8:i386:
   libffi8:amd64 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:i386 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:i386 (--configure):
   dependency problems - leaving unconfigured

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


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

[Touch-packages] [Bug 1937914] [NEW] Laptop Monitor Turns off During Startup

[Andrew White]

Public bug reported:

While starting the my laptop

(Computer Model: HP Probook 450 G6
ProdID 5YH15UT#ABA 
Memory: 15.5 GB
Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8
Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2)
Disk Capacity: 256.1 GB) 

which runs

(OS Name: Ubuntu 20.04.2 LTS
OS Type: 64-bit
GNOME Version: 3.36.8
Windowing System: X11)

the monitor turns off as soon as Ubuntu loads. The OS loads as normal
and my external monitor still works, but my laptop monitor does not. I
was able to fix the problem by pressing ESC as soon as the HP logo
appears during start-up, then selecting "Advanced Ubuntu Options", then
choosing an older version of Ubuntu (currently that's ...5.4.0-48...,
while I believe the latest version is ...5.8.0-66...).

It seems clear that this problem is caused by a bug that was introduced
in one of the more recent updates (...5.8.0-59..., maybe?). I am not at
all sure that the problem is in xorg; the package identification webpage
just suggested that, if the monitor is blank when I would expect to see
the Ubuntu logo during startup, then I should say that the relevant
package is xorg.

I am more than happy to run additional diagnostics that you would
recommend if that would help you diagnose and fix the problem.

Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 24 14:28:51 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) 
[103c:8538]
   Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:8542]
InstallationDate: Installed on 2021-07-06 (17 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 06cb:00b7 Synaptics, Inc. 
 Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera
 Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Bluetooth Radio 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ProBook 450 G6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8bde40df-a693-4c3a-b5be-05611212add4 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/27/2020
dmi.bios.vendor: HP
dmi.bios.version: R71 Ver. 01.11.01
dmi.board.name: 8538
dmi.board.vendor: HP
dmi.board.version: KBC Version 51.2A.00
dmi.chassis.asset.tag: 5CD9308H3X
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 450 G6
dmi.product.sku: 5YH15UT#ABA
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu

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

Title:
  Laptop Monitor Turns off During Startup

Status in xorg package in Ubuntu:
  New

Bug description:
  While starting the my laptop

  (Computer Model: HP Probook 450 G6
  ProdID 5YH15UT#ABA 
  Memory: 15.5 GB
  Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8
  Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2)
  Disk Capacity: 256.1 GB) 

  which runs

  (OS Name: Ubuntu 20.04.2 LTS
  OS Type: 64-bit
  GNOME Version: 3.36.8
  Windowing System: X11)

  the monitor turns off as soon as Ubuntu loads. The OS loads as normal
  and my external monitor still works, but my laptop monitor does not. I
  was able to fix the problem by pressing ESC as soon as the HP logo
  appears during start-up, then selecting "Advanced Ubuntu Options",
  then choosing an older version of Ubuntu (currently that's
  ...5.4.0-

[Touch-packages] [Bug 1875796] Re: HP Envy 5530 printer/scanner does not work

[Andrew]

I have one printer.  It is a HP Envy 5530.  I'm experiencing multiple issues.  
Sometimes CUPS finds printers, sometimes it doesn't.  It auto-adds printers 
randomly.  It auto-deletes printers randomly.  One day the printer works, the 
next it does not.

Also seeing these errors in syslog:
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, 
iface=0, altset=1, index=3
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on 
interface=0 ret=0
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface 
7/1/4: Device or resource busy
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, 
iface=3, altset=0, index=9
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on 
interface=3 ret=0
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface 
ff/4/1: Device or resource busy
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, 
iface=0, altset=0, index=11
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on 
interface=0 ret=0
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface 
ff/cc/0: Device or resource busy
Jun  9 12:42:14 yellow hp[34756]: prnt/backend/hp.c 825: INFO: open device 
failed stat=21: hp:/usb/ENVY_5530_series?serial=CN57A5636Z05XT; will retry in 
30 seconds...


** Attachment added: "Screenshot of duplicate printers in CUPS Find New 
Printers."
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1875796/+attachment/5503675/+files/screenshot-127.0.0.1_631-2021.06.09-12_38_33%281%29.png

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

Title:
  HP Envy 5530 printer/scanner does not work

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 20.04 LTS
  see troubleshoot.txt please

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 08:15:00 2020
  InstallationDate: Installed on 2020-04-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat:
   device for ENVY_5530_series_CN4A5310HJ067B_: 
implicitclass://ENVY_5530_series_CN4A5310HJ067B_/
   device for HP-ENVY-5530-series: 
hp:/usb/ENVY_5530_series?serial=CN4A5310HJ067B
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver
   Bus 001 Device 003: ID 03f0:c311 HP, Inc ENVY 5530 series
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-ENVY-5530-series.ppd', 
'/etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP-ENVY-5530-series.ppd: Permission denied
   grep: /etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd: Permission denied
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=77c5fdfc-4b0d-48ce-93d9-8aba51f17f9b ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

[Andrew Somerville]

Another confirmation for the 9i.

After set-verb.sh script my bass speaker is working.

Thanks Hui Wang! You're such a helpful person. I've heard you've managed
to fix a bunch of these, where people would just be frustrated for
months and years without you.

If you're ever in Pittsburgh, I'll buy you a beer or a dinner or
whatever!

Thanks again!

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

[Andrew Somerville]

@hui.wang is my hero!

I can't wait to test this when I get home tonight!

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1928590] [NEW] slow pc resposnisivnes when using multple programs

[andrew g]

Public bug reported:

sometimes when using multaple programs on Ubuntu 21 it causes some parts
of Ubuntu to freeze up.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 16 11:27:05 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
InstallationDate: Installed on 2021-05-14 (2 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Hewlett-Packard HP 15 TS Notebook PC
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/24/2014
dmi.bios.release: 15.22
dmi.bios.vendor: Insyde
dmi.bios.version: F.16
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2211
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 86.26
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 86.26
dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 15 TS Notebook PC
dmi.product.sku: G9D75UA#ABA
dmi.product.version: 097412405F0620180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute performance ubuntu wayland-session

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

Title:
  slow pc resposnisivnes when using multple programs

Status in xorg package in Ubuntu:
  New

Bug description:
  sometimes when using multaple programs on Ubuntu 21 it causes some
  parts of Ubuntu to freeze up.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 11:27:05 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
  InstallationDate: Installed on 2021-05-14 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard HP 15 TS Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2014
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 86.26
  dmi.modalias: 
dm

[Touch-packages] [Bug 1928475] [NEW] Xorg freeze when booting up

[andrew g]

Public bug reported:

when booting up Ubuntu 21 it hangs for a few minutes then it becomes
responsive it should not hang

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 14 10:42:48 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: I don't know
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
InstallationDate: Installed on 2021-05-14 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Hewlett-Packard HP 15 TS Notebook PC
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/24/2014
dmi.bios.release: 15.22
dmi.bios.vendor: Insyde
dmi.bios.version: F.16
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2211
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 86.26
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 86.26
dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 15 TS Notebook PC
dmi.product.sku: G9D75UA#ABA
dmi.product.version: 097412405F0620180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug freeze hirsute ubuntu wayland-session

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

Title:
  Xorg freeze when booting up

Status in xorg package in Ubuntu:
  New

Bug description:
  when booting up Ubuntu 21 it hangs for a few minutes then it becomes
  responsive it should not hang

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 14 10:42:48 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
  InstallationDate: Installed on 2021-05-14 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard HP 15 TS Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2014
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.ve

[Touch-packages] [Bug 1928406] [NEW] [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume

[andrew g]

Public bug reported:

speaker audio is low compared to windows 10 the sound needs to be better
optimized im using ubuntu 21 it should sound the same as in windows 10

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  familypc   1345 F pulseaudio
 /dev/snd/controlC1:  familypc   1345 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May 13 21:31:32 2021
InstallationDate: Installed on 2021-05-14 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: High background noise, or volume is too low
Title: [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background 
noise or low volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/24/2014
dmi.bios.release: 15.22
dmi.bios.vendor: Insyde
dmi.bios.version: F.16
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2211
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 86.26
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 86.26
dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 15 TS Notebook PC
dmi.product.sku: G9D75UA#ABA
dmi.product.version: 097412405F0620180
dmi.sys.vendor: Hewlett-Packard

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


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

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

Title:
  [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background
  noise or low volume

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  speaker audio is low compared to windows 10 the sound needs to be
  better optimized im using ubuntu 21 it should sound the same as in
  windows 10

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  familypc   1345 F pulseaudio
   /dev/snd/controlC1:  familypc   1345 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 13 21:31:32 2021
  InstallationDate: Installed on 2021-05-14 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2014
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 86.26
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 TS Notebook PC
  dmi.product.sku: G9D75UA#ABA
  dmi.product.version: 097412405F0620180
  dmi.sys.vendor: Hewlett-Packard

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

[Touch-packages] [Bug 1001035] Re: lightdm uses a hardcoded path to .xsession-errors, please make it configurable

[Andrew]

Any update on this? I'd love to move xsession-errors file out of my SSD
to minimize writes.

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

Title:
  lightdm uses a hardcoded path to .xsession-errors, please make it
  configurable

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  LightDM uses always $HOME/.xsession-errors as the log file because is
  harcoded in xsession.c. But sometimes you want to use a logfile
  outside your $HOME, suposse your $HOME is in an SSD and you want to
  minimize writes, so you want to put it in /tmp/${USER}_xsession-errors
  for example. If you try to make a $HOME/.xsession_errors ->
  /tmp/{$USER}_xsession-errors symlink to cheat LightDM, then LightDM
  will recreate the $HOME/.xsession_errors file and the hack will not
  work.

  LightDM _always_ recreates $HOME/.xsession_errors and you can't change
  it without recompiling. So, I think this log file needs to be
  configurable, or at least preserve the symlink if one is present.

  Ubuntu 12.04 LTS
  LightDM 1.2.1-0ubuntu1

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

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

[Touch-packages] [Bug 1684755] Re: Missing dependency to libtxc-dxtn-s2tc:amd64

[Andrew Hayzen]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

The package libtxc-dxtn-s2tc has been removed from later versions of
Ubuntu, therefore I am going to mark this bug as invalid for Steam.

** Changed in: steam (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Missing dependency to libtxc-dxtn-s2tc:amd64

Status in mesa package in Ubuntu:
  New
Status in steam package in Ubuntu:
  Invalid

Bug description:
  Steam is missing a dependency to libtxc-dxtn-s2tc:amd64

  How to reproduce:
  - Install steam from the Ubuntu repositories
  - Use the mesa drivers
  - Download a game that requires GL_EXT_TEXTURE_COMPRESSION_S3TC (e.g. Dota 2)
  - Steam throws an error on game start

  Workaround:
  - Install libtxc-dxtn-s2tc:amd64

  https://github.com/ValveSoftware/Dota-2/issues/1213

  Release: Ubuntu 17.04
  Package: steam:i386 (1:1.0.0.54+repack-2ubuntu5)

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

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

[Touch-packages] [Bug 1898547] Re: neutron-linuxbridge-agent fails to start with iptables 1.8.5

[Andrew Cloke]

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  neutron-linuxbridge-agent fails to start with iptables 1.8.5

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in iptables package in Ubuntu:
  Fix Released
Status in neutron package in Ubuntu:
  Invalid
Status in iptables source package in Groovy:
  Fix Released
Status in neutron source package in Groovy:
  Invalid
Status in iptables source package in Hirsute:
  Fix Released
Status in neutron source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  With iptables 1.8.5 neutron-linuxbridge-agent fails to properly start.

  The log file shows many errors like:

  2020-10-05 10:20:37.998 551 ERROR
  neutron.plugins.ml2.drivers.agent._common_agent ; Stdout: ; Stderr:
  iptables-restore: line 29 failed

  This can be demonstrated with a simple test case:

  iptables-restore 

[Touch-packages] [Bug 1898547] Re: neutron-linuxbridge-agent fails to start with iptables 1.8.5

[Andrew McLeod]

I've tested this (s390x, groovy) and im able to launch an instance with
the specific version of iptables mentioned above

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

Title:
  neutron-linuxbridge-agent fails to start with iptables 1.8.5

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in iptables package in Ubuntu:
  Fix Committed
Status in neutron package in Ubuntu:
  Invalid
Status in iptables source package in Groovy:
  Fix Committed
Status in neutron source package in Groovy:
  Invalid
Status in iptables source package in Hirsute:
  Fix Committed
Status in neutron source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  With iptables 1.8.5 neutron-linuxbridge-agent fails to properly start.

  The log file shows many errors like:

  2020-10-05 10:20:37.998 551 ERROR
  neutron.plugins.ml2.drivers.agent._common_agent ; Stdout: ; Stderr:
  iptables-restore: line 29 failed

  This can be demonstrated with a simple test case:

  iptables-restore 

[Touch-packages] [Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15

[Andrew Cloke]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

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

Title:
  [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on
  z15

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  Description:   zlib: inflateSyncPoint() returns an incorrect result on z15
  Symptom:   Certain rsync builds fail with "error in rsync protocol data
 stream" on z15.
  Problem:   inflateSyncPoint() does not take into account the hardware
 compression state and returns an incorrect result.
  Solution:  Make inflateSyncPoint() fail if the hardware compression is on.
 The hardware does not provide enough information in order to
 implement this function.
  Reproduction:  z15 only: printf 1 >1 && rsync -z 1 2

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

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

[Touch-packages] [Bug 1544251] Re: mount ignores exec option for 'users' mounts

[Andrew Kay]

same bug in 18.04LTS, it seems

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

Title:
  mount ignores exec option for 'users' mounts

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  New

Bug description:
  The version of 'mount' included in Ubuntu 14.04 LTS and 12.04 LTS has
  a bug wherein the 'exec' option in /etc/fstab is ignored on mounts
  with the 'user' or 'users' options when they are mounted by root.  For
  example:

  $ grep 48tb2d /etc/fstab
  labdisk.site.com:/Public4 /mnt/lab_48tb2d nfs users,exec,nosuid   
0 0
  $ sudo mount /mnt/lab_48tb2d
  $ mount | grep 48tb2d
  labdisk.site.com:/Public4 on /mnt/lab_48tb2d type nfs 
(rw,nosuid,nodev,noexec,addr=172.16.222.158)
  $ umount /mnt/lab_48tb2d
  $ mount /mnt/lab_48tb2d
  $ mount | grep 48tb2d
  labdisk.site.com:/Public4 on /mnt/lab_48tb2d type nfs 
(rw,nosuid,nodev,addr=172.16.222.158)

  This bug was fixed upstream several years ago and I believe therefore doesn't 
affect 15.10, but seems not to have made it into the current LTS releases of 
ubuntu.
  
https://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/mount/mount.c?id=a4c0cc75ff9744299f108c259efab1bd30c8007a
  https://bugzilla.redhat.com/show_bug.cgi?id=769636

  System info: Ubuntu 14.04.3 LTS, util-linux 2.20.1-5.1ubuntu20.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1544251/+subscriptions

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

[Touch-packages] [Bug 1896133] [NEW] [Audio Playback] right channel attenuated after random length of time

[Andrew Scott]

Public bug reported:

After playing sound for a while (minutes, not seconds), the right
channel will become attenuated.

Restoring balance can be done by unplugging the headphones (from the
built-in sound card) or disconnecting the external DAC and reconnecting
it.

Balance can be restored by altering balance in pavucontrol, but if you
balance by increasing the right side volume, it introduces a lot of
distortion.

Same behavior observed using both the internal sound device as well as
the Sound Blaster USB sound device, so it's in the mixing software
somewhere.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 17 14:33:43 2020
InstallationDate: Installed on 2020-07-10 (69 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: SoundBlaster MP3+ - Sound Blaster MP3+
Symptom_PulseAudioLog:
 Sep 15 15:45:31 vmhost01 dbus-daemon[1765]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.29' (uid=125 pid=2024 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
 Sep 15 15:45:32 vmhost01 pulseaudio[2024]: No UCM verb is valid for hw:0
 Sep 15 15:45:33 vmhost01 pulseaudio[2024]: No UCM verb is valid for hw:2
 Sep 15 15:45:34 vmhost01 dbus-daemon[1765]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.45' 
(uid=125 pid=2024 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
 Sep 15 19:01:54 vmhost01 dbus-daemon[1765]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.114' 
(uid=1000 pid=4820 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
Symptom_Type: Sound works for a while, then breaks
Title: [USB-Audio - Sound Blaster MP3+, playback] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2901
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX B450-F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2901:bd10/16/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal

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

Title:
  [Audio Playback] right channel attenuated after random length of time

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After playing sound for a while (minutes, not seconds), the right
  channel will become attenuated.

  Restoring balance can be done by unplugging the headphones (from the
  built-in sound card) or disconnecting the external DAC and
  reconnecting it.

  Balance can be restored by altering balance in pavucontrol, but if you
  balance by increasing the right side volume, it introduces a lot of
  distortion.

  Same behavior observed using both the internal sound device as well as
  the Sound Blaster USB sound device, so it's in the mixing software
  somewhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 17 14:33:43 2020
  InstallationDate: Installed on 2020-07-10 (69 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: SoundBlaster MP3+ - Sound Blaster MP3+
  Symptom_PulseAudioLog:
   Sep 15 15:45:31 vmhost01 dbus-daemon[

[Touch-packages] [Bug 1882494] Re: [UBUNTU 20.04] zlib not working on all s390x systems configurations

[Andrew Cloke]

@heinz-werner_seeck, this has been scheduled into the relevant team's current 
2-weekly cycle. As usual we'll share progress and updates in this ticket.
Thanks.

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

Title:
  [UBUNTU 20.04] zlib not working on all s390x systems configurations

Status in Ubuntu on IBM z Systems:
  Triaged
Status in zlib package in Ubuntu:
  New
Status in zlib source package in Eoan:
  Won't Fix
Status in zlib source package in Focal:
  New
Status in zlib source package in Groovy:
  New

Bug description:
  Pull request (https://github.com/madler/zlib/pull/410) and tagged
  https://github.com/iii-i/zlib/tree/dfltcc-20200511.

  The new code contains the following improvements:
  * Added support for switching between software and hardware compression.
  * Added --dfltcc configure flag (the old way of building it still works).

  Switching between software and hardware compression is not simply a
  nice-to-have feature, but is actually required by Java - that's why we
  are requesting an update.

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

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

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

22 hours no issues
# systemctl status isc-dhcp-server
● isc-dhcp-server.service - ISC DHCP IPv4 server
 Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Sun 2020-08-16 09:43:12 BST; 22h ago
   Docs: man:dhcpd(8)
   Main PID: 730 (dhcpd)
  Tasks: 4 (limit: 9571)
 Memory: 10.9M
 CGroup: /system.slice/isc-dhcp-server.service
 └─730 dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf

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

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode as follows:
     Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/
     Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/
  2) Run dhcpd as follows in both machine(s)

  # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4

  3) Leave the cluster running for a long (2h) period until the
  crash/race condition is reproduced.

  [REGRESSION POTENTIAL]

  * The fix will prevent the assertion to happen in the dispatch_send
  path, later versions of isch-dhcp upstream lack this logic and entirely 
removed the existence of this flag. Therefore, removing the need for this
  assertion at process_fd shouldn't be problematic.

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

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

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

I managed to get it working last night, but the install was a bit of a mess. It 
did how ever run over night.
 
This morning i carried out the following
sudo apt install \
isc-dhcp-server \
libdns-export1109/focal-proposed \
libirs-export161/focal-proposed \
libisc-export1105/focal-proposed 

The versions are below,and i will leave this to run as a test

GW1
# dpkg -l | grep libdns-export1109
ii  libdns-export11091:9.11.16+dfsg-3~ubuntu1   
amd64Exported DNS Shared Library
# dpkg -l | grep libirs-export161
ii  libirs-export161 1:9.11.16+dfsg-3~ubuntu1   
amd64Exported IRS Shared Library
# dpkg -l | grep libisc-export1105
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64Exported ISC Shared Library
 

GW2

# dpkg -l | grep libdns-export1109
ii  libdns-export11091:9.11.16+dfsg-3~ubuntu1   
amd64Exported DNS Shared Library
# dpkg -l | grep libirs-export161
ii  libirs-export161 1:9.11.16+dfsg-3~ubuntu1   
amd64Exported IRS Shared Library
# dpkg -l | grep libisc-export1105
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64Exported ISC Shared Library

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

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode as follows:
     Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/
     Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/
  2) Run dhcpd as follows in both machine(s)

  # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4

  3) Leave the cluster running for a long (2h) period until the
 

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

Just tried this
apt-get -y remove isc-dhcp-server
apt-get -y remove libdns-export1109/focal-proposed
apt-get -y remove libirs-export161/focal-proposed
apt-get -y remove libisc-export1105/focal-proposed
apt-get -y install isc-dhcp-server
apt-get -y install libdns1109/focal-proposed
apt-get -y install libirs161/focal-proposed
apt-get -y install  libisc1105/focal-proposed


GW1
#  dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
#  dpkg -l | grep libdns
ii  libdns-export11001:9.11.3+dfsg-1ubuntu1.12  
amd64Exported DNS Shared Library
ii  libdns-export11091:9.11.16+dfsg-3~build1
amd64Exported DNS Shared Library
ii  libdns1109:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libirs
ii  libirs-export160 1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported IRS Shared Library
ii  libirs-export161 1:9.11.16+dfsg-3~build1
amd64Exported IRS Shared Library
ii  libirs161:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libisc
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~build1
amd64Exported ISC Shared Library
ii  libisc-export169:amd64   1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC Shared Library
ii  libisc1105:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64ISC Shared Library used by BIND
ii  libisccc161:amd641:9.11.16+dfsg-3~ubuntu1   
amd64Command Channel Library used by BIND
ii  libisccfg-export160  1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC CFG Shared Library
ii  libisccfg-export163  1:9.11.16+dfsg-3~build1
amd64Exported ISC CFG Shared Library
ii  libisccfg163:amd64   1:9.11.16+dfsg-3~ubuntu1   
amd64Config File Handling Library used by BIND


GW2
# dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
# dpkg -l | grep libdns
ii  libdns-export11001:9.11.3+dfsg-1ubuntu1.12  
amd64Exported DNS Shared Library
ii  libdns-export11091:9.11.16+dfsg-3~build1
amd64Exported DNS Shared Library
ii  libdns1109:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libirs
ii  libirs-export160 1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported IRS Shared Library
ii  libirs-export161 1:9.11.16+dfsg-3~build1
amd64Exported IRS Shared Library
ii  libirs161:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libisc
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~build1
amd64Exported ISC Shared Library
ii  libisc-export169:amd64   1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC Shared Library
ii  libisc1105:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64ISC Shared Library used by BIND
ii  libisccc161:amd641:9.11.16+dfsg-3~ubuntu1   
amd64Command Channel Library used by BIND
ii  libisccfg-export160  1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC CFG Shared Library
ii  libisccfg-export163  1:9.11.16+dfsg-3~build1
amd64Exported ISC CFG Shared Library
ii  libisccfg163:amd64   1:9.11.16+dfsg-3~ubuntu1   
amd64Config File Handling Library used by BIND


still not good

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

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

not looking good,

Aug 15 20:14:55 gw2-focal sh[741]: ../../../../lib/isc/unix/socket.c:4359: 
fatal error: select() failed: Bad file descriptor
Aug 15 20:14:55 gw2-focal systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Aug 15 20:14:55 gw2-focal systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'.

have the correct files been installed ?

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

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode as follows:
     Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/
     Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/
  2) Run dhcpd as follows in both machine(s)

  # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4

  3) Leave the cluster running for a long (2h) period until the
  crash/race condition is reproduced.

  [REGRESSION POTENTIAL]

  * The fix will prevent the assertion to happen in the dispatch_send
  path, later versions of isch-dhcp upstream lack this logic and entirely 
removed the existence of this flag. Therefore, removing the need for this
  assertion at process_fd shouldn't be problematic.

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

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

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

Timo,
Just installed the updates I will let you know
I installed as follows 

apt-get install isc-dhcp-server

apt-get install libdns-export1109/focal-proposed
apt-get install libirs-export161/focal-proposed
apt-get install  libisc-export1105/focal-proposed


The installed version are
GW1
# dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
# dpkg -l | grep libdns-export1109
ii  libdns-export11091:9.11.16+dfsg-3~ubuntu1   
amd64Exported DNS Shared Library
# dpkg -l | grep libirs-export161
ii  libirs-export161 1:9.11.16+dfsg-3~ubuntu1   
amd64Exported IRS Shared Library
# dpkg -l | grep libisc-export1105
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64Exported ISC Shared Library
#


GW2
# dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
# dpkg -l | grep libdns-export1109
ii  libdns-export11091:9.11.16+dfsg-3~ubuntu1   
amd64Exported DNS Shared Library
# dpkg -l | grep libirs-export161
ii  libirs-export161 1:9.11.16+dfsg-3~build1
amd64Exported IRS Shared Library
# dpkg -l | grep libisc-export1105
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~build1
amd64Exported ISC Shared Library

Can you please confirm the correct versions are installed

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

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode as

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Pretty sure its working now ;) been running 24 hours and over 2 million
requests. Thanks for  all the effort Jorge

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Since i replaced the bad link , the patch appears to be working. been
running for 14 hours and over 1.2 Million requests both servers running
fine. Many thanks for all your effots.

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

looks like it may be fixed , been running about 5 hours about 400k
request and still alive. early signs are good, with the patch and my
dodgy link removed. Will leave running over night

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

I think on of the links was wrong, just remade it. and going to test
again

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Jorge, Here you go

andrew@gw2-focal:~$ ldd /usr/sbin/dhcpd | grep export
libirs-export.so.161 => /lib/x86_64-linux-gnu/libirs-export.so.161 
(0x00   
 007fa030e7b000)
libdns-export.so.1109 => /lib/x86_64-linux-gnu/libdns-export.so.1109 
(0x 
   7fa030c46000)
libisc-export.so.1105 => /lib/x86_64-linux-gnu/libisc-export.so.1105 
(0x 
   7fa030bcf000)
libisccfg-export.so.163 => 
/lib/x86_64-linux-gnu/libisccfg-export.so.163   
  
(0x7fa03098b000)
andrew@gw2-focal:~$ ldd /usr/sbin/dhcpd | grep export
libirs-export.so.161 => /lib/x86_64-linux-gnu/libirs-export.so.161 
(0x7fa9fbeaf000)
libdns-export.so.1109 => /lib/x86_64-linux-gnu/libdns-export.so.1109 
(0x7fa9fbc7a000)
libisc-export.so.1105 => /lib/x86_64-linux-gnu/libisc-export.so.1105 
(0x7fa9fbc03000)
libisccfg-export.so.163 => 
/lib/x86_64-linux-gnu/libisccfg-export.so.163 (0x7fa9fb9bf000)
andrew@gw2-focal:~$ dpkg -S /lib/x86_64-linux-gnu/libisc-export.so.1105
libisc-export1105:amd64: /lib/x86_64-linux-gnu/libisc-export.so.1105
andrew@gw2-focal:~$ apt-cache policy libisc-export1105  | grep -i ppa
  Installed: 1:9.11.16+dfsg-3~ppa1
  Candidate: 1:9.11.16+dfsg-3~ppa1
 *** 1:9.11.16+dfsg-3~ppa1 500
500 http://ppa.launchpad.net/niedbalski/fix-1872118/ubuntu focal/main 
amd64 Packages
andrew@gw2-focal:~$ ls -als  /lib/x86_64-linux-gnu/libirs-export.so.161

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Not sure if this helps i coped the coredump file to a test system install gdb
and got the following
# gdb /usr/sbin/dhcpd ./CoreDump
GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/dhcpd...
(No debugging symbols found in /usr/sbin/dhcpd)
[New LWP 63464]
[New LWP 63463]
[New LWP 63448]
[New LWP 63465]

warning: Unexpected size of section `.reg-xstate/63464' in core file.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dh'.
Program terminated with signal SIGABRT, Aborted.

warning: Unexpected size of section `.reg-xstate/63464' in core file.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7f0ed5c48700 (LWP 63464))]

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Yes i restarted isc-dhcp-server with systemctl restart isc-dhcp-server (
even tried a reboot once)


# dpkg -l | grep ppa1
ii  isc-dhcp-server  4.4.1-2.1ubuntu6~ppa1  
amd64ISC DHCP server for automatic IP address assignment
ii  libdns-export11091:9.11.16+dfsg-3~ppa1  
amd64Exported DNS Shared Library
ii  libirs-export161 1:9.11.16+dfsg-3~ppa1  
amd64Exported IRS Shared Library
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~ppa1  
amd64Exported ISC Shared Library
ii  libisccfg-export163  1:9.11.16+dfsg-3~ppa1  
amd64Exported ISC CFG Shared Library

# systemctl status isc-dhcp-server
● isc-dhcp-server.service - ISC DHCP IPv4 server
 Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Thu 2020-08-06 07:26:09 BST; 2min 39s ago
   Docs: man:dhcpd(8)
   Main PID: 42301 (dhcpd)
  Tasks: 4 (limit: 9569)
 Memory: 7.6M
 CGroup: /system.slice/isc-dhcp-server.service
 └─42301 dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf

Aug 06 07:28:47 gw2-focal dhcpd[42301]: Remove host declaration test or remove 
192.168.0.90
Aug 06 07:28:47 gw2-focal dhcpd[42301]: from the dynamic address pool for 
192.168.0.0/24
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.0.90 
(192.168.0.2) from MACREMOVED via ens3: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens13: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens12: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens11: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens10: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens9: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens8: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens3: ignored (not authoritative).

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Last time in only did 
sudo apt install \
isc-dhcp-server=4.4.1-2.1ubuntu6~ppa1 \ sudo systemctl restart 
isc-dhcp-server

This time i ried as someone else had done.

sudo apt install \
isc-dhcp-server=4.4.1-2.1ubuntu6~ppa1 \
libdns-export1109=1:9.11.16+dfsg-3~ppa1 \
libirs-export161=1:9.11.16+dfsg-3~ppa1 \
libisc-export1105=1:9.11.16+dfsg-3~ppa1 && \


I've uploaded the full crash dump

** Attachment added: "_usr_sbin_dhcpd.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+attachment/5398988/+files/_usr_sbin_dhcpd.0.crash

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

My config files are


PRIMARY SERVER CONFIG


default-lease-time 600;
max-lease-time 7200;

failover peer "failover-partner" {
primary;
address 192.168.0.2;
port 519;
peer address 192.168.0.3;
peer port 521;
max-response-delay 60;
max-unacked-updates 10;
mclt 3600;
split 128;
load balance max seconds 3;
}

omapi-port 7911;
omapi-key omapi_key;

key omapi_key {
 algorithm hmac-md5;
 secret  REMOVED;
}

subnet 192.168.0.0 netmask 255.255.255.0 {
 option routers 192.168.0.1;
 option domain-name-servers 192.168.0.2, 192.168.0.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.0-dhcp-static-leases.conf";
# include"/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.0.6 192.168.0.254;
deny unknown-clients;
 }
}


subnet 192.168.1.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.1.1;
 option domain-name-servers 192.168.1.2, 192.168.1.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.1-dhcp-static-leases.conf";
# include"/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
 failover peer "failover-partner";
 range 192.168.1.6 192.168.1.254;
 deny unknown-clients;

 }
}

subnet 192.168.2.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.2.1;
 option domain-name-servers 192.168.2.2, 192.168.2.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.2-dhcp-static-leases.conf";
# include"/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.2.6 192.168.2.254;
deny unknown-clients;

 }
}

subnet 192.168.3.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.3.1;
 option domain-name-servers 192.168.3.2, 192.168.3.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.3-dhcp-static-leases.conf";
# include"/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.3.6 192.168.3.254;
deny unknown-clients;
 }
}

subnet 192.168.4.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.4.1;
 option domain-name-servers 192.168.4.2, 192.168.4.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.4-dhcp-static-leases.conf";
# include"/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.4.6 192.168.4.254;
deny unknown-clients;
 }
}

subnet 192.168.5.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.5.1;
 option domain-name-servers  192.168.5.2, 192.168.5.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.5-dhcp-static-leases.conf";
# include "/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.5.6 192.168.5.254;
deny unknown-clients;
 }
}

subnet 192.168.6.0 netmask 255.255.255.0 {
 allow unknown-clients;
 option routers 192.168.6.1;
 option domain-name-servers 192.168.6.2, 192.168.6.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers 212.23.6.6,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.6-dhcp-static-leases.conf";
# include "/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.6.6 192.168.6.254;
allow unknown-clients;
 }
}

subnet 192.168.7.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.7.1;
 option domain-name-servers  192.168.7.2, 192.168.7.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.7-dhcp-static-leases.conf";
# include "/etc/dhcp/BANNED-MACs-dhcp-static-leases.conf";
 pool {
failover peer "failover-partner";
range 192.168.7.6 192.168.7.254;
deny unknown-clients;
 }
}

subnet 192.168.8.0 netmask 255.255.255.0 {
 deny unknown-clients;
 option routers 192.168.8.1;
 option domain-name-servers 192.168.8.2, 192.168.8.3;
 option domain-name "mydomain";
 option domain-search ".", "mydomain";
 option ntp-servers NTPHOST1,  NTPHOST2;
 log-facility local7;
 include "/etc/dhcp/192.168.8-dhcp-

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

isc-dhcp-server failed to start after that, a reboot fixed it and it appeared 
to stabilise. Then as a test i upgraded the primary server.
when the primary server came on line the secondary went off line and the 
stability of the environment went down fast. 
Remove the patched version and installed the version from 18.04 to be able to 
stay online

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

also noticed this  APPARMOR is not happy now
Aug  4 09:37:37 gw2-focal kernel: [257023.493017] audit: type=1400 
audit(1596530257.080:51): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/63448/task/63463/comm" pid=63448 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 09:37:37 gw2-focal kernel: [257023.493726] audit: type=1400 
audit(1596530257.084:52): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/63448/task/63464/comm" pid=63448 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 09:37:37 gw2-focal kernel: [257023.494441] audit: type=1400 
audit(1596530257.084:53): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/63448/task/63465/comm" pid=63448 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 13:49:39 gw2-focal kernel: [272145.694002] audit: type=1400 
audit(1596545379.184:54): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/67792/task/67804/comm" pid=67792 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 13:49:39 gw2-focal kernel: [272145.694558] audit: type=1400 
audit(1596545379.184:55): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/67792/task/67805/comm" pid=67792 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 13:49:39 gw2-focal kernel: [272145.694837] audit: type=1400 
audit(1596545379.184:56): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/67792/task/67806/comm" pid=67792 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 15:20:30 gw2-focal kernel: [277597.307707] audit: type=1400 
audit(1596550830.760:57): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/69853/task/69865/comm" pid=69853 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 15:20:30 gw2-focal kernel: [277597.308533] audit: type=1400 
audit(1596550830.760:58): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/69853/task/69867/comm" pid=69853 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 15:20:30 gw2-focal kernel: [277597.309043] audit: type=1400 
audit(1596550830.760:59): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/69853/task/69868/comm" pid=69853 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Aug  4 17:19:27 gw2-focal kernel: [284733.739418] audit: type=1400 
audit(1596557967.150:60): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/dhcpd" pid=73881 comm="apparmor_parser"

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhc

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

I've done the apt install on one of the failover server (Its the one
that mostly crashes)

Listing... Done
isc-dhcp-server/focal,now 4.4.1-2.1ubuntu6~ppa1 amd64 [installed]

still crashed


syslog shows
Aug  4 17:40:44 gw2-focal sh[74365]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Aug  4 17:40:44 gw2-focal sh[74365]: #0 0x7f2302a7fa4a in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #1 0x7f2302a7f980 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #2 0x7f2302abb7e1 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #3 0x7f2302862609 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #4 0x7f230299e103 in ??
Aug  4 17:40:44 gw2-focal systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Aug  4 17:40:44 gw2-focal systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'.


text part of crash shows

ProblemType: Crash
Architecture: amd64
Date: Tue Aug  4 17:44:17 2020
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/sbin/dhcpd
ExecutableTimestamp: 1596511208
ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
 Name:  dhcpd
 Umask: 0022
 State: D (disk sleep)
 Tgid:  74528
 Ngid:  0
 Pid:   74528
 PPid:  1
 TracerPid: 0
 Uid:   113 113 113 113
 Gid:   118 118 118 118
 FDSize:128
 Groups:
 NStgid:74528
 NSpid: 74528
 NSpgid:74528
 NSsid: 74528
 VmPeak:  235996 kB
 VmSize:  170540 kB
 VmLck:0 kB
 VmPin:0 kB
 VmHWM:12088 kB
 VmRSS:11904 kB
 RssAnon:   5784 kB
 RssFile:   6120 kB
 RssShmem: 0 kB
 VmData:   30568 kB
 VmStk:  132 kB
 VmExe:  592 kB
 VmLib: 5424 kB
 VmPTE:   88 kB
 VmSwap:   0 kB
 HugetlbPages: 0 kB
 CoreDumping:   1
 THP_enabled:   1
 Threads:   4
 SigQ:  0/31897
 SigPnd:
 ShdPnd:
 SigBlk:
 SigIgn:1000
 SigCgt:00018000
 CapInh:
 CapPrm:
 CapEff:
 CapBnd:003f
 CapAmb:
 NoNewPrivs:0
 Seccomp:   0
 Speculation_Store_Bypass:  thread vulnerable
 Cpus_allowed:  f
 Cpus_allowed_list: 0-3
 Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,,,0001
 Mems_allowed_list: 0
 voluntary_ctxt_switches:   22
 nonvoluntary_ctxt_switches:20
Signal: 6
Uname: Linux 5.4.0-42-generic x86_64
UserGroups: N/A
CoreDump: base64

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/cras

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

error in the above description should have been 
I've done the apt install on one of SERVERS the failover server (Its the one 
that mostly crashes)

Listing... Done
isc-dhcp-server/focal,now 4.4.1-2.1ubuntu6~ppa1 amd64 [installed]

still crashed


syslog shows
Aug  4 17:40:44 gw2-focal sh[74365]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Aug  4 17:40:44 gw2-focal sh[74365]: #0 0x7f2302a7fa4a in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #1 0x7f2302a7f980 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #2 0x7f2302abb7e1 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #3 0x7f2302862609 in ??
Aug  4 17:40:44 gw2-focal sh[74365]: #4 0x7f230299e103 in ??
Aug  4 17:40:44 gw2-focal systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Aug  4 17:40:44 gw2-focal systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'.


text part of crash shows

ProblemType: Crash
Architecture: amd64
Date: Tue Aug  4 17:44:17 2020
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/sbin/dhcpd
ExecutableTimestamp: 1596511208
ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
 Name:  dhcpd
 Umask: 0022
 State: D (disk sleep)
 Tgid:  74528
 Ngid:  0
 Pid:   74528
 PPid:  1
 TracerPid: 0
 Uid:   113 113 113 113
 Gid:   118 118 118 118
 FDSize:128
 Groups:
 NStgid:74528
 NSpid: 74528
 NSpgid:74528
 NSsid: 74528
 VmPeak:  235996 kB
 VmSize:  170540 kB
 VmLck:0 kB
 VmPin:0 kB
 VmHWM:12088 kB
 VmRSS:11904 kB
 RssAnon:   5784 kB
 RssFile:   6120 kB
 RssShmem: 0 kB
 VmData:   30568 kB
 VmStk:  132 kB
 VmExe:  592 kB
 VmLib: 5424 kB
 VmPTE:   88 kB
 VmSwap:   0 kB
 HugetlbPages: 0 kB
 CoreDumping:   1
 THP_enabled:   1
 Threads:   4
 SigQ:  0/31897
 SigPnd:
 ShdPnd:
 SigBlk:
 SigIgn:1000
 SigCgt:00018000
 CapInh:
 CapPrm:
 CapEff:
 CapBnd:003f
 CapAmb:
 NoNewPrivs:0
 Seccomp:   0
 Speculation_Store_Bypass:  thread vulnerable
 Cpus_allowed:  f
 Cpus_allowed_list: 0-3
 Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,,,0001
 Mems_allowed_list: 0
 voluntary_ctxt_switches:   22
 nonvoluntary_ctxt_switches:20
Signal: 6
Uname: Linux 5.4.0-42-generic x86_64
UserGroups: N/A
CoreDump: base64

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (p

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

As my systems are pinned not to accept isc-dhcp-server upgrades, as I run the 
18.04 version as it works. I extracted the dhcpd file from your packages and 
dropped it in place.
It ran for about 5 hours with thousands of requests.
Then it crashed with 

Aug  4 13:13:29 gw2-focal sh[63448]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Aug  4 13:13:29 gw2-focal sh[63448]: #0 0x7f0ed6a02a4a in ??
Aug  4 13:13:29 gw2-focal sh[63448]: #1 0x7f0ed6a02980 in ??
Aug  4 13:13:29 gw2-focal sh[63448]: #2 0x7f0ed6a3e7e1 in ??
Aug  4 13:13:29 gw2-focal sh[63448]: #3 0x7f0ed67e5609 in ??
Aug  4 13:13:29 gw2-focal sh[63448]: #4 0x7f0ed6921103 in ??

In the syslog

The start of the crash (up to the base64 dump) is

ProblemType: Crash
Architecture: amd64
Date: Tue Aug  4 13:13:30 2020
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/sbin/dhcpd
ExecutableTimestamp: 1596530249
ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
 Name:  dhcpd
 Umask: 0022
 State: D (disk sleep)
 Tgid:  63448
 Ngid:  0
 Pid:   63448
 PPid:  1
 TracerPid: 0
 Uid:   113 113 113 113
 Gid:   118 118 118 118
 FDSize:128
 Groups:
 NStgid:63448
 NSpid: 63448
 NSpgid:63448
 NSsid: 63448
 VmPeak:  235996 kB
 VmSize:  170540 kB
 VmLck:0 kB
 VmPin:0 kB
 VmHWM:12468 kB
 VmRSS:12468 kB
 RssAnon:   6216 kB
 RssFile:   6252 kB
 RssShmem: 0 kB
 VmData:   30872 kB
 VmStk:  132 kB
 VmExe:  592 kB
 VmLib: 5424 kB
 VmPTE:   88 kB
 VmSwap:   0 kB
 HugetlbPages: 0 kB
 CoreDumping:   1
 THP_enabled:   1
 Threads:   4
 SigQ:  0/31897
 SigPnd:
 ShdPnd:
 SigBlk:
 SigIgn:1000
 SigCgt:00018000
 CapInh:
 CapPrm:
 CapEff:
 CapBnd:003f
 CapAmb:
 NoNewPrivs:0
 Seccomp:   0
 Speculation_Store_Bypass:  thread vulnerable
 Cpus_allowed:  f
 Cpus_allowed_list: 0-3
 Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,,,0001
 Mems_allowed_list: 0
 voluntary_ctxt_switches:   40
 nonvoluntary_ctxt_switches:19
Signal: 6
Uname: Linux 5.4.0-42-generic x86_64
UserGroups: N/A

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1

[Touch-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Fix Released
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]

  Impact: The tc command does not show the correct values for tcp_flags
  (and ip_tos) on filter rules. This might break other scripts parsing
  that output but at least confuses users.

  Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output"
  from upstream iproute2.

  Testcase:
  tc qdisc add dev lo ingress
  tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32
  tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \
   tcp_flags 0x909/f00

  tc filter show dev lo parent :

  filter protocol ip pref 3 flower chain 0
  filter protocol ip pref 3 flower chain 0 handle 0x1
    eth_type ipv4
    ip_tos a9606c10 <-- bad, should be 0x8/32
    not_in_hw
  filter protocol ip pref 5 flower chain 0
  filter protocol ip pref 5 flower chain 0 handle 0x1
    eth_type ipv4
    ip_proto tcp
    tcp_flags 909909 <-- bad, should be 0x909/f00
    not_in_hw

  Note that the ip_tos value in the -j[son] output is correct, while the 
tcp_flags value is
  is incorrect in both cases.

  Risk of Regression:
  Low: Usually scripts would use the json output and that has at least the ip 
output correct. And the values shown in the bad case seem to be little useful. 
So it seems unlikely anybody relied on them. But cannot completely be ruled out.

  === Original description ===

  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r

  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
    src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
    eth_type ipv4
    ip_proto tcp
    tcp_flags 22   /* <--- Wrong */
    skip_sw
    in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r

  After that, using "tc filter show dev p0v2_r root" to verify, we still
  see the same output (tcp_flags 22) as shown in 2) above, which is
  wrong.

  Userspace tool common name: tc

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

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */

  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.

  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
    src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
    eth_type ipv4
    ip_proto tcp
    tcp_flags 0x2/7   /* <--- Correct */
    skip_sw
    in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

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

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

[Touch-packages] [Bug 1890006] Re: Hash mismatch on "apt update"

[Andrew]

VT-x status in BIOS is a red herring. Turns out modern Virtualbox won't
even start VM's without VT-x.

A true cause turned out to be "Windows Sandbox" feature (although I
imagine for some other users the problem might be triggered by "Windows
Subsystem for Linux" or anti-virus software).

Here is how to reproduce it in Windows 10:

  1. Enable "Windows Sandbox" (Control panel -> Programs and Features -> Turn 
Windows features on or off)
  2. After restart run Ubuntu live ISO in virtualbox and notice that
a) VM slows to a crawl, some apps (firefox) start crashing randomly, etc
b) Virtualbox shows "green turtle" icon (third from the right on the lower 
panel) which lists Execution engine as "native API" instead of "VT-x"
c) Running "apt update" produces error mentioning "hash mismatch"
d) Running workaround (mkdir -p /etc/gcrypt; echo intel-ssse3 > 
/etc/gcrypt/hwf.deny) fixes the apt error
  3. Disable "Windows Sandbox" feature
  4. After Windows restart run Ubuntu in Virtualbox and be surprised by green 
turtle still being there, all mentioned problems still present
  5. Restart Windows second time, run Ubuntu in Virtualbox again, this time 
there is a blue chip instead of green turtle and apt works without workarounds

Clearly it seems that gcrypt isnt at fault here and the true culprits
are Windows Sandbox (possibly some other mechanism that Windows Sandbox
enables) and/or Virtualbox. However the result is that new users are
getting wrong impression about GNU/Linux and Ubuntu in particular (it
appears slow and lags during "live" phase, fails to update after
install).

So I'd say Ubuntu should detect that it's being run in this broken
virtualization mode, show the informative explanation to user (that
their current experience isn't representative && how they can fix that)
or at least enable the workaround for gcrypt (although if SSSE3 is buggy
in this mode, I imagine more things are stealthily broken).

Surprisingly Ubuntu still finishes installation, even with default
"update from internet" option enabled. After installation, "apt update"
still produces the same "hash mismatch" errors though. Enabling
workaround and rerunning "apt update" predictably finds many more (292
right now) packages that are to be upgraded. This fail-open behavior
(installer and updater ignoring the errors) will no doubt lead to subtle
bug down the road for the users as well (I'd argue that it's a security
issue as well - users not being informed about security patches they're
missing).

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

Title:
  Hash mismatch on "apt update"

Status in apt package in Ubuntu:
  New

Bug description:
  This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live
  ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least
  apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs
  on a single PC (as far as I know). All testing was done in Virtualbox
  and moving VM's to another PC fixed issue (without changing anything
  inside the VM).

  On running "apt update", there is an error "Hash Sum mismatch" which
  shows that SHA1 and SHA256 hashes differ from expected (while MD5 and
  file size is correct). E.g.:

Hash Sum mismatch
Hashes of expected file:
 - Filesize:314536 [weak]
 - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0
 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
Hashes of received file:
 - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2
 - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
 - Filesize:314536 [weak]

  I ran packet capture and extracted archives which are getting
  verified. All of their hashes are correct (exactly as expected).

  It seems that calculating SHA1 and SHA256 the way APT does it produces
  wrong result, while running command line tools sha1sum and sha256sum
  (on the same PC inside the same VM) produces correct result.

  I wrote the minimal reproducible example (hashtest.cc) that produces
  output such as this:

  Calculating hashes same way apt does.

   - MD5Sum:c89b13b76197d0d554400e00e46c0740
   - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba
   - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - 
SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036
   - Checksum-FileSize:892549

  Calculating hashes through command line tools.

   - md5sum: c89b13b76197d0d554400e00e46c0740
   - sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba
   - sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - sha512sum: 
7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a0

[Touch-packages] [Bug 1890006] Re: Hash mismatch on "apt update"

[Andrew]

Here is apport stuff, and there are more news.

I confirmed that the problem was in the gcrypt. More precisely,
disabling SSSE3 fixes this issue (echo intel-ssse3 >
/etc/gcrypt/hwf.deny).

The Virtualbox (running on Windows 10) was using software virtualization
("execution engine: native API") instead of VT-x - this might be the
root cause (i.e. bug is in Virtualbox), but I'm helping a friend and
don't have direct access to that PC, so can't test what's blocking VT-x.
Hyper-V and WSL are disabled in Windows features, the person hasn't
checked whether VT-x is enabled in BIOS yet.

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

Title:
  Hash mismatch on "apt update"

Status in apt package in Ubuntu:
  New

Bug description:
  This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live
  ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least
  apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs
  on a single PC (as far as I know). All testing was done in Virtualbox
  and moving VM's to another PC fixed issue (without changing anything
  inside the VM).

  On running "apt update", there is an error "Hash Sum mismatch" which
  shows that SHA1 and SHA256 hashes differ from expected (while MD5 and
  file size is correct). E.g.:

Hash Sum mismatch
Hashes of expected file:
 - Filesize:314536 [weak]
 - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0
 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
Hashes of received file:
 - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2
 - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
 - Filesize:314536 [weak]

  I ran packet capture and extracted archives which are getting
  verified. All of their hashes are correct (exactly as expected).

  It seems that calculating SHA1 and SHA256 the way APT does it produces
  wrong result, while running command line tools sha1sum and sha256sum
  (on the same PC inside the same VM) produces correct result.

  I wrote the minimal reproducible example (hashtest.cc) that produces
  output such as this:

  Calculating hashes same way apt does.

   - MD5Sum:c89b13b76197d0d554400e00e46c0740
   - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba
   - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - 
SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036
   - Checksum-FileSize:892549

  Calculating hashes through command line tools.

   - md5sum: c89b13b76197d0d554400e00e46c0740
   - sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba
   - sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - sha512sum: 
7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036

  It's in the attachment alongside with an example file that causes this
  hash mismatch. There's also debug.log which contains various versions,
  etc (although as I said, it has been verified on latest Ubuntu Live
  ISO).

  I have a suspicion that the bug is in the gcrypt library, not apt itself, but 
I haven't yet verified it. The libgcrypt20 version in Ubuntu is 1.8.5-5ubuntu1 
(in Kali as well), while Debian 10 (which isn't affected) uses 1.8.4-5.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.445
  DistroRelease: Ubuntu 20.04
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: apt 2.0.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1890006] Re: Hash mismatch on "apt update"

[Andrew]

apport information

** Tags added: apport-collected focal

** Description changed:

  This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live
  ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least apt
  2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs on a
  single PC (as far as I know). All testing was done in Virtualbox and
  moving VM's to another PC fixed issue (without changing anything inside
  the VM).
  
  On running "apt update", there is an error "Hash Sum mismatch" which
  shows that SHA1 and SHA256 hashes differ from expected (while MD5 and
  file size is correct). E.g.:
  
Hash Sum mismatch
Hashes of expected file:
 - Filesize:314536 [weak]
 - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0
 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
Hashes of received file:
 - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2
 - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
 - Filesize:314536 [weak]
  
  I ran packet capture and extracted archives which are getting verified.
  All of their hashes are correct (exactly as expected).
  
  It seems that calculating SHA1 and SHA256 the way APT does it produces
  wrong result, while running command line tools sha1sum and sha256sum (on
  the same PC inside the same VM) produces correct result.
  
  I wrote the minimal reproducible example (hashtest.cc) that produces
  output such as this:
  
  Calculating hashes same way apt does.
  
   - MD5Sum:c89b13b76197d0d554400e00e46c0740
   - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba
   - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - 
SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036
   - Checksum-FileSize:892549
  
  Calculating hashes through command line tools.
  
   - md5sum: c89b13b76197d0d554400e00e46c0740
   - sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba
   - sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - sha512sum: 
7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036
  
  It's in the attachment alongside with an example file that causes this
  hash mismatch. There's also debug.log which contains various versions,
  etc (although as I said, it has been verified on latest Ubuntu Live
  ISO).
  
- I have a suspicion that the bug is in the gcrypt library, not apt
- itself, but I haven't yet verified it. The libgcrypt20 version in Ubuntu
- is 1.8.5-5ubuntu1 (in Kali as well), while Debian 10 (which isn't
- affected) uses 1.8.4-5.
+ I have a suspicion that the bug is in the gcrypt library, not apt itself, but 
I haven't yet verified it. The libgcrypt20 version in Ubuntu is 1.8.5-5ubuntu1 
(in Kali as well), while Debian 10 (which isn't affected) uses 1.8.4-5.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckMismatches: ./casper/filesystem.squashfs
+ CasperMD5CheckResult: fail
+ CasperVersion: 1.445
+ DistroRelease: Ubuntu 20.04
+ LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: apt 2.0.2
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
+ Tags:  focal
+ Uname: Linux 5.4.0-26-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1890006/+attachment/5397968/+files/Dependencies.txt

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

Title:
  Hash mismatch on "apt update"

Status in apt package in Ubuntu:
  New

Bug description:
  This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live
  ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least
  apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs
  on a single PC (as far as I know). All testing was done in Virtualbox
  and moving VM's to another PC fixed issue (without changing anything
  inside the VM).

  On running "apt update", there is an error "Hash Sum mismatch" which
  shows that SHA1 and SHA256 hashes differ from expected (while MD5 and
  file size is correct). E.g.:

Hash Sum mismatch
Hashes of expected file:
 - Filesize:314536 [weak]
 - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0
 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak]
 - MD5Sum:

[Touch-packages] [Bug 1890006] ProcCpuinfoMinimal.txt

[Andrew]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1890006/+attachment/5397969/+files/ProcCpuinfoMinimal.txt

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

Title:
  Hash mismatch on "apt update"

Status in apt package in Ubuntu:
  New

Bug description:
  This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live
  ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least
  apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs
  on a single PC (as far as I know). All testing was done in Virtualbox
  and moving VM's to another PC fixed issue (without changing anything
  inside the VM).

  On running "apt update", there is an error "Hash Sum mismatch" which
  shows that SHA1 and SHA256 hashes differ from expected (while MD5 and
  file size is correct). E.g.:

Hash Sum mismatch
Hashes of expected file:
 - Filesize:314536 [weak]
 - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0
 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
Hashes of received file:
 - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2
 - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
 - Filesize:314536 [weak]

  I ran packet capture and extracted archives which are getting
  verified. All of their hashes are correct (exactly as expected).

  It seems that calculating SHA1 and SHA256 the way APT does it produces
  wrong result, while running command line tools sha1sum and sha256sum
  (on the same PC inside the same VM) produces correct result.

  I wrote the minimal reproducible example (hashtest.cc) that produces
  output such as this:

  Calculating hashes same way apt does.

   - MD5Sum:c89b13b76197d0d554400e00e46c0740
   - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba
   - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - 
SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036
   - Checksum-FileSize:892549

  Calculating hashes through command line tools.

   - md5sum: c89b13b76197d0d554400e00e46c0740
   - sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba
   - sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - sha512sum: 
7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036

  It's in the attachment alongside with an example file that causes this
  hash mismatch. There's also debug.log which contains various versions,
  etc (although as I said, it has been verified on latest Ubuntu Live
  ISO).

  I have a suspicion that the bug is in the gcrypt library, not apt itself, but 
I haven't yet verified it. The libgcrypt20 version in Ubuntu is 1.8.5-5ubuntu1 
(in Kali as well), while Debian 10 (which isn't affected) uses 1.8.4-5.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.445
  DistroRelease: Ubuntu 20.04
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: apt 2.0.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1890006] [NEW] Hash mismatch on "apt update"

[Andrew]

Public bug reported:

This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live
ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least apt
2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs on a
single PC (as far as I know). All testing was done in Virtualbox and
moving VM's to another PC fixed issue (without changing anything inside
the VM).

On running "apt update", there is an error "Hash Sum mismatch" which
shows that SHA1 and SHA256 hashes differ from expected (while MD5 and
file size is correct). E.g.:

  Hash Sum mismatch
  Hashes of expected file:
   - Filesize:314536 [weak]
   - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0
   - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak]
   - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
  Hashes of received file:
   - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2
   - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak]
   - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
   - Filesize:314536 [weak]

I ran packet capture and extracted archives which are getting verified.
All of their hashes are correct (exactly as expected).

It seems that calculating SHA1 and SHA256 the way APT does it produces
wrong result, while running command line tools sha1sum and sha256sum (on
the same PC inside the same VM) produces correct result.

I wrote the minimal reproducible example (hashtest.cc) that produces
output such as this:

Calculating hashes same way apt does.

 - MD5Sum:c89b13b76197d0d554400e00e46c0740
 - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba
 - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
 - 
SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036
 - Checksum-FileSize:892549

Calculating hashes through command line tools.

 - md5sum: c89b13b76197d0d554400e00e46c0740
 - sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba
 - sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
 - sha512sum: 
7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036

It's in the attachment alongside with an example file that causes this
hash mismatch. There's also debug.log which contains various versions,
etc (although as I said, it has been verified on latest Ubuntu Live
ISO).

I have a suspicion that the bug is in the gcrypt library, not apt
itself, but I haven't yet verified it. The libgcrypt20 version in Ubuntu
is 1.8.5-5ubuntu1 (in Kali as well), while Debian 10 (which isn't
affected) uses 1.8.4-5.

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

** Attachment added: "minimal poc, file producing hash mismatches, version 
listing"
   
https://bugs.launchpad.net/bugs/1890006/+attachment/5397801/+files/hash_mismatch_poc.tgz

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

Title:
  Hash mismatch on "apt update"

Status in apt package in Ubuntu:
  New

Bug description:
  This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live
  ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least
  apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs
  on a single PC (as far as I know). All testing was done in Virtualbox
  and moving VM's to another PC fixed issue (without changing anything
  inside the VM).

  On running "apt update", there is an error "Hash Sum mismatch" which
  shows that SHA1 and SHA256 hashes differ from expected (while MD5 and
  file size is correct). E.g.:

Hash Sum mismatch
Hashes of expected file:
 - Filesize:314536 [weak]
 - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0
 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
Hashes of received file:
 - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2
 - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
 - Filesize:314536 [weak]

  I ran packet capture and extracted archives which are getting
  verified. All of their hashes are correct (exactly as expected).

  It seems that calculating SHA1 and SHA256 the way APT does it produces
  wrong result, while running command line tools sha1sum and sha256sum
  (on the same PC inside the same VM) produces correct result.

  I wrote the minimal reproducible example (hashtest.cc) that produces
  output such as this:

  Calculating hashes same way apt does.

   - MD5Sum:c89b13b76197d0d554400e00e46c0740
   - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba
   - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - 
SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f9428

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Tomek, Please remember I tried the version 4.4.2 as suggested and as you
say Ubuntu used 4.4.1, so it could be something to do with the 4.4.1
release or the ubuntu changes. Either way it looks like its not going to
be fixed. Given this how do you apply to have a ISC-DHCP_Server removed
form the Ubuntu bundle for no maintenance.

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

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+subscriptions

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

tried it on a single server in the cluster and it looks like it better,
i.e it actually launches, however there is no -user or -group options,
with different directories and it must be started as root (with no
change of id_  to start, so not secure. I guess thee other changes are
added by ubuntu

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

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+subscriptions

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

[Touch-packages] [Bug 1387825] Re: The default NAME_REGEX value in /etc/adduser.conf is incorrect

[Andrew Meyer]

This just bit me. It's especially confusing for beginners because the
config file syntax looks a lot like bash, and in bash that extra
backslash would be correct as it would simply prevent the proceeding
dollar symbol from being interpreted as an environment variable, and the
backslash wouldn't show up in the final regex.

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

Title:
  The default NAME_REGEX value in /etc/adduser.conf is incorrect

Status in adduser package in Ubuntu:
  Confirmed
Status in adduser package in Debian:
  New

Bug description:
  Refer the Debian bug report for more information.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: adduser 3.113+nmu3ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4
  Uname: Linux 3.16.0-22-lowlatency i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Oct 31 01:55:03 2014
  InstallationDate: Installed on 2013-03-08 (600 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  PackageArchitecture: all
  SourcePackage: adduser
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (194 days ago)

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

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

[Touch-packages] [Bug 1387825] Re: The default NAME_REGEX value in /etc/adduser.conf is incorrect

[Andrew Meyer]

Another example of someone getting confused by this bug:
https://askubuntu.com/q/892419/166655

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

Title:
  The default NAME_REGEX value in /etc/adduser.conf is incorrect

Status in adduser package in Ubuntu:
  Confirmed
Status in adduser package in Debian:
  New

Bug description:
  Refer the Debian bug report for more information.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: adduser 3.113+nmu3ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4
  Uname: Linux 3.16.0-22-lowlatency i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Oct 31 01:55:03 2014
  InstallationDate: Installed on 2013-03-08 (600 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  PackageArchitecture: all
  SourcePackage: adduser
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (194 days ago)

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

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Looking at the history around isc-dhcp, it appears if i read it properly that 
isc-dhcp sever for Ubuntu has been abandoned.
If this is the case should it even be in the focal build

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

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+subscriptions

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

Thats what I did, but had a couple of outages, I had a choice of extending the 
lease time or downgrade. I did also try to disable apparmor, and dhcp gave an 
error (can't remember what though) and crashed I guess AppArmor just detected 
this and killed the process. So far about a week in ad every thing looks good.
The other option i guess (until they fix this) is to build the latest release 
from source. I did not do this due to no automatic patching

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

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+subscriptions

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

[Touch-packages] [Bug 1871154] Re: Error message displayed during boot (mountroot hook, premount)

[Andrew]

Hello guys. I'm just ordinary user, please help me to understand how to fix 
this error?
>From what PPA you are getting it?

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

Title:
  Error message displayed during boot (mountroot hook, premount)

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Fix Committed
Status in lvm2 source package in Focal:
  Invalid

Bug description:
  [Impact] 
  * People using lvm2 on ubuntu focal are getting a strange and weird message 
due to a wrong path

  [Test Case]
  * Install lvm2 on Ubuntu 20.04

  [Regression Potential] 
  * Low, the fix is already part of groovy

  [Other info]
  Hi,

  my Ubuntu system uses LVM2 for its root file system.  It boots
  correctly, but an ugly error message is displayed during boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr  6 17:59:03 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage

[Andrew]

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

The same for me.

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

Title:
  Definition of add_mountroot_fail_hook doesnt match lvm2's usage

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Package lvm2 contains a init-premount script named /usr/share
  /initramfs-tools/scripts/init-premount/lvm2

  In this script there is the function call:
  add_mountroot_fail_hook "20-lvm2"

  Which is defined in /usr/share/initramfs-tools/scripts/functions

  In focal's 0.136ubuntu6 , this is defined as:

  add_mountroot_fail_hook()
  {
  mkdir -p /tmp/mountroot-fail-hooks.d
  ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
  }

  The final line of the function will execute as
  ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"

  And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
  not exist.

  It is clear from lvm2's invocation that it expects the symlink to be
  named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
  the case:

  add_mountroot_fail_hook()
  {
  mkdir -p /tmp/mountroot-fail-hooks.d
  ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
  }

  focal's version needs to be updated to either support the "$1"
  argument or strip the directory from "$0".

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

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

No response, I actually wondering if I logged the bug in the wrong
place. Anyone building a cluster of DHCP servers on Ubuntu 20.04 should
run into this. The above or no one is using Ubuntu for DHCP clusters ?

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

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+subscriptions

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

[Andrew Welham]

MM , Thanks I install the isc-dhcp-server from the Bionic-Security repository, 
and it appears to work.
For anyone else here is how to install an older version of the server,and then 
block updates to the focal version

PLEASE USE AT YOUR OWN RISK

#Backup your old config
sudo mkdir /etc/dhcp.20.04
sudo cp -r /etc/dhcp /etc/dhcp.20.04

#Remove your old isc-dhcp server
sudo apt remove isc-dhcp-server

#Add the old Bionic repository
add-apt-repository 'deb http://security.ubuntu.com/ubuntu bionic-security main'
sudo apt update

#Install isc-dhcp-server from the bionic-security repository
sudo apt-get install -t bionic-security/main isc-dhcp-server
sudo systemctl restart isc-dhcp-server


#Block upgrades of the package from the Focal Repository
edit /etc/apt/preferences.d/repo and add the following lines


Package: isc-dhcp-server
Pin: release a=bionic-security
Pin-Priority: 900

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

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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