[Touch-packages] [Bug 1813581] Re: gpgme1.0 ftbfs in 18.04 LTS
** Changed in: gpgme1.0 (Ubuntu) Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1813581 Title: gpgme1.0 ftbfs in 18.04 LTS Status in gpgme1.0 package in Ubuntu: Fix Released Status in gpgme1.0 source package in Bionic: Fix Committed Bug description: [Impact] according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html gpgme1.0 ftbfs. * Start testing of TofuInfoTest * Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0) PASS : TofuInfoTest::initTestCase() PASS : TofuInfoTest::testTofuNull() PASS : TofuInfoTest::testTofuInfo() PASS : TofuInfoTest::testTofuSignCount() PASS : TofuInfoTest::testTofuKeyList() PASS : TofuInfoTest::testTofuPolicy() FAIL! : TofuInfoTest::testTofuConflict() 'sig.validity() == Signature::Marginal' returned FALSE. () Loc: [t-tofuinfo.cpp(458)] PASS : TofuInfoTest::cleanupTestCase() Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms * Finished testing of TofuInfoTest * FAIL: t-tofuinfo [Test case] build it [Regression potential] This only changes the test suite run during build, and that one currently fails, so it can't cause any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1813581/+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 1901528] Re: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip)
** No longer affects: zlib (Ubuntu) ** No longer affects: zlib (Ubuntu Groovy) ** Changed in: gzip (Ubuntu) Importance: Undecided => High ** Changed in: gzip (Ubuntu Groovy) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1901528 Title: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip) Status in Ubuntu on IBM z Systems: Fix Committed Status in gzip package in Ubuntu: Fix Released Status in gzip source package in Groovy: Fix Committed Bug description: When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB. This problem does not happen when running gzip against a single file at a time. It only happens when you provide multiple files as gzip arguments. So this works whether zlib acceleration is enabled or not: for file in file1 file2; do gzip $file ; done But this fails (when zlib acceleration is enabled): gzip file1 file2 The patch to fix this has been accepted upstream: https://git.savannah.gnu.org/cgit/gzip.git/commit/?id=be0a534ba2b6e77da289de8da79e70843b1028cc [Impact] * With zlib acceleration enabled, attempting to compress multiple files over 5MB would cause a segmentation fault. * The files could still be compressed in separate commands [Test Case] * Create two files that are larger than 5MB * Enable zlib acceleration (z15 hardware required) * Run the command gzip * NOTE: we do not have access to z15 hardware and therefore are relying on IBM to verify this fix [Where problems could occur] * Due to lack of testing resources, it's possible the bug has not been fully fixed, and the segmentation fault could still occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1901528/+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 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
** Changed in: binutils (Ubuntu) Importance: Undecided => Medium ** Changed in: binutils (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: binutils (Ubuntu Groovy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: In Progress Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: New Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak
Hi Mauricio,
It seems riscv64 passes on Groovy due to tests being skipped on the
riscv64 architecture.
>From Groovy's build log:
https://paste.ubuntu.com/p/NCJPDVSbSW/
If you look at the man page for dh_auto_test it mentions:
If the DEB_BUILD_OPTIONS environment variable contains nocheck, no tests
will be performed.
nocheck was added to riscv64 by default for all packages in Groovy as a
part of this change to dpkg in bug 1891686.
The test cases basic-realistic.sh and tls-basic-realistic.sh fail on
Focal because they attempt to send 100,000 packets between the server
and the client, and we get to various stages, like 00029000 msgs sent,
and now 00047000 msgs sent with some changes William made to the
builders, before it times out and assumes the channel is dead, and the
test fails.
https://paste.ubuntu.com/p/hwYXSbKPPV/
We aren't going to hit the 100,000 packets on riscv anytime soon. I
think I will open a new bug to adjust the packet counts from 100,000
down to 10,000 for basic-realistic.sh and tls-basic-realistic.sh, which
resembles what has been done for receiver-abort.sh and tls-receiver-
abort.sh.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads to file descriptor leak
Status in librelp package in Ubuntu:
Fix Released
Status in rsyslog package in Ubuntu:
Fix Released
Status in librelp source package in Focal:
Fix Committed
Status in rsyslog source package in Focal:
Won't Fix
Status in librelp source package in Groovy:
Fix Committed
Status in rsyslog source package in Groovy:
Fix Released
Status in librelp source package in Hirsute:
Fix Released
Status in rsyslog source package in Hirsute:
Fix Released
Bug description:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks
file descriptors due to a bug where it does not correctly close
sockets, and instead, leaves them in the CLOSE_WAIT state.
This causes rsyslogd on busy servers to eventually hit the limit of
maximum open files allowed, which locks rsyslogd up until it is
restarted.
A workaround is to restart rsyslogd every month or so to manually
close all of the open sockets.
Only users of the imrelp module are affected, and not rsyslog users in
general.
[Testcase]
Install the rsyslog-relp module like so:
$ sudo apt install rsyslog rsyslog-relp
Next, generate a working directory, and make a config file that loads
the relp module.
$ sudo mkdir /workdir
$ cat << EOF >> ./spool.conf
\$LocalHostName spool
\$AbortOnUncleanConfig on
\$PreserveFQDN on
global(
workDirectory="/workdir"
maxMessageSize="256k"
)
main_queue(queue.type="Direct")
module(load="imrelp")
input(
type="imrelp"
name="imrelp"
port="601"
ruleset="spool"
MaxDataSize="256k"
)
ruleset(name="spool" queue.type="direct") {
}
# Just so rsyslog doesn't whine that we do not have outputs
ruleset(name="noop" queue.type="direct") {
action(
type="omfile"
name="omfile"
file="/workdir/spool.log"
)
}
EOF
Verify that the config is valid, then start a rsyslog server.
$ sudo rsyslogd -f ./spool.conf -N9
$ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid
Fetch the rsyslogd PID and check for open files.
$ RLOGPID=$(cat /workdir/rsyslogd.pid)
$ sudo ls -l /proc/$RLOGPID/fd
total 0
lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'
We have 3 sockets open by default. Next, use netcat to open 100
connections:
$ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done
Now check for open file descriptors, and there will be an extra 100 sockets
in the list:
$ sudo ls -l /proc/$RLOGPID/fd
https://paste.ubuntu.com/p/f6NQVNbZcR/
We can check the state of these sockets with:
$ ss -t
https://paste.ubuntu.com/p/7Ts2FbxJrg/
The listening sockets will be in CLOSE-WAIT, and the netcat sockets
will be in FIN-WAIT-2.
$ ss -t | grep CLOSE-WAIT | wc -l
100
If you install the test package available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf299578-test
When you open connections with netcat, these will be closed properly,
and the file descriptor leak will be fixed.
[Where problems could occur]
If a regression were to occur, it would be limited to users of the
imrelp module, which is a part of the rsyslogd-relp package, and
depends on librelp.
rsyslog-relp is not part of a default installation of rsyslog, and is
opt in by changing a
[Touch-packages] [Bug 1904902] Re: Pulseaudio produces a lot of crackling audio after awhile
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1904902 Title: Pulseaudio produces a lot of crackling audio after awhile Status in pulseaudio package in Ubuntu: Expired Bug description: 1) Description: Ubuntu 20.10 Release: 20.10 2) pulseaudio: Instalado: 1:13.99.2-1ubuntu2 Candidato: 1:13.99.2-1ubuntu2 Tabela de versão: *** 1:13.99.2-1ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 3) What you expected to happen: It shouldn't produce any crackles in the audio after a set amount of time. 4) What happened instead: It starts to crackle with a very low volume, then it keeps increasing until it reaches the same volume as the music/audio. Running systemctl --user restart pulseaudio.service fixes the issue until the next restart. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 19 14:09:37 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-06-16 (156 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2202 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1904902/+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 1905076] Re: module-alsa-sink's "control" argument causes segmentation fault
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1905076 Title: module-alsa-sink's "control" argument causes segmentation fault Status in pulseaudio package in Ubuntu: Expired Bug description: Loading the pulseaudio module 'module-alsa-sink' with the "control" argument causes pulseaudio to segfault on my system. In /etc/pulse/default.pa find this line: #load-module module-alsa-sink and change it to this: load-module module-alsa-sink control=Master then restart pulseaudio by running these commands: pulseaudio -k pulseaudio --start Notice that it prints this into the terminal. E: [pulseaudio] main.c: Daemon startup failed. Try starting pulseaudio itself in the terminal, and you see what's happening: W: [pulseaudio] pid.c: Stale PID file, overwriting. Segmentation fault (core dumped) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-04-15 (219 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: groovy Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905076/+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 1835660] Re: initramfs unpacking failed
Fix this bug with a patch, please have a try. ** Patch added: "Fix padding parse error" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+attachment/5455378/+files/0001-initramfs-fix-Decoding-failed.patch -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1912091] Re: Memory Leak GNU Tar 1.33
** Changed in: tar (Ubuntu) Importance: Undecided => Low ** Tags removed: security tar ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1912091 Title: Memory Leak GNU Tar 1.33 Status in tar package in Ubuntu: New Bug description: An issue was discovered in GNU Tar 1.33 and earlier. There is a memory leak in read_header() in list.c in the tar application. Occastionally, ASAN detects an out of bounds memory read. Valgrind confirms the memory leak in the standard tar tool installed by default. This degrades the availability of the tar tool, and could potentially result in other memory-related issues. Common Weakness Enumeration IDs for reference: CWE-401: Missing Release of Memory after Effective Lifetime CWE-125: Out-of-bounds Read Attached to this report is a PoC malcrafted file "1311745-out- bounds.tar" VALGRIND OUTPUT: valgrind tar -xf 1311745-out-bounds.tar ==3776== Memcheck, a memory error detector ==3776== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==3776== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==3776== Command: tar -xf output/1311745-out-bounds.tar ==3776== tar: Unexpected EOF in archive tar: Exiting with failure status due to previous errors ==3776== ==3776== HEAP SUMMARY: ==3776== in use at exit: 1,311,761 bytes in 2 blocks ==3776== total heap usage: 52 allocs, 50 frees, 1,349,212 bytes allocated ==3776== ==3776== LEAK SUMMARY: ==3776==definitely lost: 1,311,745 bytes in 1 blocks ... NOTE: Version 1.30, 1.32, 1.33 were tested and confirmed to be vulnerable. lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 apt-cache policy tar tar: Installed: 1.30+dfsg-7ubuntu0.20.04.1 Candidate: 1.30+dfsg-7ubuntu0.20.04.1 --- Carlos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1912091/+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 1912673] Re: sounds not working on Dell XPS 17 (9700)
** Package changed: pulseaudio (Ubuntu) => alsa-ucm-conf (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1912673 Title: sounds not working on Dell XPS 17 (9700) Status in alsa-ucm-conf package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: My investigation process: Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds worked. I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, using linux-image-5.4.0-42-generic, I did not try blutooth. I sudo apt upgrade, dist-upgrade to get kernels linux-image-5.8.0-38-generic linux-image-5.8.0-40-generic Sounds did not work. I download linux-image-unsigned-5.10.9-051009-generic. Sounds did not work. I upgrade Dell XPS 9700 firmware from 1.3 to 1.63. Sounds did not work. After googling I found this solution in the comments: https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700 """ Download and install dkms module: https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem- dkms/+packages Alternatively, you can install linux-oem-20.04, it will install the 5.6 kernel with the above driver. Your system may be more stable with 5.4 kernel since it is in wide use. Manually install sof-firmware from Arch Linux: https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof- firmware-1.5.1-1-any.pkg.tar.zst.html You will need to delete the existing "sof" and "sof-tplg" files from the Ubuntu linux-firmware package first. Note if this package gets updated from Canoncial and they don't update these, you will have to delete and then reextract. Files go into the /usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg folders. Manually install the ucm2 files: http://xps17.ddns.net/sof-soundwire.zip These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the contents of the existing sof-soundwire folder (if you have it) and replace them with the ones from the archive. Reboot. You should now have all your audio devices available. If speakers do not play, you may need to run alsamixer (non-root) from a terminal and unmute and set the mixer levels all the way up. """ This solution worked for me on linux-image-5.6.0-1042-oem AFTER manually opening alsa-mixer and changing soundcard to sof. The sound would otherwise just show 'dummy'. My sounds still do not work on 5.8 or 5.10, full name listed above. I did not get to test this temporary fix with 5.4. my full alsa-info: http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff based on some google research, this seems to be a common problem: https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/ https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/ https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/ etc... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 Uname: Linux 5.6.0-1042-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neoh 1786 F pulseaudio /dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio /dev/snd/controlC0: neoh 1786 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 12:08:45 2021 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0CXCCY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1912673/+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 1912670] Re: Mouse buttons and keyboard unresponsive after idle time
Thanks for the bug report. This sounds a power management problem. 1. If you have 'tlp' installed the please uninstall it. It's known to cause bugs like this. 2. Try installing 'powertop' and then look in its 'Tunables' section. By changing some of those to 'Bad' (which is actually better than 'Good' in this case) you can stop them suspending so much. 3. The kernel team should have some more ideas. I will move this bug there... ** Package changed: xorg (Ubuntu) => linux (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/1912670 Title: Mouse buttons and keyboard unresponsive after idle time Status in linux package in Ubuntu: New Bug description: If I leave my desktop (Xubuntu 20.04.1 LTS, Xfce xfdesktop4 4.14.2-1, Xorg 1:7.7+19ubuntu14) idle for a few minutes, the mouse buttons and most keyboard presses become unresponsive. My "system power saving" setting is disabled (set to "never") and "display power management" is set to blank after 15 minutes, but the problem seems to occur sooner than that. Unplugging and re-inserting the mouse after a few seconds has no effect. The only keystrokes that have any effect are Ctrl+Alt+F1 for a terminal session (where I can type normally). Returning to the desktop with Ctrl+Alt+F7 the mouse and keyboard remain unresponsive as before. This occurs with kernel 5.4.0-62, and I also installed the 5.4.0-26 kernel and the problem happens with that too. When I reboot the machine everything works fine again, but after a few minutes of idle time, the same problem occurs again. I've only noticed the problem occurring in the last ~2-3 weeks. When I leave a terminal window open on the desktop running the command: tail -f /var/log/Xorg.0.log and allow lots of time for the problem to occur, no lines are appended in the terminal even after the problem has happened, but when I then use Ctrl+Alt+F1 and log in at the terminal console, the following additional lines appear in /var/log/xorg.0.log : [ 3805.283] (II) event1 - Power Button: device removed [ 3805.296] (II) event0 - Power Button: device removed [ 3805.312] (II) event3 - Logitech USB Optical Mouse: device removed [ 3805.344] (II) event4 - Eee PC WMI hotkeys: device removed [ 3805.364] (II) event2 - AT Translated Set 2 keyboard: device removed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 16:37:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:8501] InstallationDate: Installed on 2020-05-17 (249 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-62-generic root=UUID=c8acacab-7716-4698-b0e0-6041467d4517 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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
[Touch-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
"Because of Bluetooth" sounds like a stretch. Hedda, please open a new bug by running: ubuntu-bug gnome-shell so we can analyse your issue separately. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: New Status in bluez source package in Groovy: New Status in bluez source package in Hirsute: New Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+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 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak
Hi Matthew,
I've kicked one or two rebuilds today, and still see the (same) one or
two tests failing.
I'm out this week so can't look much more into it (althogh I'm
admittedly curious about it :)
If you can take a look at these FTBFS test case failures, that would be
awesome; all archs must pass for the SRU to be released. Maybe you can
get access to a riscv64 instance, or the issue perhaps reproduces in
QEMU?
Otherwise I can try and take a look on Monday.
cheers,
Mauricio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads to file descriptor leak
Status in librelp package in Ubuntu:
Fix Released
Status in rsyslog package in Ubuntu:
Fix Released
Status in librelp source package in Focal:
Fix Committed
Status in rsyslog source package in Focal:
Won't Fix
Status in librelp source package in Groovy:
Fix Committed
Status in rsyslog source package in Groovy:
Fix Released
Status in librelp source package in Hirsute:
Fix Released
Status in rsyslog source package in Hirsute:
Fix Released
Bug description:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks
file descriptors due to a bug where it does not correctly close
sockets, and instead, leaves them in the CLOSE_WAIT state.
This causes rsyslogd on busy servers to eventually hit the limit of
maximum open files allowed, which locks rsyslogd up until it is
restarted.
A workaround is to restart rsyslogd every month or so to manually
close all of the open sockets.
Only users of the imrelp module are affected, and not rsyslog users in
general.
[Testcase]
Install the rsyslog-relp module like so:
$ sudo apt install rsyslog rsyslog-relp
Next, generate a working directory, and make a config file that loads
the relp module.
$ sudo mkdir /workdir
$ cat << EOF >> ./spool.conf
\$LocalHostName spool
\$AbortOnUncleanConfig on
\$PreserveFQDN on
global(
workDirectory="/workdir"
maxMessageSize="256k"
)
main_queue(queue.type="Direct")
module(load="imrelp")
input(
type="imrelp"
name="imrelp"
port="601"
ruleset="spool"
MaxDataSize="256k"
)
ruleset(name="spool" queue.type="direct") {
}
# Just so rsyslog doesn't whine that we do not have outputs
ruleset(name="noop" queue.type="direct") {
action(
type="omfile"
name="omfile"
file="/workdir/spool.log"
)
}
EOF
Verify that the config is valid, then start a rsyslog server.
$ sudo rsyslogd -f ./spool.conf -N9
$ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid
Fetch the rsyslogd PID and check for open files.
$ RLOGPID=$(cat /workdir/rsyslogd.pid)
$ sudo ls -l /proc/$RLOGPID/fd
total 0
lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'
We have 3 sockets open by default. Next, use netcat to open 100
connections:
$ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done
Now check for open file descriptors, and there will be an extra 100 sockets
in the list:
$ sudo ls -l /proc/$RLOGPID/fd
https://paste.ubuntu.com/p/f6NQVNbZcR/
We can check the state of these sockets with:
$ ss -t
https://paste.ubuntu.com/p/7Ts2FbxJrg/
The listening sockets will be in CLOSE-WAIT, and the netcat sockets
will be in FIN-WAIT-2.
$ ss -t | grep CLOSE-WAIT | wc -l
100
If you install the test package available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf299578-test
When you open connections with netcat, these will be closed properly,
and the file descriptor leak will be fixed.
[Where problems could occur]
If a regression were to occur, it would be limited to users of the
imrelp module, which is a part of the rsyslogd-relp package, and
depends on librelp.
rsyslog-relp is not part of a default installation of rsyslog, and is
opt in by changing a configuration file to enable imrelp.
The changes to rsyslog implement a testcase which exercises the problematic
code to ensure things are working as expected; this
can be enabled manually on build, and has been verified to pass (#7).
[Other]
Upstream bug list:
https://github.com/rsyslog/rsyslog/issues/4350
https://github.com/rsyslog/rsyslog/issues/4005
https://github.com/rsyslog/librelp/issues/188
https://github.com/rsyslog/librelp/pull/193
The following commits fix the problem:
rsyslogd
commit baee0bd5420649329793746f0daf87c4f59fe6a6
Author: Andre lorbach
Date: Thu Apr 9 13:00:35 2020 +0200
[Touch-packages] [Bug 1872824] Re: Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package ke
Revisiting this as the fix I posted was inaccurate. I did manage to resolve it successfully as I will explain. I had to manually upgrade the three packages in the dependency chain that was causing the issue like so (order is important): # keyboard-configuration console-setup-linux console-setup dpkg -i /path/to/keyboard-configuration_*.deb dpkg -i /path/to/console-setup-linux_*.deb dpkg -i /path/to/console-setup_*.deb I think I ran into other conflicts, but this was the trickiest, as apt always wanted to install them in what appears to be out of the logical dependency order, and would always result in the above error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1872824 Title: Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console- setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 Status in console-setup package in Ubuntu: Confirmed Bug description: Upgrade path from 16.04 to 20.04 fails. console-setup-linux_1.194ubuntu3_all.deb tries to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5. I have reproduced this bug on bare metal and WSL. Log: Unpacking console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5) ... dpkg: error processing archive /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb (--unpack): trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../keyboard-configuration_1.194ubuntu3_all.deb ... Unpacking keyboard-configuration (1.194ubuntu3) over (1.108ubuntu15.5) ... Preparing to unpack .../busybox-initramfs_1%3a1.30.1-4ubuntu6_amd64.deb ... Unpacking busybox-initramfs (1:1.30.1-4ubuntu6) over (1:1.22.0-15ubuntu1.4) ... Preparing to unpack .../initramfs-tools-bin_0.136ubuntu6_amd64.deb ... Unpacking initramfs-tools-bin (0.136ubuntu6) over (0.122ubuntu8.16) ... Preparing to unpack .../cpio_2.13+dfsg-2_amd64.deb ... Unpacking cpio (2.13+dfsg-2) over (2.11+dfsg-5ubuntu1.1) ... Preparing to unpack .../liblz4-1_1.9.2-2_amd64.deb ... Unpacking liblz4-1:amd64 (1.9.2-2) over (0.0~r131-2ubuntu2) ... Processing triggers for libc-bin (2.31-0ubuntu7) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.27) ... Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1872824/+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 1303316] Re: Digital S/PDIF output is not present in 5.1 mode
Nothing new? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1303316 Title: Digital S/PDIF output is not present in 5.1 mode Status in pulseaudio package in Ubuntu: New Bug description: I have the sound connected through digital S / PDIF Sound works properly selecting stereo, but can not get it to work using 5.1 When I select stereo sound, appears on the tab below to phonon spdif output option. When I select Output 5.1, that option does not appear. I imagine the error will also occur selecting 7.1 Deputy screenshots. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: phonon 4:4.7.0really4.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Apr 6 13:12:42 2014 InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: phonon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303316/+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 1889742] binutils_focal_sru.debdiff
Default Comment by Bridge ** Attachment added: "binutils_focal_sru.debdiff" https://bugs.launchpad.net/bugs/1889742/+attachment/5455305/+files/binutils_focal_sru.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: In Progress Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: New Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
** Patch removed: "binutils_focal_sru.debdiff" https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1889742/+attachment/5455201/+files/binutils_focal_sru.debdiff ** Patch added: "binutils_focal_sru.debdiff" https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1889742/+attachment/5455304/+files/binutils_focal_sru.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: In Progress Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: New Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
I haven't looked at the debdiff in detail but the version number could use changing to ubuntu1.1 per https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: In Progress Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: New Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1912687] [NEW] package linux-firmware 1.187.8 failed to install/upgrade: podproces zainstalowany pakiet linux-firmware skrypt post-installation zwrócił kod błędu 1
Public bug reported: Error while installing package during apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.8 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zolw 2916 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jan 21 20:45:57 2021 Dependencies: ErrorMessage: podproces zainstalowany pakiet linux-firmware skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2019-08-01 (538 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20L7001SPB PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgroot-lvroot ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.8 failed to install/upgrade: podproces zainstalowany pakiet linux-firmware skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: Upgraded to focal on 2020-10-01 (112 days ago) dmi.bios.date: 02/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET62W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7001SPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET62W(1.39):bd02/18/2020:svnLENOVO:pn20L7001SPB:pvrThinkPadT480s:rvnLENOVO:rn20L7001SPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7001SPB dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO ** 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/1912687 Title: package linux-firmware 1.187.8 failed to install/upgrade: podproces zainstalowany pakiet linux-firmware skrypt post-installation zwrócił kod błędu 1 Status in initramfs-tools package in Ubuntu: New Bug description: Error while installing package during apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.8 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zolw 2916 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jan 21 20:45:57 2021 Dependencies: ErrorMessage: podproces zainstalowany pakiet linux-firmware skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2019-08-01 (538 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20L7001SPB PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgroot-lvroot ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.8 failed to install/upgrade: podproces zainstalowany pakiet linux-firmware skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: Upgraded to focal on 2020-10-01 (112 days ago) dmi.bios.date: 02/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET62W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7001SPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET62W(1.39):bd02/18/2020:svnLENOVO:pn20L7001SPB:pvrThinkPadT480s:rvnLENOVO:rn20L7001SPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7001SPB dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor:
[Touch-packages] [Bug 1912526] Re: cannot import new keys if another malformed key exists
It's in the latest Ubuntu LTS and will stay be there until 2025. If it is legacy and deprecated, maybe it should have been removed? In its current state, this apt-key issue has some security implications: First, the Ubuntu update GUI is not very intuitive in handling this issue. It presents the user only with a message that there is a connection issue, which is not true in this case. Options then are to "try again" which will never resolve an issue with unsigned repos, or acknowledge the issue with "Ok". This can be confusing as the "Ok" does not indicate that updates can still be installed. A user might just close the dialog and never install additional updates. The update manager should just install all updates available and not bother the user with unintuitive choices. Second, even if you manage to decipher the update manager GUI, you will still be left with a browser (e.g. Google Chrome in the example above) that will never be updated. This means in the worst case that someone is using a browser on Ubuntu LTS that gathered 5 years of security issues. -- 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/1912526 Title: cannot import new keys if another malformed key exists Status in apt package in Ubuntu: New Bug description: "apt-key add" fails to import keys if there exists another key with a malformed file name. Such malformed key names used to be provided by the openSUSE Build Service (https://github.com/openSUSE/software-o-o/issues/842). After importing such malformed key, future key imports will fail with something like: $ sudo apt-key add linux_signing_key.pub gpg: invalid key resource URL '/tmp/apt-key-gpghome.f8IaqZ48Ze/isv:ownCloud:desktop.asc.gpg' gpg: keyblock resource '(null)': General error even though no such file "isv:ownCloud:desktop.asc.gpg" exists anywhere on the filesystem. This affects deb packages that import public repo keys during installation, such as Google Chrome or Vivaldi, and results in minor issues such as breaking GUI tools and CLI warnings, and the major issue that the installed repo cannot be used anymore to update the software (Google Chrome, Vivaldi). apt-key should be robust to such issues and continue importing keys. As in the example above, apt-key should import "linux_signing_key.pub" no matter if another unrelated key is malformed etc. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.2 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: openafs nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 19:24:34 2021 InstallationDate: Installed on 2020-04-24 (271 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1912526/+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 1887210] Re: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer
Hello, I got the same problem with the Schiit Audio Fulla 3 and the kernel 5.10.8 on Fedora. But I got no problem with the Kernel 5.4.59 on Raspbian. Kurt Bonatz reported a problem with the 5.4.0. Maybe there is a difference in audio stack between Ubuntu and Raspbian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1887210 Title: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am experiencing the same issue with the same device described in this report comment: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1267866/comments/26 The device works as expected with Windows 10 and macOS no drivers required. However, the device is not an option from Ubuntu's sound settings. It is visible in alsamixer, however, it crashes immediately upon selection with 'cannot load mixer controls: Broken pipe'. Here's some more debug information. Let me know if there is anymore I can provide or feel free to redirect me if there is another place this is better reported. Device: Schiit Audio Fulla 3 USB DAC/AMP Kernel version: 5.4.0-40-generic Ubuntu version: 20.04 Alsa debug output: http://alsa- project.org/db/?f=3f494b2155bdde7f5ee0e52240da77468bcb `dmesg -w` output upon re-plugging in the device: [ 895.624302] usb 3-2.3: new high-speed USB device number 8 using xhci_hcd [ 895.739125] usb 3-2.3: New USB device found, idVendor=30be, idProduct=0100, bcdDevice= 1.02 [ 895.739129] usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 895.739131] usb 3-2.3: Product: I'm Fulla Schiit [ 895.739133] usb 3-2.3: Manufacturer: Schiit Audio [ 896.076914] input: Schiit Audio I'm Fulla Schiit as /devices/pci:00/:00:07.1/:11:00.3/usb3/3-2/3-2.3/3-2.3:1.3/0003:30BE:0100.0007/input/input20 [ 896.136457] hid-generic 0003:30BE:0100.0007: input,hidraw5: USB HID v1.00 Device [Schiit Audio I'm Fulla Schiit] on usb-:11:00.3-2.3/input3 [ 896.228480] audit: type=1107 audit(1594446870.681:57): pid=1286 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.8" mask="receive" pid=10228 label="snap.spotify.spotify" peer_pid=1287 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [ 896.238190] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.298659] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.427249] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.618498] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1887210/+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 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
Because of Bluetooth, my system hangs frequently and inputs are no longer possible. Maybe the Xorg log could help? ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+attachment/5455265/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: New Status in bluez source package in Groovy: New Status in bluez source package in Hirsute: New Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+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 1912673] [NEW] sounds not working on Dell XPS 17 (9700)
Public bug reported: My investigation process: Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds worked. I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, using linux-image-5.4.0-42-generic, I did not try blutooth. I sudo apt upgrade, dist-upgrade to get kernels linux-image-5.8.0-38-generic linux-image-5.8.0-40-generic Sounds did not work. I download linux-image-unsigned-5.10.9-051009-generic. Sounds did not work. I upgrade Dell XPS 9700 firmware from 1.3 to 1.63. Sounds did not work. After googling I found this solution in the comments: https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700 """ Download and install dkms module: https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem- dkms/+packages Alternatively, you can install linux-oem-20.04, it will install the 5.6 kernel with the above driver. Your system may be more stable with 5.4 kernel since it is in wide use. Manually install sof-firmware from Arch Linux: https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof- firmware-1.5.1-1-any.pkg.tar.zst.html You will need to delete the existing "sof" and "sof-tplg" files from the Ubuntu linux-firmware package first. Note if this package gets updated from Canoncial and they don't update these, you will have to delete and then reextract. Files go into the /usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg folders. Manually install the ucm2 files: http://xps17.ddns.net/sof-soundwire.zip These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the contents of the existing sof-soundwire folder (if you have it) and replace them with the ones from the archive. Reboot. You should now have all your audio devices available. If speakers do not play, you may need to run alsamixer (non-root) from a terminal and unmute and set the mixer levels all the way up. """ This solution worked for me on linux-image-5.6.0-1042-oem AFTER manually opening alsa-mixer and changing soundcard to sof. The sound would otherwise just show 'dummy'. My sounds still do not work on 5.8 or 5.10, full name listed above. I did not get to test this temporary fix with 5.4. my full alsa-info: http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff based on some google research, this seems to be a common problem: https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/ https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/ https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/ etc... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 Uname: Linux 5.6.0-1042-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neoh 1786 F pulseaudio /dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio /dev/snd/controlC0: neoh 1786 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 12:08:45 2021 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0CXCCY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed ** Description changed: My investigation process: Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds worked. - I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, + I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, using linux-image-5.4.0-42-generic, I did not try blutooth. I sudo apt upgrade, dist-upgrade to get kernels - linux-image-5.8.0-38-generic + linux-image-5.8.0-38-generic linux-image-5.8.0-40-generic - Sounds did not work. + Sounds did not work. I download linux-image-unsigned-5.10.9-051009-generic. Sounds did not work. I upgrade Dell XPS 9700 firmware from 1.3 to 1.63. Sounds did not work. After googling I found this solution in the comments:
[Touch-packages] [Bug 1912675] [NEW] [USB-Audio - Yeti X, recording] Underruns, dropouts or crackling sound
Public bug reported: I tried to record with my microphone but its making crackling noises both microphone and headset ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julletime 1530 F pulseaudio /dev/snd/controlC2: julletime 1530 F pulseaudio /dev/snd/controlC3: julletime 1530 F pulseaudio /dev/snd/controlC1: julletime 1530 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:29:42 2021 InstallationDate: Installed on 2021-01-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:X failed Symptom_Card: Built-in Audio - Loopback Symptom_PulseAudioLog: jan 21 18:13:50 julletimes-dator dbus-daemon[793]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=992 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - Yeti X, recording] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2020 dmi.bios.release: 1.25 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17E2IMS.119 dmi.board.asset.tag: Default string dmi.board.name: MS-17E2 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.:bvrE17E2IMS.119:bd03/16/2020:br1.25:svnMicro-StarInternationalCo.,Ltd.:pnGP75Leopard9SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17E2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP75 Leopard 9SD dmi.product.sku: 17E2.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1912675 Title: [USB-Audio - Yeti X, recording] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: I tried to record with my microphone but its making crackling noises both microphone and headset ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julletime 1530 F pulseaudio /dev/snd/controlC2: julletime 1530 F pulseaudio /dev/snd/controlC3: julletime 1530 F pulseaudio /dev/snd/controlC1: julletime 1530 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:29:42 2021 InstallationDate: Installed on 2021-01-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:X failed Symptom_Card: Built-in Audio - Loopback Symptom_PulseAudioLog: jan 21 18:13:50 julletimes-dator dbus-daemon[793]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=992 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - Yeti X, recording] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2020 dmi.bios.release: 1.25 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17E2IMS.119 dmi.board.asset.tag: Default string dmi.board.name: MS-17E2 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:
[Touch-packages] [Bug 1912670] [NEW] Mouse buttons and keyboard unresponsive after idle time
Public bug reported: If I leave my desktop (Xubuntu 20.04.1 LTS, Xfce xfdesktop4 4.14.2-1, Xorg 1:7.7+19ubuntu14) idle for a few minutes, the mouse buttons and most keyboard presses become unresponsive. My "system power saving" setting is disabled (set to "never") and "display power management" is set to blank after 15 minutes, but the problem seems to occur sooner than that. Unplugging and re-inserting the mouse after a few seconds has no effect. The only keystrokes that have any effect are Ctrl+Alt+F1 for a terminal session (where I can type normally). Returning to the desktop with Ctrl+Alt+F7 the mouse and keyboard remain unresponsive as before. This occurs with kernel 5.4.0-62, and I also installed the 5.4.0-26 kernel and the problem happens with that too. When I reboot the machine everything works fine again, but after a few minutes of idle time, the same problem occurs again. I've only noticed the problem occurring in the last ~2-3 weeks. When I leave a terminal window open on the desktop running the command: tail -f /var/log/Xorg.0.log and allow lots of time for the problem to occur, no lines are appended in the terminal even after the problem has happened, but when I then use Ctrl+Alt+F1 and log in at the terminal console, the following additional lines appear in /var/log/xorg.0.log : [ 3805.283] (II) event1 - Power Button: device removed [ 3805.296] (II) event0 - Power Button: device removed [ 3805.312] (II) event3 - Logitech USB Optical Mouse: device removed [ 3805.344] (II) event4 - Eee PC WMI hotkeys: device removed [ 3805.364] (II) event2 - AT Translated Set 2 keyboard: device removed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 16:37:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:8501] InstallationDate: Installed on 2020-05-17 (249 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-62-generic root=UUID=c8acacab-7716-4698-b0e0-6041467d4517 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1912670 Title: Mouse buttons and keyboard unresponsive after idle time Status in xorg package in Ubuntu: New Bug description: If I leave my desktop (Xubuntu 20.04.1 LTS, Xfce xfdesktop4 4.14.2-1, Xorg 1:7.7+19ubuntu14) idle for a few minutes, the mouse buttons and most keyboard presses become unresponsive. My "system power saving" setting is disabled (set to "never") and "display power management" is set to blank after 15 minutes, but the problem seems to occur sooner than that. Unplugging and re-inserting the mouse after a few seconds has no effect. The only keystrokes that have any effect are Ctrl+Alt+F1 for a terminal
[Touch-packages] [Bug 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: In Progress Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: New Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1912668] [NEW] [Q1U dynamic microphone - AT2020 USB, recording] fails after a while
Public bug reported: Opening sound control panel, or Audacity, ATH2020-USB microphone will show signal for a few seconds, then cut off (the meter stays stuck in last updated position). Same behavior using other apps that use the microphone. Changed USB port, still the same result. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: surefoot 1972 F pulseaudio /dev/snd/controlC2: surefoot 1972 F pulseaudio /dev/snd/controlC1: surefoot 1972 F pulseaudio /dev/snd/pcmC1D0c: surefoot 1972 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:00:16 2021 InstallationDate: Installed on 2020-10-31 (81 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 100 (Xonar Essence STX II)) - Xonar STX II Symptom_PulseAudioLog: janv. 21 14:34:39 STH10 dbus-daemon[1083]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3902 dmi.board.asset.tag: Default string dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3902:bd03/21/2018:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1912668 Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Opening sound control panel, or Audacity, ATH2020-USB microphone will show signal for a few seconds, then cut off (the meter stays stuck in last updated position). Same behavior using other apps that use the microphone. Changed USB port, still the same result. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: surefoot 1972 F pulseaudio /dev/snd/controlC2: surefoot 1972 F pulseaudio /dev/snd/controlC1: surefoot 1972 F pulseaudio /dev/snd/pcmC1D0c: surefoot 1972 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:00:16 2021 InstallationDate: Installed on 2020-10-31 (81 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 100 (Xonar Essence STX II)) - Xonar STX II Symptom_PulseAudioLog: janv. 21 14:34:39 STH10 dbus-daemon[1083]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3902 dmi.board.asset.tag: Default string dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default
[Touch-packages] [Bug 1876495] Re: bash-completion incorrectly shows source package names for APT
This bug was fixed in the package apt - 2.0.4 --- apt (2.0.4) focal; urgency=medium [ Julian Andres Klode ] * Merge 2.0.2ubuntu0.1 and 2.0.2ubuntu0.2 security updates with 2.0.3 release. * pkgnames: Correctly set the default for AllNames to false, and do not exclude virtual packages if --all-names is specified (LP: #1876495) * Remove expired domain that became nsfw from debian/changelog * patterns: Terminate short pattern by ~ and ! (LP: #1911676) * Improve immediate configuration handling (LP: #1871268) - Do not immediately configure m-a: same packages in lockstep - Ignore failures from immediate configuration. This does not change the actual installation ordering - we never passed the return code to the caller and installation went underway anyway if it could be ordered at a later stage, this just removes spurious after-the-fact errors. [ JCGoran ] * Fix "extended_states" typo in apt-mark(8) (Closes: #969086) apt (2.0.3) focal; urgency=medium [ Frans Spiesschaert ] * Dutch manpages translation update (Closes: #956313) [ David Kalnischkies ] * Add correct std namespace to nullptr_t [ Julian Andres Klode ] * Reinstate * wildcards (Closes: #953531) (LP: #1872200) * apt list: Fix behavior of regex vs fnmatch vs wildcards * debian/gbp.conf: We're in the 2.0.y branch * CI: Test on ubuntu:focal, not debian:unstable -- Julian Andres Klode Thu, 14 Jan 2021 12:49:00 +0100 ** Changed in: apt (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1876495 Title: bash-completion incorrectly shows source package names for APT Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] Source packages have been included in apt-cache pkgnames, and virtual packages have not been included in apt-cache pkgnames --all-names. The former leads to completions autocompleting to source package names where they only should complete to binaries. [Test case] An automated test case is included in the test suite test-ubuntu-bug-1876495-pkgnames-virtual It verifies that pkgnames does not return source package names, and that pkgnames --all-names does return source package names and virtual package names. [Where problems could occur] In the pkgnames command only. If there's a bug, it could exclude or include packages it should not. [Original bug report] Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Open terminal, enter one of the commands below 2a. apt install brisk 2b. apt source brisk-menu 2c. apt-get install brisk 2d. apt-get source brisk-menu 2e. apt-cache policy brisk Expected results: * The bash-completion should not lead to package name as there are no binary packages named with starting part "brisk" (see https://packages.ubuntu.com/search?suite=all=names=brisk ) Actual results: * all commands below get completed to the name of source package - in this example named "brisk-menu" (see https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames). This is absolutely unexpected, as user can not really install this package in binary form. ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30 Uname: Linux 5.4.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 2 20:35:48 2020 Dependencies: InstallationDate: Installed on 2020-04-22 (9 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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 1872200] Re: apt does not accept globs and regexes in some cases
This bug was fixed in the package apt - 2.0.4 --- apt (2.0.4) focal; urgency=medium [ Julian Andres Klode ] * Merge 2.0.2ubuntu0.1 and 2.0.2ubuntu0.2 security updates with 2.0.3 release. * pkgnames: Correctly set the default for AllNames to false, and do not exclude virtual packages if --all-names is specified (LP: #1876495) * Remove expired domain that became nsfw from debian/changelog * patterns: Terminate short pattern by ~ and ! (LP: #1911676) * Improve immediate configuration handling (LP: #1871268) - Do not immediately configure m-a: same packages in lockstep - Ignore failures from immediate configuration. This does not change the actual installation ordering - we never passed the return code to the caller and installation went underway anyway if it could be ordered at a later stage, this just removes spurious after-the-fact errors. [ JCGoran ] * Fix "extended_states" typo in apt-mark(8) (Closes: #969086) apt (2.0.3) focal; urgency=medium [ Frans Spiesschaert ] * Dutch manpages translation update (Closes: #956313) [ David Kalnischkies ] * Add correct std namespace to nullptr_t [ Julian Andres Klode ] * Reinstate * wildcards (Closes: #953531) (LP: #1872200) * apt list: Fix behavior of regex vs fnmatch vs wildcards * debian/gbp.conf: We're in the 2.0.y branch * CI: Test on ubuntu:focal, not debian:unstable -- Julian Andres Klode Thu, 14 Jan 2021 12:49:00 +0100 ** Changed in: apt (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Bug description: [Impact] Users can't use * wildcards anymore in focal, except by accident in apt list. For apt list, we now start restricting wildcard syntax to the same syntax install now accepts, and at the same time we remove the restrictions on which patterns are accepted (which only accepted patterns starting in ~ or ?), so !~napt now works, and does not accidentally match as a wildcard. [Test case] Test that * wildcards work for both install and list, and test that a ? wildcard does not. We included autopkgtests for those: BEGIN TESTS # # * wildcards should still work testsuccessequal "Listing... automatic1/now 1.0 i386 [installed,local] automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*' testfailureequal "Reading package lists... Building dependency tree... Reading state information... Note, selecting 'automatic1' for glob 'automatic*' Note, selecting 'automatic2' for glob 'automatic*' automatic1 is already the newest version (1.0). automatic1 set to manually installed. automatic2 is already the newest version (1.0). automatic2 set to manually installed. You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: broken : Depends: does-not-exist but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)." apt install -s 'automatic*' # other wildcards should fail testfailureequal "Listing... E: input:0-10: error: Expected pattern automatic? ^^" apt list 'automatic?' testfailureequal "Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package automatic?" apt install -s 'automatic?' END TESTS # Also it might be worth checking that apt list !~napt works. This used to produce an empty list, as it was accidentally matched as a wildcard and produced no result - now it produces every package whose name does not contain "apt". [Regression potential] The changes only affect interactive users, as apt(8) is not stable for in-script use, hence they can fix up their command-line if it stops working for them (though, really, more should work now). No scripts will be broken :) [Squashed in changes] The SRU also fixes potential build failures by correctly prefxing nullptr_t with the std:: namespace, and includes updated Dutch documentation. [Original bug report] Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
This bug was fixed in the package apt - 2.0.4 --- apt (2.0.4) focal; urgency=medium [ Julian Andres Klode ] * Merge 2.0.2ubuntu0.1 and 2.0.2ubuntu0.2 security updates with 2.0.3 release. * pkgnames: Correctly set the default for AllNames to false, and do not exclude virtual packages if --all-names is specified (LP: #1876495) * Remove expired domain that became nsfw from debian/changelog * patterns: Terminate short pattern by ~ and ! (LP: #1911676) * Improve immediate configuration handling (LP: #1871268) - Do not immediately configure m-a: same packages in lockstep - Ignore failures from immediate configuration. This does not change the actual installation ordering - we never passed the return code to the caller and installation went underway anyway if it could be ordered at a later stage, this just removes spurious after-the-fact errors. [ JCGoran ] * Fix "extended_states" typo in apt-mark(8) (Closes: #969086) apt (2.0.3) focal; urgency=medium [ Frans Spiesschaert ] * Dutch manpages translation update (Closes: #956313) [ David Kalnischkies ] * Add correct std namespace to nullptr_t [ Julian Andres Klode ] * Reinstate * wildcards (Closes: #953531) (LP: #1872200) * apt list: Fix behavior of regex vs fnmatch vs wildcards * debian/gbp.conf: We're in the 2.0.y branch * CI: Test on ubuntu:focal, not debian:unstable -- Julian Andres Klode Thu, 14 Jan 2021 12:49:00 +0100 ** Changed in: apt (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find
[Touch-packages] [Bug 1888654] Re: [UBUNTU 20.10] Accept vector alignment hints on z13 (binutils)
** Patch removed: "binutils_focal_sru.debdiff" https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654/+attachment/5455193/+files/binutils_focal_sru.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1888654 Title: [UBUNTU 20.10] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Groovy: Fix Released Bug description: On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. ---Additional Hardware Info--- n/a ---uname output--- n/a ---Debugger Data--- n/a Machine Type = z13 2964 ---Steps to Reproduce--- n/a Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888654/+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 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
** Patch added: "binutils_focal_sru.debdiff" https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1889742/+attachment/5455201/+files/binutils_focal_sru.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: Triaged Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: New Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Status in Ubuntu on IBM z Systems:
Fix Released
Status in elfutils package in Ubuntu:
Fix Released
Status in elfutils source package in Groovy:
Fix Released
Status in elfutils source package in Hirsute:
Fix Released
Bug description:
SRU Bug Template:
=
[Impact]
* There is an endianess problem in pid_memory_read that impacts
s390x.
* Due to this elfutils biarch test fails on s390x doing unwinding for
a 32 bit process.
[Fix]
* e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess
problem in pid_memory_read"
[Test Case]
* Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM
that comes with elfutils 0.181 or 0.182.
* Run the test script: 'run-backtrace-native-biarch.sh'
* It either core dumps without the patch in place - look for
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
[Where problems could occur]
* If the translation is not done right (shift of the upper 4 bytes + down on
big endian 64 bit targets) the situation is broken in the same way, and things
stay the same.
* But in worst case the changes in 'pid_memory_read' of
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures
other than s390x, in case the check for the endiness is wrong.
* But the changes are quite traceable and the additional code that fixes the
endianess problem is really only active on a big endian architecture.
[Other]
* The fix is upstream accepted with elfutils > 0.182.
__
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32
bit process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to
use libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+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 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat
This bug was fixed in the package elfutils - 0.181-1ubuntu0.1
---
elfutils (0.181-1ubuntu0.1) groovy; urgency=medium
* debian/patches/elfutils-lp1908756-groovy.patch:
IBM Z: Fix endianess problem in pid_memory_read
backport from elfutils 0.182+
- libdwfl/linux-pid-attach.c: shift the upper 4 bytes + down on big
endian 64 bit targets
- libdwfl/ChangeLog: updated the projects ChangeLog, too
Thanks to Andreas Krebbel (LP: #1908756)
-- Frank Heimes Fri, 08 Jan 2021 09:49:33
+0100
** Changed in: elfutils (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Status in Ubuntu on IBM z Systems:
Fix Released
Status in elfutils package in Ubuntu:
Fix Released
Status in elfutils source package in Groovy:
Fix Released
Status in elfutils source package in Hirsute:
Fix Released
Bug description:
SRU Bug Template:
=
[Impact]
* There is an endianess problem in pid_memory_read that impacts
s390x.
* Due to this elfutils biarch test fails on s390x doing unwinding for
a 32 bit process.
[Fix]
* e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess
problem in pid_memory_read"
[Test Case]
* Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM
that comes with elfutils 0.181 or 0.182.
* Run the test script: 'run-backtrace-native-biarch.sh'
* It either core dumps without the patch in place - look for
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
[Where problems could occur]
* If the translation is not done right (shift of the upper 4 bytes + down on
big endian 64 bit targets) the situation is broken in the same way, and things
stay the same.
* But in worst case the changes in 'pid_memory_read' of
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures
other than s390x, in case the check for the endiness is wrong.
* But the changes are quite traceable and the additional code that fixes the
endianess problem is really only active on a big endian architecture.
[Other]
* The fix is upstream accepted with elfutils > 0.182.
__
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32
bit process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to
use libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+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 1911676] Re: Short pattern not terminated by ~ or !
This bug was fixed in the package apt - 2.0.4
---
apt (2.0.4) focal; urgency=medium
[ Julian Andres Klode ]
* Merge 2.0.2ubuntu0.1 and 2.0.2ubuntu0.2 security updates with 2.0.3
release.
* pkgnames: Correctly set the default for AllNames to false, and do not
exclude virtual packages if --all-names is specified (LP: #1876495)
* Remove expired domain that became nsfw from debian/changelog
* patterns: Terminate short pattern by ~ and ! (LP: #1911676)
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
[ JCGoran ]
* Fix "extended_states" typo in apt-mark(8) (Closes: #969086)
apt (2.0.3) focal; urgency=medium
[ Frans Spiesschaert ]
* Dutch manpages translation update (Closes: #956313)
[ David Kalnischkies ]
* Add correct std namespace to nullptr_t
[ Julian Andres Klode ]
* Reinstate * wildcards (Closes: #953531) (LP: #1872200)
* apt list: Fix behavior of regex vs fnmatch vs wildcards
* debian/gbp.conf: We're in the 2.0.y branch
* CI: Test on ubuntu:focal, not debian:unstable
-- Julian Andres Klode Thu, 14 Jan 2021 12:49:00
+0100
** Changed in: apt (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1911676
Title:
Short pattern not terminated by ~ or !
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Bug description:
[Impact]
Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)
[Test Case]
Unit tests have been added that are run during build and check they are
parsed correctly
+ EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
+ EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");
[Where problems could occur]
Really just changing a string constant for this change in a function that
parses of words, so well, the only problem arising could be that words inside
patterns are recognized wrongly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1911676/+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 1912659] [NEW] [X570 UD, Realtek ALC887-VD, Green Headphone Out, Front] losing the sound
Public bug reported: alsa force-reload + reboot helps, but only temporarily (similar to Bug #1874689) Unplugging and plugging in the headphones again results in losing the sound. During the time I was reporting the bug, the sound was OK. I unplugged and plugged the headphones in -> no sound. Quite surprisingly, when I finished the bug reporting, the sound was back. Using Ubuntu 20.04 LTS. I have quite a new desktop, so some newer hardware may be responsible for the issues ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 17:20:23 2021 InstallationDate: Installed on 2020-07-02 (203 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: led 21 10:23:45 majkl-X570-UD dbus-daemon[1082]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=125 pid=1276 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") led 21 10:23:46 majkl-X570-UD dbus-daemon[1082]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=125 pid=1276 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [X570 UD, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20a dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20a:bd06/16/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1912659 Title: [X570 UD, Realtek ALC887-VD, Green Headphone Out, Front] losing the sound Status in alsa-driver package in Ubuntu: New Bug description: alsa force-reload + reboot helps, but only temporarily (similar to Bug #1874689) Unplugging and plugging in the headphones again results in losing the sound. During the time I was reporting the bug, the sound was OK. I unplugged and plugged the headphones in -> no sound. Quite surprisingly, when I finished the bug reporting, the sound was back. Using Ubuntu 20.04 LTS. I have quite a new desktop, so some newer hardware may be responsible for the issues ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 17:20:23 2021 InstallationDate: Installed on 2020-07-02 (203 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: led 21 10:23:45 majkl-X570-UD dbus-daemon[1082]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=125 pid=1276 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") led 21 10:23:46 majkl-X570-UD dbus-daemon[1082]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=125 pid=1276 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [X570 UD, Realtek ALC887-VD, Green Headphone
[Touch-packages] [Bug 1872200] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Bug description: [Impact] Users can't use * wildcards anymore in focal, except by accident in apt list. For apt list, we now start restricting wildcard syntax to the same syntax install now accepts, and at the same time we remove the restrictions on which patterns are accepted (which only accepted patterns starting in ~ or ?), so !~napt now works, and does not accidentally match as a wildcard. [Test case] Test that * wildcards work for both install and list, and test that a ? wildcard does not. We included autopkgtests for those: BEGIN TESTS # # * wildcards should still work testsuccessequal "Listing... automatic1/now 1.0 i386 [installed,local] automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*' testfailureequal "Reading package lists... Building dependency tree... Reading state information... Note, selecting 'automatic1' for glob 'automatic*' Note, selecting 'automatic2' for glob 'automatic*' automatic1 is already the newest version (1.0). automatic1 set to manually installed. automatic2 is already the newest version (1.0). automatic2 set to manually installed. You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: broken : Depends: does-not-exist but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)." apt install -s 'automatic*' # other wildcards should fail testfailureequal "Listing... E: input:0-10: error: Expected pattern automatic? ^^" apt list 'automatic?' testfailureequal "Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package automatic?" apt install -s 'automatic?' END TESTS # Also it might be worth checking that apt list !~napt works. This used to produce an empty list, as it was accidentally matched as a wildcard and produced no result - now it produces every package whose name does not contain "apt". [Regression potential] The changes only affect interactive users, as apt(8) is not stable for in-script use, hence they can fix up their command-line if it stops working for them (though, really, more should work now). No scripts will be broken :) [Squashed in changes] The SRU also fixes potential build failures by correctly prefxing nullptr_t with the std:: namespace, and includes updated Dutch documentation. [Original bug report] Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+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 1908756] Update Released
The verification of the Stable Release Update for elfutils has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in elfutils package in Ubuntu:
Fix Released
Status in elfutils source package in Groovy:
Fix Released
Status in elfutils source package in Hirsute:
Fix Released
Bug description:
SRU Bug Template:
=
[Impact]
* There is an endianess problem in pid_memory_read that impacts
s390x.
* Due to this elfutils biarch test fails on s390x doing unwinding for
a 32 bit process.
[Fix]
* e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess
problem in pid_memory_read"
[Test Case]
* Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM
that comes with elfutils 0.181 or 0.182.
* Run the test script: 'run-backtrace-native-biarch.sh'
* It either core dumps without the patch in place - look for
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
[Where problems could occur]
* If the translation is not done right (shift of the upper 4 bytes + down on
big endian 64 bit targets) the situation is broken in the same way, and things
stay the same.
* But in worst case the changes in 'pid_memory_read' of
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures
other than s390x, in case the check for the endiness is wrong.
* But the changes are quite traceable and the additional code that fixes the
endianess problem is really only active on a big endian architecture.
[Other]
* The fix is upstream accepted with elfutils > 0.182.
__
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32
bit process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to
use libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+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 1888654] Re: [UBUNTU 20.10] Accept vector alignment hints on z13 (binutils)
I applied the upstream change. ** Patch added: "binutils_focal_sru.debdiff" https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654/+attachment/5455193/+files/binutils_focal_sru.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1888654 Title: [UBUNTU 20.10] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Groovy: Fix Released Bug description: On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. ---Additional Hardware Info--- n/a ---uname output--- n/a ---Debugger Data--- n/a Machine Type = z13 2964 ---Steps to Reproduce--- n/a Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888654/+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 1871268] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
This bug was fixed in the package apt - 2.1.10ubuntu0.2 --- apt (2.1.10ubuntu0.2) groovy; urgency=medium [ JCGoran ] * Fix "extended_states" typo in apt-mark(8) (Closes: #969086) [ Jordi Mallach ] * Fix typo in Catalan translation. [ Julian Andres Klode ] * doc: Bump Ubuntu release from focal to groovy * pkgnames: Correctly set the default for AllNames to false, and do not exclude virtual packages if --all-names is specified (LP: #1876495) * Remove expired domain that became nsfw from debian/changelog * patterns: Terminate short pattern by ~ and ! (LP: #1911676) * Improve immediate configuration handling (LP: #1871268) - Do not immediately configure m-a: same packages in lockstep - Ignore failures from immediate configuration. This does not change the actual installation ordering - we never passed the return code to the caller and installation went underway anyway if it could be ordered at a later stage, this just removes spurious after-the-fact errors. [ Frans Spiesschaert ] * Dutch manpages translation update (Closes: #970037) [ Américo Monteiro ] * Portuguese manpages translation update (Closes: #968414) [ Helge Kreutzmann ] * German program translation update (Closes: #977938) [ Vangelis Skarmoutsos ] * Greek program translation update -- Julian Andres Klode Thu, 14 Jan 2021 12:29:25 +0100 ** Changed in: apt (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for
[Touch-packages] [Bug 1876495] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1876495 Title: bash-completion incorrectly shows source package names for APT Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] Source packages have been included in apt-cache pkgnames, and virtual packages have not been included in apt-cache pkgnames --all-names. The former leads to completions autocompleting to source package names where they only should complete to binaries. [Test case] An automated test case is included in the test suite test-ubuntu-bug-1876495-pkgnames-virtual It verifies that pkgnames does not return source package names, and that pkgnames --all-names does return source package names and virtual package names. [Where problems could occur] In the pkgnames command only. If there's a bug, it could exclude or include packages it should not. [Original bug report] Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Open terminal, enter one of the commands below 2a. apt install brisk 2b. apt source brisk-menu 2c. apt-get install brisk 2d. apt-get source brisk-menu 2e. apt-cache policy brisk Expected results: * The bash-completion should not lead to package name as there are no binary packages named with starting part "brisk" (see https://packages.ubuntu.com/search?suite=all=names=brisk ) Actual results: * all commands below get completed to the name of source package - in this example named "brisk-menu" (see https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames). This is absolutely unexpected, as user can not really install this package in binary form. ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30 Uname: Linux 5.4.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 2 20:35:48 2020 Dependencies: InstallationDate: Installed on 2020-04-22 (9 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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 1876495] Re: bash-completion incorrectly shows source package names for APT
This bug was fixed in the package apt - 2.1.10ubuntu0.2 --- apt (2.1.10ubuntu0.2) groovy; urgency=medium [ JCGoran ] * Fix "extended_states" typo in apt-mark(8) (Closes: #969086) [ Jordi Mallach ] * Fix typo in Catalan translation. [ Julian Andres Klode ] * doc: Bump Ubuntu release from focal to groovy * pkgnames: Correctly set the default for AllNames to false, and do not exclude virtual packages if --all-names is specified (LP: #1876495) * Remove expired domain that became nsfw from debian/changelog * patterns: Terminate short pattern by ~ and ! (LP: #1911676) * Improve immediate configuration handling (LP: #1871268) - Do not immediately configure m-a: same packages in lockstep - Ignore failures from immediate configuration. This does not change the actual installation ordering - we never passed the return code to the caller and installation went underway anyway if it could be ordered at a later stage, this just removes spurious after-the-fact errors. [ Frans Spiesschaert ] * Dutch manpages translation update (Closes: #970037) [ Américo Monteiro ] * Portuguese manpages translation update (Closes: #968414) [ Helge Kreutzmann ] * German program translation update (Closes: #977938) [ Vangelis Skarmoutsos ] * Greek program translation update -- Julian Andres Klode Thu, 14 Jan 2021 12:29:25 +0100 ** Changed in: apt (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1876495 Title: bash-completion incorrectly shows source package names for APT Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] Source packages have been included in apt-cache pkgnames, and virtual packages have not been included in apt-cache pkgnames --all-names. The former leads to completions autocompleting to source package names where they only should complete to binaries. [Test case] An automated test case is included in the test suite test-ubuntu-bug-1876495-pkgnames-virtual It verifies that pkgnames does not return source package names, and that pkgnames --all-names does return source package names and virtual package names. [Where problems could occur] In the pkgnames command only. If there's a bug, it could exclude or include packages it should not. [Original bug report] Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Open terminal, enter one of the commands below 2a. apt install brisk 2b. apt source brisk-menu 2c. apt-get install brisk 2d. apt-get source brisk-menu 2e. apt-cache policy brisk Expected results: * The bash-completion should not lead to package name as there are no binary packages named with starting part "brisk" (see https://packages.ubuntu.com/search?suite=all=names=brisk ) Actual results: * all commands below get completed to the name of source package - in this example named "brisk-menu" (see https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames). This is absolutely unexpected, as user can not really install this package in binary form. ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30 Uname: Linux 5.4.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 2 20:35:48 2020 Dependencies: InstallationDate: Installed on 2020-04-22 (9 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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 1911676] Update Released
The verification of the Stable Release Update for apt has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/1911676
Title:
Short pattern not terminated by ~ or !
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Focal:
Fix Committed
Status in apt source package in Groovy:
Fix Released
Bug description:
[Impact]
Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)
[Test Case]
Unit tests have been added that are run during build and check they are
parsed correctly
+ EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
+ EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");
[Where problems could occur]
Really just changing a string constant for this change in a function that
parses of words, so well, the only problem arising could be that words inside
patterns are recognized wrongly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1911676/+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 1911676] Re: Short pattern not terminated by ~ or !
This bug was fixed in the package apt - 2.1.10ubuntu0.2
---
apt (2.1.10ubuntu0.2) groovy; urgency=medium
[ JCGoran ]
* Fix "extended_states" typo in apt-mark(8) (Closes: #969086)
[ Jordi Mallach ]
* Fix typo in Catalan translation.
[ Julian Andres Klode ]
* doc: Bump Ubuntu release from focal to groovy
* pkgnames: Correctly set the default for AllNames to false, and do not
exclude virtual packages if --all-names is specified (LP: #1876495)
* Remove expired domain that became nsfw from debian/changelog
* patterns: Terminate short pattern by ~ and ! (LP: #1911676)
* Improve immediate configuration handling (LP: #1871268)
- Do not immediately configure m-a: same packages in lockstep
- Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
[ Frans Spiesschaert ]
* Dutch manpages translation update (Closes: #970037)
[ Américo Monteiro ]
* Portuguese manpages translation update (Closes: #968414)
[ Helge Kreutzmann ]
* German program translation update (Closes: #977938)
[ Vangelis Skarmoutsos ]
* Greek program translation update
-- Julian Andres Klode Thu, 14 Jan 2021 12:29:25
+0100
** Changed in: apt (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1911676
Title:
Short pattern not terminated by ~ or !
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Focal:
Fix Committed
Status in apt source package in Groovy:
Fix Released
Bug description:
[Impact]
Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)
[Test Case]
Unit tests have been added that are run during build and check they are
parsed correctly
+ EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
+ EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");
[Where problems could occur]
Really just changing a string constant for this change in a function that
parses of words, so well, the only problem arising could be that words inside
patterns are recognized wrongly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1911676/+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 1912631] Re: package python-apt 2.0.0ubuntu0.20.04.3 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 127
It seems like this system is corrupted, it is missing /usr/bin/pycompile despite python2-minimal being installed. Probably python2-minimal needs to be reinstalled? ** Changed in: python-defaults (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1912631 Title: package python-apt 2.0.0ubuntu0.20.04.3 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 127 Status in python-defaults package in Ubuntu: Incomplete Bug description: E: Sub-process /usr/bin/dpkg returned an error code (1) this error occur from last 2 days i don't know why please provide solution. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python-apt 2.0.0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: python-apt:amd64: Install python-pycurl:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 17:32:21 2021 ErrorMessage: installed python-apt package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-29 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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.2ubuntu0.2 SourcePackage: python-apt Title: package python-apt 2.0.0ubuntu0.20.04.3 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1912631/+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 1912631] Re: package python-apt 2.0.0ubuntu0.20.04.3 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 127
Setting up python-wxversion (3.0.2.0+dfsg-8build1) ... /var/lib/dpkg/info/python-wxversion.postinst: 6: pycompile: not found [1mdpkg:[0m error processing package python-wxversion (--configure): installed python-wxversion package post-installation script subprocess returned error exit status 127 Setting up python-apt (2.0.0ubuntu0.20.04.3) ... /var/lib/dpkg/info/python-apt.postinst: 6: pycompile: not found [1mdpkg:[0m error processing package python-apt (--configure): installed python-apt package post-installation script subprocess returned error exit status 127 ** Package changed: python-apt (Ubuntu) => python-defaults (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1912631 Title: package python-apt 2.0.0ubuntu0.20.04.3 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 127 Status in python-defaults package in Ubuntu: Incomplete Bug description: E: Sub-process /usr/bin/dpkg returned an error code (1) this error occur from last 2 days i don't know why please provide solution. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python-apt 2.0.0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: python-apt:amd64: Install python-pycurl:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 17:32:21 2021 ErrorMessage: installed python-apt package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-29 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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.2ubuntu0.2 SourcePackage: python-apt Title: package python-apt 2.0.0ubuntu0.20.04.3 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1912631/+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 1904082] Re: apport's log collecting leaks MAC addresses maybe helping WiFi attacks?
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1904082 Title: apport's log collecting leaks MAC addresses maybe helping WiFi attacks? Status in apport package in Ubuntu: New Bug description: Some people configure their Internet WiFi modems such that only certain devices, defined by their MAC addresses, can (try to?) connect. I am aware this is VERY WEAK "security" since MAC addresses are easily spoofed. It occurs to me that the logs collected by apport-cli(1) and friends, when reporting a bug, contain the system's MAC addresses. Those logs are normally publicly readable by anyone browsing Launchpad. That means villains could reap (collect) MAC addresses to spoof and try to obtain an unintended WiFi connection. (Isn't necessarily easy since the attacker would have(?) to be within range of the modem to try?) I am NOT saying this has happened — I have no idea. I just wanted to bring this hypothetical(?) problem/attack to your attention. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.12 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 664:1000:125:0:2020-11-13 03:00:18.498740147 +0100:2020-11-13 03:00:18.498740147 +0100:/var/crash/_usr_bin_kglobalaccel5.1000.upload 600:118:125:37:2020-11-13 03:00:19.490721528 +0100:2020-11-13 03:00:19.490721528 +0100:/var/crash/_usr_bin_kglobalaccel5.1000.uploaded 640:1000:125:798567:2020-11-13 03:00:16.626756668 +0100:2020-11-13 03:00:17.626756668 +0100:/var/crash/_usr_bin_kglobalaccel5.1000.crash Date: Fri Nov 13 03:03:36 2020 InstallationDate: Installed on 2020-10-19 (24 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1904082/+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 1848330] Re: Installing auditd sometimes fails in post-inst
I'd like to see some testing from someone actually affected please.
Otherwise we'd be releasing a change that risks regression to users not
affected, for a bug that we're not even sure if we've fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1848330
Title:
Installing auditd sometimes fails in post-inst
Status in audit package in Ubuntu:
Fix Released
Status in audit source package in Bionic:
Fix Committed
Status in audit package in Debian:
New
Bug description:
[Impact]
Sometimes, auditd will get stuck when starting up, causing systemd to
kill it after a while since it (systemd) never got the start
notification.
Upstream troubleshooted this to be caused by calling a syslog()
function inside a signal handler.
[Test Case]
There is no reliable test case to reproduce the bug, other than trying the
fixed packages on an affected system where the hang occurs more frequently.
Basically:
sudo systemctl stop auditd
sudo systemctl start auditd
should work reliably. Do not run that in a tight loop, however, as
that will trigger a it's-restarting-too-frequently failure.
[Where problems could occur]
- if auditd fails to start, then the first fallback is syslog, and if that is
not picking up the audit messages, the last resort is the kernel buffer, which
can fill up. In the case it fills up, audit logs will be lost.
- it's possible to configure the audit system to panic() the machine
if audit messages are lost or otherwise not able to be recorded
(auditctl -f 2; default is 1 which is printk())
- the update restarts auditd as expected. Misconfiguration on very
very busy systems could mean that audit logs would be lost during the
brief moment the service is restarted. If that's the case, this update
would just be one more way to trigger it, but not be the root cause of
the problem
- similarly, as is usual with updates that restart services, it's
possible than an incorrect configuration for auditd is present, but
was never loaded before. The restart will load the config, and will
fail in such a case.
- this update removes a logging statement that occurs during startup:
("dispatcher %d reaped", pid)
It's unlikely, but possible, that some monitoring software could be
looking for that message in the logs. It won't be there anymore after
this update.
[Other Info]
The patch is committed upstream and part of the 2.8.5 release, which is
present in Focal and later.
The real fix for this bug is just dropping the audit_msg() call in the signal
handler code. But the original reporter of the bug, who is also who came up
with the fix (see https://bugzilla.redhat.com/show_bug.cgi?id=1587995#c4)
stated that with the 3 changes in the patch the startup hang didn't happen to
him anymore. Since this bug is difficult to reproduce elsewhere (either you
have it, or you don't), I chose to keep the 3 changes instead of just the
removal of the audit_msg() call.
[Original Description]
This happens sometimes when installing auditd on Ubuntu 18.04.2, most
installations work successfully, though. Re-running the install also
fixes the issue, but the failure breaks our automation. The log from
the failure looks like this:
# apt install auditd
...
Setting up auditd (1:2.8.2-1ubuntu1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/auditd.service →
/lib/systemd/system/auditd.service.
Job for auditd.service failed because a timeout was exceeded.
See "systemctl status auditd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript auditd, action "start" failed.
● auditd.service - Security Auditing Service
Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor
preset: enabled)
Active: failed (Result: timeout) since Tue 2019-09-17 18:43:06 UTC; 11ms
ago
Docs: man:auditd(8)
https://github.com/linux-audit/audit-documentation
Process: 9702 ExecStart=/sbin/auditd (code=killed, signal=KILL)
Sep 17 18:40:06 compute-node21 systemd[1]: Starting Security Auditing
Service...
Sep 17 18:40:06 compute-node21 auditd[9703]: Started dispatcher:
/sbin/audispd pid: 9705
Sep 17 18:40:06 compute-node21 audispd[9705]: No plugins found, exiting
Sep 17 18:41:36 compute-node21 systemd[1]: auditd.service: Start operation
timed out. Terminating.
Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: State
'stop-sigterm' timed out. Killing.
Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Killing process
9702 (auditd) with signal SIGKILL.
Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Killing process
9703 (auditd) with signal SIGKILL.
Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Control process
exited, code=killed status=9
Sep 17 18:43:06 compute-node21 systemd[1]: auditd.service: Failed
[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)
Oh yeah, that helps! :-) Uldis, can you confirm? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1910537 Title: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer) Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.family: Type1Family dmi.product.name: AO756 dmi.product.sku: Type1Sku0 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
[Touch-packages] [Bug 1911903] Re: Auto-reconnection of wifi doesn't work
** Attachment added: "Evidences" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1911903/+attachment/5455167/+files/Evidences -- 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/1911903 Title: Auto-reconnection of wifi doesn't work Status in network-manager package in Ubuntu: Incomplete Bug description: Hi everyone :) It's a problem that occurs without any possible correlation with other event (wake up, sleep etc). In the middle of a session the Wi-Fi simply stop working and not only the system doesn't reconnect automatically, but you need to turn off and back on the Wi-Fi to be able to continue your activities. IDK if it's related, but sometimes also happens that the other Wi-Fi networks around me are not visible in the setting. If I can help in any way with logs of any other information please contact me Antonio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 12:56:08 2021 InstallationDate: Installed on 2020-11-03 (73 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.178.1 dev wlp2s0b1 proto dhcp metric 20600 169.254.0.0/16 dev br-90c79c39374f scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-90c79c39374f proto kernel scope link src 172.18.0.1 linkdown 192.168.178.0/24 dev wlp2s0b1 proto kernel scope link src 192.168.178.52 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1911903/+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 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in elfutils package in Ubuntu:
Fix Released
Status in elfutils source package in Groovy:
Fix Committed
Status in elfutils source package in Hirsute:
Fix Released
Bug description:
SRU Bug Template:
=
[Impact]
* There is an endianess problem in pid_memory_read that impacts
s390x.
* Due to this elfutils biarch test fails on s390x doing unwinding for
a 32 bit process.
[Fix]
* e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess
problem in pid_memory_read"
[Test Case]
* Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM
that comes with elfutils 0.181 or 0.182.
* Run the test script: 'run-backtrace-native-biarch.sh'
* It either core dumps without the patch in place - look for
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
[Where problems could occur]
* If the translation is not done right (shift of the upper 4 bytes + down on
big endian 64 bit targets) the situation is broken in the same way, and things
stay the same.
* But in worst case the changes in 'pid_memory_read' of
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures
other than s390x, in case the check for the endiness is wrong.
* But the changes are quite traceable and the additional code that fixes the
endianess problem is really only active on a big endian architecture.
[Other]
* The fix is upstream accepted with elfutils > 0.182.
__
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32
bit process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to
use libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+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 1908756] Comment bridged from LTC Bugzilla
--- Comment From andreas.kreb...@de.ibm.com 2021-01-21 07:35 EDT---
I've enabled groovy-proposed on my system and have seen the problematic
testcase running successfully with:
apt-get --build source elfutils
PASS: run-backtrace-native-biarch.sh
As expected it fails with the old version of the package:
apt-get --build source elfutils=0.181-1
FAIL: run-backtrace-native-biarch.sh
I see the test being skipped in the canonical build logs. Is biarch
testing disabled in that environment?
https://launchpadlibrarian.net/497757891/buildlog_ubuntu-groovy-
s390x.elfutils_0.181-1_BUILDING.txt.gz
SKIP: run-backtrace-native-biarch.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Status in Ubuntu on IBM z Systems:
In Progress
Status in elfutils package in Ubuntu:
Fix Released
Status in elfutils source package in Groovy:
Fix Committed
Status in elfutils source package in Hirsute:
Fix Released
Bug description:
SRU Bug Template:
=
[Impact]
* There is an endianess problem in pid_memory_read that impacts
s390x.
* Due to this elfutils biarch test fails on s390x doing unwinding for
a 32 bit process.
[Fix]
* e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess
problem in pid_memory_read"
[Test Case]
* Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM
that comes with elfutils 0.181 or 0.182.
* Run the test script: 'run-backtrace-native-biarch.sh'
* It either core dumps without the patch in place - look for
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
[Where problems could occur]
* If the translation is not done right (shift of the upper 4 bytes + down on
big endian 64 bit targets) the situation is broken in the same way, and things
stay the same.
* But in worst case the changes in 'pid_memory_read' of
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures
other than s390x, in case the check for the endiness is wrong.
* But the changes are quite traceable and the additional code that fixes the
endianess problem is really only active on a big endian architecture.
[Other]
* The fix is upstream accepted with elfutils > 0.182.
__
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32
bit process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to
use libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+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 1912609] Re: mac80211_hwsim: hostapd fails to start with S1G band
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1912609 Title: mac80211_hwsim: hostapd fails to start with S1G band Status in wpa package in Ubuntu: New Status in wpa source package in Hirsute: New Bug description: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+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 1912631] [NEW] package python-apt 2.0.0ubuntu0.20.04.3 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 127
Public bug reported: E: Sub-process /usr/bin/dpkg returned an error code (1) this error occur from last 2 days i don't know why please provide solution. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python-apt 2.0.0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: python-apt:amd64: Install python-pycurl:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 17:32:21 2021 ErrorMessage: installed python-apt package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-29 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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.2ubuntu0.2 SourcePackage: python-apt Title: package python-apt 2.0.0ubuntu0.20.04.3 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-apt (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 python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1912631 Title: package python-apt 2.0.0ubuntu0.20.04.3 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 127 Status in python-apt package in Ubuntu: New Bug description: E: Sub-process /usr/bin/dpkg returned an error code (1) this error occur from last 2 days i don't know why please provide solution. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python-apt 2.0.0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: python-apt:amd64: Install python-pycurl:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 17:32:21 2021 ErrorMessage: installed python-apt package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-29 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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.2ubuntu0.2 SourcePackage: python-apt Title: package python-apt 2.0.0ubuntu0.20.04.3 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1912631/+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 1838258] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-21 06:06 EDT--- IBM Bugzilla status->closed, Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1838258 Title: Unable to configure VLAN on an additional OSA interface Status in Ubuntu on IBM z Systems: Fix Released Status in iproute2 package in Ubuntu: Expired Status in linux package in Ubuntu: Fix Released Bug description: After installing a base Ubuntu 18.04.1 server, an additional OSA device "e530" is attached and configured with chzdev. Then a VLAN configuration should be applied using the ip command. However this results in the error message "RTNETLINK answers: File exists". >snip ip link add link ence530 name ence530.209 type vlan id 209 RTNETLINK answers: File exists snip< Executing the same steps on an Ubuntu 16.04.5 server, the ip command finishes without an error message but the VLAN interface is also not configured. Reproduction: - Install a 18.04.1 server - attach an additional OSA interface - configure a VLAN using the ip command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1838258/+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 1838258] Re: Unable to configure VLAN on an additional OSA interface
Thx for the re-test and update - with that I'm closing this ticket now. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: ubuntu-z-systems Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1838258 Title: Unable to configure VLAN on an additional OSA interface Status in Ubuntu on IBM z Systems: Fix Released Status in iproute2 package in Ubuntu: Expired Status in linux package in Ubuntu: Fix Released Bug description: After installing a base Ubuntu 18.04.1 server, an additional OSA device "e530" is attached and configured with chzdev. Then a VLAN configuration should be applied using the ip command. However this results in the error message "RTNETLINK answers: File exists". >snip ip link add link ence530 name ence530.209 type vlan id 209 RTNETLINK answers: File exists snip< Executing the same steps on an Ubuntu 16.04.5 server, the ip command finishes without an error message but the VLAN interface is also not configured. Reproduction: - Install a 18.04.1 server - attach an additional OSA interface - configure a VLAN using the ip command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1838258/+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 1912616] [NEW] missing GDPR consent for Agenda application for meteo data (Ubuntu 20.10)
Public bug reported: Hello I've just installed a fresh Ubuntu 20.10. I launch the Agenda application and see that meteo data are displayed in 3 days. I think those meteo data come from a tier provider, but Ubuntu or Agenda application never ask me for consent like GDPR require. Best regards (and thanks a lot for those so great softwares!) ** Affects: agenda.app (Ubuntu) Importance: Undecided Status: New ** Tags: gdpr ** Summary changed: - missing GDPR consent for Agenda application at Ubuntu installation + missing GDPR consent for Agenda application for meteo data (Ubuntu 20.10) ** Package changed: base-files (Ubuntu) => agenda.app (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1912616 Title: missing GDPR consent for Agenda application for meteo data (Ubuntu 20.10) Status in agenda.app package in Ubuntu: New Bug description: Hello I've just installed a fresh Ubuntu 20.10. I launch the Agenda application and see that meteo data are displayed in 3 days. I think those meteo data come from a tier provider, but Ubuntu or Agenda application never ask me for consent like GDPR require. Best regards (and thanks a lot for those so great softwares!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/agenda.app/+bug/1912616/+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 1838258] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-21 04:47 EDT--- Try Installation UBUNTU 18.04.02 add Vlan Interface to additional Qeth device works fine for me encbd00: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 02:00:00:13:f0:1b brd ff:ff:ff:ff:ff:ff inet 172.18.40.17/15 brd 172.19.255.255 scope global encbd00 valid_lft forever preferred_lft forever inet6 fe80::ff:fe13:f01b/64 scope link valid_lft forever preferred_lft forever 24: encb000: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 02:00:00:15:0f:2c brd ff:ff:ff:ff:ff:ff inet6 fe80::ff:fe15:f2c/64 scope link valid_lft forever preferred_lft forever 25: encb00.202@encb000: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:15:0f:2c brd ff:ff:ff:ff:ff:ff inet6 fe80::ff:fe15:f2c/64 scope link valid_lft forever preferred_lft forever root@t83lp17:~# uname Linux root@t83lp17:~# uname -a Linux t83lp17 4.15.0-132-generic #136-Ubuntu SMP Tue Jan 12 15:00:49 UTC 2021 s390x s390x s390x GNU/Linux root@t83lp17:~# lsb lsblklsb_release root@t83lp17:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 root@t83lp17:~# uname -a Linux t83lp17 4.15.0-132-generic #136-Ubuntu SMP Tue Jan 12 15:00:49 UTC 2021 s390x s390x s390x GNU/Linux root@t83lp17:~# Try to do an upgrade from UBUNTU18.04.01 as described from Frank, work as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1838258 Title: Unable to configure VLAN on an additional OSA interface Status in Ubuntu on IBM z Systems: Incomplete Status in iproute2 package in Ubuntu: Expired Status in linux package in Ubuntu: Incomplete Bug description: After installing a base Ubuntu 18.04.1 server, an additional OSA device "e530" is attached and configured with chzdev. Then a VLAN configuration should be applied using the ip command. However this results in the error message "RTNETLINK answers: File exists". >snip ip link add link ence530 name ence530.209 type vlan id 209 RTNETLINK answers: File exists snip< Executing the same steps on an Ubuntu 16.04.5 server, the ip command finishes without an error message but the VLAN interface is also not configured. Reproduction: - Install a 18.04.1 server - attach an additional OSA interface - configure a VLAN using the ip command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1838258/+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 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
** Changed in: ubuntu-z-systems Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: Triaged Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: New Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1912609] Re: mac80211_hwsim: hostapd fails to start with S1G band
** Patch added: "Upstream cherry pick for S1G band fix" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+attachment/5455144/+files/wpa_2.9-1ubuntu10.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1912609 Title: mac80211_hwsim: hostapd fails to start with S1G band Status in wpa package in Ubuntu: New Status in wpa source package in Hirsute: New Bug description: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+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 1912609] [NEW] mac80211_hwsim: hostapd fails to start with S1G band
Public bug reported: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Affects: wpa (Ubuntu Hirsute) Importance: Undecided Status: New ** Patch added: "Upstream cherry pick for S1G band fix" https://bugs.launchpad.net/bugs/1912609/+attachment/5455142/+files/wpa_2.9-1ubuntu10.debdiff ** Also affects: wpa (Ubuntu Hirsute) Importance: Undecided Status: New ** Patch removed: "Upstream cherry pick for S1G band fix" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+attachment/5455142/+files/wpa_2.9-1ubuntu10.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1912609 Title: mac80211_hwsim: hostapd fails to start with S1G band Status in wpa package in Ubuntu: New Status in wpa source package in Hirsute: New Bug description: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+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 1912526] Re: cannot import new keys if another malformed key exists
It's a legacy tool nobody should be using anymore. It's been like what, half a decade or so, we've been telling people to stop it, and drop files into trusted.gpg.d. It will go away in 2022. So I'm not super excited about spending time investigating and fixing this, but I guess I'll have a crack at it. -- 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/1912526 Title: cannot import new keys if another malformed key exists Status in apt package in Ubuntu: New Bug description: "apt-key add" fails to import keys if there exists another key with a malformed file name. Such malformed key names used to be provided by the openSUSE Build Service (https://github.com/openSUSE/software-o-o/issues/842). After importing such malformed key, future key imports will fail with something like: $ sudo apt-key add linux_signing_key.pub gpg: invalid key resource URL '/tmp/apt-key-gpghome.f8IaqZ48Ze/isv:ownCloud:desktop.asc.gpg' gpg: keyblock resource '(null)': General error even though no such file "isv:ownCloud:desktop.asc.gpg" exists anywhere on the filesystem. This affects deb packages that import public repo keys during installation, such as Google Chrome or Vivaldi, and results in minor issues such as breaking GUI tools and CLI warnings, and the major issue that the installed repo cannot be used anymore to update the software (Google Chrome, Vivaldi). apt-key should be robust to such issues and continue importing keys. As in the example above, apt-key should import "linux_signing_key.pub" no matter if another unrelated key is malformed etc. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.2 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: openafs nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 19:24:34 2021 InstallationDate: Installed on 2020-04-24 (271 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1912526/+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
