[Touch-packages] [Bug 1983605] Re: exim4 autopkgtest failure on ppc64el with libx11 1.8
** Tags added: rls-kk-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1983605 Title: exim4 autopkgtest failure on ppc64el with libx11 1.8 Status in libx11 package in Ubuntu: New Bug description: I'm just filing a tracker bug for this issue but am not working on it myself. exim4's autopkgtest fails with the new libx11 on kinetic on the ppc64el architecture. https://autopkgtest.ubuntu.com/packages/e/exim4/kinetic/ppc64el This test doesn't fail on Debian. Ubuntu's ppc64el is slightly different than Debian's (we enable -O3 for instance only on that architecture by default). https://ci.debian.net/packages/e/exim4/testing/ppc64el/ This issue is blocking other packages from migrating out of kinetic- proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1983605/+subscriptions -- Mailing list: https://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 1971523] Re: Static build does not work for libmnl (-lmnl)
This bug was fixed in the package libmnl - 1.0.4-3ubuntu1
---
libmnl (1.0.4-3ubuntu1) kinetic; urgency=medium
* Static build does not work for libmnl (-lmnl) (LP: #1971523)
-- Michal Maloszewski Thu, 21 Jul
2022 14:02:16 +0200
** Changed in: libmnl (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl package in Ubuntu:
Fix Released
Status in libmnl source package in Jammy:
Triaged
Status in libmnl package in Debian:
Fix Committed
Bug description:
[Test Case]
$ cat > /tmp/hello.c <
int main() {
printf("Hello world! (and LP: #1971523)\n");
}
EOF
$ gcc -o /tmp/hello /tmp/hello.c -lmnl
(dynamic libs work)
$ gcc -static -o /tmp/hello /tmp/hello.c -lmnl
/usr/bin/ld: cannot find -lmnl: No such file or directory
[Original Report]
My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the
-lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu
22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for
static builds. This is very awkward during the transition 20.04->22.04 when
both should be supported.
I compensated in Ubuntu 20.04 by building netfilter_queue locally;
https://github.com/Nordix/nfqueue-loadbalancer#build
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libmnl0:amd64 1.0.4-3build2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed May 4 07:33:26 2022
InstallationDate: Installed on 2018-09-07 (1334 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: libmnl
UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+subscriptions
--
Mailing list: https://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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
This bug was fixed in the package livecd-rootfs - 2.774 --- livecd-rootfs (2.774) kinetic; urgency=medium * Remove modemmanager and udisks2 from cloud images in addition to fwupd. The use of tasks at install means all packages are marked manually installed in the apt database, so removing fwupd does not remove its dependencies. LP: #1981109. -- Steve Langasek Thu, 04 Aug 2022 11:24:55 -0700 ** Changed in: livecd-rootfs (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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions -- Mailing list: https://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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu Jammy) Status: New => Confirmed -- 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/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Triaged Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Jammy: Confirmed Bug description: With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+subscriptions -- Mailing list: https://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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Triaged Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Jammy: Confirmed Bug description: With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+subscriptions -- Mailing list: https://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 1972939] Re: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes
It appears the issue is resolved in libssl3 3.0.4-1ubuntu1 from kinetic (in addition to enabling the legacy providers) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1972939 Title: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes Status in Release Notes for Ubuntu: New Status in openssl package in Ubuntu: New Status in tinc package in Ubuntu: New Bug description: The tinc included in Jammy (1.0.36-2build1 linked with libssl3) cannot connect to tinc nodes running e.g. tinc from Xenial (1.0.26-1). (Tinc from Impish, which is also v1.0.36-2 but is linked to libssl1.1, can connect to these nodes without problems.) The symptom is a log message (on the system running Jammy) during the metadata channel negotiation (with debug level set to 5): Error during initialisation of cipher from tinc_xenial [...] error:0308010C:digital envelope routines::unsupported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1972939/+subscriptions -- Mailing list: https://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 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.
This bug was fixed in the package apt - 2.5.2 --- apt (2.5.2) unstable; urgency=medium [ Julian Andres Klode ] * Mark broken reverse depends for upgrade (LP: #1974196) * Upgrade all binaries in a source package [ Michael Vogt ] * apt-pkg: (re)export pkgTagSection::Key to fix FTBFS in python-apt (Closes: #1011678) -- Julian Andres Klode Sun, 24 Jul 2022 17:57:24 +0200 ** Changed in: apt (Ubuntu Kinetic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1974196 Title: Installing libudev1 on a new Jammy installation uninstalls many packages. Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Status in apt source package in Kinetic: Fix Released Bug description: [Impact] On an Ubuntu 22.04 desktop system created using the current installation image without enabling package updates over the network, installing the package libudev1 results in a large number of critical packages being removed and rendering the system essentially unusable. [Test plan] Comprehensive regression test suite validating a full solver dump with the issue is run as autopkgtest. [Where problems could occur] We could break other things from resolving. The solver is a bit finicky. Hopefully this is isolated enough. [Other info] https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile which also demonstrates the issue. Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, and then running `apt install libudev1` in the generated image results in The following packages will be REMOVED: libnss-systemd libpam-systemd systemd-timesyncd udev The following packages will be upgraded: libudev1 This is completely prevented by ensuring that updates are installed from the jammy-updates repository before installing any additional packages and that is almost certainly the correct thing to do. But this is a punishing result for such a mistake. I would expect the installation to either force the upgrade of the other systemd packages or refuse to install libudev1 at the incorrect version relative to the other systemd packages until the system is upgraded. We found this out via a user report for ROS 2 Humble which is releasing on top of Ubuntu 22.04 next week: https://github.com/ros2/ros2/issues/1272 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+subscriptions -- Mailing list: https://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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3
Thank you. I will be offline for a few days, so I will upload this next
week.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1981807
Title:
qt5-network openssl3 armhf does not support tls1.3
Status in qtbase-opensource-src package in Ubuntu:
New
Bug description:
lsb_release
Description:Ubuntu 22.04 LTS
Release:22.04
libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf
the qt5 armhf version shipped with ubuntu jammy has a regression in
tls1.3 support (simply missing in runtime).
openssl supports tls1.3, so the underlying library works.
x86_64 is obviously not affected
the short sample applications writes -1 on armhf, 15 on x86_64 (unknown
protocol vs tls1.3)
QSslSocket* s = new QSslSocket();
QSslConfiguration cfg = s->sslConfiguration();
cfg.setProtocol(QSsl::TlsV1_3OrLater);
s->setSslConfiguration(cfg);
s->connectToHostEncrypted("tls13-enabled.server",443);
s->waitForConnected();
printf("%d\n",s->sessionProtocol());
marking it as security since the most secure tls protocol is not used
on some platforms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions
--
Mailing list: https://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 1703821] Re: Dovecot and Apparmor complains at operation file_inherit
** Changed in: apparmor (Ubuntu) Status: Expired => Fix Released -- 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/1703821 Title: Dovecot and Apparmor complains at operation file_inherit Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in apparmor source package in Bionic: Incomplete Status in dovecot source package in Bionic: Fix Released Bug description: [Impact] Users report that while running dovecot there are some issues reported by AppArmor, specifically regarding "file_inherit" operations: Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400 audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit" profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/sbin/dovecot" Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400 audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit" profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/anvil" This is likely caused by an anonymous socket communication channel between dovecot and anvil. A fix in the dovecot AppArmor policy was already merged upstream in commit 1ce8cd21, which is being backported in this SRU. There was a change upstream that renamed the dovecot profile, so it was necessary to make a small change on the backport to reference the correct profile name. [Test Plan] Clone the qa-regression-testing repo https://git.launchpad.net/qa-regression-testing Setup the machine according to the instructions in the README.multipurpose-vm - specifically the Email section. Run the dovecot tests from the qa-regression-testing repo: python3 ./script test-dovecot.py After running the tests, check dmesg for no DENIED messages: dmesg | grep DENIED [Where problems could occur] This update broadens the dovecot policy, so it won't to cause any issues regarding a behavior that was previously allowed and it is now denied. In addition, the dovecot policy is already in complain mode in bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1703821/+subscriptions -- Mailing list: https://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 1703821] Re: Dovecot and Apparmor complains at operation file_inherit
Robie, thank you for taking a look at it. In this case, the user is impacted by noisy logs, since the dovecot profile is in complain mode. That means that AppArmor does not block actions, it only logs them, so that's probably the reason we are not getting more users reporting this. I believe you are correct, perhaps an SRU is not worth it here, not because the user can modify the policy, but because dovecot functionality is not being affected. -- 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/1703821 Title: Dovecot and Apparmor complains at operation file_inherit Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Expired Status in dovecot package in Ubuntu: Fix Released Status in apparmor source package in Bionic: Incomplete Status in dovecot source package in Bionic: Fix Released Bug description: [Impact] Users report that while running dovecot there are some issues reported by AppArmor, specifically regarding "file_inherit" operations: Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400 audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit" profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/sbin/dovecot" Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400 audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit" profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/anvil" This is likely caused by an anonymous socket communication channel between dovecot and anvil. A fix in the dovecot AppArmor policy was already merged upstream in commit 1ce8cd21, which is being backported in this SRU. There was a change upstream that renamed the dovecot profile, so it was necessary to make a small change on the backport to reference the correct profile name. [Test Plan] Clone the qa-regression-testing repo https://git.launchpad.net/qa-regression-testing Setup the machine according to the instructions in the README.multipurpose-vm - specifically the Email section. Run the dovecot tests from the qa-regression-testing repo: python3 ./script test-dovecot.py After running the tests, check dmesg for no DENIED messages: dmesg | grep DENIED [Where problems could occur] This update broadens the dovecot policy, so it won't to cause any issues regarding a behavior that was previously allowed and it is now denied. In addition, the dovecot policy is already in complain mode in bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1703821/+subscriptions -- Mailing list: https://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 1983618] Re: New upstream microrelease 2.5.13
** Description changed: [ Impact ] - * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13. + * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] - * See the list of bugs fixed in this release here: + * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/3PLJDVP7QWTRFHC2GPQTGBLEQFCBUZZ2/ [ Test Plan ] - * Upstream gitlab pipeline results: + * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/pipelines/4504 - * Upstream "call for testing": + * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/RXOSXVLKTIDM4XJUA5EZZ42677JXRHYN/ - * As described in the MRE wiki page for OpenLDAP, the test plan is to + * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in bileto and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. - * Build log (amd64) confirming that the build-time testsuite has been - performed and completed successfully: TBD + * Build log (amd64) confirming that the build-time testsuite has been + performed and completed successfully: https://launchpad.net/~ci-train- + ppa-service/+archive/ubuntu/4887/+build/24250107 - * Bileto ticket: TBD + * Bileto ticket: https://bileto.ubuntu.com/#/ticket/4887 [ Where problems could occur ] - * Upstream tests are always executed during build-time. There are many + * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] - * This is a reoccurring MRE. See below for links to previous OpenLDAP + * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. - * CVEs fixed by this release: -- None. + * CVEs fixed by this release: + - None. Current versions in supported releases that got updates: - openldap | 2.5.12+dfsg-0ubuntu0.22.04.1 | jammy-updates | source + openldap | 2.5.12+dfsg-0ubuntu0.22.04.1 | jammy-updates | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 As usual we test and prep from the PPA and then push through SRU/Security as applicable. ** Tags added: server-todo ** Tags added: needs-mre-backport ** Changed in: openldap (Ubuntu) Milestone: ubuntu-22.08 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1983618 Title: New upstream microrelease 2.5.13 Status in openldap package in Ubuntu: Invalid Status in openldap source package in Jammy: In Progress Bug description: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/3PLJDVP7QWTRFHC2GPQTGBLEQFCBUZZ2/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/pipelines/4504 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/RXOSXVLKTIDM4XJUA5EZZ42677JXRHYN/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in bileto and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: https://launchpad.net/~ci-train- ppa-service/+archive/ubuntu/4887/+build/24250107 * Bileto ticket: https://bileto.ubuntu.com/#/ticket/4887 [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. * CVEs fixed by this release: - None. Current versions in
[Touch-packages] [Bug 1983618] [NEW] New upstream microrelease 2.5.13
Public bug reported: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/3PLJDVP7QWTRFHC2GPQTGBLEQFCBUZZ2/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/pipelines/4504 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/RXOSXVLKTIDM4XJUA5EZZ42677JXRHYN/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in bileto and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: TBD * Bileto ticket: TBD [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. * CVEs fixed by this release: - None. Current versions in supported releases that got updates: openldap | 2.5.12+dfsg-0ubuntu0.22.04.1 | jammy-updates | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 As usual we test and prep from the PPA and then push through SRU/Security as applicable. ** Affects: openldap (Ubuntu) Importance: High Status: Invalid ** Affects: openldap (Ubuntu Jammy) Importance: High Assignee: Sergio Durigan Junior (sergiodj) Status: In Progress ** Also affects: openldap (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: openldap (Ubuntu Jammy) Status: New => In Progress ** Changed in: openldap (Ubuntu Jammy) Importance: Undecided => High ** Changed in: openldap (Ubuntu Jammy) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Changed in: openldap (Ubuntu) Status: In Progress => Invalid ** Changed in: openldap (Ubuntu) Assignee: Sergio Durigan Junior (sergiodj) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1983618 Title: New upstream microrelease 2.5.13 Status in openldap package in Ubuntu: Invalid Status in openldap source package in Jammy: In Progress Bug description: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/3PLJDVP7QWTRFHC2GPQTGBLEQFCBUZZ2/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/pipelines/4504 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/RXOSXVLKTIDM4XJUA5EZZ42677JXRHYN/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in bileto and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: TBD * Bileto ticket: TBD [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. * CVEs fixed by this release: - None. Current versions in supported releases that got updates: openldap | 2.5.12+dfsg-0ubuntu0.22.04.1 | jammy-updates | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 As usual we test and prep from the PPA and then push through SRU/Security as applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1983618/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1952533] Re: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while
I have the same problem. It started late in 2021, I think. I have no damn clue what's going on. Sound often works when booting from "off". It often breaks if I put my laptop to sleep and wake it. It may break at other times? When the sound stops, it stops sound on the whole machine. I have a USB-A to 3.5" headphone adapter and I thought I could use that because it is separate hardware, but, no, that doesn't work either. I've tried blacklisting the snd_hda_codec_realtek module, but it still happens. I've tried installing the original OS (Ubuntu 18.04 from Dell) and it still happens. Maybe I zapped the audio card with static electricity and it stopped working? But why would that affect the USB-A dongle? Maybe there was a firmware update from Dell that changed its behavior? I'm stupified. But I need audio. I love Linux, but I'm thinking of abandoning Linux and going to MacOS, because I need working audio! -- 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/1952533 Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sometimes if I run `pulseaudio -k` a few times, sound returns. Sometimes if I run `sudo alsa force-reload`, sound returns. Sometimes if I shutdown and start the laptop, sound returns. This first occurred a few months ago when I was running 20.04, and I upgraded to 21.10 in the hope it would fix the issue. It did not - sound continues to be intermittent. I use the Brave browser, not firefox. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sheehan3636 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 27 20:21:47 2021 InstallationDate: Installed on 2021-10-15 (43 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated successfully. Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated successfully. Symptom_Type: Sound works for a while, then breaks Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952533/+subscriptions -- Mailing list: https://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 1952533] Re: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1952533 Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sometimes if I run `pulseaudio -k` a few times, sound returns. Sometimes if I run `sudo alsa force-reload`, sound returns. Sometimes if I shutdown and start the laptop, sound returns. This first occurred a few months ago when I was running 20.04, and I upgraded to 21.10 in the hope it would fix the issue. It did not - sound continues to be intermittent. I use the Brave browser, not firefox. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sheehan3636 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 27 20:21:47 2021 InstallationDate: Installed on 2021-10-15 (43 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated successfully. Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated successfully. Symptom_Type: Sound works for a while, then breaks Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952533/+subscriptions -- Mailing list: https://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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3
This is my suggested backport of the upstream patch.
since, as you might know, the file locations changed a bit, lso the file
defining the new datatype moved from qsslsocket_openssl_symbols_p.h to
qsslsocket_openssl_p.h since it is required there (setupOpenSslOptions
is defined there, but qsslsocket_openssl.cpp, which includes
qsslsocket_openssl_p.h includes qsslsocket_openssl_symbols_p.h too late;
this is done differently in qt6 where setupOpenSslOptions is in
qsslcontext_openssl.cpp)
** Patch added: "openssl_set_options.diff"
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+attachment/5607054/+files/openssl_set_options.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1981807
Title:
qt5-network openssl3 armhf does not support tls1.3
Status in qtbase-opensource-src package in Ubuntu:
New
Bug description:
lsb_release
Description:Ubuntu 22.04 LTS
Release:22.04
libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf
the qt5 armhf version shipped with ubuntu jammy has a regression in
tls1.3 support (simply missing in runtime).
openssl supports tls1.3, so the underlying library works.
x86_64 is obviously not affected
the short sample applications writes -1 on armhf, 15 on x86_64 (unknown
protocol vs tls1.3)
QSslSocket* s = new QSslSocket();
QSslConfiguration cfg = s->sslConfiguration();
cfg.setProtocol(QSsl::TlsV1_3OrLater);
s->setSslConfiguration(cfg);
s->connectToHostEncrypted("tls13-enabled.server",443);
s->waitForConnected();
printf("%d\n",s->sessionProtocol());
marking it as security since the most secure tls protocol is not used
on some platforms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions
--
Mailing list: https://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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
** Changed in: livecd-rootfs (Ubuntu) Status: In Progress => Fix Committed -- 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/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Committed Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions -- Mailing list: https://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 1983605] [NEW] exim4 autopkgtest failure on ppc64el with libx11 1.8
Public bug reported: I'm just filing a tracker bug for this issue but am not working on it myself. exim4's autopkgtest fails with the new libx11 on kinetic on the ppc64el architecture. https://autopkgtest.ubuntu.com/packages/e/exim4/kinetic/ppc64el This test doesn't fail on Debian. Ubuntu's ppc64el is slightly different than Debian's (we enable -O3 for instance only on that architecture by default). https://ci.debian.net/packages/e/exim4/testing/ppc64el/ This issue is blocking other packages from migrating out of kinetic- proposed. ** Affects: libx11 (Ubuntu) Importance: High Status: New ** Tags: kinetic update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1983605 Title: exim4 autopkgtest failure on ppc64el with libx11 1.8 Status in libx11 package in Ubuntu: New Bug description: I'm just filing a tracker bug for this issue but am not working on it myself. exim4's autopkgtest fails with the new libx11 on kinetic on the ppc64el architecture. https://autopkgtest.ubuntu.com/packages/e/exim4/kinetic/ppc64el This test doesn't fail on Debian. Ubuntu's ppc64el is slightly different than Debian's (we enable -O3 for instance only on that architecture by default). https://ci.debian.net/packages/e/exim4/testing/ppc64el/ This issue is blocking other packages from migrating out of kinetic- proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1983605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982462] Re: Some modprobe loading services requested by the pstore service fail
I have tested a modified systemd-pstore.service in UC20 (focal based) adding: [Unit] After=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service As a result I get failures in the services trying to load modules for pstore, for instance: ubuntu@ubuntu:~$ sudo systemctl status modprobe@mtdpstore.service ● modprobe@mtdpstore.service - Load Kernel Module mtdpstore Loaded: loaded (/lib/systemd/system/modprobe@.service; static; vendor preset: enabled) Active: inactive (dead) since Thu 2022-08-04 15:59:31 UTC; 25s ago Docs: man:modprobe(8) Process: 400 ExecStart=/sbin/modprobe -abq mtdpstore (code=exited, status=1/FAILURE) Main PID: 400 (code=exited, status=1/FAILURE) Aug 04 15:59:31 ubuntu systemd[1]: modprobe@mtdpstore.service: Succeeded. Aug 04 15:59:31 ubuntu systemd[1]: Finished Load Kernel Module mtdpstore. Which is fine, but there is the potential of too many successive restart of these services, which would result in https://github.com/systemd/systemd/issues/23742. To prevent this, https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1 should be included in the next systemd focal SRU. ** Bug watch added: github.com/systemd/systemd/issues #23742 https://github.com/systemd/systemd/issues/23742 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982462 Title: Some modprobe loading services requested by the pstore service fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] It has been detected that some modprobe services fail on UC22 after the jammy upgrade 249.11-0ubuntu3.4: $ systemctl --system --no-ask-password --no-pager list-units --state=failed Failed units: UNIT LOAD ACTIVE SUBDESCRIPTION ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module chromeos_pstore ● modprobe@efi_pstore.service loaded failed failed Load Kernel Module efi_pstore ● modprobe@mtdpstore.service loaded failed failed Load Kernel Module mtdpstore ● modprobe@pstore_blk.service loaded failed failed Load Kernel Module pstore_blk ● modprobe@pstore_zone.service loaded failed failed Load Kernel Module pstore_zone ● modprobe@ramoops.service loaded failed failed Load Kernel Module ramoops This happens because of some changes to systemd-pstore.service that now has: After=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service This causes too many tries of the modprobe services, that fail in the end with Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service: Start request repeated too quickly. Although we have seen this only on UC22, it potentially can affect classic systems as well, as systemd-pstore.service is re-tried there a few times too. See https://github.com/snapcore/core-base/issues/72 for more details. A fix for this is available upstream: https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1 [Test Plan] Start the device and check that there is no modprobe-pstore related failed service. This is racy, so a few tries will be needed to make sure things are fine. [Where problems could occur] The modprobe services are usually dependencies from other services, so it should be fine if the retry behavior is controlled by those other services. Risk should be small. If something goes wrong we might see a lot of restarts for these services. [Other Info] Testing should happen on UC22 too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
This fix was incomplete; because all of these packages were installed as part of a task (ubuntu-server), they are all marked as manually installed. So additional changes are needed to remove the packages pulled in by fwupd. ** Changed in: livecd-rootfs (Ubuntu) Status: Fix Released => In Progress -- 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/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: In Progress Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions -- Mailing list: https://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 1315559] Re: UpgradeStatus can be incorrect
** Tags added: fr-2590
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1315559
Title:
UpgradeStatus can be incorrect
Status in apport package in Ubuntu:
Triaged
Status in apport source package in Kinetic:
Triaged
Bug description:
In the general hook for ubuntu there is the following code:
log = '/var/log/dist-upgrade/main.log'
if os.path.exists(log):
mtime = os.stat(log).st_mtime
human_mtime = time.strftime('%Y-%m-%d', time.gmtime(mtime))
delta = time.time() - mtime
# Would be nice if this also showed which release was originally
installed
report['UpgradeStatus'] = 'Upgraded to %s on %s (%d days ago)' %
(release_codename, human_mtime, delta / 86400)
else:
report['UpgradeStatus'] = 'No upgrade log present (probably fresh
install)'
This does no checking of main.log to see if the upgrade was actually
successful, so if someone is reporting a bug about a failed upgrade of
ubuntu-release-upgrader they'll have a confusing 'UpgradeStatus' of
today for the previous release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1315559/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
** Tags removed: fr-2591 rls-jj-incoming rls-kk-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: Triaged Bug description: I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu 22.04 - Linux 5.15.0-40-generic - systemd 249.11-0ubuntu3.3 - util-linux 2.37.2-4ubuntu3 This appears on both Ubuntu 22.04 machines that I have (a hardware machine and a VM). To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1979952/+subscriptions -- Mailing list: https://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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
** Tags added: fr-2592 -- 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/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Triaged Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
** Tags added: fr-2591 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: Triaged Bug description: I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu 22.04 - Linux 5.15.0-40-generic - systemd 249.11-0ubuntu3.3 - util-linux 2.37.2-4ubuntu3 This appears on both Ubuntu 22.04 machines that I have (a hardware machine and a VM). To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1979952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Kinetic) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: Triaged Bug description: I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu 22.04 - Linux 5.15.0-40-generic - systemd 249.11-0ubuntu3.3 - util-linux 2.37.2-4ubuntu3 This appears on both Ubuntu 22.04 machines that I have (a hardware machine and a VM). To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1979952/+subscriptions -- Mailing list: https://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 1315559] Re: UpgradeStatus can be incorrect
** Also affects: apport (Ubuntu Kinetic)
Importance: Medium
Status: Triaged
** Tags removed: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1315559
Title:
UpgradeStatus can be incorrect
Status in apport package in Ubuntu:
Triaged
Status in apport source package in Kinetic:
Triaged
Bug description:
In the general hook for ubuntu there is the following code:
log = '/var/log/dist-upgrade/main.log'
if os.path.exists(log):
mtime = os.stat(log).st_mtime
human_mtime = time.strftime('%Y-%m-%d', time.gmtime(mtime))
delta = time.time() - mtime
# Would be nice if this also showed which release was originally
installed
report['UpgradeStatus'] = 'Upgraded to %s on %s (%d days ago)' %
(release_codename, human_mtime, delta / 86400)
else:
report['UpgradeStatus'] = 'No upgrade log present (probably fresh
install)'
This does no checking of main.log to see if the upgrade was actually
successful, so if someone is reporting a bug about a failed upgrade of
ubuntu-release-upgrader they'll have a confusing 'UpgradeStatus' of
today for the previous release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1315559/+subscriptions
--
Mailing list: https://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 1930482] Re: netplan crash on ubuntu 20.04 disabling network
Hi Ruben,
I have tried to reproduce this by duplicating your config as best I can,
but I have not been able to trigger the issue. Can you please try and
provide a minimal reproducer that can be demonstrated on another
machine?
** Changed in: systemd (Ubuntu Focal)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930482
Title:
netplan crash on ubuntu 20.04 disabling network
Status in netplan:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Incomplete
Bug description:
On ubuntu 20.04 with netplan 0.102-0ubuntu1~20.04.2, the server loss
both IPv4 and IPv6 address in a while with DHCP config. The are no way
to restore network, only by rebooting the server.
Trying to restart the server networking using "systemctl restart
systemd-networkd" or "netplan apply" fails.
Note: systemctl and netplay apply fails also with a netplan with
static IP address
The server runs on OVS in cloud.ramnode.com
I'm pasting config, logs, netplan and restart output (IP and mac
address are masked)
I don't see a workaound yet, only to restart server to change the
network configuration.
File: 50-cloud-init.yaml
==
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
accept-ra: true
dhcp4: true
dhcp6: true
match:
macaddress: **:**:**:**:**:**:**
mtu: 1500
set-name: ens3
=
Syslog
=
2021-06-01T19:31:01.063935-04:00 server systemd[1]: Stopped Network Service.
2021-06-01T19:31:01.066766-04:00 server systemd[1]: Starting Network
Service...
2021-06-01T19:31:01.161797-04:00 server systemd-networkd[2302]:
/run/systemd/network/10-netplan-ens3.network: MTUBytes= in [Link] section and
UseMTU= in [DHCP] section are set. Disabling UseMTU=.
2021-06-01T19:31:01.161990-04:00 server systemd-networkd[2302]: loop3456:
netdev ready
2021-06-01T19:31:01.162073-04:00 server systemd-networkd[2302]: Tunnel127:
Gained IPv6LL
2021-06-01T19:31:01.162184-04:00 server systemd-networkd[2302]: Tunnel126:
Gained IPv6LL
2021-06-01T19:31:01.162275-04:00 server systemd-networkd[2302]: loop3456:
Gained IPv6LL
2021-06-01T19:31:01.162349-04:00 server systemd-networkd[2302]: ens3: Gained
IPv6LL
2021-06-01T19:31:01.164685-04:00 server systemd-networkd[2302]: Assertion
'ifindex' failed at src/network/networkd-link.c:757, function link_get().
Aborting.
2021-06-01T19:31:01.553611-04:00 server systemd[1]: systemd-networkd.service:
Main process exited, code=dumped, status=6/ABRT
2021-06-01T19:31:01.553796-04:00 server systemd[1]: systemd-networkd.service:
Failed with result 'core-dump'.
2021-06-01T19:31:01.553892-04:00 server systemd[1]: Failed to start Network
Service.
2021-06-01T19:31:01.553983-04:00 server systemd[1]: systemd-networkd.service:
Scheduled restart job, restart counter is at 2.
output of: netapply --debug try
DEBUG:ens3 not found in {}
DEBUG:loop3456 not found in {}
DEBUG:Merged config:
network:
bridges:
loop3456:
accept-ra: false
addresses:
- 10.65.0.3/32
dhcp4: false
dhcp6: false
interfaces: []
ethernets:
ens3:
accept-ra: true
addresses:
- XXX.XXX.XXX.XXX/24
dhcp4: false
dhcp6: true
gateway4: XXX.XXX.XXX.XXX
match:
macaddress: **:**:**:**:**:**:**
mtu: 1500
nameservers:
addresses:
- 8.8.8.8
- 8.8.4.4
search:
- uc.edu.ve
set-name: ens3
version: 2
DEBUG:New interfaces: set()
** (generate:1484): DEBUG: 20:14:22.895: Processing input file
/etc/netplan/50-static.yaml..
** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
** (generate:1484): DEBUG: 20:14:22.895: Processing input file
/etc/netplan/99-local.yaml..
** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
** (generate:1484): DEBUG: 20:14:22.895: We have some netdefs, pass them
through a final round of validation
** (generate:1484): DEBUG: 20:14:22.895: ens3: setting default backend to 1
** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid
** (generate:1484): DEBUG: 20:14:22.895:
[Touch-packages] [Bug 1974265] Re: `demangle_const` causes infinite recursion and stack overflow
Launchpad has imported 3 comments from the remote bug at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105115. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-03-31T00:32:23+00:00 2019 wrote: Created attachment 52721 output.txt is output of ASAN, and inf-recursion is the poc At commit `b8e92c571baed4e794bd62b7bf417fa8bbaf5c95` of `binutils-gdb`, the given poc can produces crash on `cxxfilt`: build2/binutils/cxxfilt < inf-recursion Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1974265/comments/0 On 2022-05-17T18:22:53+00:00 2019 wrote: Hello, It's already more than one month since my post, and the bug still exists at latest commit (e.i. e84412c6a3c3eed1a4eca5fe18f329bfa7efea40), so I would like to know why it is still `UNCONFIRMED`. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1974265/comments/1 On 2022-05-17T20:44:54+00:00 2019 wrote: The simplified PoC: $ echo _RYAbB2_ | ./binutils/cxxfilt Segmentation fault Root Cause Analysis: 1. In `rust_demangle_callback`, "_R" at beginning causes `rdm.version == 0`[1][2], so `demangle_path` in the else-branch is called[3] with `rdm.sym == "YAbB2_"`, with `rdm.next` field initialized to 0. 2. Next char 'Y' causes `demangle_type` to be called[4] in a switch-case branch, with `rdm.next == 1`. 3. Next char 'A' causes `demangle_type` to be called first[5] to consume char 'b', then `demangle_const` is called[6] with `rdm.next == 3`. 4. Next char 'B' is consumed[7], and "2_" is parsed as `integer_62`[8] to be value 3, and this vlaue is assigned to `rdm.next`, then `demangle_const` is called recursively[9]. However, currently the situation is `rdm.next == 3` again, which is exactly same as last call to `demangle_const`, and this causes infinite recursion. [1] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1356 [2] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1362 [3] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1453 [4] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L759 [5] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L934 [6] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L938 [7] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1151 [8] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1153 [9] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1158 Possible Fix: The infinite recursion check added in this [commit](https://github.com/bminor/binutils- gdb/commit/f10f8617a302f45dae721eae0cd659911f03d864) should also be applied to `demangle_const` Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1974265/comments/2 ** Changed in: binutils Status: Unknown => New ** Changed in: binutils Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1974265 Title: `demangle_const` causes infinite recursion and stack overflow Status in binutils: New Status in binutils package in Ubuntu: New Bug description: Original Post: `https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105115` The bug is similar to CVE-2021-3530, which was reported here: `https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1925348`. Commit: `e84412c6a3c3eed1a4eca5fe18f329bfa7efea40` at `https://github.com/bminor/binutils-gdb`. The simplified PoC: $ echo _RYAbB2_ | ./binutils/cxxfilt Segmentation fault Root Cause Analysis: 1. In `rust_demangle_callback`, "_R" at beginning causes `rdm.version == 0`[1][2], so `demangle_path` in the else-branch is called[3] with `rdm.sym == "YAbB2_"`, with `rdm.next` field initialized to 0. 2. Next char 'Y' causes `demangle_type` to be called[4] in a switch- case branch, with `rdm.next == 1`. 3. Next char 'A' causes `demangle_type` to be called first[5] to consume char 'b', then `demangle_const` is called[6] with `rdm.next == 3`. 4. Next char 'B' is consumed[7], and "2_" is parsed as `integer_62`[8] to be value 3, and
[Touch-packages] [Bug 1974265] Re: `demangle_const` causes infinite recursion and stack overflow
Since the upstream bug is public, I am making this bug public also. ** Bug watch added: GCC Bugzilla #105115 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105115 ** Also affects: binutils via https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105115 Importance: Unknown Status: Unknown ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1974265 Title: `demangle_const` causes infinite recursion and stack overflow Status in binutils: Unknown Status in binutils package in Ubuntu: New Bug description: Original Post: `https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105115` The bug is similar to CVE-2021-3530, which was reported here: `https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1925348`. Commit: `e84412c6a3c3eed1a4eca5fe18f329bfa7efea40` at `https://github.com/bminor/binutils-gdb`. The simplified PoC: $ echo _RYAbB2_ | ./binutils/cxxfilt Segmentation fault Root Cause Analysis: 1. In `rust_demangle_callback`, "_R" at beginning causes `rdm.version == 0`[1][2], so `demangle_path` in the else-branch is called[3] with `rdm.sym == "YAbB2_"`, with `rdm.next` field initialized to 0. 2. Next char 'Y' causes `demangle_type` to be called[4] in a switch- case branch, with `rdm.next == 1`. 3. Next char 'A' causes `demangle_type` to be called first[5] to consume char 'b', then `demangle_const` is called[6] with `rdm.next == 3`. 4. Next char 'B' is consumed[7], and "2_" is parsed as `integer_62`[8] to be value 3, and this vlaue is assigned to `rdm.next`, then `demangle_const` is called recursively[9]. However, currently the situation is `rdm.next == 3` again, which is exactly same as last call to `demangle_const`, and this causes infinite recursion. [1] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1356 [2] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1362 [3] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1453 [4] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L759 [5] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L934 [6] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L938 [7] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1151 [8] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1153 [9] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1158 Possible Fix: The infinite recursion check added in this [commit](https://github.com/bminor/binutils- gdb/commit/f10f8617a302f45dae721eae0cd659911f03d864) should also be applied to `demangle_const` To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1974265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1958055 Title: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP) Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Jammy: New Bug description: [Impact] Running ubuntu-bug as normal user has the correct theme (see screenshots attached to bug #1881640), but running "sudo ubuntu-bug" has a different, non-matching theme (see attached screenshot). This applies to all Qt applications. [Test Plan] This problem can be reproduce by running a KDE application on Ubuntu Desktop (GNOME): 1. Launch ubuntu-22.04-desktop-amd64.iso 2. Install apport-kde 3. Run: /usr/share/apport/apport-kde -f 4. Run: sudo /usr/share/apport/apport-kde -f 5. Compare both windows. They have different icons and font size. Same result with KDE: 1. Use kubuntu-22.04-desktop-amd64.iso 2. Run ubuntu-bug -f 3. Run: sudo ubuntu-bug -f [Analysis] Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme, but XDG_CURRENT_DESKTOP is not in the list of environment variables to preserve (and not in env_keep in /etc/sudoers). On other other hand, sudo preserves the DISPLAY environment variable: $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)' XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 MAIL=/var/mail/root LOGNAME=root USER=root HOME=/root SHELL=/bin/bash [Workaround] Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f [Other Info] This changes was accepted upstream: https://github.com/sudo- project/sudo/pull/165 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:04:24 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1958055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
** Description changed:
+ [Impact]
+
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that does
not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b
(openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background threads
are still running when exit() is called, which can cause SIGSEGV if a
background thread interacts with OpenSSL after/while it has unloaded.
For that reason, we always initialize OpenSSL 1.1.1 with the
OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only has no
effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published into
the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
+
+ [Test Plan]
+
+ The described behavior can be reproduced by passing the
+ OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
+ terminate with a SEGFAULT. More concretely, a minimal reproducer is:
+
+ #include
+ #include
+ #include
+
+ #ifndef OPENSSL_INIT_NO_ATEXIT
+ #define OPENSSL_INIT_NO_ATEXIT 0x0008L
+ #endif
+
+ static void print_error_string()
+ {
+ printf("print_error_string:\n");
+ printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
+ }
+
+ int main(int argc, char* argv[])
+ {
+ // register this handler first, so it runs last.
+ atexit(print_error_string);
+
+ OPENSSL_init_ssl(
+ OPENSSL_INIT_ADD_ALL_CIPHERS |
+ OPENSSL_INIT_ADD_ALL_DIGESTS |
+ OPENSSL_INIT_LOAD_CONFIG |
+ OPENSSL_INIT_NO_ATEXIT |
+ OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
+ OPENSSL_INIT_LOAD_SSL_STRINGS,
+ NULL);
+
+ print_error_string();
+
+ return 0;
+ }
+
+ Building
+
+ $ sudo apt install libssl-dev
+ $ gcc test.c -lssl -lcrypto
+ $ ./a.out
+ print_error_string:
+ ERR_reason_error_string(0) => (null)
+ print_error_string:
+ Segmentation fault (core dumped)
+
+ [Where problems could occur]
+
+ * Think about what the upload changes in the software. Imagine the change is
+wrong or breaks something else: how would this show up?
+
+ * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+
+ * This must '''never''' be "None" or "Low", or entirely an argument as to why
+your upload is low risk.
+
+ * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+
+
+ [Other Info]
+
+ * Anything else you think is useful to include
+ * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
+ * and address these questions in advance
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build intermittently crashes with segfault on Ubuntu 18.04
Status in openssl package in Ubuntu:
New
Status in openssl source package in Bionic:
New
Bug description:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that
does not have support for the OPENSSL_NO_ATEXIT functionality from
1.1.1b (openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background
threads are still running when exit() is called, which can cause
SIGSEGV if a background thread interacts with OpenSSL after/while it
has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with
the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only
has no effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published
into the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
[Test Plan]
The described behavior can be reproduced by passing the
OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
terminate with a SEGFAULT. More concretely, a minimal reproducer is:
#include
#include
#include
#ifndef OPENSSL_INIT_NO_ATEXIT
#define OPENSSL_INIT_NO_ATEXIT 0x0008L
#endif
static void print_error_string()
{
printf("print_error_string:\n");
printf("ERR_reason_error_string(0) =>
[Touch-packages] [Bug 1976233] Re: "File has unexpected size" error on Focal ddebs repository
** Package changed: apt (Ubuntu) => ddeb-retriever ** Changed in: ddeb-retriever Status: Invalid => Confirmed -- 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/1976233 Title: "File has unexpected size" error on Focal ddebs repository Status in ddeb-retriever: Confirmed Bug description: Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865 but affecting Ubuntu 20.04 "Focal" Steps to reproduce: 1. Configure the debug repositories, like how it is explained in https://wiki.ubuntu.com/Debug%20Symbol%20Packages I ran these commands on a newly created Docker container (docker run --pull always --rm -ti ubuntu:20.04), but a typical bare metal installation should present the same issue: apt-get update ; apt-get install --yes gnupg apt-key adv \ --keyserver keyserver.ubuntu.com \ --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 source /etc/lsb-release tee /etc/apt/sources.list.d/ddebs.list >/dev/null
[Touch-packages] [Bug 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)
Uploaded sudo 1.9.10-3ubuntu1 to kinetic and sudo 1.9.9-1ubuntu2.1 to jammy (patch attached). ** Patch added: "sudo_1.9.9-1ubuntu2.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1958055/+attachment/5607012/+files/sudo_1.9.9-1ubuntu2.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1958055 Title: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP) Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Jammy: New Bug description: [Impact] Running ubuntu-bug as normal user has the correct theme (see screenshots attached to bug #1881640), but running "sudo ubuntu-bug" has a different, non-matching theme (see attached screenshot). This applies to all Qt applications. [Test Plan] This problem can be reproduce by running a KDE application on Ubuntu Desktop (GNOME): 1. Launch ubuntu-22.04-desktop-amd64.iso 2. Install apport-kde 3. Run: /usr/share/apport/apport-kde -f 4. Run: sudo /usr/share/apport/apport-kde -f 5. Compare both windows. They have different icons and font size. Same result with KDE: 1. Use kubuntu-22.04-desktop-amd64.iso 2. Run ubuntu-bug -f 3. Run: sudo ubuntu-bug -f [Analysis] Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme, but XDG_CURRENT_DESKTOP is not in the list of environment variables to preserve (and not in env_keep in /etc/sudoers). On other other hand, sudo preserves the DISPLAY environment variable: $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)' XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 MAIL=/var/mail/root LOGNAME=root USER=root HOME=/root SHELL=/bin/bash [Workaround] Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f [Other Info] This changes was accepted upstream: https://github.com/sudo- project/sudo/pull/165 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:04:24 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1958055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)
** Description changed: + [Impact] + Running ubuntu-bug as normal user has the correct theme (see screenshots attached to bug #1881640), but running "sudo ubuntu-bug" has a - different, non-matching theme (see attached screenshot). + different, non-matching theme (see attached screenshot). This applies to + all Qt applications. + + [Test Plan] This problem can be reproduce by running a KDE application on Ubuntu Desktop (GNOME): 1. Launch ubuntu-22.04-desktop-amd64.iso 2. Install apport-kde 3. Run: /usr/share/apport/apport-kde -f 4. Run: sudo /usr/share/apport/apport-kde -f 5. Compare both windows. They have different icons and font size. Same result with KDE: 1. Use kubuntu-22.04-desktop-amd64.iso 2. Run ubuntu-bug -f 3. Run: sudo ubuntu-bug -f [Analysis] Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme, but XDG_CURRENT_DESKTOP is not in the list of environment variables to preserve (and not in env_keep in /etc/sudoers). On other other hand, sudo preserves the DISPLAY environment variable: $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)' XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 MAIL=/var/mail/root LOGNAME=root USER=root HOME=/root SHELL=/bin/bash [Workaround] Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f + [Other Info] + + This changes was accepted upstream: https://github.com/sudo- + project/sudo/pull/165 + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:04:24 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1958055 Title: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP) Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Jammy: New Bug description: [Impact] Running ubuntu-bug as normal user has the correct theme (see screenshots attached to bug #1881640), but running "sudo ubuntu-bug" has a different, non-matching theme (see attached screenshot). This applies to all Qt applications. [Test Plan] This problem can be reproduce by running a KDE application on Ubuntu Desktop (GNOME): 1. Launch ubuntu-22.04-desktop-amd64.iso 2. Install apport-kde 3. Run: /usr/share/apport/apport-kde -f 4. Run: sudo /usr/share/apport/apport-kde -f 5. Compare both windows. They have different icons and font size. Same result with KDE: 1. Use kubuntu-22.04-desktop-amd64.iso 2. Run ubuntu-bug -f 3. Run: sudo ubuntu-bug -f [Analysis] Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme, but XDG_CURRENT_DESKTOP is not in the list of environment variables to preserve (and not in env_keep in /etc/sudoers). On other other hand, sudo preserves the DISPLAY environment variable: $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)' XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 MAIL=/var/mail/root LOGNAME=root USER=root HOME=/root SHELL=/bin/bash [Workaround] Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f [Other Info] This changes was accepted upstream: https://github.com/sudo- project/sudo/pull/165 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:04:24 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1958055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1976233] Re: "File has unexpected size" error on Focal ddebs repository
** Changed in: apt (Ubuntu) Status: Confirmed => Invalid -- 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/1976233 Title: "File has unexpected size" error on Focal ddebs repository Status in apt package in Ubuntu: Invalid Bug description: Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865 but affecting Ubuntu 20.04 "Focal" Steps to reproduce: 1. Configure the debug repositories, like how it is explained in https://wiki.ubuntu.com/Debug%20Symbol%20Packages I ran these commands on a newly created Docker container (docker run --pull always --rm -ti ubuntu:20.04), but a typical bare metal installation should present the same issue: apt-get update ; apt-get install --yes gnupg apt-key adv \ --keyserver keyserver.ubuntu.com \ --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 source /etc/lsb-release tee /etc/apt/sources.list.d/ddebs.list >/dev/null
[Touch-packages] [Bug 1983481] Re: _run_hook called with ui=None
...and I could reproduce it:
```
totem&
killall -11 totem
ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
```
** Changed in: apport (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1983481
Title:
_run_hook called with ui=None
Status in apport package in Ubuntu:
Triaged
Bug description:
When totem crashes and I try to report the crash with ubuntu-bug,
sometimes I get a stack trace:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
jik@jik5:~$
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem-common 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 3 10:35:28 2022
InstallationDate: Installed on 2019-01-02 (1308 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
LogAlsaMixer:
Simple mixer control 'Line',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [15.00dB] [on]
PackageArchitecture: all
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1983481/+subscriptions
--
Mailing list: https://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 1983481] Re: _run_hook called with ui=None
From the stack trace it is clear that _run_hook was called with ui=None
(which is wrong). The followed back the call to at least:
Report.add_hooks_info -> Report._add_hooks_info -> _run_hook
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1983481
Title:
_run_hook called with ui=None
Status in apport package in Ubuntu:
Triaged
Bug description:
When totem crashes and I try to report the crash with ubuntu-bug,
sometimes I get a stack trace:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
jik@jik5:~$
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem-common 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 3 10:35:28 2022
InstallationDate: Installed on 2019-01-02 (1308 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
LogAlsaMixer:
Simple mixer control 'Line',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [15.00dB] [on]
PackageArchitecture: all
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1983481/+subscriptions
--
Mailing list: https://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 1983481] Re: Can't report totem crash with ubuntu-bug
Let untangle the different problem and make this bug report only about
the stack trace. Bug #1983294 seems to be addressed and bug #1972115
will track the requested changed workflow.
** Description changed:
- When totem crashes and I try to report the crash with ubuntu-bug, one of
- two things happens:
-
- 1) Sometimes after the dialog pops up and I click the "Send" button,
- ubuntu-bug immediately exits without doing anything:
-
- jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
- jik@jik5:~$
-
- 2) Sometimes I get a stack trace before it exits:
+ When totem crashes and I try to report the crash with ubuntu-bug,
+ sometimes I get a stack trace:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
- File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
- symb['add_info'](report, ui)
- File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
- response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
+ File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
+ symb['add_info'](report, ui)
+ File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
+ response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
- jik@jik5:~$
-
- Either way, my browser doesn't open to launchpad as it should after
- ubuntu-bug posts a report.
-
- This makes it difficult, to say the least, to report a totem crash
- properly.
+ jik@jik5:~$
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem-common 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 3 10:35:28 2022
InstallationDate: Installed on 2019-01-02 (1308 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
LogAlsaMixer:
- Simple mixer control 'Line',0
-Capabilities: cvolume cvolume-joined cswitch cswitch-joined
-Capture channels: Mono
-Limits: Capture 0 - 15
-Mono: Capture 15 [100%] [15.00dB] [on]
+ Simple mixer control 'Line',0
+ Capabilities: cvolume cvolume-joined cswitch cswitch-joined
+ Capture channels: Mono
+ Limits: Capture 0 - 15
+ Mono: Capture 15 [100%] [15.00dB] [on]
PackageArchitecture: all
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
** Summary changed:
- Can't report totem crash with ubuntu-bug
+ _run_hook called with ui=None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1983481
Title:
_run_hook called with ui=None
Status in apport package in Ubuntu:
New
Bug description:
When totem crashes and I try to report the crash with ubuntu-bug,
sometimes I get a stack trace:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
jik@jik5:~$
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem-common 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 3 10:35:28 2022
InstallationDate: Installed on 2019-01-02 (1308 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
LogAlsaMixer:
Simple mixer control 'Line',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [15.00dB] [on]
PackageArchitecture: all
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
To manage notifications about this bug go to:
[Touch-packages] [Bug 1664844] Re: No distinction between link-up and link-down interfaces
If there are users who would like MAAS to generate netplan yaml with explicit support of optional link down interfaces, please let us know. Closing the issue for now. ** Changed in: maas Status: Triaged => Won't Fix -- 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Won't Fix Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Status in netplan.io source package in Bionic: Won't Fix Status in systemd source package in Bionic: Won't Fix Status in netplan.io source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in netplan.io source package in Groovy: Won't Fix Status in systemd source package in Groovy: Fix Released Status in netplan.io source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [Impact] Since very long, we had a feature request in netplan to determine the activation mode of a given network interface. We got requests to enable marking some interfaces as 'manual', meaning that networkd (or any other backend) would not control its state in any way, requiring the administrator to bring the interface up or down manually. The other request was to mark a interface as 'off', that is: forcing the network interface to always be down until the configuration option isn't changed. This was mainly requested for the networkd backend and requires the new feature of specifying ActivationPolicy= for interfaces, alongside the required netplan changes. This feature is present in systemd 248 - for netplan supported stable series we have decided to cherry-pick and backport this feature on top of current systemd. The networkd feature basically adds the following 5 ActivationPolicy modes: always-down, down, manual, up, always-up. For netplan purposes we only use 'always-down' and 'manual'. The netplan feature, hopefully landing as part of 0.103, is called 'activation-mode' and supports two values: 'manual' and 'off'. [Test Case] For the systemd part: * Bring up a VM test environment with either a dummy interface or an interface that can be safely manipulated. * Upgrade systemd to the -proposed version * For the target interface, create/modify the networkd configuration to include the ActivationPolicy= setting in [Link], for instance: [Match] Name=dummy0 [Network] Address=192.168.10.30/24 Gateway=192.168.10.1 [Link] ActivationPolicy=manual * Try all 5 combinations of ActivationPolicy values: always-down, down, manual, up, always-up - doing `sudo networkctl reload` everytime and checking if the interface behaves as expected. [Where problems could occur] The patchset modifies quite a lot of code in the networkd link handling code paths, so regressions could appear in how networkd manages links - maybe by suddenly certain interfaces not getting brought up as they were before. By code inspection, the implementation defaults to ACTIVATION_POLICY_UP as the default, equivalent to the current behavior, so this risk is small. --- [Original Description] [Old Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Old Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Old Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything
[Touch-packages] [Bug 1971523] Re: Static build does not work for libmnl (-lmnl)
Sure. I am ready to deeply investigate it to make a proper decision.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl package in Ubuntu:
Triaged
Status in libmnl source package in Jammy:
Triaged
Status in libmnl package in Debian:
Fix Committed
Bug description:
[Test Case]
$ cat > /tmp/hello.c <
int main() {
printf("Hello world! (and LP: #1971523)\n");
}
EOF
$ gcc -o /tmp/hello /tmp/hello.c -lmnl
(dynamic libs work)
$ gcc -static -o /tmp/hello /tmp/hello.c -lmnl
/usr/bin/ld: cannot find -lmnl: No such file or directory
[Original Report]
My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the
-lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu
22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for
static builds. This is very awkward during the transition 20.04->22.04 when
both should be supported.
I compensated in Ubuntu 20.04 by building netfilter_queue locally;
https://github.com/Nordix/nfqueue-loadbalancer#build
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libmnl0:amd64 1.0.4-3build2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed May 4 07:33:26 2022
InstallationDate: Installed on 2018-09-07 (1334 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: libmnl
UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+subscriptions
--
Mailing list: https://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 1983566] Re: package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1983565 *** https://bugs.launchpad.net/bugs/1983565 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1983565, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1983565 package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 -- 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/1983566 Title: package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up initramfs-tools (0.136ubuntu6.7) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.187.33) ... update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu6.7) ... update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-firmware initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.33 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 4 11:20:49 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-01 (640 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. X705UDR PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X705UDR.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X705UDR 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:
[Touch-packages] [Bug 1983565] Re: package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1983565 Title: package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up initramfs-tools (0.136ubuntu6.7) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.187.33) ... update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu6.7) ... update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-firmware initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.33 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 4 11:20:49 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-01 (640 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. X705UDR PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X705UDR.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X705UDR 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.:bvrX705UDR.317:bd04/17/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX705UDR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX705UDR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: X705UDR 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/initramfs-tools/+bug/1983565/+subscriptions -- Mailing list: https://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 1983565] [NEW] package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up initramfs-tools (0.136ubuntu6.7) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.187.33) ... update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu6.7) ... update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-firmware initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.33 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 4 11:20:49 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-01 (640 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. X705UDR PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X705UDR.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X705UDR 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.:bvrX705UDR.317:bd04/17/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX705UDR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX705UDR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: X705UDR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ** Attachment added: "unattended-upgrades-dpkg.log" https://bugs.launchpad.net/bugs/1983565/+attachment/5606941/+files/unattended-upgrades-dpkg.log -- 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/1983565 Title: package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up initramfs-tools (0.136ubuntu6.7) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.187.33) ...
[Touch-packages] [Bug 1983566] [NEW] package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1983565 *** https://bugs.launchpad.net/bugs/1983565 Public bug reported: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up initramfs-tools (0.136ubuntu6.7) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.187.33) ... update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu6.7) ... update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-firmware initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.33 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 4 11:20:49 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-01 (640 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. X705UDR PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X705UDR.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X705UDR 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.:bvrX705UDR.317:bd04/17/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX705UDR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX705UDR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: X705UDR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ** Attachment added: "unattended-upgrades-dpkg.log" https://bugs.launchpad.net/bugs/1983566/+attachment/5606966/+files/unattended-upgrades-dpkg.log -- 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/1983566 Title: package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up initramfs-tools (0.136ubuntu6.7) ... update-initramfs:
[Touch-packages] [Bug 1971523] Re: Static build does not work for libmnl (-lmnl)
@Michal
Sponsored for Kinetic, once complete there please have a look at considering an
SRU.
This might be on the brink between fix and feature depending on someones
POV.
Make your own decision and add some arguments for it to the SRU template
(if that is what you go for). Or explain why you decided against it here
on the bug and set the Jammy task to Won't Fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl package in Ubuntu:
Triaged
Status in libmnl source package in Jammy:
Triaged
Status in libmnl package in Debian:
Fix Committed
Bug description:
[Test Case]
$ cat > /tmp/hello.c <
int main() {
printf("Hello world! (and LP: #1971523)\n");
}
EOF
$ gcc -o /tmp/hello /tmp/hello.c -lmnl
(dynamic libs work)
$ gcc -static -o /tmp/hello /tmp/hello.c -lmnl
/usr/bin/ld: cannot find -lmnl: No such file or directory
[Original Report]
My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the
-lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu
22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for
static builds. This is very awkward during the transition 20.04->22.04 when
both should be supported.
I compensated in Ubuntu 20.04 by building netfilter_queue locally;
https://github.com/Nordix/nfqueue-loadbalancer#build
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libmnl0:amd64 1.0.4-3build2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed May 4 07:33:26 2022
InstallationDate: Installed on 2018-09-07 (1334 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: libmnl
UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+subscriptions
--
Mailing list: https://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 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
Joel, thank you very much for your analysis and for posting Debian bug #1016622, as the fix has to be applied in the Debian package. ** Package changed: cups (Ubuntu) => cups-filters (Ubuntu) ** Changed in: cups-filters (Ubuntu) Status: Confirmed => Triaged ** Bug watch added: Debian Bug tracker #1016622 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016622 ** Also affects: cups-filters (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016622 Importance: Unknown Status: Unknown -- 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/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) Status in cups-filters package in Ubuntu: Triaged Status in cups-filters package in Debian: Unknown Bug description: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1897369/+subscriptions -- Mailing list: https://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 1976233] Re: "File has unexpected size" error on Focal ddebs repository
** Tags added: focal -- 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/1976233 Title: "File has unexpected size" error on Focal ddebs repository Status in apt package in Ubuntu: Confirmed Bug description: Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865 but affecting Ubuntu 20.04 "Focal" Steps to reproduce: 1. Configure the debug repositories, like how it is explained in https://wiki.ubuntu.com/Debug%20Symbol%20Packages I ran these commands on a newly created Docker container (docker run --pull always --rm -ti ubuntu:20.04), but a typical bare metal installation should present the same issue: apt-get update ; apt-get install --yes gnupg apt-key adv \ --keyserver keyserver.ubuntu.com \ --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 source /etc/lsb-release tee /etc/apt/sources.list.d/ddebs.list >/dev/null
[Touch-packages] [Bug 1976233] Re: "File has unexpected size" error on Focal ddebs repository
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- 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/1976233 Title: "File has unexpected size" error on Focal ddebs repository Status in apt package in Ubuntu: Confirmed Bug description: Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865 but affecting Ubuntu 20.04 "Focal" Steps to reproduce: 1. Configure the debug repositories, like how it is explained in https://wiki.ubuntu.com/Debug%20Symbol%20Packages I ran these commands on a newly created Docker container (docker run --pull always --rm -ti ubuntu:20.04), but a typical bare metal installation should present the same issue: apt-get update ; apt-get install --yes gnupg apt-key adv \ --keyserver keyserver.ubuntu.com \ --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 source /etc/lsb-release tee /etc/apt/sources.list.d/ddebs.list >/dev/null
[Touch-packages] [Bug 1976233] Re: "File has unexpected size" error on Focal ddebs repository
Release file for focal-updates debug symbols is out of date again curl -I http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages.xz date: Thu, 04 Aug 2022 07:46:41 GMT last-modified: Tue, 02 Aug 2022 13:44:48 GMT curl -I http://ddebs.ubuntu.com/dists/focal-updates/Release last-modified: Wed, 27 Jul 2022 20:48:02 GMT Please, update server content to consistent state. I do not know if it is intentional, but TLS (SSL) certificate is not suitable for the ddebs.ubuntu.com host: curl -I https://ddebs.ubuntu.com/ curl: (60) SSL: no alternative certificate subject name matches target host name 'ddebs.ubuntu.com' -- 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/1976233 Title: "File has unexpected size" error on Focal ddebs repository Status in apt package in Ubuntu: Confirmed Bug description: Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865 but affecting Ubuntu 20.04 "Focal" Steps to reproduce: 1. Configure the debug repositories, like how it is explained in https://wiki.ubuntu.com/Debug%20Symbol%20Packages I ran these commands on a newly created Docker container (docker run --pull always --rm -ti ubuntu:20.04), but a typical bare metal installation should present the same issue: apt-get update ; apt-get install --yes gnupg apt-key adv \ --keyserver keyserver.ubuntu.com \ --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 source /etc/lsb-release tee /etc/apt/sources.list.d/ddebs.list >/dev/null
[Touch-packages] [Bug 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
Had the same issue, the suggestion from Fernando Ruiz (fru1z) fixed my problem as well: Edited /usr/lib/ssl/openssl.cnf And just added to the system_default_sect section Options = UnsafeLegacyRenegotiation I am using Linux Mint 21 (vanessa) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: Expired Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+subscriptions -- Mailing list: https://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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q
** Summary changed: - gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() + gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() -- 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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: New Status in mesa package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
