[Touch-packages] [Bug 2037569] Re: udev issues with mantic beta
Spent some time analyzing this. Frank loaned me a test system. The test system in the "idle" state is enough to see the issue, with a persistent load of 3+ when nothing is happening except event loop spin. The test system is using a dasd as the disk that it is running from. With some udev tracing, one can see an apparent loop, with udisks2 opening /dev/dasda, which triggers an inotify, which triggers udev rules, which trigger udisks2 again, or something similar to this flow. Workarounds include: * adding a nowatch rule 'ACTION=="add|change", KERNEL=="dasd*", OPTIONS:="nowatch"' * systemctl stop udisks2 I've begun exploring udev changes for udisks2 to ignore dasd. -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: New Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037349] Re: package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1
** Package changed: ubuntu => cups (Ubuntu) -- 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/2037349 Title: package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: New Bug description: DOnt know, but crome always cras, i migt be infected ProblemType: Package DistroRelease: Ubuntu 22.04 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 CupsErrorLog: Date: Thu Sep 21 06:28:18 2023 DuplicateSignature: package:cups:2.4.1op1-1ubuntu4.7 Setting up cups (2.4.1op1-1ubuntu4.7) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 1 ErrorMessage: installed cups package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-04-06 (172 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 002: ID 145f:02d7 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Power Laptop 15-cb0xx Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=23c97043-a6af-4600-a6fe-bae17d889351 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=23c97043-a6af-4600-a6fe-bae17d889351 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 Snap: cups 2.4.6-4 (stable) Snap.Changes: no changes found Title: package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2020 dmi.bios.release: 15.41 dmi.bios.vendor: Insyde dmi.bios.version: F.41 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 836B dmi.board.vendor: HP dmi.board.version: 46.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 46.24 dmi.modalias: dmi:bvnInsyde:bvrF.41:bd12/01/2020:br15.41:efr46.24:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.24:cvnHP:ct10:cvrChassisVersion:sku2CK98EA#ABE: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Power Laptop 15-cb0xx dmi.product.sku: 2CK98EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2037349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037349] [NEW] package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1
You have been subscribed to a public bug: DOnt know, but crome always cras, i migt be infected ProblemType: Package DistroRelease: Ubuntu 22.04 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 CupsErrorLog: Date: Thu Sep 21 06:28:18 2023 DuplicateSignature: package:cups:2.4.1op1-1ubuntu4.7 Setting up cups (2.4.1op1-1ubuntu4.7) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 1 ErrorMessage: installed cups package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-04-06 (172 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 002: ID 145f:02d7 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Power Laptop 15-cb0xx Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=23c97043-a6af-4600-a6fe-bae17d889351 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=23c97043-a6af-4600-a6fe-bae17d889351 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 Snap: cups 2.4.6-4 (stable) Snap.Changes: no changes found Title: package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2020 dmi.bios.release: 15.41 dmi.bios.vendor: Insyde dmi.bios.version: F.41 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 836B dmi.board.vendor: HP dmi.board.version: 46.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 46.24 dmi.modalias: dmi:bvnInsyde:bvrF.41:bd12/01/2020:br15.41:efr46.24:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.24:cvnHP:ct10:cvrChassisVersion:sku2CK98EA#ABE: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Power Laptop 15-cb0xx dmi.product.sku: 2CK98EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/2037349 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037595] Re: _gpgme_io_select breaks when more than 1024 file descriptors are open
** Patch added: "patch for jammy"
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+attachment/5705027/+files/gpgme1.0_1.16.0-1.2ubuntu4.2.debdiff
** Changed in: gpgme1.0 (Ubuntu Focal)
Assignee: (unassigned) => Colin Watson (cjwatson)
** Changed in: gpgme1.0 (Ubuntu Jammy)
Assignee: (unassigned) => Colin Watson (cjwatson)
** Changed in: gpgme1.0 (Ubuntu Focal)
Status: New => In Progress
** Changed in: gpgme1.0 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: gpgme1.0 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: gpgme1.0 (Ubuntu Jammy)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
In Progress
Status in gpgme1.0 source package in Jammy:
In Progress
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is
wrong the package will be pretty broken. On the other hand, that also
means any glaring problems are likely to be caught by the package's
test suite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037595] Re: _gpgme_io_select breaks when more than 1024 file descriptors are open
** Patch added: "patch for focal"
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+attachment/5705026/+files/gpgme1.0_1.13.1-7ubuntu2.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
In Progress
Status in gpgme1.0 source package in Jammy:
In Progress
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from
upstream for a few weeks now, and I'd like to get that SRUed back into
Ubuntu so that we don't accidentally lose this patch in the event of a
security update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is
wrong the package will be pretty broken. On the other hand, that also
means any glaring problems are likely to be caught by the package's
test suite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/2037595/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037595] [NEW] _gpgme_io_select breaks when more than 1024 file descriptors are open
Public bug reported:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that manages
several hundred builders on production. As such, it can often end up
with more than 1024 file descriptors open. It also uses gpgme from time
to time to fetch signing keys for PPAs when dispatching builds that
involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select` is
implemented using select(2), whose manual page says: "WARNING: select()
can monitor only file descriptors numbers that are less than FD_SETSIZE
(1024)—an unreasonably low limit for many modern applications—and this
limitation will not change. All modern applications should instead use
poll(2) or epoll(7), which do not suffer this limitation." This is
exactly the limitation we're running into, resulting in mysterious "Too
many open files" errors despite resource limits being set to more than
comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a similar
problem with older LTSes too, but I only care about it back to focal).
buildd-manager currently runs on focal.
We've been running buildd-manager with a cherry-picked fix from upstream
for a few weeks now, and I'd like to get that SRUed back into Ubuntu so
that we don't accidentally lose this patch in the event of a security
update or similar.
[Test Plan]
William Grant provided this minimal reproducer:
```
root@tmp:~# python3
Python 3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpg
>>> c = gpg.Context()
>>> list(c.keylist())
[]
>>> fs = []
>>> for i in range(1024):
... fs.append(open('/dev/null'))
...
>>> list(c.keylist())
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gpg/core.py", line 751, in keylist
key = self.op_keylist_next()
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1195, in
op_keylist_next
raise excp
File "/usr/lib/python3/dist-packages/gpg/core.py", line 1190, in
op_keylist_next
errorcheck(gpgme.gpgme_op_keylist_next(self.wrapped, ptr))
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: GPGME: Too many open files
```
[Where problems could occur]
`_gpgme_io_select` is pretty central to gpgme, so if something is wrong
the package will be pretty broken. On the other hand, that also means
any glaring problems are likely to be caught by the package's test
suite.
** Affects: gpgme1.0 (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: gpgme1.0 (Ubuntu Focal)
Importance: High
Assignee: Colin Watson (cjwatson)
Status: In Progress
** Affects: gpgme1.0 (Ubuntu Jammy)
Importance: High
Assignee: Colin Watson (cjwatson)
Status: In Progress
** Also affects: gpgme1.0 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: gpgme1.0 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gpgme1.0 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2037595
Title:
_gpgme_io_select breaks when more than 1024 file descriptors are open
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Focal:
In Progress
Status in gpgme1.0 source package in Jammy:
In Progress
Bug description:
[Impact]
Launchpad's buildd-manager is a complex event-driven daemon that
manages several hundred builders on production. As such, it can often
end up with more than 1024 file descriptors open. It also uses gpgme
from time to time to fetch signing keys for PPAs when dispatching
builds that involve PPAs.
On focal (and also on jammy), this breaks because `_gpgme_io_select`
is implemented using select(2), whose manual page says: "WARNING:
select() can monitor only file descriptors numbers that are less than
FD_SETSIZE (1024)—an unreasonably low limit for many modern
applications—and this limitation will not change. All modern
applications should instead use poll(2) or epoll(7), which do not
suffer this limitation." This is exactly the limitation we're running
into, resulting in mysterious "Too many open files" errors despite
resource limits being set to more than comfortable values.
Fortunately, this was fixed upstream in https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=8148237cb4ae20755c06a44d71761c7030973c3d,
and lunar has that fix. focal and jammy do not (there may be a
similar problem with older LTSes too, but I only care about it back to
focal). buildd-manager
[Touch-packages] [Bug 2037569] Re: udev issues with mantic beta
** Also affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Changed in: udisks2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: New Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037569] Re: udev issues with mantic beta
** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: New Status in systemd package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037531] Re: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1
The error in the log is: ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xcd00080, needed 0xeb00080) So this is a problem with perl, as loaded by debconf from the pam maintainer scripts. This is the first report I've ever seen of such a perl problem on upgrade. Do you have any locally installed copies of perl? ** Package changed: pam (Ubuntu) => perl (Ubuntu) ** Changed in: perl (Ubuntu) Importance: Undecided => High ** Changed in: perl (Ubuntu) Status: New => Incomplete -- 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/2037531 Title: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 Status in perl package in Ubuntu: Incomplete Bug description: Doing a release upgrade from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.4.0-11ubuntu2.3 ProcVersionSignature: Ubuntu 5.4.0-163.180-generic 5.4.246 Uname: Linux 5.4.0-163-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Sep 27 11:19:52 2023 DuplicateSignature: package:libpam0g:amd64:1.4.0-11ubuntu2.3 Setting up libpam0g:amd64 (1.4.0-11ubuntu2.3) ... ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xcd00080, needed 0xeb00080) dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-14 (1016 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.0.9 SourcePackage: pam Title: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2037531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
The 6.5.0-6.6 linux kernel in mantic-proposed also fails. -- 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in systemd package in Ubuntu: New Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/452304 -- 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/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037340] Re: Four Screens
** Information type changed from Private Security to Public -- 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/2037340 Title: Four Screens Status in xorg package in Ubuntu: New Bug description: I apologize for any grammar issues, but I can barely see what I am typing. Essentially, when I installed Ubuntu, I had to do so in safe graphics mode, as the screen would otherwise split itself into four different displays that had small amounts of resolution and are rather pale. I managed to install it, but once that happend, and it restarted, it went back to being four screens. I am not sure what to do, as I cannot really read any lines of code. Thank you for your help. I am using an iMac a1311, with an HDD and installed from a flashed usb. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 20:33:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2023-09-24 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac10,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=be40ad74-149a-443c-99b3-2dbae10973a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268CC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268CC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268CC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268CC8:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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/xorg/+bug/2037340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed Status in launchpad-buildd: New Status in init-system-helpers package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in sssd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565 New deb-systemd-invoke added functionality for systemd v250 which ubuntu does not have yet. But it also appears to break postinst calls to deb-systemd-invoke, at least as seen during snap builds in lxd containers operated by launchpad-buildd. I wonder if there is a regression in new code, or new systemd, which may warrant a revert. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sssd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed Status in launchpad-buildd: New Status in init-system-helpers package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in sssd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565 New deb-systemd-invoke added functionality for systemd v250 which ubuntu does not have yet. But it also appears to break postinst calls to deb-systemd-invoke, at least as seen during snap builds in lxd containers operated by launchpad-buildd. I wonder if there is a regression in new code, or new systemd, which may warrant a revert. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed Status in launchpad-buildd: New Status in init-system-helpers package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in sssd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565 New deb-systemd-invoke added functionality for systemd v250 which ubuntu does not have yet. But it also appears to break postinst calls to deb-systemd-invoke, at least as seen during snap builds in lxd containers operated by launchpad-buildd. I wonder if there is a regression in new code, or new systemd, which may warrant a revert. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: init-system-helpers (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed Status in launchpad-buildd: New Status in init-system-helpers package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in sssd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565 New deb-systemd-invoke added functionality for systemd v250 which ubuntu does not have yet. But it also appears to break postinst calls to deb-systemd-invoke, at least as seen during snap builds in lxd containers operated by launchpad-buildd. I wonder if there is a regression in new code, or new systemd, which may warrant a revert. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
As a workaround, I added a `sleep 1` at the end of `_set_available_devices_to_up()` in `scripts/functions` in the Mantic initrd. -- 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/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
I've confirmed this problem on amd64 and ppc64el (https://bugs.launchpad.net/maas/+bug/2037475). ** Summary changed: - mantic arm64 images are failing to deploy with failure to mount root and kernel filesystems + mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems -- 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in systemd package in Ubuntu: New Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037569] [NEW] udev issues with mantic beta
Public bug reported: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... ** Affects: ubuntu-z-systems Importance: High Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: mantic s390x ** Attachment added: "installation_testing.txt" https://bugs.launchpad.net/bugs/2037569/+attachment/5704968/+files/installation_testing.txt ** Also 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: New Status in systemd package in Ubuntu: New Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891165] Re: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed
This was solved for me by doing `apt full-upgrade`. `man apt` describes: `upgrade is used to install available upgrades of all packages currently installed on the system from the, but existing packages will never be removed. If an upgrade for a package requires the remove of an installed package the upgrade for this package isn't performed.` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1891165 Title: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Bug description: I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3 install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is. But i got more errors The following packages have unmet dependencies: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but 3.26.1-2ubuntu1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. sudo ln -sf /usr/bin/python2.7 /usr/bin/python ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 11 20:38:08 2020 InstallationDate: Installed on 2020-02-08 (184 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Confirming the same problem on Razer Blade 16 and Galaxy Book3 pro, both running Arch Linux -- 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
[Touch-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
razer blade 18 2023 is also affected. so is the asus strix 17 -- 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
[Touch-packages] [Bug 2037186] Re: Update cairo to 1.18.0
This bug was fixed in the package cairo - 1.18.0-1 --- cairo (1.18.0-1) unstable; urgency=medium * New upstream release (LP: #2037186) * Drop all patches: applied in new release * debian/libcairo*.symbols: Add new symbols -- Jeremy Bícha Sat, 23 Sep 2023 18:39:51 -0400 ** Changed in: cairo (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/2037186 Title: Update cairo to 1.18.0 Status in cairo package in Ubuntu: Fix Released Bug description: Impact -- Ubuntu 23.10 includes cairo 1.17.8, the final pre-release snapshot of what eventually became the stable 1.18.0. It would be nicer to include the stable release than a beta release. Debian's autopkgtests completed successfully. News https://cairographics.org/news/cairo-1.18.0/ Detailed changelog -- https://gitlab.freedesktop.org/cairo/cairo/-/compare/1.17.8...1.18.0 Why This Didn't Land Sooner -- I was told by cairo upstream developers to expect cairo 1.18.0 in August 2023. It was released September 23 instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/2037186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037531] Re: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/2037531 Title: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 Status in pam package in Ubuntu: New Bug description: Doing a release upgrade from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.4.0-11ubuntu2.3 ProcVersionSignature: Ubuntu 5.4.0-163.180-generic 5.4.246 Uname: Linux 5.4.0-163-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Sep 27 11:19:52 2023 DuplicateSignature: package:libpam0g:amd64:1.4.0-11ubuntu2.3 Setting up libpam0g:amd64 (1.4.0-11ubuntu2.3) ... ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xcd00080, needed 0xeb00080) dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-14 (1016 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.0.9 SourcePackage: pam Title: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2037531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037531] [NEW] package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status
Public bug reported: Doing a release upgrade from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.4.0-11ubuntu2.3 ProcVersionSignature: Ubuntu 5.4.0-163.180-generic 5.4.246 Uname: Linux 5.4.0-163-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Sep 27 11:19:52 2023 DuplicateSignature: package:libpam0g:amd64:1.4.0-11ubuntu2.3 Setting up libpam0g:amd64 (1.4.0-11ubuntu2.3) ... ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xcd00080, needed 0xeb00080) dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-14 (1016 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.0.9 SourcePackage: pam Title: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-09-27 (0 days ago) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages uec-images -- 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/2037531 Title: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 Status in pam package in Ubuntu: New Bug description: Doing a release upgrade from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.4.0-11ubuntu2.3 ProcVersionSignature: Ubuntu 5.4.0-163.180-generic 5.4.246 Uname: Linux 5.4.0-163-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Sep 27 11:19:52 2023 DuplicateSignature: package:libpam0g:amd64:1.4.0-11ubuntu2.3 Setting up libpam0g:amd64 (1.4.0-11ubuntu2.3) ... ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xcd00080, needed 0xeb00080) dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-14 (1016 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.0.9 SourcePackage: pam Title: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2037531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036124] Re: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
There are multiple ways to cut down the initramfs size: Do your devices has a dedicated nvidia graphics card? If not, you could remove the nvidia drivers and cut the initramfs size by half. The zstd compression is faster, but xz produces smaller files. So setting COMPRESS=xz will reduce the initramfs size for you. My test showed a reduction from 203 MB to 153 MB (and build time increase from 7 to 22 seconds). Setting COMPRESS=xz and COMPRESSLEVEL=9 will reduce the size further. On my test to 143 MB (build time 82 seconds). -- 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/2036124 Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~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: Incomplete Bug description: A crash notification popped up when I was not doing anything so I'm not sure what caused it. I hope the automatically-added debug information contains something useful. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Sep 11 00:24:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (704 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-08-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036124/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2013083] Re: libwebp-dev doesn't install CMake configs
This is fixed in Debian sid/testing, will be fixed for mantic if bug: 2037527 is accepted, or to 24.04 otherwise. Setting right now as fix released. ** Changed in: libwebp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2013083 Title: libwebp-dev doesn't install CMake configs Status in libwebp package in Ubuntu: Fix Released Bug description: Libwebp source archive ships Cmake configs. Unlike vcpkg, the Ubuntu package doesn't install them. This prevents client applications from using the recommended find_package(WebP) functionality. Please install the CMake configs along with the pkg-config files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2013083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037527] [NEW] [Ffe] libwebp
Public bug reported: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) ** Affects: libwebp (Ubuntu) Importance: Undecided Assignee: Ubuntu Release Team (ubuntu-release) Status: New ** Changed in: libwebp (Ubuntu) Assignee: (unassigned) => Ubuntu Release Team (ubuntu-release) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2037527 Title: [Ffe] libwebp Status in libwebp package in Ubuntu: New Bug description: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2037527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037509] [NEW] Gnome/Ubuntu desktop wayland
Public bug reported: Good day, I hasten to inform you about a problem that has not left your distribution for several releases in a row. When the Wayland secant is launched, some window elements for control are not active. In particular, the open new tab/settings expand/collapse buttons in browsers and ower applications do not work. Snap and Deb are equally susceptible to this problem. The solution is to login to X11 and immediately log out and log into Wayland again. In the current builds of the Minotaur, the problem appeared quite recently, with the release of the public beta; in the builds for developers, this problem did not occur. I will be very upset if this problem goes into release. Please correct it if possible. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:14:33 2023 InstallationDate: Installed on 2023-06-21 (98 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230620) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2037509 Title: Gnome/Ubuntu desktop wayland Status in ubuntu-meta package in Ubuntu: New Bug description: Good day, I hasten to inform you about a problem that has not left your distribution for several releases in a row. When the Wayland secant is launched, some window elements for control are not active. In particular, the open new tab/settings expand/collapse buttons in browsers and ower applications do not work. Snap and Deb are equally susceptible to this problem. The solution is to login to X11 and immediately log out and log into Wayland again. In the current builds of the Minotaur, the problem appeared quite recently, with the release of the public beta; in the builds for developers, this problem did not occur. I will be very upset if this problem goes into release. Please correct it if possible. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:14:33 2023 InstallationDate: Installed on 2023-06-21 (98 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230620) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention
That's sad. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1628591 Title: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention Status in ifupdown package in Ubuntu: Won't Fix Bug description: The regular expressions used in /etc/network/if-post-down.d/vlan and /etc/network/if-pre-up.d/vlan do not match the name of my network card enp4s0f0. This can be fixed by broadening the regular expression. This is only a problem when the device is a vlan device! See below for the fix that worked on my system. if-pre-up: #!/bin/sh # Most of this stuff is to enable vlans case "$IFACE" in # Ignore any alias (#272891) which uses : *:*) exit 0 ;; vlan0*) vconfig set_name_type VLAN_PLUS_VID VLANID=`echo $IFACE|sed "s/vlan0*//"` ;; vlan*) vconfig set_name_type VLAN_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/vlan0*//"` ;; eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*.0*) vconfig set_name_type DEV_PLUS_VID VLANID=`echo $IFACE|sed "s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.0*//g"` IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"` ;; eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*.*) vconfig set_name_type DEV_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.//g"` IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"` ;; *.0*) # Silently ignore interfaces which we do not (know how to) support [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 vconfig set_name_type DEV_PLUS_VID VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"` ;; *.*) # Silently ignore interfaces which we do not (know how to) support [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 vconfig set_name_type DEV_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"` ;; *) exit 0 ;; esac if [ -n "$IF_VLAN_RAW_DEVICE" ] && [ ! -d /sys/class/net/$IFACE ]; then if [ ! -x /sbin/vconfig ]; then exit 0 fi if ! ip link show dev "$IF_VLAN_RAW_DEVICE" > /dev/null; then echo "$IF_VLAN_RAW_DEVICE does not exist, unable to create $IFACE" exit 1 fi if [ ! -e "/sys/class/net/$IFACE" ]; then ip link set up dev $IF_VLAN_RAW_DEVICE vconfig add $IF_VLAN_RAW_DEVICE $VLANID fi fi # This is not vlan specific, and should actually go somewhere else. if [ -n "$IF_HW_MAC_ADDRESS" ]; then ip link set $IFACE address $IF_HW_MAC_ADDRESS fi if-post-down: #!/bin/sh # If IFACE is an automagic vlan interface (without the vlan-raw-device # parameter) then let's try to discover the magic here.. Another way would be # to just probe for the right device name in /proc/net/vlan case "$IFACE" in # Ignore any alias (#272891) *:*) exit 0 ;; eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*\.0*) IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"` ;; eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*\.*) IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"` ;; # Test for vlan raw device (#196890, #292648) *) [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 ;; esac if [ ! -x /sbin/vconfig ]; then exit 0 fi vconfig rem $IFACE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037497] Re: gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
** Tags added: regression-release -- 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/2037497 Title: gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
