[Touch-packages] [Bug 413278]
gdb/dwarf: disable per-BFD resource sharing for -readnow objfiles
New in v2:
- Disable sharing only for -readnow objfiles, not all objfiles.
As described in PR 27541, we hit an internal error when loading a binary
the standard way and then loading it with the -readnow option:
$ ./gdb -nx -q --data-directory=data-directory ~/a.out -ex "set confirm
off" -ex "file -readnow ~/a.out"
Reading symbols from /home/simark/a.out...
Reading symbols from ~/a.out...
/home/simark/src/binutils-gdb/gdb/dwarf2/read.c:8098: internal-error:
void create_all_comp_units(dwarf2_per_objfile*): Assertion
`per_objfile->per_bfd->all_comp_units.empty ()' failed.
This is a recurring problem that exposes a design issue in the DWARF
per-BFD sharing feature. Things work well when loading a binary with
the same method (with/without index, with/without readnow) twice in a
row. But they don't work so well when loading a binary with different
methods. See this previous fix, for example:
efb763a5ea35 ("gdb: check for partial symtab presence in
dwarf2_initialize_objfile")
That one handled the case where the first load is normal (uses partial
symbols) and the second load uses an index.
The problem is that when loading an objfile with a method A, we create a
dwarf2_per_bfd and some dwarf2_per_cu_data and initialize them with the
data belonging to that method. When loading another obfile sharing the
same BFD but with a different method B, it's not clear how to re-use the
dwarf2_per_bfd/dwarf2_per_cu_data previously created, because they
contain the data specific to method A. https://komiya-dental.com/
I think the most sensible fix would be to not share a dwarf2_per_bfd
between two objfiles loaded with different methods. That means that two
objfiles sharing the same BFD and loaded the same way would share a
dwarf2_per_bfd. Two objfiles sharing the same BFD but loaded with
different methods would use two different dwarf2_per_bfd structures.
http://www.iu-bloomington.com/
However, this isn't a trivial change. So to fix the known issue quickly
(including in the gdb 10 branch), this patch just disables all
dwarf2_per_bfd sharing for objfiles using READNOW.
Generalize the gdb.base/index-cache-load-twice.exp test to test all
the possible combinations of loading a file with partial symtabs, index
and readnow. Move it to gdb.dwarf2, since it really exercises features
of the DWARF
gdb/dwarf: disable per-BFD resource sharing for -readnow objfiles
https://www.webb-dev.co.uk/
New in v2:
- Disable sharing only for -readnow objfiles, not all objfiles.
As described in PR 27541, we hit an internal error when loading a binary
the standard way and then loading it with the -readnow option:
https://waytowhatsnext.com/
$ ./gdb -nx -q --data-directory=data-directory ~/a.out -ex "set confirm
off" -ex "file -readnow ~/a.out"
Reading symbols from /home/simark/a.out...
Reading symbols from ~/a.out...
/home/simark/src/binutils-gdb/gdb/dwarf2/read.c:8098: internal-error:
void create_all_comp_units(dwarf2_per_objfile*): Assertion
`per_objfile->per_bfd->all_comp_units.empty ()' failed.
http://www.acpirateradio.co.uk/
This is a recurring problem that exposes a design issue in the DWARF
per-BFD sharing feature. Things work well when loading a binary with
the same method (with/without index, with/without readnow) twice in a
row. But they don't work so well when loading a binary with different
methods. See this previous fix, for example: http://www.logoarts.co.uk/
efb763a5ea35 ("gdb: check for partial symtab presence in
dwarf2_initialize_objfile")
That one handled the case where the first load is normal (uses partial
symbols) and the second load uses an index. http://www.slipstone.co.uk/
The problem is that when loading an objfile with a method A, we create a
dwarf2_per_bfd and some dwarf2_per_cu_data and initialize them with the
data belonging to that method. When loading another obfile sharing the
same BFD but with a different method B, it's not clear how to re-use the
dwarf2_per_bfd/dwarf2_per_cu_data previously created, because they
contain the data specific to method A. http://embermanchester.uk/
I think the most sensible fix would be to not share a dwarf2_per_bfd
between two objfiles loaded with different methods. http://connstr.net/
That means that two
objfiles sharing the same BFD and loaded the same way would share a
dwarf2_per_bfd. Two objfiles http://joerg.li/ sharing the same BFD but
loaded with
different methods would use two different dwarf2_per_bfd structures.
http://www.jopspeech.com/
However, this isn't a trivial change. So to fix the known
[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0
The rebuild of protobuf no longer has lto information according to objdump, but the reported version certainly does. The "bad" version was built during hirsute devel, so I took a current hirsute system and systematically downgraded build-deps to the versions in the log of the "bad" build. Turns out, the relevant difference is a couple libs from elfutils: libdw1 and libelf1. If I build protobuf w/ the 0.183-6 versions, I can reproduce the problem. 0.183-8 does not (0.183-7 FTBFS, so could not be tested). Strangely the delta between elfutils 0.183-6 and 0.183-8 appears innocuous - it all looks like packaging cleanup, no changes to upstream source. ** Also affects: elfutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1939413 Title: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Status in elfutils package in Ubuntu: New Status in mozc package in Ubuntu: Invalid Status in protobuf package in Ubuntu: Triaged Bug description: When trying to build package mozc for arm64 the following error popped up: lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux- gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Why does the library contain LTO information at all? Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1939413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943288] Re: Soname change and transition started without a ffe
I've reviewed the history here; libffi8 has been in impish-proposed since June 30. So this is not something that requires a freeze exception, just follow-through on the migration. ** Changed in: libffi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1943288 Title: Soname change and transition started without a ffe Status in libffi package in Ubuntu: Fix Released Bug description: It seems the recent upload includes a soname change and is starting a transition, such changes at the point of the cycle would require a ffe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943288] [NEW] Soname change and transition started without a ffe
Public bug reported: It seems the recent upload includes a soname change and is starting a transition, such changes at the point of the cycle would require a ffe ** Affects: libffi (Ubuntu) Importance: High Status: New ** Tags: block-proposed impish rls-ii-incoming ** Changed in: libffi (Ubuntu) Importance: Undecided => High ** Tags added: impish rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1943288 Title: Soname change and transition started without a ffe Status in libffi package in Ubuntu: New Bug description: It seems the recent upload includes a soname change and is starting a transition, such changes at the point of the cycle would require a ffe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943125] Re: devscripts breaks apt
from my (devscripts) side, no idea. also I have no clue how a command that has || in there can even "return an error code". I'm strongly convinced there is nothing special in devscripts that could cause this, so I'm not considering it a bug in there. ** Changed in: devscripts (Ubuntu) Status: New => 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/1943125 Title: devscripts breaks apt Status in apt package in Ubuntu: New Status in devscripts package in Ubuntu: Invalid Bug description: Hello, devscripts package seem to break apt installs. using following Dockerfile: FROM ubuntu:impish ENV DEBIAN_FRONTEND noninteractive RUN apt-get update -qq && apt-get install -y nano RUN apt-get update -qq && apt-get install -y devscripts RUN apt-get update -qq && apt-get install -y htop docker build -t test . Will break installing "htop" with random post apt install errors: E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true' E: Sub-process returned an error code Excluding devscripts package will solve the issue. Any idears why devscripts is breaking apt? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1943125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943285] [NEW] login screen lagging.
Public bug reported: After boot or logout, login screen slow to appear, and I cannot type in my password for 4 to 5 seconds after login screen has appeared. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Sep 10 21:37:00 2021 InstallationDate: Installed on 2020-05-05 (493 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) LightdmConfig: [Seat:*] autologin-guest=false greeter-show-manual-login=false greeter-session=slick-greeter SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1943285 Title: login screen lagging. Status in lightdm package in Ubuntu: New Bug description: After boot or logout, login screen slow to appear, and I cannot type in my password for 4 to 5 seconds after login screen has appeared. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Sep 10 21:37:00 2021 InstallationDate: Installed on 2020-05-05 (493 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) LightdmConfig: [Seat:*] autologin-guest=false greeter-show-manual-login=false greeter-session=slick-greeter SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1943285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943277] Re: libxml2 2.9.12+dfsg-3 causes regression
** Changed in: libxml2 (Ubuntu)
Assignee: (unassigned) => Mattia Rizzolo (mapreri)
** Changed in: libxml2 (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1943277
Title:
libxml2 2.9.12+dfsg-3 causes regression
Status in libxml2 package in Ubuntu:
Fix Committed
Bug description:
root@i1:~# cat example.xml
fake-name
root@i1:~# cat xml.py
from lxml import etree
def parseXML(xmlFile):
# Parse the xml
with open(xmlFile) as fobj:
xml = fobj.read()
doc = etree.fromstring(xml)
ret = doc.findall('./devices/interface')
node_xml = etree.tostring(ret[0]).decode()
print("node_xml={}".format(node_xml))
if __name__ == "__main__":
parseXML("example.xml")
== Expected result ==
root@i1:~# python3 xml.py
node_xml=
== Actual Result ==
root@i1:~# python3 xml.py
node_xml=
This is broken in 2.9.12+dfsg-3 on impish.
It is not broken in 2.9.10+dfsg-6.3ubuntu0.1 on hirsute.
There are some fixes in master since the 2.9.12 release was cut.
https://gitlab.gnome.org/GNOME/libxml2/-/commits/master
I'm planning to pick all 3 of the following commits from upstream
master since they are all intertwined. With this patches the
regression is fixed.
85b1792e37b131e7a51af98a37f92472e8de5f3f:
Work around lxml API abuse. Make xmlNodeDumpOutput and
htmlNodeDumpFormatOutput work with corrupted parent pointers.
13ad8736d294536da4cbcd70a96b0a2fbf47070c:
Add patch from upstream to fix regression in xmlNodeDumpOutputInternal.
Commit 85b1792e could cause additional whitespace if xmlNodeDump was called
with a non-zero starting level.
92d9ab4c28842a09ca2b76d3ff2f933e01b6cd6f:
Add patch from upstream to fix whitespace when serializing empty HTML
documents.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1943277/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943280] [NEW] OpenLDAP's ufw profile is redundant and can be removed
Public bug reported: The openldap package currently carries its own ufw profile as a delta against its Debian counterpart. Ryan (Debian openldap maintainer) noticed that the ufw package already installs a profile that covers OpenLDAP as well as other related services: https://git.launchpad.net/ufw/tree/profiles/ufw-directoryserver I'm filing this bug to serve as a reminder to make sure that we remove this unnecessary delta from the openldap package. ** Affects: openldap (Ubuntu) Importance: Medium Status: Triaged -- 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/1943280 Title: OpenLDAP's ufw profile is redundant and can be removed Status in openldap package in Ubuntu: Triaged Bug description: The openldap package currently carries its own ufw profile as a delta against its Debian counterpart. Ryan (Debian openldap maintainer) noticed that the ufw package already installs a profile that covers OpenLDAP as well as other related services: https://git.launchpad.net/ufw/tree/profiles/ufw-directoryserver I'm filing this bug to serve as a reminder to make sure that we remove this unnecessary delta from the openldap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1943280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943189] Re: "cannot refresh whilst network offline" bug
Pull request has been merged. https://github.com/PackageKit/PackageKit/pull/506 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1943189 Title: "cannot refresh whilst network offline" bug Status in packagekit package in Ubuntu: New Bug description: In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. Unfortunately, the upstream PackageKit maintainers seem to be unwilling to apply this fix themselves, seeing it as not an issue per https://github.com/PackageKit/PackageKit/issues/336 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943189] Re: "cannot refresh whilst network offline" bug
The packagekit maintainer (Richard Hughes) has requested this patch as a pull request, so this will be in packagekit upstream very, very soon. https://github.com/PackageKit/PackageKit/issues/336#issuecomment-91713 ** Bug watch added: github.com/PackageKit/PackageKit/issues #336 https://github.com/PackageKit/PackageKit/issues/336 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1943189 Title: "cannot refresh whilst network offline" bug Status in packagekit package in Ubuntu: New Bug description: In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. Unfortunately, the upstream PackageKit maintainers seem to be unwilling to apply this fix themselves, seeing it as not an issue per https://github.com/PackageKit/PackageKit/issues/336 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
** Attachment added: "expat_2.4.1-1_amd64.build" https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+attachment/5524437/+files/expat_2.4.1-1_amd64.build ** Summary changed: - Sync expat 2.4.1-1 (main) from Debian experimental (main) + [FFe] Sync expat 2.4.1-1 (main) from Debian experimental (main) ** Description changed: Please sync expat 2.4.1-1 (main) from Debian experimental (main) https://github.com/libexpat/libexpat/blob/R_2_4_1/expat/Changes CVE-2013-0340 https://github.com/libexpat/libexpat/pull/466/files Changelog entries since current impish version 2.3.0-1: expat (2.4.1-1) experimental; urgency=high * New upstream release: - fix CVE-2013-0340: protect against billion laughs attacks (denial-of-service; flavors targeting CPU time or RAM or both, leveraging general entities or parameter entities or both). * Update libexpat1 symbols. -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 +0200 - - Release 2.4.1 Sun May 23 2021 - Bug fixes: - #488 #490 Autotools: Fix installed header expat_config.h for multilib - systems; regression introduced in 2.4.0 by pull request #486 - - Other changes: - #491 #492 Version info bumped from 9:0:8 to 9:1:8; - see https://verbump.de/ for what these numbers do - - Release 2.4.0 Sun May 23 2021 - Security fixes: - #34 #466 #484 CVE-2013-0340/CWE-776 -- Protect against billion laughs attacks - (denial-of-service; flavors targeting CPU time or RAM or both, - leveraging general entities or parameter entities or both) - by tracking and limiting the input amplification factor - ( := ( + ) / ). - By conservative default, amplification up to a factor of 100.0 - is tolerated and rejection only starts after 8 MiB of output bytes - (= + ) have been processed. - The fix adds the following to the API: - - A new error code XML_ERROR_AMPLIFICATION_LIMIT_BREACH to - signals this specific condition. - - Two new API functions .. - - XML_SetBillionLaughsAttackProtectionMaximumAmplification and - - XML_SetBillionLaughsAttackProtectionActivationThreshold - .. to further tighten billion laughs protection parameters - when desired. Please see file "doc/reference.html" for details. - If you ever need to increase the defaults for non-attack XML - payload, please file a bug report with libexpat. - - Two new XML_FEATURE_* constants .. - - that can be queried using the XML_GetFeatureList function, and - - that are shown in "xmlwf -v" output. - - Two new environment variable switches .. - - EXPAT_ACCOUNTING_DEBUG=(0|1|2|3) and - - EXPAT_ENTITY_DEBUG=(0|1) - .. for runtime debugging of accounting and entity processing. - Specific behavior of these values may change in the future. - - Two new command line arguments "-a FACTOR" and "-b BYTES" - for xmlwf to further tighten billion laughs protection - parameters when desired. - If you ever need to increase the defaults for non-attack XML - payload, please file a bug report with libexpat. - - Bug fixes: - #332 #470 For (non-default) compilation with -DEXPAT_MIN_SIZE=ON (CMake) - or CPPFLAGS=-DXML_MIN_SIZE (GNU Autotools): Fix segfault - for UTF-16 payloads containing CDATA sections. - #485 #486 Autotools: Fix generated CMake files for non-64bit and - non-Linux platforms (e.g. macOS and MinGW in particular) - that were introduced with release 2.3.0 - - Other changes: - #468 #469 xmlwf: Improve help output and the xmlwf man page - #463 xmlwf: Improve maintainability through some refactoring - #477 xmlwf: Fix man page DocBook validity - #458 #459 CMake: Support absolute paths for both CMAKE_INSTALL_LIBDIR - and CMAKE_INSTALL_INCLUDEDIR - #471 #481 CMake: Add support for standard variable BUILD_SHARED_LIBS - #457 Unexpose symbol _INTERNAL_trim_to_complete_utf8_characters - #467 Resolve macro HAVE_EXPAT_CONFIG_H - #472 Delete unused legacy helper file "conftools/PrintPath" - #473 #483 Improve attribution - #464 #465 #477 doc/reference.html: Fix XHTML validity - #475 #478 doc/reference.html: Replace the 90s look
[Touch-packages] [Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
** Patch added: "expat_2.4.1-1.debdiff" https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+attachment/5524435/+files/expat_2.4.1-1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1943133 Title: [FFe] Sync expat 2.4.1-1 (main) from Debian experimental (main) Status in expat package in Ubuntu: New Bug description: Please sync expat 2.4.1-1 (main) from Debian experimental (main) https://github.com/libexpat/libexpat/blob/R_2_4_1/expat/Changes CVE-2013-0340 https://github.com/libexpat/libexpat/pull/466/files Changelog entries since current impish version 2.3.0-1: expat (2.4.1-1) experimental; urgency=high * New upstream release: - fix CVE-2013-0340: protect against billion laughs attacks (denial-of-service; flavors targeting CPU time or RAM or both, leveraging general entities or parameter entities or both). * Update libexpat1 symbols. -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
** Attachment added: "expat_2.4.1-1.changelog" https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+attachment/5524436/+files/expat_2.4.1-1.changelog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1943133 Title: [FFe] Sync expat 2.4.1-1 (main) from Debian experimental (main) Status in expat package in Ubuntu: New Bug description: Please sync expat 2.4.1-1 (main) from Debian experimental (main) https://github.com/libexpat/libexpat/blob/R_2_4_1/expat/Changes CVE-2013-0340 https://github.com/libexpat/libexpat/pull/466/files Changelog entries since current impish version 2.3.0-1: expat (2.4.1-1) experimental; urgency=high * New upstream release: - fix CVE-2013-0340: protect against billion laughs attacks (denial-of-service; flavors targeting CPU time or RAM or both, leveraging general entities or parameter entities or both). * Update libexpat1 symbols. -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
This has quite an impact with 264 reverse-depends, so does this security issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1943133 Title: Sync expat 2.4.1-1 (main) from Debian experimental (main) Status in expat package in Ubuntu: New Bug description: Please sync expat 2.4.1-1 (main) from Debian experimental (main) https://github.com/libexpat/libexpat/blob/R_2_4_1/expat/Changes CVE-2013-0340 https://github.com/libexpat/libexpat/pull/466/files Changelog entries since current impish version 2.3.0-1: expat (2.4.1-1) experimental; urgency=high * New upstream release: - fix CVE-2013-0340: protect against billion laughs attacks (denial-of-service; flavors targeting CPU time or RAM or both, leveraging general entities or parameter entities or both). * Update libexpat1 symbols. -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 +0200 Release 2.4.1 Sun May 23 2021 Bug fixes: #488 #490 Autotools: Fix installed header expat_config.h for multilib systems; regression introduced in 2.4.0 by pull request #486 Other changes: #491 #492 Version info bumped from 9:0:8 to 9:1:8; see https://verbump.de/ for what these numbers do Release 2.4.0 Sun May 23 2021 Security fixes: #34 #466 #484 CVE-2013-0340/CWE-776 -- Protect against billion laughs attacks (denial-of-service; flavors targeting CPU time or RAM or both, leveraging general entities or parameter entities or both) by tracking and limiting the input amplification factor ( := ( + ) / ). By conservative default, amplification up to a factor of 100.0 is tolerated and rejection only starts after 8 MiB of output bytes (= + ) have been processed. The fix adds the following to the API: - A new error code XML_ERROR_AMPLIFICATION_LIMIT_BREACH to signals this specific condition. - Two new API functions .. - XML_SetBillionLaughsAttackProtectionMaximumAmplification and - XML_SetBillionLaughsAttackProtectionActivationThreshold .. to further tighten billion laughs protection parameters when desired. Please see file "doc/reference.html" for details. If you ever need to increase the defaults for non-attack XML payload, please file a bug report with libexpat. - Two new XML_FEATURE_* constants .. - that can be queried using the XML_GetFeatureList function, and - that are shown in "xmlwf -v" output. - Two new environment variable switches .. - EXPAT_ACCOUNTING_DEBUG=(0|1|2|3) and - EXPAT_ENTITY_DEBUG=(0|1) .. for runtime debugging of accounting and entity processing. Specific behavior of these values may change in the future. - Two new command line arguments "-a FACTOR" and "-b BYTES" for xmlwf to further tighten billion laughs protection parameters when desired. If you ever need to increase the defaults for non-attack XML payload, please file a bug report with libexpat. Bug fixes: #332 #470 For (non-default) compilation with -DEXPAT_MIN_SIZE=ON (CMake) or CPPFLAGS=-DXML_MIN_SIZE (GNU Autotools): Fix segfault for UTF-16 payloads containing CDATA sections. #485 #486 Autotools: Fix generated CMake files for non-64bit and non-Linux platforms (e.g. macOS and MinGW in particular) that were introduced with release 2.3.0 Other changes: #468 #469 xmlwf: Improve help output and the xmlwf man page #463 xmlwf: Improve maintainability through some refactoring #477 xmlwf: Fix man page DocBook validity #458 #459 CMake: Support absolute paths for both CMAKE_INSTALL_LIBDIR and CMAKE_INSTALL_INCLUDEDIR #471 #481 CMake: Add support for standard variable BUILD_SHARED_LIBS #457 Unexpose symbol _INTERNAL_trim_to_complete_utf8_characters #467 Resolve macro HAVE_EXPAT_CONFIG_H #472 Delete unused legacy helper file "conftools/PrintPath" #473 #483 Improve attribution #464 #465 #477 doc/reference.html: Fix XHTML validity #475 #478
[Touch-packages] [Bug 1943277] [NEW] libxml2 2.9.12+dfsg-3 causes regression
Public bug reported:
root@i1:~# cat example.xml
fake-name
root@i1:~# cat xml.py
from lxml import etree
def parseXML(xmlFile):
# Parse the xml
with open(xmlFile) as fobj:
xml = fobj.read()
doc = etree.fromstring(xml)
ret = doc.findall('./devices/interface')
node_xml = etree.tostring(ret[0]).decode()
print("node_xml={}".format(node_xml))
if __name__ == "__main__":
parseXML("example.xml")
== Expected result ==
root@i1:~# python3 xml.py
node_xml=
== Actual Result ==
root@i1:~# python3 xml.py
node_xml=
This is broken in 2.9.12+dfsg-3 on impish.
It is not broken in 2.9.10+dfsg-6.3ubuntu0.1 on hirsute.
There are some fixes in master since the 2.9.12 release was cut.
https://gitlab.gnome.org/GNOME/libxml2/-/commits/master
I'm planning to pick all 3 of the following commits from upstream master
since they are all intertwined. With this patches the regression is
fixed.
85b1792e37b131e7a51af98a37f92472e8de5f3f:
Work around lxml API abuse. Make xmlNodeDumpOutput and htmlNodeDumpFormatOutput
work with corrupted parent pointers.
13ad8736d294536da4cbcd70a96b0a2fbf47070c:
Add patch from upstream to fix regression in xmlNodeDumpOutputInternal. Commit
85b1792e could cause additional whitespace if xmlNodeDump was called with a
non-zero starting level.
92d9ab4c28842a09ca2b76d3ff2f933e01b6cd6f:
Add patch from upstream to fix whitespace when serializing empty HTML documents.
** Affects: libxml2 (Ubuntu)
Importance: High
Status: Triaged
** Summary changed:
- libxml2 causes regression in python3-lxml2
+ libxml2 2.9.12+dfsg-3 causes regression
** Description changed:
- root@i1:~# cat example.xml
+ root@i1:~# cat example.xml
- fake-name
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+ fake-name
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
- root@i1:~# cat xml.py
+ root@i1:~# cat xml.py
from lxml import etree
def parseXML(xmlFile):
- # Parse the xml
- with open(xmlFile) as fobj:
- xml = fobj.read()
+ # Parse the xml
+ with open(xmlFile) as fobj:
+ xml = fobj.read()
- doc = etree.fromstring(xml)
- ret = doc.findall('./devices/interface')
- node_xml = etree.tostring(ret[0]).decode()
- print("node_xml={}".format(node_xml))
+ doc = etree.fromstring(xml)
+ ret = doc.findall('./devices/interface')
+ node_xml = etree.tostring(ret[0]).decode()
+ print("node_xml={}".format(node_xml))
if __name__ == "__main__":
- parseXML("example.xml")
+ parseXML("example.xml")
+ == Expected result ==
- Expected result:
+ root@i1:~# python3 xml.py
+ node_xml=
+
+
+
+
+
+
+
+
+
+
- root@i1:~# python3 xml.py
+ == Actual Result ==
+
+ root@i1:~# python3 xml.py
node_xml=
-
-
-
-
-
-
-
-
-
-
-
- Actual Result:
-
- root@i1:~# python3 xml.py
- node_xml=
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
This is broken in 2.9.12+dfsg-3 on impish.
It is not broken in 2.9.10+dfsg-6.3ubuntu0.1 on hirsute.
There are some fixes in master since the 2.9.12 release was cut.
https://gitlab.gnome.org/GNOME/libxml2/-/commits/master
I'm planning to pick all 3 of these from upstream master since they are all
intertwined. With this patches the regression is fixed.
85b1792e37b131e7a51af98a37f92472e8de5f3f:
Work around lxml API abuse. Make xmlNodeDumpOutput and
htmlNodeDumpFormatOutput work with corrupted parent pointers.
13ad8736d294536da4cbcd70a96b0a2fbf47070c:
Add patch from upstream to fix regression in xmlNodeDumpOutputInternal.
Commit 85b1792e could cause additional whitespace if xmlNodeDump was called
with a non-zero starting level.
92d9ab4c28842a09ca2b76d3ff2f933e01b6cd6f:
Add patch from upstream to fix whitespace when serializing empty HTML
documents.
** Description changed:
root@i1:~# cat example.xml
fake-name
root@i1:~# cat xml.py
from lxml import etree
def parseXML(xmlFile):
# Parse the xml
with open(xmlFile) as fobj:
xml = fobj.read()
doc = etree.fromstring(xml)
ret = doc.findall('./devices/interface')
node_xml = etree.tostring(ret[0]).decode()
[Touch-packages] [Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
** Description changed: Please sync expat 2.4.1-1 (main) from Debian experimental (main) Changelog entries since current impish version 2.3.0-1: expat (2.4.1-1) experimental; urgency=high - * New upstream release: - - fix CVE-2013-0340: protect against billion laughs attacks - (denial-of-service; flavors targeting CPU time or RAM or both, - leveraging general entities or parameter entities or both). - * Update libexpat1 symbols. + * New upstream release: + - fix CVE-2013-0340: protect against billion laughs attacks + (denial-of-service; flavors targeting CPU time or RAM or both, + leveraging general entities or parameter entities or both). + * Update libexpat1 symbols. - -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 + -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 +0200 + + + Release 2.4.1 Sun May 23 2021 + Bug fixes: +#488 #490 Autotools: Fix installed header expat_config.h for multilib + systems; regression introduced in 2.4.0 by pull request #486 + + Other changes: +#491 #492 Version info bumped from 9:0:8 to 9:1:8; + see https://verbump.de/ for what these numbers do + + + Release 2.4.0 Sun May 23 2021 + Security fixes: +#34 #466 #484 CVE-2013-0340/CWE-776 -- Protect against billion laughs attacks + (denial-of-service; flavors targeting CPU time or RAM or both, + leveraging general entities or parameter entities or both) + by tracking and limiting the input amplification factor + ( := ( + ) / ). + By conservative default, amplification up to a factor of 100.0 + is tolerated and rejection only starts after 8 MiB of output bytes + (= + ) have been processed. + The fix adds the following to the API: + - A new error code XML_ERROR_AMPLIFICATION_LIMIT_BREACH to + signals this specific condition. + - Two new API functions .. + - XML_SetBillionLaughsAttackProtectionMaximumAmplification and + - XML_SetBillionLaughsAttackProtectionActivationThreshold + .. to further tighten billion laughs protection parameters + when desired. Please see file "doc/reference.html" for details. + If you ever need to increase the defaults for non-attack XML + payload, please file a bug report with libexpat. + - Two new XML_FEATURE_* constants .. + - that can be queried using the XML_GetFeatureList function, and + - that are shown in "xmlwf -v" output. + - Two new environment variable switches .. + - EXPAT_ACCOUNTING_DEBUG=(0|1|2|3) and + - EXPAT_ENTITY_DEBUG=(0|1) + .. for runtime debugging of accounting and entity processing. + Specific behavior of these values may change in the future. + - Two new command line arguments "-a FACTOR" and "-b BYTES" + for xmlwf to further tighten billion laughs protection + parameters when desired. + If you ever need to increase the defaults for non-attack XML + payload, please file a bug report with libexpat. + + Bug fixes: +#332 #470 For (non-default) compilation with -DEXPAT_MIN_SIZE=ON (CMake) + or CPPFLAGS=-DXML_MIN_SIZE (GNU Autotools): Fix segfault + for UTF-16 payloads containing CDATA sections. +#485 #486 Autotools: Fix generated CMake files for non-64bit and + non-Linux platforms (e.g. macOS and MinGW in particular) + that were introduced with release 2.3.0 + + Other changes: +#468 #469 xmlwf: Improve help output and the xmlwf man page + #463 xmlwf: Improve maintainability through some refactoring + #477 xmlwf: Fix man page DocBook validity +#458 #459 CMake: Support absolute paths for both CMAKE_INSTALL_LIBDIR + and CMAKE_INSTALL_INCLUDEDIR +#471 #481 CMake: Add support for standard variable BUILD_SHARED_LIBS + #457 Unexpose symbol _INTERNAL_trim_to_complete_utf8_characters + #467 Resolve macro HAVE_EXPAT_CONFIG_H + #472 Delete unused legacy helper file "conftools/PrintPath" +#473 #483 Improve attribution + #464 #465 #477 doc/reference.html: Fix XHTML validity +#475 #478 doc/reference.html: Replace the 90s look by OK.css + #479 Version info bumped from 8:0:7 to 9:0:8 + due to addition of new symbols and
[Touch-packages] [Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
Per our discussion in IRC given where we are in the release cycle this would require a Feature Freeze Exception. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1943133 Title: Sync expat 2.4.1-1 (main) from Debian experimental (main) Status in expat package in Ubuntu: New Bug description: Please sync expat 2.4.1-1 (main) from Debian experimental (main) Changelog entries since current impish version 2.3.0-1: expat (2.4.1-1) experimental; urgency=high * New upstream release: - fix CVE-2013-0340: protect against billion laughs attacks (denial-of-service; flavors targeting CPU time or RAM or both, leveraging general entities or parameter entities or both). * Update libexpat1 symbols. -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939751] Re: openssh FTBFS with glibc >= 2.34
*** This bug is a duplicate of bug 1941799 *** https://bugs.launchpad.net/bugs/1941799 ** This bug has been marked a duplicate of bug 1941799 Please merge openssh 1:8.4p1-6 from Debian unstable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1939751 Title: openssh FTBFS with glibc >= 2.34 Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: Fix Released Bug description: Due to an incompatible function prototype in openbsd-compat tests, this package FTBFS with glibc >= 2.34. There is an upstream patch already in place to address this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1939751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
I'm unsubscribing sponsors since this has been uploaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1941799 Title: Please merge openssh 1:8.4p1-6 from Debian unstable Status in openssh package in Ubuntu: In Progress Bug description: This merge is needed because there are changes in Ubuntu that are not present in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943268] [NEW] battery not charging and shows estimating only
Public bug reported: ubuntu 20.04 LTS after updating software a problem of battery not charging appeared. Even thoughc harger is still pluged in, icon on battery shows estimating only. Now there is 0 percent charge and can only be run by direct charging only. ** Affects: upower (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1943268 Title: battery not charging and shows estimating only Status in upower package in Ubuntu: New Bug description: ubuntu 20.04 LTS after updating software a problem of battery not charging appeared. Even thoughc harger is still pluged in, icon on battery shows estimating only. Now there is 0 percent charge and can only be run by direct charging only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1943268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942623] Re: [Wishlist] systemctl CLI UI should allow glob expansion throughout the service name
** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1942623 Title: [Wishlist] systemctl CLI UI should allow glob expansion throughout the service name Status in systemd package in Ubuntu: Invalid Bug description: When attempting to craft a command to query and/or restart all services with name 'something-*-else', such as 'neutron-*-agent' to match [neutron-l3-agent, neutron-openvswitch-agent, and neutron-dhcp- agent], I've found that no services are returned from globs in the middle of the string. The only supported glob seems to be a * at the end of the service name. Also, single character globbing with ? is not honored (as in the last example). To provide an example, I expect each of these commands to return the dbus.socket and dbus.service, but only 'systemctl status dbu*' shows the proper return. drew@grimoire:~$ systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static) Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 1357 (dbus-daemon) Tasks: 1 (limit: 57290) Memory: 4.9M CGroup: /system.slice/dbus.service └─1357 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only Warning: some journal files were not opened due to insufficient permissions. drew@grimoire:~$ systemctl status *bus drew@grimoire:~$ systemctl status '*bus' drew@grimoire:~$ systemctl status 'dbu*' ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static) Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 1357 (dbus-daemon) Tasks: 1 (limit: 57290) Memory: 5.0M CGroup: /system.slice/dbus.service └─1357 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only Warning: some journal files were not opened due to insufficient permissions. ● dbus.socket - D-Bus System Message Bus Socket Loaded: loaded (/lib/systemd/system/dbus.socket; static) Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago Triggers: ● dbus.service Listen: /run/dbus/system_bus_socket (Stream) drew@grimoire:~$ systemctl status 'db*s' drew@grimoire:~$ systemctl status 'dbu?' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Merge proposal linked: https://code.launchpad.net/~vorlon/ubuntu-seeds/+git/platform/+merge/408418 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Incomplete Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Incomplete Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error
[Touch-packages] [Bug 1943251] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Apparently I was out of space on my /boot partition. Maybe a more descriptive error message? -- 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/1943251 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 - I do have SecureBoot enabled Status in initramfs-tools package in Ubuntu: New Bug description: I have Secure Boot enabled. The MOK key is already configured in the EFI. Have VMware Workstation installed and signed the modules so that would work. Not sure what initramfs is trying to do. I didn't kick anything off, this ran by itself in the background and just popped up with a warning. So I don't know if it is involved with Secure Boot, or if initramfs needs to sign a new image when it creates one, but the MOK key is there in the right place so it should be able to do so if it needs to. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 10 07:43:46 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-05 (5 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1943251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943261] Re: Wrong decoding of accented characters
** Attachment added: "Swiss QR bill with QR code with accents" https://bugs.launchpad.net/ubuntu/+source/zbar/+bug/1943261/+attachment/5524424/+files/swissqr_bill.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zbar in Ubuntu. https://bugs.launchpad.net/bugs/1943261 Title: Wrong decoding of accented characters Status in zbar package in Ubuntu: New Bug description: When decoding a QR code containing latin accented characters, the output text uses the wrong encoding and outputs some Asian characters. Attached is an example image (from this page showing a sample of a Swiss QR bill : https://developer.pdf4me.com/docs/api/swiss-qr/), and a cropped version with only the QR code itself. The text output by zbarimg swissqr_bill-qrcode.jpg shows : H繹rnlistrasse # on line 7 Pf瓣ffikon # on line 10 T繹distrasse # on line 23 Z羹rich# on line 26 instead of : Hörnlistrasse Pfäffikon Tödistrasse Zürich $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ zbarimg --version 0.23 $ dpkg -l | grep zbar ii libzbar0:amd640.23-1.3 amd64 QR code / bar code scanner and decoder (library) ii libzbargtk0:amd64 0.23-1.3 amd64 QR code / bar code scanner and decoder (GTK+ bindings) ii python3-zbar:amd640.23-1.3 amd64 QR code / bar code scanner and decoder (Python bindings) ii zbar-tools0.23-1.3 amd64 QR code / bar code scanner and decoder (utilities) ii zbarcam-gtk 0.23-1.3 amd64 QR code / bar code scanner and decoder (Gtk camera tool) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zbar/+bug/1943261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943261] [NEW] Wrong decoding of accented characters
Public bug reported: When decoding a QR code containing latin accented characters, the output text uses the wrong encoding and outputs some Asian characters. Attached is an example image (from this page showing a sample of a Swiss QR bill : https://developer.pdf4me.com/docs/api/swiss-qr/), and a cropped version with only the QR code itself. The text output by zbarimg swissqr_bill-qrcode.jpg shows : H繹rnlistrasse # on line 7 Pf瓣ffikon # on line 10 T繹distrasse # on line 23 Z羹rich# on line 26 instead of : Hörnlistrasse Pfäffikon Tödistrasse Zürich $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ zbarimg --version 0.23 $ dpkg -l | grep zbar ii libzbar0:amd640.23-1.3 amd64 QR code / bar code scanner and decoder (library) ii libzbargtk0:amd64 0.23-1.3 amd64 QR code / bar code scanner and decoder (GTK+ bindings) ii python3-zbar:amd640.23-1.3 amd64 QR code / bar code scanner and decoder (Python bindings) ii zbar-tools0.23-1.3 amd64 QR code / bar code scanner and decoder (utilities) ii zbarcam-gtk 0.23-1.3 amd64 QR code / bar code scanner and decoder (Gtk camera tool) ** Affects: zbar (Ubuntu) Importance: Undecided Status: New ** Tags: encoding ** Attachment added: "qr-code with accented chars" https://bugs.launchpad.net/bugs/1943261/+attachment/5524423/+files/swissqr_bill-qrcode.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zbar in Ubuntu. https://bugs.launchpad.net/bugs/1943261 Title: Wrong decoding of accented characters Status in zbar package in Ubuntu: New Bug description: When decoding a QR code containing latin accented characters, the output text uses the wrong encoding and outputs some Asian characters. Attached is an example image (from this page showing a sample of a Swiss QR bill : https://developer.pdf4me.com/docs/api/swiss-qr/), and a cropped version with only the QR code itself. The text output by zbarimg swissqr_bill-qrcode.jpg shows : H繹rnlistrasse # on line 7 Pf瓣ffikon # on line 10 T繹distrasse # on line 23 Z羹rich# on line 26 instead of : Hörnlistrasse Pfäffikon Tödistrasse Zürich $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ zbarimg --version 0.23 $ dpkg -l | grep zbar ii libzbar0:amd640.23-1.3 amd64 QR code / bar code scanner and decoder (library) ii libzbargtk0:amd64 0.23-1.3 amd64 QR code / bar code scanner and decoder (GTK+ bindings) ii python3-zbar:amd640.23-1.3 amd64 QR code / bar code scanner and decoder (Python bindings) ii zbar-tools0.23-1.3 amd64 QR code / bar code scanner and decoder (utilities) ii zbarcam-gtk 0.23-1.3 amd64 QR code / bar code scanner and decoder (Gtk camera tool) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zbar/+bug/1943261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
similar problem with Gthumb 3.11 and exiv2 0.27.3-3ubuntu1.5 on Ubuntu 21.04 and jpg generated with darktable. gthumb crash: terminate called after throwing an instance of 'std::out_of_range' what(): basic_string:At __n (which is 19) >= this->size() (which is 19) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
We do now have an upstream patch/PR: https://github.com/systemd/systemd/pull/20705 It's not much different from what was already landed in the systemd package (skipping the test in this scenario). So we should probably only stage it for the next systemd upload, after it was merged upstream. -- 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/1942113 Title: systemd unit test regression in autopkgtest (oomd-utils) Status in systemd: Unknown Status in glibc package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The latest systemd upload fails its tests against glibc 2.34. The failing test is test-oomd-util within the unit-tests, with the following logs: Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a Got message type=method_return sender=:1.0 destination=:1.23 path=n/a interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a error-message=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.23 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. Got message type=signal sender=:1.0 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=304 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a Got result done/Success for job test-oomd-util-9beb716b2ffb3d99.scope Bus n/a: changing state RUNNING → CLOSED Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy test-oomd-util: Cannot set user xattrs, skipping tests. Error getting memory.current from /system.slice/test-oomd-util-9beb716b2ffb3d99.scope: No data available Assertion 'oomd_cgroup_context_acquire(cgroup, ) == 0' failed at src/oom/test-oomd-util.c:117, function test_oomd_cgroup_context_acquire_and_insert(). Aborting. I wasn't able to reproduce the failure, either using autopkgtest-virt- lxd or manually in an armhf VM. You'll find below the test logs of the VM run for this particular test, as a comparison point. ubuntu@autopkgtest:~$ sudo /usr/lib/systemd/tests/test-oomd-util Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last
[Touch-packages] [Bug 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
** Also affects: glibc via https://github.com/systemd/systemd/issues/20593 Importance: Unknown Status: Unknown ** Project changed: glibc => systemd -- 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/1942113 Title: systemd unit test regression in autopkgtest (oomd-utils) Status in systemd: Unknown Status in glibc package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The latest systemd upload fails its tests against glibc 2.34. The failing test is test-oomd-util within the unit-tests, with the following logs: Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a Got message type=method_return sender=:1.0 destination=:1.23 path=n/a interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a error-message=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.23 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. Got message type=signal sender=:1.0 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=304 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a Got result done/Success for job test-oomd-util-9beb716b2ffb3d99.scope Bus n/a: changing state RUNNING → CLOSED Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy test-oomd-util: Cannot set user xattrs, skipping tests. Error getting memory.current from /system.slice/test-oomd-util-9beb716b2ffb3d99.scope: No data available Assertion 'oomd_cgroup_context_acquire(cgroup, ) == 0' failed at src/oom/test-oomd-util.c:117, function test_oomd_cgroup_context_acquire_and_insert(). Aborting. I wasn't able to reproduce the failure, either using autopkgtest-virt- lxd or manually in an armhf VM. You'll find below the test logs of the VM run for this particular test, as a comparison point. ubuntu@autopkgtest:~$ sudo /usr/lib/systemd/tests/test-oomd-util Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET →
[Touch-packages] [Bug 1943251] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools 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/1943251 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 - I do have SecureBoot enabled Status in initramfs-tools package in Ubuntu: New Bug description: I have Secure Boot enabled. The MOK key is already configured in the EFI. Have VMware Workstation installed and signed the modules so that would work. Not sure what initramfs is trying to do. I didn't kick anything off, this ran by itself in the background and just popped up with a warning. So I don't know if it is involved with Secure Boot, or if initramfs needs to sign a new image when it creates one, but the MOK key is there in the right place so it should be able to do so if it needs to. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 10 07:43:46 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-05 (5 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1943251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
Unfortunately, it doesn't seem to be the same bug, but might be similar.
I can still reporduce the issue with the upstream daily-build.
I can reproduce it on an Ubuntu Impish host (kernel 5.11.0-31-generic, systemd
248.3-1ubuntu3), running an Ubuntu Impish container (kernel 5.11.0-31-generic,
systemd 249.743.g8fd4d27f3c+21.10.20210909132725 – daily upstream build from
[ppa:ubuntu-support-team/systemd](https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/systemd))
– or basically any container that uses the unified cgroups hierarchy (like
Fedora 34, as mentioned before).
Interestingly, in other places that try to read `memory.current`
(cgtop.c/cgroup.c) there is a fallback to `memory.usage_in_bytes` if the
system does not detect an all unified hierarchy. But those seem to be
mutually exclusive:
On a host using the **hybrid** hierarchy I can only see `memory.usage_in_bytes`
(same goes for hybrid container on hybrid host):
```
$ find /sys/fs/cgroup/ -wholename *system.slice/memory.current
$ find /sys/fs/cgroup/ -wholename *system.slice/memory.usage_in_bytes
/sys/fs/cgroup/memory/system.slice/memory.usage_in_bytes
```
=> Tests are skipped ("test-oomd-util: cgroups are not running in unified mode,
skipping tests.")
On a host using the **unified** hierarchy I can only see `memory.current` (same
goes for unified container on unified host and hybrid container on unified
host):
```
$ find /sys/fs/cgroup/ -wholename *system.slice/memory.current
/sys/fs/cgroup/system.slice/memory.current
$ find /sys/fs/cgroup/ -wholename *system.slice/memory.usage_in_bytes
```
=> Tests pass as expected.
BUT: Inside a **unified** container on a **hybrid** host, I can see neither:
```
$ find /sys/fs/cgroup/ -wholename *system.slice/memory.current
$ find /sys/fs/cgroup/ -wholename *system.slice/memory.usage_in_bytes
```
=> This is a problem. The test fails, because it cannot access `memory.current`
but is not skiped either.
--
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/1942113
Title:
systemd unit test regression in autopkgtest (oomd-utils)
Status in glibc package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
The latest systemd upload fails its tests against glibc 2.34. The
failing test is test-oomd-util within the unit-tests, with the
following logs:
Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope.
Using last pgscan of zero.
Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope.
Using last pgscan of zero.
Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last
pgscan of zero.
Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last
pgscan of zero.
Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope.
Using last pgscan of zero.
Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last
pgscan of zero.
Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope.
Using last pgscan of zero.
Bus n/a: changing state UNSET → OPENING
sd-bus: starting bus by connecting to /run/dbus/system_bus_socket...
Bus n/a: changing state OPENING → AUTHENTICATING
Bus n/a: changing state AUTHENTICATING → HELLO
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1
reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch
cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Got message type=method_return sender=org.freedesktop.DBus destination=:1.23
path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s
error-name=n/a error-message=n/a
Bus n/a: changing state HELLO → RUNNING
Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1
path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager
member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv))
error-name=n/a error-message=n/a
Got message type=method_return sender=:1.0 destination=:1.23 path=n/a
interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a
error-message=n/a
Got message type=signal sender=org.freedesktop.DBus destination=:1.23
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired
cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Got message type=method_return sender=org.freedesktop.DBus destination=:1.23
path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a
error-name=n/a error-message=n/a
Match
[Touch-packages] [Bug 1943251] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: I have Secure Boot enabled. The MOK key is already configured in the EFI. Have VMware Workstation installed and signed the modules so that would work. Not sure what initramfs is trying to do. I didn't kick anything off, this ran by itself in the background and just popped up with a warning. So I don't know if it is involved with Secure Boot, or if initramfs needs to sign a new image when it creates one, but the MOK key is there in the right place so it should be able to do so if it needs to. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 10 07:43:46 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-05 (5 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1943251 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 - I do have SecureBoot enabled Status in initramfs-tools package in Ubuntu: New Bug description: I have Secure Boot enabled. The MOK key is already configured in the EFI. Have VMware Workstation installed and signed the modules so that would work. Not sure what initramfs is trying to do. I didn't kick anything off, this ran by itself in the background and just popped up with a warning. So I don't know if it is involved with Secure Boot, or if initramfs needs to sign a new image when it creates one, but the MOK key is there in the right place so it should be able to do so if it needs to. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 10 07:43:46 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-05 (5 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1943251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943239] Re: second monitor
Thanks for the bug report. Your second monitor is not working apparently because you are using the 'fbdev' Xorg driver, which shouldn't happen. It looks like that happened because the proper 'modesetting' driver failed to find a graphics device at /dev/dri/card0. So it would appear this is a kernel bug. Please try removing the 'biosdevname=0' kernel parameter and tell us if that resolves the problem. Please also try booting an older kernel version and tell us if that fixes it. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - second monitor + [amdgpu] second monitor ** Summary changed: - [amdgpu] second monitor + [amdgpu] /dev/dri/card0 is missing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943239 Title: [amdgpu] /dev/dri/card0 is missing Status in linux package in Ubuntu: Incomplete Bug description: the second monitor is not connected on laptop MSI Modern 14 B4MW ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 11:52:09 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir [1462:12c8] InstallationDate: Installed on 2021-09-09 (1 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) MachineType: Micro-Star International Co., Ltd. Modern 14 B4MW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=54f1902f-8670-4bf3-9b25-b3ae9ba6e80c ro net.ifnames=0 biosdevname=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14DKAMS.114 dmi.board.asset.tag: Default string dmi.board.name: MS-14DK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14DKAMS.114:bd06/02/2021:svnMicro-StarInternationalCo.,Ltd.:pnModern14B4MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14DK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Modern dmi.product.name: Modern 14 B4MW dmi.product.sku: 14DK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943239] [NEW] second monitor
Public bug reported: the second monitor is not connected on laptop MSI Modern 14 B4MW ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 11:52:09 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir [1462:12c8] InstallationDate: Installed on 2021-09-09 (1 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) MachineType: Micro-Star International Co., Ltd. Modern 14 B4MW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=54f1902f-8670-4bf3-9b25-b3ae9ba6e80c ro net.ifnames=0 biosdevname=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14DKAMS.114 dmi.board.asset.tag: Default string dmi.board.name: MS-14DK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14DKAMS.114:bd06/02/2021:svnMicro-StarInternationalCo.,Ltd.:pnModern14B4MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14DK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Modern dmi.product.name: Modern 14 B4MW dmi.product.sku: 14DK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943239 Title: second monitor Status in xorg package in Ubuntu: New Bug description: the second monitor is not connected on laptop MSI Modern 14 B4MW ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 11:52:09 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir [1462:12c8] InstallationDate: Installed on 2021-09-09 (1 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) MachineType: Micro-Star International Co., Ltd. Modern 14 B4MW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=54f1902f-8670-4bf3-9b25-b3ae9ba6e80c ro net.ifnames=0 biosdevname=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14DKAMS.114 dmi.board.asset.tag: Default string dmi.board.name: MS-14DK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14DKAMS.114:bd06/02/2021:svnMicro-StarInternationalCo.,Ltd.:pnModern14B4MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14DK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Modern dmi.product.name: Modern 14 B4MW dmi.product.sku: 14DK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core
[Touch-packages] [Bug 1943109] Re: Merge 1.1.1l-1 version from Debian
Turns out I cannot unsubscribe the sponsors :/ -- 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/1943109 Title: Merge 1.1.1l-1 version from Debian Status in openssl package in Ubuntu: Fix Committed Bug description: This new upstream version consists only of a couple security fixes, and should thus be merged into Impish. Upstream changelog: Changes between 1.1.1k and 1.1.1l [24 Aug 2021] *) Fixed an SM2 Decryption Buffer Overflow. In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. (CVE-2021-3711) [Matt Caswell] *) Fixed various read buffer overruns processing ASN.1 strings ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). (CVE-2021-3712) [Matt Caswell] Debian changelog: openssl (1.1.1l-1) unstable; urgency=medium * New upstream version. - CVE-2021-3711 (SM2 Decryption Buffer Overflow). - CVE-2021-3712 (Read buffer overruns processing ASN.1 strings). -- Sebastian Andrzej Siewior Wed, 25 Aug 2021 00:19:05 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1943109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe
[Touch-packages] [Bug 1943109] Re: Merge 1.1.1l-1 version from Debian
Uploaded by juliank, but I forgot to add the LP number in the changelog. I'll change the status manually, and unsubscribe the sponsors list. ** Changed in: openssl (Ubuntu) Status: New => Fix Committed -- 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/1943109 Title: Merge 1.1.1l-1 version from Debian Status in openssl package in Ubuntu: Fix Committed Bug description: This new upstream version consists only of a couple security fixes, and should thus be merged into Impish. Upstream changelog: Changes between 1.1.1k and 1.1.1l [24 Aug 2021] *) Fixed an SM2 Decryption Buffer Overflow. In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. (CVE-2021-3711) [Matt Caswell] *) Fixed various read buffer overruns processing ASN.1 strings ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). (CVE-2021-3712) [Matt Caswell] Debian changelog: openssl (1.1.1l-1) unstable; urgency=medium * New upstream version. - CVE-2021-3711 (SM2 Decryption Buffer Overflow). - CVE-2021-3712 (Read buffer overruns processing ASN.1 strings). -- Sebastian Andrzej Siewior Wed, 25 Aug 2021 00:19:05 +0200 To manage notifications about this bug go to:
[Touch-packages] [Bug 1943109] Re: Merge 1.1.1l-1 version from Debian
The attachment "DIff to 1.1.1k-1ubuntu1 (Ubuntu)" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/1943109 Title: Merge 1.1.1l-1 version from Debian Status in openssl package in Ubuntu: New Bug description: This new upstream version consists only of a couple security fixes, and should thus be merged into Impish. Upstream changelog: Changes between 1.1.1k and 1.1.1l [24 Aug 2021] *) Fixed an SM2 Decryption Buffer Overflow. In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. (CVE-2021-3711) [Matt Caswell] *) Fixed various read buffer overruns processing ASN.1 strings ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). (CVE-2021-3712) [Matt Caswell] Debian changelog: openssl (1.1.1l-1) unstable; urgency=medium *
[Touch-packages] [Bug 1943109] Re: Merge 1.1.1l-1 version from Debian
The package has also been uploaded to the following PPA: https://launchpad.net/~schopin/+archive/ubuntu/test- ppa/+sourcepub/12697790/+listing-archive-extra -- 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/1943109 Title: Merge 1.1.1l-1 version from Debian Status in openssl package in Ubuntu: New Bug description: This new upstream version consists only of a couple security fixes, and should thus be merged into Impish. Upstream changelog: Changes between 1.1.1k and 1.1.1l [24 Aug 2021] *) Fixed an SM2 Decryption Buffer Overflow. In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. (CVE-2021-3711) [Matt Caswell] *) Fixed various read buffer overruns processing ASN.1 strings ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). (CVE-2021-3712) [Matt Caswell] Debian changelog: openssl (1.1.1l-1) unstable; urgency=medium * New upstream version. - CVE-2021-3711 (SM2 Decryption Buffer Overflow). - CVE-2021-3712 (Read buffer overruns processing ASN.1 strings). -- Sebastian Andrzej Siewior Wed, 25 Aug 2021 00:19:05 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1943109/+subscriptions -- Mailing
[Touch-packages] [Bug 1943109] Re: Merge 1.1.1l-1 version from Debian
** Patch added: "Diff to 1.1.1l-1 (Debian)" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1943109/+attachment/5524338/+files/openssl_diff_from_debian.debdiff -- 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/1943109 Title: Merge 1.1.1l-1 version from Debian Status in openssl package in Ubuntu: New Bug description: This new upstream version consists only of a couple security fixes, and should thus be merged into Impish. Upstream changelog: Changes between 1.1.1k and 1.1.1l [24 Aug 2021] *) Fixed an SM2 Decryption Buffer Overflow. In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. (CVE-2021-3711) [Matt Caswell] *) Fixed various read buffer overruns processing ASN.1 strings ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). (CVE-2021-3712) [Matt Caswell] Debian changelog: openssl (1.1.1l-1) unstable; urgency=medium * New upstream version. - CVE-2021-3711 (SM2 Decryption Buffer Overflow). - CVE-2021-3712 (Read buffer overruns processing ASN.1 strings). -- Sebastian Andrzej Siewior Wed, 25 Aug 2021 00:19:05 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1943109/+subscriptions --
[Touch-packages] [Bug 1943109] Re: Merge 1.1.1l-1 version from Debian
** Patch added: "DIff to 1.1.1k-1ubuntu1 (Ubuntu)" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1943109/+attachment/5524337/+files/openssl_diff_from_ubuntu.debdiff -- 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/1943109 Title: Merge 1.1.1l-1 version from Debian Status in openssl package in Ubuntu: New Bug description: This new upstream version consists only of a couple security fixes, and should thus be merged into Impish. Upstream changelog: Changes between 1.1.1k and 1.1.1l [24 Aug 2021] *) Fixed an SM2 Decryption Buffer Overflow. In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. (CVE-2021-3711) [Matt Caswell] *) Fixed various read buffer overruns processing ASN.1 strings ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). (CVE-2021-3712) [Matt Caswell] Debian changelog: openssl (1.1.1l-1) unstable; urgency=medium * New upstream version. - CVE-2021-3711 (SM2 Decryption Buffer Overflow). - CVE-2021-3712 (Read buffer overruns processing ASN.1 strings). -- Sebastian Andrzej Siewior Wed, 25 Aug 2021 00:19:05 +0200 To manage notifications about this bug go to:
[Touch-packages] [Bug 1942975] Re: gcr 3.40.0-2 ftbfs
Trevinho fixed it in https://bugs.launchpad.net/ubuntu/+source/gcr/3.40.0-3 ** Changed in: gcr (Ubuntu) Importance: Undecided => High ** Changed in: gcr (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1942975 Title: gcr 3.40.0-2 ftbfs Status in gcr package in Ubuntu: Fix Released Bug description: Reported upstream as https://gitlab.gnome.org/GNOME/gcr/-/issues/84. Looks like it might be a flaky test? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1942975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574582] Re: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager
Does not work here, too :-( Ubuntu 21.04 (upgraded) HP EliteBook 840 G3 after adding udev rule I get dmesg error: [ 1318.326793] usb 1-3: unknown number of interfaces: 5 [ 1318.333270] qmi_wwan 1-3:1.1: cdc-wdm0: USB WDM device [ 1318.333610] qmi_wwan 1-3:1.1 wwan0: register 'qmi_wwan' at usb-:00:14.0-3, WWAN/QMI device, fa:9c:a4:df:ff:eb [ 1318.333702] qmi_wwan 1-3:1.2: bogus CDC Union: master=0, slave=0 [ 1318.334491] qmi_wwan 1-3:1.2: cdc-wdm1: USB WDM device [ 1318.334790] qmi_wwan 1-3:1.2 wwan1: register 'qmi_wwan' at usb-:00:14.0-3, WWAN/QMI device, fa:9c:a4:df:ff:eb [ 1318.334870] qmi_wwan 1-3:1.3: bogus CDC Union: master=0, slave=0 [ 1318.336461] qmi_wwan 1-3:1.3: cdc-wdm2: USB WDM device [ 1318.336702] qmi_wwan 1-3:1.3 wwan2: register 'qmi_wwan' at usb-:00:14.0-3, WWAN/QMI device, fa:9c:a4:df:ff:eb [ 1318.339062] qmi_wwan 1-3:1.4: bogus CDC Union: master=0, slave=0 [ 1318.339838] qmi_wwan 1-3:1.4: cdc-wdm3: USB WDM device [ 1318.340172] qmi_wwan 1-3:1.4 wwan3: register 'qmi_wwan' at usb-:00:14.0-3, WWAN/QMI device, fa:9c:a4:df:ff:eb [ 1318.370397] qmi_wwan 1-3:1.1 wwan0: unregister 'qmi_wwan' usb-:00:14.0-3, WWAN/QMI device [ 1318.389216] qmi_wwan 1-3:1.2 wwan1: unregister 'qmi_wwan' usb-:00:14.0-3, WWAN/QMI device [ 1318.413358] qmi_wwan 1-3:1.3 wwan2: unregister 'qmi_wwan' usb-:00:14.0-3, WWAN/QMI device [ 1318.437003] qmi_wwan 1-3:1.4 wwan3: unregister 'qmi_wwan' usb-:00:14.0-3, WWAN/QMI device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574582 Title: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network- manager Status in network-manager package in Ubuntu: Confirmed Bug description: USB modem not recognized by network-manager. Modem information in attached ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Mon Apr 25 11:14:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.106.36.1 dev wlp2s0 proto static metric 600 1.1.1.1 via 10.106.36.1 dev wlp2s0 proto dhcp metric 600 10.106.36.0/22 dev wlp2s0 proto kernel scope link src 10.106.39.123 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 IQORAMS_REPAIR 3b1e13ff-f9c9-4a49-a576-465bc2713e21 /org/freedesktop/NetworkManager/ActiveConnection/1 enxb2e41f35ffe1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp0s31f6ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939409] Re: e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir
** No longer affects: e2fsprogs (Ubuntu Impish) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939409 Title: e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir Status in e2fsprogs package in Ubuntu: Fix Released Bug description: e2fsprogs 1.46.3-1ubuntu1 is in proposed. Architecture s390x fail in test f_baddotdir. The test image was changed with the new release. Next step should be analyzing the error on a s390x virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943163] Re: systemd.mount constantly unmounts an in use drive!
** Description changed: systemd.mount constantly unmounts an in use sshfs drive! Sep 09 11:20:01 $HOSTNAME systemd[4613]: pathtomount.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit UNIT has successfully entered the 'dead' state. Sep 09 11:20:01 $HOSTNAME systemd[1]: pathtomount.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit pathtomount.mount has successfully entered the 'dead' state. Change my kernel and the issue *seems* to have subsided. Coincidence or swapping kernels reconfigured whatever was causing the issue. Did not change kernel expecting to fix this, just so happened after I did this stopped happening. Judging by the time stamps (that 01 seconds) something was misbehaving with cron. This only seemed to affect the fuse mounts which correlates with other reports elsewhere I found but no real fixes and me changing kernels and rebuilding some things were just happenstance. i.e. magically fixed yields no answers. I installed a snap app around the time it started misbehaving but again could be pointless coincidence. I just noticed in the logs snap was playing with mounts for sandboxing. + + Just occurred to me that I think I've seen this before. When 20.04 came + out I updated my roommates laptop with it. It's old, just plays movies + off the network and the hard drive died so I just did an install to a + little flash drive. She'd be watching something and it would do that + little buffer stutter like you just yanked the drive out mid audio/video + playback and crash. Eventually I just moved the machine back to 18.04 + because there was no rhyme or reason to why it was doing that. I spent a + month hunting thermal trip issues, power saving, you name it but not + systemd. I never found anything in the logs but I was looking for + power/thermal/shutdown stuff not something idiotic unmounting the + rootfs! + + While I fear my angry bits are seen as trolling there is a distinct fall + off from 18.04. Every release past 19 has been riddled with massive + problems across several machines. Another friend I upgraded to 20.04, + couldn't print. Worked fine in 18.04. Found a solution after months of + printing from an 18.04 vm. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.4 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Sep 9 10:05:11 2021 EcryptfsInUse: Yes MachineType: Micro-Star International Co., Ltd MS-7C02 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd -- 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/1943163 Title: systemd.mount constantly unmounts an in use drive! Status in systemd package in Ubuntu: New Bug description: systemd.mount constantly unmounts an in use sshfs drive! Sep 09 11:20:01 $HOSTNAME systemd[4613]: pathtomount.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit UNIT has successfully entered the
