[Touch-packages] [Bug 2051990] Re: python3-defaults 3.12 causes aubio to fail to build from source
** Changed in: aubio (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults 3.12 causes aubio to fail to build from source
Status in aubio package in Ubuntu:
New
Status in python3-defaults package in Ubuntu:
New
Status in aubio package in Debian:
New
Bug description:
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
/<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence
'\d'
return re.split('\d+$',s)[0]
/<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape
sequence '\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
/<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape
sequence '\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
Traceback (most recent call last):
File "/<>/./waf", line 164, in
from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in
from waflib import
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in
from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in
from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in
import os,re,imp,sys
ModuleNotFoundError: No module named 'imp'
make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2024-02-01T21:23:22Z
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aubio/+bug/2051990/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
Hi Krister, I have finally seen this occur in real life with my own two eyes! You are absolutely correct, the 4-retry doesn't seem to be sufficient sometimes. The reproducer works on Focal and previous in about 20 minutes, so its easy to see the issue trigger on Focal. But Focal and previous doesn't retry at all. On Jammy, Mantic and noble, it took about a week straight, but I managed to get it to trigger for each of them. Start Tue Jan 16 01:57:20 UTC 2024 Tue Jan 16 02:18:53 UTC 2024 End Tue Jan 23 20:12:28 UTC 2024 Tue Jan 23 14:32:08 UTC 2024 The 4-retry does help, and helps quite a lot really. Anyway, I upgraded my test environment to the test packages, and I will leave them running for a week. If things look good then, I'll get these patches sponsored for SRU. Sorry for the delay, but I really wanted to see it fail on Jammy, Mantic and Noble before we go patching them. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: In Progress Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: In Progress Status in e2fsprogs source package in Jammy: In Progress Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: In Progress Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 1958019]
(In reply to Lukas from comment #814) > (In reply to Jacob Garby from comment #813) > > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of nowhere, > > the speaker started working. I have no idea how -- I did not change > anything > > manually. I suspect it's a new kernel version that did it. > > > > I'm on Arch Linux, and I can't remember which kernel version I have > > installed (but I can update when I get home later today). > > > > Anyway, good news! > > Amazing > > I would like to reproduce this. You can find out your current kernel version > with the command "uname -r". The installed sound packages/libs would also be > interesting. What I know of would be to look at the alsa version. > Someone else surely has more information on what to specificly look for and > how. Okay, so my kernel version is 6.7.2-arch1-1 These are some (maybe all) of the audio related packages I have installed: kpipewire 5.27.10-1 libpipewire 1:1.0.1-2 pipewire 1:1.0.1-2 pipewire-alsa 1:1.0.1-2 pipewire-audio 1:1.0.1-2 pipewire-jack 1:1.0.1-2 pipewire-pulse 1:1.0.1-2 libpulse 17.0-3 pipewire-pulse 1:1.0.1-2 projectm-pulseaudio 3.1.12-4 But I can verify that my speaker did also work _before_ I switched from Pulseaudio to Pipewire, seems both should work. The result of running alsa-info is here: http://alsa- project.org/db/?f=07a1fdaf34a424adc27dbb6be3f417995df6994f Good luck! -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1970069] Re: Annoying boot messages interfering with splash screen
The blanking from GRUB_TIMEOUT>0 will be made much worse by CONFIG_FB_EFI=n because usually in Ubuntu it's the efifb that restores the logo after Grub has wiped it. I think not having CONFIG_FB_EFI at the same time as using GRUB_TIMEOUT>0 explains your previous "really long time of a black screen". I can tell you've restored GRUB_TIMEOUT=0 in the video and the one remaining screen blank at Plymouth's startup might be bug 1836858. But either way it's not this bug. Related bugs can be found at https://bugs.launchpad.net/ubuntu/+bugs?field.tag=flickerfreeboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
With your change Fedora and Ubuntu are now behaving relatively similarly. * Both have a deficiency where the handoff from BGRT logo to Plymouth is doing a modeset for some reason. * Due to something in Fedora's GRUB it's a little clearer when GRUB starts. Here's various artifacts if you want to be able to compare anything since I have both on the same hardware. I ran the same kernel binary that has your patches on both (but on Fedora it behavedthe same with a stock one). Ubuntu booting (video): https://youtu.be/1J0_Vg1pScQ Kernel config: https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-kernel-config-both Ubuntu /etc/default/grub: https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-ubuntu-etc-default-grub Ubuntu journal: https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-ubuntu-journal Fedora booting (video): https://youtu.be/IzesNHpM-nw Fedora journal: https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-fedora-journal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
Ah I did have GRUB_TIMEOUT set; I hadn't expected that caused a black screen. Moving that to zero certainly helps. It's a lot better; but still not perfect. Let me get things back to as close as possible to stock and capture logs and a videos to compare with Ubuntu and Fedora with this exact same kernel and I'll get back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2051512] Re: apport ftbfs with Python 3.12 as the default
After fixing uninitialized variable or ignoring linter, the following
test failures occur:
=== FAILURES ===
_ TestApportUnpack.test_unpack _
self =
def test_unpack(self):
"""apport-unpack for all possible data types"""
process = self._call_apport_unpack([self.report_file, self.unpack_dir])
self.assertEqual(process.returncode, 0)
self.assertEqual(process.stderr, "")
self.assertEqual(process.stdout, "")
self.assertEqual(self._get_unpack("utf8"), self.utf8_str)
self.assertEqual(self._get_unpack("unicode"), self.utf8_str)
self.assertEqual(self._get_unpack("binary"), self.bindata)
> self.assertEqual(self._get_unpack("compressed"), b"FooFoo!")
E AssertionError: b'' != b'FooFoo!'
tests/integration/test_apport_unpack.py:65: AssertionError
___ T.test_compressed_values ___
self =
def test_compressed_values(self):
"""Handle of CompressedValue values."""
large_val = b"A" * 500
pr = problem_report.ProblemReport()
pr["Foo"] = problem_report.CompressedValue(b"FooFoo!")
pr["Bin"] = problem_report.CompressedValue()
pr["Bin"].set_value(bin_data)
pr["Large"] = problem_report.CompressedValue(large_val)
self.assertTrue(isinstance(pr["Foo"], problem_report.CompressedValue))
self.assertTrue(isinstance(pr["Bin"], problem_report.CompressedValue))
> self.assertEqual(pr["Foo"].get_value(), b"FooFoo!")
tests/integration/test_problem_report.py:42:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
problem_report.py:79: in get_value
return gzip.GzipFile(fileobj=io.BytesIO(self.gzipvalue)).read()
/usr/lib/python3.12/gzip.py:324: in read
return self._buffer.read(size)
/usr/lib/python3.12/_compression.py:118: in readall
while data := self.read(sys.maxsize):
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , size =
9223372036854775807
def read(self, size=-1):
if size < 0:
return self.readall()
# size=0 is special because decompress(max_length=0) is not supported
if not size:
return b""
# For certain input data, a single
# call to decompress() may not return
# any data. In this case, retry until we get some data or reach EOF.
while True:
if self._decompressor.eof:
# Ending case: we've come to the end of a member in the file,
# so finish up this member, and read a new gzip header.
# Check the CRC and file size, and set the flag so we read
# a new member
self._read_eof()
self._new_member = True
self._decompressor = self._decomp_factory(
**self._decomp_args)
if self._new_member:
# If the _new_member flag is set, we have to
# jump to the next member, if there is one.
self._init_read()
if not self._read_gzip_header():
self._size = self._pos
return b""
self._new_member = False
# Read a chunk of data from the file
if self._decompressor.needs_input:
buf = self._fp.read(READ_BUFFER_SIZE)
uncompress = self._decompressor.decompress(buf, size)
else:
uncompress = self._decompressor.decompress(b"", size)
if self._decompressor.unused_data != b"":
# Prepend the already read bytes to the fileobj so they can
# be seen by _read_eof() and _read_gzip_header()
self._fp.prepend(self._decompressor.unused_data)
if uncompress != b"":
break
if buf == b"":
> raise EOFError("Compressed file ended before the "
"end-of-stream marker was reached")
E EOFError: Compressed file ended before the end-of-stream marker
was reached
/usr/lib/python3.12/gzip.py:547: EOFError
_ T.test_extract_keys __
self =
def test_extract_keys(self):
"""extract_keys() with various binary elements."""
# create a test report with binary elements
large_val = b"A" * 500
pr = problem_report.ProblemReport()
pr["Txt"] = "some text"
pr["MoreTxt"] = "some more text"
pr["Foo"] = problem_report.CompressedValue(b"FooFoo!")
pr["Uncompressed"] = bin_data
pr["Bin"] = problem_report.CompressedValue()
pr["Bin"].set_value(bin_data)
pr["Large"] = problem_report.CompressedValue(large_val)
pr["Multiline"] =
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
GRUB_TIMEOUT > 0 also causes the vendor logo to be replaced by a black screen, but that seems to be Grub's fault. Default Ubuntu won't have that problem since it ships GRUB_TIMEOUT=0. And if you want a nonzero timeout without the blackness then GRUB_TERMINAL=console is a workaround. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 241000] Re: Pairing: passcode dialogue disappears in <1 second
This bug has been closed for over 14 years so if you have any current issues then please open new bugs for each of them. -- 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/241000 Title: Pairing: passcode dialogue disappears in <1 second Status in bluez package in Ubuntu: Fix Released Status in bluez-utils package in Ubuntu: Invalid Bug description: Binary package hint: bluez-utils The pairing dialogues to allow entering a pin and initiate pairing disappear too fast. If I do the following: sudo hcitool cc 00:19:DB:0A:xx:yy && sudo hcitool auth 00:19:DB:0A:xx:yy a notifier window will pop up for ~1 second and then disappear. If I click on the notifier window fastest, the main passcode/pincode entry dialogue will disappear. This also disappears within 1second. The key seems to be that it is necessary to 'auth', click and 'pincode' within 1 second of a connection being made. This should actually wait until the user is able to and none of the dialogue boxes should cut-off early and disappear without warning. Forum post discussing the same thing, with screenshots: http://ph.ubuntuforums.com/showthread.php?p=5044322 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/241000/+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 1970069] Re: Annoying boot messages interfering with splash screen
I think that's a different bug. I believe it's when plymouthd is starting and is the handover (mode set?) from efifb to DRM. It doesn't happen at all if you add "nomodeset" (please try that). "Really long time" might be subjective though? How long? VT switches (or more accurately virtual console switches if fbcon isn't active yet) shouldn't ever be affected by the patch. It only defers the introduction of text to the screen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2051990] Re: python3-defaults 3.12 causes aubio to fail to build from source
** Bug watch added: Debian Bug tracker #1061736
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061736
** Also affects: aubio (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061736
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults 3.12 causes aubio to fail to build from source
Status in aubio package in Ubuntu:
New
Status in python3-defaults package in Ubuntu:
New
Status in aubio package in Debian:
Unknown
Bug description:
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
/<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence
'\d'
return re.split('\d+$',s)[0]
/<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape
sequence '\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
/<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape
sequence '\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
Traceback (most recent call last):
File "/<>/./waf", line 164, in
from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in
from waflib import
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in
from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in
from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in
import os,re,imp,sys
ModuleNotFoundError: No module named 'imp'
make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2024-02-01T21:23:22Z
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aubio/+bug/2051990/+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 2051990] Re: python3-defaults 3.12 causes aubio to fail to build from source
Upstream bug: https://github.com/aubio/aubio/issues/394
** Bug watch added: github.com/aubio/aubio/issues #394
https://github.com/aubio/aubio/issues/394
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults 3.12 causes aubio to fail to build from source
Status in aubio package in Ubuntu:
New
Status in python3-defaults package in Ubuntu:
New
Status in aubio package in Debian:
Unknown
Bug description:
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
/<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence
'\d'
return re.split('\d+$',s)[0]
/<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape
sequence '\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
/<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape
sequence '\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
Traceback (most recent call last):
File "/<>/./waf", line 164, in
from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in
from waflib import
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in
from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in
from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in
import os,re,imp,sys
ModuleNotFoundError: No module named 'imp'
make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2024-02-01T21:23:22Z
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aubio/+bug/2051990/+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 2051997] Re: bdebstrap fails to build with python3-defaults 3.12
We can either suppress linter errors, or upgrade setup.
** Also affects: bdebstrap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051997
Title:
bdebstrap fails to build with python3-defaults 3.12
Status in bdebstrap package in Ubuntu:
New
Status in python3-defaults package in Ubuntu:
New
Bug description:
When building bdebstrap with python3-default 3.12 the following error occurs
--
usr/bin/python3.12 -m pylint --rcfile=/<>/tests/pylint.conf --
/<>/bdebstrap tests /<>/setup.py
FAIL
test_flake8 (tests.test_shellcheck.ShellcheckTestCase.test_flake8)
Test: Run shellcheck on Shell source code. ... Running following command:
shellcheck /<>/hooks/disable-units
/<>/hooks/enable-units
ok
==
FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
Test: Run pylint on Python source code.
--
Traceback (most recent call last):
File "/<>/tests/test_pylint.py", line 74, in test_pylint
self.fail("\n".join(msgs))
AssertionError: pylint found issues:
* Module setup
/<>/setup.py:26:0: E0401: Unable to import 'distutils.log'
(import-error)
/<>/setup.py:27:0: E0401: Unable to import
'distutils.command.build' (import-error)
/<>/setup.py:28:0: E0401: Unable to import
'distutils.command.clean' (import-error)
/<>/setup.py:57:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:54:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
/<>/setup.py:65:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:62:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
--
due to removal of distutils in python 3.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/2051997/+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 2051997] [NEW] bdebstrap fails to build with python3-defaults 3.12
Public bug reported:
When building bdebstrap with python3-default 3.12 the following error occurs
--
usr/bin/python3.12 -m pylint --rcfile=/<>/tests/pylint.conf --
/<>/bdebstrap tests /<>/setup.py
FAIL
test_flake8 (tests.test_shellcheck.ShellcheckTestCase.test_flake8)
Test: Run shellcheck on Shell source code. ... Running following command:
shellcheck /<>/hooks/disable-units
/<>/hooks/enable-units
ok
==
FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
Test: Run pylint on Python source code.
--
Traceback (most recent call last):
File "/<>/tests/test_pylint.py", line 74, in test_pylint
self.fail("\n".join(msgs))
AssertionError: pylint found issues:
* Module setup
/<>/setup.py:26:0: E0401: Unable to import 'distutils.log'
(import-error)
/<>/setup.py:27:0: E0401: Unable to import
'distutils.command.build' (import-error)
/<>/setup.py:28:0: E0401: Unable to import
'distutils.command.clean' (import-error)
/<>/setup.py:57:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:54:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
/<>/setup.py:65:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:62:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
--
due to removal of distutils in python 3.12
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051997
Title:
bdebstrap fails to build with python3-defaults 3.12
Status in python3-defaults package in Ubuntu:
New
Bug description:
When building bdebstrap with python3-default 3.12 the following error occurs
--
usr/bin/python3.12 -m pylint --rcfile=/<>/tests/pylint.conf --
/<>/bdebstrap tests /<>/setup.py
FAIL
test_flake8 (tests.test_shellcheck.ShellcheckTestCase.test_flake8)
Test: Run shellcheck on Shell source code. ... Running following command:
shellcheck /<>/hooks/disable-units
/<>/hooks/enable-units
ok
==
FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
Test: Run pylint on Python source code.
--
Traceback (most recent call last):
File "/<>/tests/test_pylint.py", line 74, in test_pylint
self.fail("\n".join(msgs))
AssertionError: pylint found issues:
* Module setup
/<>/setup.py:26:0: E0401: Unable to import 'distutils.log'
(import-error)
/<>/setup.py:27:0: E0401: Unable to import
'distutils.command.build' (import-error)
/<>/setup.py:28:0: E0401: Unable to import
'distutils.command.clean' (import-error)
/<>/setup.py:57:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:54:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
/<>/setup.py:65:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:62:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
--
due to removal of distutils in python 3.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2051997/+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 1970069] Re: Annoying boot messages interfering with splash screen
I tested it on Noble with a hand built kernel and it at least does what you planned (don't see any console messages), but also I'm not seeing the OEM vendor logo stick all the way through. There's a really long time of a black screen. Not sure if this is because it was an upstream kernel and it's missing a VT switch patch or something. Does that match what you're seeing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1989599] Re: Random auditd start failures on Ubuntu 20.04 EC2 AMIs
Also seeing this intermittently on Debian 10 / latest kernel 4.19 there, so it appears to be something kernel related that was backported as the original report here mentions 5.15. The workaround I've come up with (not fully validated yet, but manually starting when it fails on boot seems to work) is to add a systemd override (systemctl edit auditd.service) like follows: [Unit] StartLimitBurst=5 StartLimitIntervalSec=60 [Service] Restart=on-failure RestartSec=5 Kinda gross, but better than having audit messages spam dmesg. I didn't bisect, but I suspect it's one of these: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/kernel/audit.c?h=v4.19.306 audit: ensure userspace is penalized the same as the kernel when under pressure audit: improve audit queue handling when "audit=1" on cmdline Might be worthwhile to try reverting those and rebuilding kernel to see if the issue persists. -- 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/1989599 Title: Random auditd start failures on Ubuntu 20.04 EC2 AMIs Status in audit package in Ubuntu: Confirmed Bug description: Description:Ubuntu 20.04.5 LTS Release:20.04 linux-image-aws 5.15.0.1019.23~20.04.11 auditd 1:2.8.5-2ubuntu6 I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs. I have tested this with published AMIs ami-0123376e204addb71 and ami-00bb3d0b5b36e89b8. I am following a process that has worked up to June 20 2022. The process installs and configures the audit package for CIS hardening. The process steps are: • Launch an instance as a base, I’ve used ami-0123376e204addb71 or ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs). • Installed the packages listed below. • Copied the “auditdconf” contents as /etc/audit/auditd.conf • Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules • Edit /etc/default/grub, and set: GRUB_CMDLINE_LINUX="audit=1 selinux=1 audit_backlog_limit=8192" • Run: grub-mkconfig > /boot/grub/grub.cfg • Stopped the instance, and created an AMI. I then launch 10 or 14 instances of this AMI in us-west-2. Most will come up with auditd service running, and all rules loaded. Usually at least two come up broken for unknown reason, with the auditd service reporting an error I cannot understand: ● auditd.service - Security Auditing Service Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2022-09-14 15:08:14 UTC; 22min ago Docs: man:auditd(8) https://github.com/linux-audit/audit-documentation Process: 357 ExecStart=/sbin/auditd (code=exited, status=1/FAILURE) Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Starting Security Auditing Service... Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error receiving audit netlink packet (No buffer space available) Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error setting audit daemon pid (No buffer space available) Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Unable to set audit pid, exiting Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: Cannot daemonize (Success) Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: The audit daemon is exiting. Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: The audit daemon is exiting. Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Control process exited, code=exited, status=1/FAILURE Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Failed with result 'exit-code'. Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Failed to start Security Auditing Service. When I launch the above, it is a launch of 10 or so instances from the same AMI, with the same parameters. Matter of fact, the launch is done by requesting X number of instances during the EC2 instance launch I've been trying to solve this for some time, and I've found the only way I can make the instances always start correctly is to remove the kernel "audit_backlog_limit" setting entirely - no value for the parameter works correctly (tried 320, 8192, 16384, 32768). See attachments for the above mentioned files. Thanks. -Alan expected behavior is: * service loaded and active * "auditctl -l" shows list of loaded rules seen behavior: * service dead with errors shown above. * "auditctl -l" reports "No rules". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1989599/+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 2051990] Re: python3-defaults 3.12 causes aubio to fail to build from source
WAF library has fixed this issue in the following commit[1].
[1]
https://gitlab.com/ita1024/waf/-/commit/d2060dfd8af4edb5824153ff24e207b39ecd67a2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults 3.12 causes aubio to fail to build from source
Status in aubio package in Ubuntu:
New
Status in python3-defaults package in Ubuntu:
New
Bug description:
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
/<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence
'\d'
return re.split('\d+$',s)[0]
/<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape
sequence '\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
/<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape
sequence '\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
Traceback (most recent call last):
File "/<>/./waf", line 164, in
from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in
from waflib import
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in
from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in
from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in
import os,re,imp,sys
ModuleNotFoundError: No module named 'imp'
make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2024-02-01T21:23:22Z
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aubio/+bug/2051990/+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 2051990] [NEW] python3-defaults 3.12 causes aubio to fail to build from source
Public bug reported:
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
/<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence
'\d'
return re.split('\d+$',s)[0]
/<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape sequence
'\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
/<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape sequence
'\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
Traceback (most recent call last):
File "/<>/./waf", line 164, in
from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in
from waflib import
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in
from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in
from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in
import os,re,imp,sys
ModuleNotFoundError: No module named 'imp'
make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2024-02-01T21:23:22Z
** Affects: aubio (Ubuntu)
Importance: Undecided
Status: New
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Also affects: aubio (Ubuntu)
Importance: Undecided
Status: New
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults 3.12 causes aubio to fail to build from source
Status in aubio package in Ubuntu:
New
Status in python3-defaults package in Ubuntu:
New
Bug description:
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
/<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence
'\d'
return re.split('\d+$',s)[0]
/<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape
sequence '\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
/<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape
sequence '\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
Traceback (most recent call last):
File "/<>/./waf", line 164, in
from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in
from waflib import
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in
from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in
from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in
import os,re,imp,sys
ModuleNotFoundError: No module named 'imp'
make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2024-02-01T21:23:22Z
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aubio/+bug/2051990/+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 2032577] Re: xz crashed with SIGSEGV in lzma_lzma_optimum_normal
XZ developers have a couple questions regarding this after looking at the trace: - is it reproducible? did it happen several times? - does the machine use ECC memory? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2032577 Title: xz crashed with SIGSEGV in lzma_lzma_optimum_normal Status in xz-utils package in Ubuntu: New Bug description: xz segfaults. More details in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379 From Dmesg.txt on that report [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000] ProblemType: Crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 ExecutablePath: /usr/bin/xz ExecutableTimestamp: 1649422298 InstallationDate: Installed on 2021-04-09 (863 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xz-utils 5.2.5-2ubuntu1 ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9 ProcCwd: / ProcEnviron: LC_CTYPE=C.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 SegvAnalysis: Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d PC (0x7f9b3f780c1a) ok source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 0x7f9a90021000-0x7f9a9400 ---p None destination "%r10d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading VMA None Signal: 11 SourcePackage: xz-utils Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago) UserGroups: N/A StacktraceTop: bt_find_func (len_limit=64, pos=9137198, cur=0x7f9a943edc3d "", cur_match=4194304, depth=24, son=son@entry=0x7f9a8afbd010, cyclic_pos=748589, cyclic_size=8388609, matches=0x7f9adc0ec324, len_best=11) at ../../../../src/liblzma/lz/lz_encoder_mf.c:483 lzma_mf_bt4_find (mf=0x7f9a9c70, matches=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:721 lzma_mf_find (mf=mf@entry=0x7f9a9c70, count_ptr=count_ptr@entry=0x7f9adc0ecb94, matches=matches@entry=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:28 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:846 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2032577/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
** Merge proposal linked: https://code.launchpad.net/~mitchdz/ubuntu/+source/python2.7/+git/python2.7/+merge/459844 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/2002043 Title: Python extension modules get built using wrong compiler flags with python2 Status in python2.7 package in Ubuntu: Invalid Status in python2.7 source package in Bionic: Won't Fix Status in python2.7 source package in Focal: In Progress Status in python2.7 source package in Jammy: In Progress Status in python2.7 source package in Kinetic: Invalid Status in python2.7 source package in Lunar: Invalid Status in python2.7 source package in Mantic: Invalid Bug description: [ Impact ] When compiling Python extensions using Python2, CFLAGS optimization flags are dropped. This behavior has been caused by our update in this patch http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz which differs from upstream. The fix modifies the portion of code in Lib/distutils/sysconfig.py which gets the cflags from the environments, and includes the dropped OPT flag from get_config_vars(). [ Test Plan ] There will be 2 separate tests for this bug: * Ensuring no-change rebuilds are not changed * Ensuring local builds are not changed unless environment variable is set Test 1) No-change rebuilds To test that no-change rebuilds are not changed, the package python- stdlib-extensions will be built against the new python2.7, and confirm the compiler flags are not altered. This will be a manual test and visual inspection of the build logs. Test 2) Functional test 1. Create test container $ lxc launch ubuntu:jammy jammy-2002043 $ lxc shell ubuntu:jammy jammy-2002043 2. Install required packages For Jammy # apt update -y && apt install -y python2 python-pip For Focal # apt update -y && apt install -y python2 python-setuptools 3. Create test files # mkdir testprog # cd testprog # cat >setup.py
[Touch-packages] [Bug 2047450] Re: tail emits no output for sysfs files when using large page kernels
I've examined all of the test failures, and all have root causes unrelated to this fix. I've cleared all from the excuses page except: mantic/initramfs-tools/armhf: bug 2043579 jammy/linux-azure-5.19/arm64: the kernel build test timed out. retries keep hitting slow builders :( jammy/linux-lowlatency-hwe-5.19/arm64: same jammy/linux-nvidia-6.5: bug 2051941 jammy/linux-nvidia-tegra-igx/arm64: bug 2051942 Could the SRU team override those? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Committed Status in coreutils source package in Lunar: Won't Fix Status in coreutils source package in Mantic: Fix Committed Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+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 2051540] Re: ufw ftbfs with Python 3.12 as default
** Changed in: ufw (Debian)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in ufw:
Fix Committed
Status in ufw package in Ubuntu:
Confirmed
Status in ufw package in Debian:
New
Bug description:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2051540/+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 2048914] Re: System program problem detected at every login Xubuntu Update Notifier
After testing the latest Noble daily build of Xubuntu (Version 20240201), I did not experience this error. Has this been fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2048914 Title: System program problem detected at every login Xubuntu Update Notifier Status in update-notifier package in Ubuntu: New Status in whoopsie package in Ubuntu: Incomplete Bug description: Every time I log in to my new installation of Xubuntu 24.04 (daily ISO) after a reboot, I get an error message that says, "System program problem detected." Clicking either Cancel or Report Problem only dismisses the pop-up without any further action. This has occurred on multiple computers. This began with the first boot after installation and occurs at each subsequent reboot upon logging in. Logging out and back in does not cause the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: update-notifier 3.192.66 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Jan 10 09:57:25 2024 ExecutablePath: /usr/bin/update-notifier InstallationDate: Installed on 2024-01-10 (0 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240110) ProcEnviron: LANG=C.UTF-8 LANGUAGE=en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2048914/+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 2051541] Re: unattended-upgrades ftbfs with Python 3.12 as default
** Tags removed: ftbfs rls-nn-incoming ** Tags added: foundations-todo ** Also affects: unattended-upgrades (Ubuntu Noble) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2051541 Title: unattended-upgrades ftbfs with Python 3.12 as default Status in unattended-upgrades package in Ubuntu: Confirmed Status in unattended-upgrades source package in Noble: Confirmed Bug description: [...] Running ./test_pep484.py with python3 s -- Ran 0 tests in 0.000s NO TESTS RAN (skipped=1) make[2]: *** [Makefile:9: check] Error 5 make[2]: Leaving directory '/<>/test' make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2 5 is a new exit value when all tests are skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2051541/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2051672] Re: Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main)
** Summary changed: - Sync iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main) + Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main) -- 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/2051672 Title: Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main) Status in iproute2 package in Ubuntu: New Bug description: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting features from more recent kernels? Please note that Ubuntu Noble 24.04 will probably be shipped with the v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 kernel, so missing the ones added to earlier versions. Switching to the v6.7 now should ease the upgrade to the v6.8 later. [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958 Upstream ChangeLog: - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ (Previous changelog: https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 ) ChangeLog from Debian: iproute2 (6.7.0-2) unstable; urgency=medium * Backport fix for 'ss' output -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + iproute2 (6.7.0-1) unstable; urgency=medium * Add Italian debconf translation (Closes: #1056582) * Update upstream source from tag 'upstream/6.7.0' * Bump copyright year ranges in d/copyright * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, merged upstream * Default config files moved from /usr/lib to /usr/share -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + iproute2 (6.6.0-1) unstable; urgency=medium * Update upstream source from tag 'upstream/6.6.0' * Backport patch to fix configuration installation * Remove handling of qt_atm.so, dropped upstream -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + iproute2 (6.5.0-5) unstable; urgency=medium * Use dh-sequence-movetousr -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 iproute2 (6.5.0-4) unstable; urgency=medium * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 iproute2 (6.5.0-3) unstable; urgency=medium * Remove further leftovers as part of upstream's move of config to /usr (Closes: #1051577) -- Luca Boccassi <> Mon, 11 Sep 2023 09:42:12 +0100 iproute2 (6.5.0-2) unstable; urgency=medium * Add maintscript to remove conffiles that upstream has moved to /usr (Closes: #1051577) -- Luca Boccassi <> Sun, 10 Sep 2023 21:28:28 +0100 iproute2 (6.5.0-1) unstable; urgency=medium [ Luca Boccassi ] * Use wildcard for Lintian overrides [ Peter Kvillegård ] * Add Swedish translation of debconf messages (Closes: #1050442) [ Luca Boccassi ] * Update upstream source from tag 'upstream/6.5.0' * Use cap_bpf instead of cap_sys_admin for ip vrf-exec * Package-provided config files are now shipped in /usr/iproute2 instead of /etc/iproute2 -- Luca Boccassi <> Sat, 09 Sep 2023 16:32:54 +0100 iproute2 (6.4.0-1) unstable; urgency=medium * Fix patch header Forwarded field * Enable ELF metadata stamping * Update upstream source from tag 'upstream/6.4.0' * Update Lintian overrides -- Luca Boccassi <> Fri, 30 Jun 2023 12:16:40 +0100 iproute2 (6.3.0-1) unstable; urgency=medium * Drop obsolete conflicts/replaces * Update upstream source from tag 'upstream/6.3.0' -- Luca Boccassi <> Tue, 13 Jun 2023 23:49:37 +0100 iproute2 (6.1.0-3) unstable; urgency=medium * Ensure 'ip mo' resolves to 'ip monitor' (Closes: #1036534) -- Luca Boccassi <> Mon, 22 May 2023 14:19:52 +0100 iproute2 (6.1.0-2) unstable; urgency=medium * Add Romanian language translation for debconf (Closes: #1031917) * Bump Standards-Version to 4.6.2, no changes * Bump d/copyright year range -- Luca Boccassi <> Sat, 25 Feb 2023 19:46:35 + To
[Touch-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
Technically, the verification from prior comments was performed on 23.2.1-1ubuntu3.1~22.04.1, not 23.2.1-1ubuntu3.1~22.04.2. I think they need to be done on the mesa package that is in proposed now, which is .2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2018439] Re: Apparmor crashes GPU acceleration
Hi Daniel! Thanks for testing and making sure. As you were able to figure out, the AppArmor parser accepts both include and #includes, although we are deprecating the latter. Since the AppArmor policy is distributed by the Mozilla Team's firefox, they need to add this permission to their AppArmor profile in the package. ** Changed in: apparmor (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2018439 Title: Apparmor crashes GPU acceleration Status in apparmor package in Ubuntu: Invalid Status in firefox package in Ubuntu: Confirmed Bug description: Apparmor crashes GPU acceleration Firefox GPU acceleration started crashing after updating from Ubuntu 22.10 to 23.04. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 $ apt-cache policy firefox firefox: Installed: 113.0+build1-0ubuntu0.23.04.1~mt1 Candidate: 113.0+build1-0ubuntu0.23.04.1~mt1 Version table: 1:1snap1-0ubuntu3 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages *** 113.0+build1-0ubuntu0.23.04.1~mt1 999 500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 23.0.3~kisak1~k Candidate: 23.0.3~kisak1~k Version table: *** 23.0.3~kisak1~k 500 500 https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 23.0.2-1ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages $ apt-cache policy apparmor apparmor: Installed: 3.0.8-1ubuntu2 Candidate: 3.0.8-1ubuntu2 Version table: *** 3.0.8-1ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status # Expected behavior Firefox should not crash in WebGL aquarium and continue to work properly like on 22.10. It should successfully use my GPU to make scrolling smooths and save battery when watching videos. # Actual behavior 1. Startup takes a second or two longer than usual 2. Typing in the address bar is slow 3. Scrolling takes 400% CPU usage 4. Scrolling stutters 5. VAAPI on https://www.w3schools.com/html/html5_video.asp is no longer used as shown in intel_gpu_top 6. Fans start spinning and battery goes down fast 7. glxtest failures had to be manually deleted in about:config 8. Only a few fish in WebGL aquarium (https://webglsamples.org/aquarium/aquarium.html) load before Firefox force-closes with the message: "Mozilla Crash Reporter Firefox had a problem and crashed. Unfortunately, the crash reporter is unable to submit a crash report. Details: The application did not leave a crash dump file. Close" 9. The following lines are relevant in dmesg after clearing it: [22157.695580] kauditd_printk_skb: 6 callbacks suppressed [22157.695582] audit: type=1400 audit(1683153440.994:2583): apparmor="DENIED" operation="capable" class="cap" profile="firefox" pid=15898 comm="firefox" capability=21 capname="sys_admin" [22157.739641] audit: type=1400 audit(1683153441.038:2584): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739647] audit: type=1400 audit(1683153441.038:2585): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739719] audit: type=1400 audit(1683153441.038:2586): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739729] audit: type=1400 audit(1683153441.038:2587): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.769407] audit: type=1400 audit(1683153441.070:2588): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/15898/oom_score_adj" pid=15898 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [22157.773042] audit: type=1400 audit(1683153441.074:2589): apparmor="DENIED" operation="file_mmap" class="file" profile="firefox//lsb_release" name="/usr/bin/dash" pid=15934 comm="lsb_release" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.974718] audit: type=1400 audit(1683153441.274:2590):
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Here's a no-compromises patch set. No bugs, no delays, it just does the right thing. If I haven't changed my mind again on Friday then it will be sent upstream. ** Patch added: "lp1970069-patchset-20240201a.patch" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/5744101/+files/lp1970069-patchset-20240201a.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2051118] Re: DEP8 error on armhf
This bug was fixed in the package libseccomp - 2.5.4-2ubuntu2 --- libseccomp (2.5.4-2ubuntu2) noble; urgency=medium * d/t/testsuite-live-python3: skip this test if on a) armhf; b) ubuntu; c) lxd (LP: #2051118) libseccomp (2.5.4-2ubuntu1) noble; urgency=medium * Merge with Debian; remaining changes: - Add autopkgtests -- Andreas Hasenack Fri, 26 Jan 2024 15:04:52 -0300 ** Changed in: libseccomp (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2051118 Title: DEP8 error on armhf Status in libseccomp package in Ubuntu: Fix Released Bug description: Version 2.5.4-2 introduced this change in d/t/control: libseccomp (2.5.4-2) unstable; urgency=medium * Fix watch file. (Closes: #1050659) * Dynamically skip autopkgtests when the test runner already applies seccomp restrictions. - Drop isolation-machine restriction. -Restrictions: isolation-machine, allow-stderr +Restrictions: skippable, allow-stderr This made the test run in Ubuntu again on armhf, where we use a lxd container (it wasn't running previously). This change is relying on this check in d/t/common: if ! grep -q -E '^Seccomp:[[:blank:]]+0$' /proc/self/status; then echo "Skipping autpkgptest as the test environment already applies a seccomp filter" exit 77 fi In Debian, where they also use containers, the testsuite-live-python3 test is skipped correctly, but in Ubuntu, it is run and fails[1] with timeout limit: 541s live 541s ./regression: line 253: cd: /tmp/autopkgtest.X55y55/autopkgtest_tmp/tests/../src/python/build/lib.*: No such file or directory 10468s autopkgtest [01:49:37]: kill with SIGTERM did not work sending SIGKILL 1. https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/libs/libseccomp/20231225_015646_12139@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/2051118/+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 241000] Re: Pairing: passcode dialogue disappears in <1 second
Resetting the bluez package did NOT fix the problem. Removing the bluez package(s), removing /var/lib/bluetooth and re-installing. sudo apt remove --purge bluez rm -rf /var/lib/bluetooth sudo apt install bluez gnome-bluetooth gnome-bluetooth-sendto The bluetooth system need to be started, and this empties the list of discovered bluetoothe devices, but the popup for the keyboard auth number disappears again. -- 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/241000 Title: Pairing: passcode dialogue disappears in <1 second Status in bluez package in Ubuntu: Fix Released Status in bluez-utils package in Ubuntu: Invalid Bug description: Binary package hint: bluez-utils The pairing dialogues to allow entering a pin and initiate pairing disappear too fast. If I do the following: sudo hcitool cc 00:19:DB:0A:xx:yy && sudo hcitool auth 00:19:DB:0A:xx:yy a notifier window will pop up for ~1 second and then disappear. If I click on the notifier window fastest, the main passcode/pincode entry dialogue will disappear. This also disappears within 1second. The key seems to be that it is necessary to 'auth', click and 'pincode' within 1 second of a connection being made. This should actually wait until the user is able to and none of the dialogue boxes should cut-off early and disappear without warning. Forum post discussing the same thing, with screenshots: http://ph.ubuntuforums.com/showthread.php?p=5044322 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/241000/+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 241000] Re: Pairing: passcode dialogue disappears in <1 second
- This occurs on my daily use laptopm which has been upgraded from 23.04 -> 23.10 - I have just tried to pair on another laptop with freshly installed 23.10 - The dialog displaying the pairing code persists and I can pair correctly with same keyboard (it can pair with 3 separate devices) - bluez 5.68-0ubuntu1.1 -- 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/241000 Title: Pairing: passcode dialogue disappears in <1 second Status in bluez package in Ubuntu: Fix Released Status in bluez-utils package in Ubuntu: Invalid Bug description: Binary package hint: bluez-utils The pairing dialogues to allow entering a pin and initiate pairing disappear too fast. If I do the following: sudo hcitool cc 00:19:DB:0A:xx:yy && sudo hcitool auth 00:19:DB:0A:xx:yy a notifier window will pop up for ~1 second and then disappear. If I click on the notifier window fastest, the main passcode/pincode entry dialogue will disappear. This also disappears within 1second. The key seems to be that it is necessary to 'auth', click and 'pincode' within 1 second of a connection being made. This should actually wait until the user is able to and none of the dialogue boxes should cut-off early and disappear without warning. Forum post discussing the same thing, with screenshots: http://ph.ubuntuforums.com/showthread.php?p=5044322 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/241000/+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 241000] Re: Pairing: passcode dialogue disappears in <1 second
I am seeing this bug in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop- up disappears very quickly (as described, <1sec). -- 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/241000 Title: Pairing: passcode dialogue disappears in <1 second Status in bluez package in Ubuntu: Fix Released Status in bluez-utils package in Ubuntu: Invalid Bug description: Binary package hint: bluez-utils The pairing dialogues to allow entering a pin and initiate pairing disappear too fast. If I do the following: sudo hcitool cc 00:19:DB:0A:xx:yy && sudo hcitool auth 00:19:DB:0A:xx:yy a notifier window will pop up for ~1 second and then disappear. If I click on the notifier window fastest, the main passcode/pincode entry dialogue will disappear. This also disappears within 1second. The key seems to be that it is necessary to 'auth', click and 'pincode' within 1 second of a connection being made. This should actually wait until the user is able to and none of the dialogue boxes should cut-off early and disappear without warning. Forum post discussing the same thing, with screenshots: http://ph.ubuntuforums.com/showthread.php?p=5044322 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/241000/+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 1782709] Re: Updating systemd kills network on bionic
Despite my comment above, I still have this problem when using netplan. Here is my /etc/netplan/config.yaml (external IP quatrains have been changed), the setup is that enp8s1 provides internet access (with metric 49) and enp7s0 provides local lan access *and* (with metric 51) fallback internet access: network: version: 2 renderer: networkd ethernets: enp8s1: dhcp4: false wakeonlan: true addresses: [111.94.100.80/24] nameservers: addresses: [111.94.100.1] # makes this the default route - deprecated #gateway4: 111.94.100.1 link-local: [] routes: - to: default via: 111.94.100.1 metric: 49 on-link: true enp7s0: dhcp4: false wakeonlan: true addresses: [192.168.20.88/24] nameservers: addresses: [192.168.20.1] link-local: [] routes: - to: default via: 192.168.20.1 metric: 51 on-link: true # to avoid conflict with enp8s1 default route, but makes no difference #table: 76 - to: 192.168.20.0/24 via: 192.168.20.1 metric: 48 When working properly: # ip route show to default default via 111.94.100.1 dev enp8s1 proto static metric 49 onlink default via 192.168.20.1 dev enp7s0 proto static metric 51 onlink But after systemd reconfiguration we have two default routes with a metric of 0! We have to delete one of them to restore the correct setup (as above) and get internet access via enp8s1 again. My workaround is continuous monitoring of syslog for a line indicating that the network has been (re)configured by systemd and then running some bash code like this (extract): if [[ -n $(ip route show to default metric 0 via 192.168.20.1) ]]; then NUM_DEFAULT_ROUTES=$(ip route show to default|wc -l) if [[ $NUM_DEFAULT_ROUTES -gt 2 ]]; then ip route delete to default metric 0 via 192.168.20.1 fi fi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine:
