[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Hi Dan, Before the upstream openssl fix [1] the behavior was to send a proper CertificateStatus if the client requested the status_request extension from the server in a CertificateRequest. In other words, the additional information contains valid data. [1] https://github.com/openssl/openssl/pull/9780 -- 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/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 The issue leads to various client failures with TLS 1.3 as described in, e.g. https://github.com/golang/go/issues/35722 https://github.com/golang/go/issues/34040 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
** Changed in: charm-ceph-osd
Status: New => Invalid
** Changed in: lvm2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
Invalid
Status in curtin package in Ubuntu:
Invalid
Status in lvm2 package in Ubuntu:
Invalid
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+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 1679346] Re: Missing dep8 tests
** Changed in: net-tools (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1679346 Title: Missing dep8 tests Status in net-tools package in Ubuntu: Fix Committed Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of April 3, 2017, this source package did not contain package tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source net-tools zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. The package was also checked for 1) a test suite declaration in the debian/control file, 2) any 'test', 'tests', 'testsuite', or 'test-suite' directories, 3) go tests (if applicable), and 4) a test suite declared in a setup.py (if applicable). If you feel this report is incorrect (e.g. this is a library or a source only package) or the check above missed some other package level test please reply explaining why and mark this bug as 'invalid'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. Thanks! [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/net-tools status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY4siLAAoJEIP8BxPaZgwlKlgP/1tp7NP3mLPZyukvkknbekpa 0Cd02/t3Jy9JNJK/hnH50b0JUQ3HMFAvOIPb6SZgUH7NOlrE2Hgprcyo/OFZ5rRB fX3qc5PRX83VUM2D7IQtaQZqBU+y0vHDZ5DjWWfhke6E9SZsUHybVCAP+yBQXorQ DiEffoTUGkOfi+5S7V57FWw3rBxjeNRBxeoerfq/a0GS4YvTanQgFOMC1weOz/8J I64olcq3EMrUpClxKF2LQ6H0xDdpbF0i3SZfhi5h294p1qF8l4PS0rLT2sqr85Pr 1yz0jORhribXZy3M7thUMz/aLDmimL9+7nPL2lz40JjbNjNTVPZ+s8RguKWYYBx3 DBDJBfdG5JoLhsDDon7PKOILKj40S14KtmdbBY0VGNGuVSz3+m0WiTnTdJQzWWHR FNsfGjD+mdARcXqr11xgp/zY6VEVhG0AFIaZZgs1PbqvqL3FtGPgEGwXetgIU5bS J2suTN+WEEf8nI8kMi6PsUFfGsMogZTRHy04PCfPem0MBB3Olrmulm9bXcfbZ1Le 0eep3OVn06fm43x7YQaI/hzGl959pdppAahlFWTKvF0vfq7mJcSb6n1QpeWhvqeB tBAaV1redyI5ovDGAAVuFzrxJ7rWRKw4PVYln/C2Mayzb1S2dTwpjLtA9kcfQZJQ ZY8eSrPyf6eh2z8LVlR+ =WKVW -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1679346/+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 1917920] Autopkgtest regression report (livecd-rootfs/2.664.32)
All autopkgtests for the newly accepted livecd-rootfs (2.664.32) for focal have finished running. The following regressions have been reported in tests triggered by the package: ubuntu-image/1.11+20.04ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#livecd-rootfs [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in iptables source package in Bionic: Invalid Status in livecd-rootfs source package in Bionic: Invalid Status in lxd source package in Bionic: Invalid Status in iptables source package in Focal: Invalid Status in livecd-rootfs source package in Focal: Fix Committed Status in lxd source package in Focal: Invalid Status in iptables source package in Hirsute: Invalid Status in livecd-rootfs source package in Hirsute: New Status in lxd source package in Hirsute: Invalid Bug description: [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1946499] Re: SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all
Thanks everyone, the issue is now resolved by installing the update from Impish. Regards, Roland Johnston On Sun, 31 Oct 2021 at 11:20, Bryan Snyder <1946...@bugs.launchpad.net> wrote: > This resolved my issue installing my backup program Cloudberry backup. > (version 3.2.2.125-01) Previously deb wouldn’t install on Impish with Bad > file descriptor issue. > *Validated issue remained. > *Enabled proposed updates. > *Updated gdebi and gdebi-core from 0.9.5.7+nmu5ubuntu1to > 0.9.5.7+nmu5ubuntu2 > *deb file installed without issue. > > Thanks everyone. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1946499 > > Title: > SRU: GDebi - installation of deb-packages with gdebi-gtk not working > at all > > Status in Ubuntu MATE: > Invalid > Status in gdebi package in Ubuntu: > Fix Released > Status in vte2.91 package in Ubuntu: > Confirmed > Status in gdebi source package in Impish: > Fix Committed > > Bug description: > Steps to reproduce: > 1. Install Ubuntu MATE 21.10 > 2. Open Firefox, navigate to discord.com > 3. Download deb-file. At time of writing from the > https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link > 4. Open Caja in ~/Downloads folder and use GDebi to install the > discord-0.0.16.deb file > 5. In the GDebi window click Install button > > Expected results: > * Gdebi quietly install discord package, there are no error messages in > its terminal > > Actual results: > * Gdebi terminal shows the error in the last line > > ``` > Selecting previously unselected package gconf2-common. > (Reading database ... 457178 files and directories currently installed.) > Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... > Unpacking gconf2-common (3.2.6-7ubuntu2) ... > Selecting previously unselected package libgconf-2-4:amd64. > Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... > Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... > Selecting previously unselected package gconf-service-backend. > Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb > ... > Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... > Selecting previously unselected package gconf-service. > Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... > Unpacking gconf-service (3.2.6-7ubuntu2) ... > Selecting previously unselected package libappindicator1. > Preparing to unpack > .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... > Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... > Selecting previously unselected package libunwind-13:amd64. > Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... > Unpacking libunwind-13:amd64 (1:13.0.0-2) ... > Selecting previously unselected package libc++abi1-13:amd64. > Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... > Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... > Selecting previously unselected package libc++1-13:amd64. > Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... > Unpacking libc++1-13:amd64 (1:13.0.0-2) ... > Selecting previously unselected package libc++1:amd64. > Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... > Unpacking libc++1:amd64 (1:13.0-53~exp1) ... > Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... > Setting up gconf2-common (3.2.6-7ubuntu2) ... > > Creating config file /etc/gconf/2/path with new version > Setting up libunwind-13:amd64 (1:13.0.0-2) ... > Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... > Setting up libc++1-13:amd64 (1:13.0.0-2) ... > Setting up libc++1:amd64 (1:13.0-53~exp1) ... > Setting up gconf-service (3.2.6-7ubuntu2) ... > Processing triggers for libc-bin (2.34-0ubuntu2) ... > Processing triggers for sgml-base (1.30) ... > Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... > Setting up gconf-service-backend (3.2.6-7ubuntu2) ... > Processing triggers for libc-bin (2.34-0ubuntu2) ... > dpkg: error: unable to read filedescriptor flags for progress file descriptor>: Bad file descriptor > ``` > > and as the result Discord package is not installed . > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: gdebi 0.9.5.7+nmu5ubuntu1 > ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 > Uname: Linux 5.13.0-16-generic x86_64 > ApportVersion: 2.20.11-0ubuntu70 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: MATE > Date: Fri Oct 8 18:17:36 2021 > InstallationDate: Installed on 2021-10-08 (0 days ago) > InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 > (20211008) > PackageArchitecture: all > SourcePackage: gdebi > UpgradeStatus: No upgrade log present (probably fresh install) > modified.conffile..etc.default.apport: ># set this to 0 to disable apport, or to 1 to enable it ># you can
[Touch-packages] [Bug 1813052] Re: who returns no results
** Attachment added: "who.strace.txt"
https://bugs.launchpad.net/bugs/1813052/+attachment/5537446/+files/who.strace.txt
** Attachment added: "dpkg_-l.txt"
https://bugs.launchpad.net/bugs/1813052/+attachment/5537447/+files/dpkg_-l.txt
--
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/1813052
Title:
who returns no results
Status in systemd package in Ubuntu:
Invalid
Bug description:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and
an strace on a system that works (an unupdated xenial or a bionic
system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eed000
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f225391c000
mprotect(0x7f2253adc000, 2097152, PROT_NONE) = 0
mmap(0x7f2253cdc000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f2253cdc000
mmap(0x7f2253ce2000, 14752, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f2253ce2000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eec000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eeb000
arch_prctl(ARCH_SET_FS, 0x7f2253eec700) = 0
mprotect(0x7f2253cdc000, 16384, PROT_READ) = 0
mprotect(0x60a000, 4096, PROT_READ) = 0
mprotect(0x7f2253f0b000, 4096, PROT_READ) = 0
munmap(0x7f2253eee000, 117369) = 0
brk(NULL) = 0x9f9000
brk(0xa1a000) = 0xa1a000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253644000
close(3)= 0
access("/var/run/utmpx", F_OK) = 0
open("/var/run/utmpx", O_RDONLY|O_CLOEXEC) = 3
lseek(3, 0, SEEK_SET) = 0
alarm(0)= 0
rt_sigaction(SIGALRM, {0x7f2253a5d380, [], SA_RESTORER, 0x7f22539514b0},
{SIG_DFL, [], 0}, 8) = 0
alarm(10) = 0
fcntl(3, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
read(3, 0x7f2253ce5120, 384)= -1 EISDIR (Is a directory)
fcntl(3, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
alarm(0)= 10
rt_sigaction(SIGALRM, {SIG_DFL, [], SA_RESTORER, 0x7f22539514b0}, NULL, 8) = 0
close(3)= 0
close(1)= 0
close(2)= 0
exit_group(0) = ?
+++ exited with 0 +++
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu3~16.04
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Jan 23 10:39:00 2019
InstallationDate: Installed on 2016-07-08 (929 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813052/+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 1948698] Autopkgtest regression report (tzdata/2021e-0ubuntu0.20.04)
All autopkgtests for the newly accepted tzdata (2021e-0ubuntu0.20.04) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
php7.4/7.4.3-4ubuntu2.6 (armhf)
python3.9/3.9.5-3~20.04.1 (ppc64el)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#tzdata
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1948698
Title:
Update tzdata to version 2021e
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Hirsute:
Fix Released
Status in tzdata source package in Impish:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Asia/Gaza
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1948698/+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 1948698] Autopkgtest regression report (tzdata/2021e-0ubuntu0.21.04)
All autopkgtests for the newly accepted tzdata (2021e-0ubuntu0.21.04) for
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:
python3.9/3.9.5-3~21.04 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#tzdata
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1948698
Title:
Update tzdata to version 2021e
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Hirsute:
Fix Released
Status in tzdata source package in Impish:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Asia/Gaza
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1948698/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1813052] Re: who returns no results
Please find attached the dpkg -l output and the strace of who output.
This is from Ubuntu 20.04 running lightdm and cinnamon desktop.
On Thu, Oct 14, 2021 at 2:06 PM A Godshall wrote:
>
> It was fixed by pinning versions in Ubuntu 16.04.
>
> It only just recurred in Ubuntu 20.04.
>
> When I'm back in the office I will see if I can identify the versions
> affected and whether rolling back packages fixed it again.
>
>
>
> On Wed, Jun 30, 2021, 4:20 PM Dan Streetman <1813...@bugs.launchpad.net>
> wrote:
>>
>> please reopen if this is still an issue
>>
>> ** Changed in: systemd (Ubuntu)
>>Status: New => Invalid
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1813052
>>
>> Title:
>> who returns no results
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813052/+subscriptions
--
Best Regards.
This is unedited.
P-)
--
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/1813052
Title:
who returns no results
Status in systemd package in Ubuntu:
Invalid
Bug description:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and
an strace on a system that works (an unupdated xenial or a bionic
system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eed000
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f225391c000
mprotect(0x7f2253adc000, 2097152, PROT_NONE) = 0
mmap(0x7f2253cdc000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f2253cdc000
mmap(0x7f2253ce2000, 14752, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f2253ce2000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eec000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eeb000
arch_prctl(ARCH_SET_FS, 0x7f2253eec700) = 0
mprotect(0x7f2253cdc000, 16384, PROT_READ) = 0
mprotect(0x60a000, 4096, PROT_READ) = 0
mprotect(0x7f2253f0b000, 4096, PROT_READ) = 0
munmap(0x7f2253eee000, 117369) = 0
brk(NULL) = 0x9f9000
brk(0xa1a000) = 0xa1a000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253644000
close(3)= 0
access("/var/run/utmpx", F_OK) = 0
open("/var/run/utmpx", O_RDONLY|O_CLOEXEC) = 3
lseek(3, 0, SEEK_SET) = 0
alarm(0)= 0
rt_sigaction(SIGALRM, {0x7f2253a5d380, [], SA_RESTORER, 0x7f22539514b0},
{SIG_DFL, [], 0}, 8) = 0
alarm(10) = 0
fcntl(3, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
read(3, 0x7f2253ce5120, 384)= -1 EISDIR (Is a directory)
fcntl(3, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
alarm(0)= 10
rt_sigaction(SIGALRM, {SIG_DFL, [], SA_RESTORER, 0x7f22539514b0}, NULL, 8) = 0
close(3)= 0
close(1)= 0
close(2)= 0
exit_group(0) = ?
+++ exited with 0 +++
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu3~16.04
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Jan 23 10:39:00 2019
InstallationDate: Installed on 2016-07-08 (929 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
[Touch-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
Yes, there was no change in the J serie yet. Uploaded now to current and stables ** Changed in: alsa-lib (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: alsa-lib (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: alsa-lib (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: alsa-lib (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-lib source package in Impish: Fix Committed Status in alsa-lib source package in Jammy: Fix Committed Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
** Description changed: - This bug is for tracking purpose. + [Impact] + In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. + + [Fix] + Backport a commit from upstream, this commit is merged to upstream from v1.2.5 + + [Test] + After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. + + [Where problems will occur] + This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Hirsute: In Progress Status in alsa-lib source package in Impish: In Progress Status in alsa-lib source package in Jammy: In Progress Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
And I can't download the docker image of Jammy, Maybe the Jammy share the same libasound2 with Impish? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Hirsute: In Progress Status in alsa-lib source package in Impish: In Progress Status in alsa-lib source package in Jammy: In Progress Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
This is the debdiff for impish Thanks. ** Patch added: "alsa-lib_1.2.4-1.1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1949329/+attachment/5537419/+files/alsa-lib_1.2.4-1.1ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Hirsute: In Progress Status in alsa-lib source package in Impish: In Progress Status in alsa-lib source package in Jammy: In Progress Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
This is the debdiff for hirsute. Thanks. ** Patch added: "alsa-lib_1.2.4-1.1ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1949329/+attachment/5537418/+files/alsa-lib_1.2.4-1.1ubuntu3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Hirsute: In Progress Status in alsa-lib source package in Impish: In Progress Status in alsa-lib source package in Jammy: In Progress Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
This is the debdiff for focal. Thanks. ** Patch added: "alsa-lib_1.2.2-2.1ubuntu2.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1949329/+attachment/5537417/+files/alsa-lib_1.2.2-2.1ubuntu2.5.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Hirsute: In Progress Status in alsa-lib source package in Impish: In Progress Status in alsa-lib source package in Jammy: In Progress Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949329] [NEW] [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: alsa-lib (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: alsa-lib (Ubuntu Focal) Importance: High Status: In Progress ** Affects: alsa-lib (Ubuntu Hirsute) Importance: High Status: In Progress ** Affects: alsa-lib (Ubuntu Impish) Importance: High Status: In Progress ** Affects: alsa-lib (Ubuntu Jammy) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: oem-priority originate-from-1943203 somerville ** Also affects: alsa-lib (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-lib (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: alsa-lib (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: alsa-lib (Ubuntu Jammy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Changed in: alsa-lib (Ubuntu Focal) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Impish) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Jammy) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Focal) Status: New => In Progress ** Changed in: alsa-lib (Ubuntu Hirsute) Status: New => In Progress ** Changed in: alsa-lib (Ubuntu Impish) Status: New => In Progress ** Changed in: alsa-lib (Ubuntu Jammy) Status: New => In Progress ** Tags added: oem-priority originate-from-1943203 somerville -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Hirsute: In Progress Status in alsa-lib source package in Impish: In Progress Status in alsa-lib source package in Jammy: In Progress Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949331] [NEW] package libp11-kit0 0.23.20-1ubuntu0.1 [modified: usr/share/doc/libp11-kit0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/
Public bug reported: I tried to uninstall a package "Déjà Dup Backup Tool" and got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libp11-kit0 0.23.20-1ubuntu0.1 [modified: usr/share/doc/libp11-kit0/changelog.Debian.gz] ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 1 12:24:23 2021 DpkgTerminalLog: Preparing to unpack .../libp11-kit0_0.23.20-1ubuntu0.1_i386.deb ... Unpacking libp11-kit0:i386 (0.23.20-1ubuntu0.1) over (0.23.20-1build1) ... dpkg: error processing archive /var/cache/apt/archives/libp11-kit0_0.23.20-1ubuntu0.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libp11-kit0/changelog.Debian.gz', which is different from other instances of package libp11-kit0:i386 DuplicateSignature: package:libp11-kit0:0.23.20-1ubuntu0.1 [modified: usr/share/doc/libp11-kit0/changelog.Debian.gz] Unpacking libp11-kit0:i386 (0.23.20-1ubuntu0.1) over (0.23.20-1build1) ... dpkg: error processing archive /var/cache/apt/archives/libp11-kit0_0.23.20-1ubuntu0.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libp11-kit0/changelog.Debian.gz', which is different from other instances of package libp11-kit0:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libp11-kit0/changelog.Debian.gz', which is different from other instances of package libp11-kit0:i386 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: p11-kit Title: package libp11-kit0 0.23.20-1ubuntu0.1 [modified: usr/share/doc/libp11-kit0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libp11-kit0/changelog.Debian.gz', which is different from other instances of package libp11-kit0:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: p11-kit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1949331 Title: package libp11-kit0 0.23.20-1ubuntu0.1 [modified: usr/share/doc/libp11-kit0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libp11-kit0/changelog.Debian.gz', which is different from other instances of package libp11-kit0:i386 Status in p11-kit package in Ubuntu: New Bug description: I tried to uninstall a package "Déjà Dup Backup Tool" and got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libp11-kit0 0.23.20-1ubuntu0.1 [modified: usr/share/doc/libp11-kit0/changelog.Debian.gz] ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 1 12:24:23 2021 DpkgTerminalLog: Preparing to unpack .../libp11-kit0_0.23.20-1ubuntu0.1_i386.deb ... Unpacking libp11-kit0:i386 (0.23.20-1ubuntu0.1) over (0.23.20-1build1) ... dpkg: error processing archive /var/cache/apt/archives/libp11-kit0_0.23.20-1ubuntu0.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libp11-kit0/changelog.Debian.gz', which is different from other instances of package libp11-kit0:i386 DuplicateSignature: package:libp11-kit0:0.23.20-1ubuntu0.1 [modified: usr/share/doc/libp11-kit0/changelog.Debian.gz] Unpacking libp11-kit0:i386 (0.23.20-1ubuntu0.1) over (0.23.20-1build1) ... dpkg: error processing archive /var/cache/apt/archives/libp11-kit0_0.23.20-1ubuntu0.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libp11-kit0/changelog.Debian.gz', which is different from other instances of package libp11-kit0:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libp11-kit0/changelog.Debian.gz', which is different from other instances of package libp11-kit0:i386 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: p11-kit Title: package libp11-kit0 0.23.20-1ubuntu0.1 [modified: usr/share/doc/libp11-kit0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libp11-kit0/changelog.Debian.gz', which is different from other instances of package libp11-kit0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1949331/+subscriptions -- Mailing list:
