[Touch-packages] [Bug 2081334] Re: further performance improvement for dracut-install 060
Verified in a VM with encrypted root disk: ``` $ dpkg -l | grep initramfs-tools ii initramfs-tools 0.142ubuntu25.2 all generic modular initramfs generator (automation) ii initramfs-tools-bin 0.142ubuntu25.2 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.142ubuntu25.2 all generic modular initramfs generator (core tools) $ lsinitramfs /boot/initrd.img > initrd.before $ sudo apt install initramfs-tools=0.142ubuntu25.4 initramfs-tools-bin=0.142ubuntu25.4 initramfs-tools-core=0.142ubuntu25.4 $ lsinitramfs /boot/initrd.img > initrd.after $ diff -u initrd.before initrd.after --- initrd.before 2024-09-30 11:45:50.711468655 +0200 +++ initrd.after2024-09-30 11:47:15.761367461 +0200 @@ -1377,6 +1377,13 @@ usr/lib/modules/6.8.0-45-generic/kernel/drivers/ufs usr/lib/modules/6.8.0-45-generic/kernel/drivers/ufs/core usr/lib/modules/6.8.0-45-generic/kernel/drivers/ufs/core/ufshcd-core.ko.zst +usr/lib/modules/6.8.0-45-generic/kernel/drivers/ufs/host +usr/lib/modules/6.8.0-45-generic/kernel/drivers/ufs/host/cdns-pltfrm.ko.zst +usr/lib/modules/6.8.0-45-generic/kernel/drivers/ufs/host/tc-dwc-g210-pci.ko.zst +usr/lib/modules/6.8.0-45-generic/kernel/drivers/ufs/host/tc-dwc-g210.ko.zst +usr/lib/modules/6.8.0-45-generic/kernel/drivers/ufs/host/ufshcd-dwc.ko.zst +usr/lib/modules/6.8.0-45-generic/kernel/drivers/ufs/host/ufshcd-pci.ko.zst +usr/lib/modules/6.8.0-45-generic/kernel/drivers/ufs/host/ufshcd-pltfrm.ko.zst usr/lib/modules/6.8.0-45-generic/kernel/drivers/uio usr/lib/modules/6.8.0-45-generic/kernel/drivers/uio/uio.ko.zst usr/lib/modules/6.8.0-45-generic/kernel/drivers/usb ``` The added modules are due to bug #2081020. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2081334 Title: further performance improvement for dracut-install 060 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Noble: Fix Committed Bug description: [ Impact ] This is a follow-up for bug #2065180 implementing the suggestion from comment #44 there. When compared to Ubuntu 23.10, creating intramfs files with update- initramfs takes 2 to 5 times more time on ARM devices. IIUC, dracut-install usage was added to initramfs-tools to speed up the process. But now its way slower. Even running update-initramfs on jammy, which doesn't use dracut-install, is way faster then the time taken on Noble. first bad commit - https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870 Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble) with initramfs-tools 0.142ubuntu25.1 takes over six minutes: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 402.751 s ± 5.592 s [User: 166.316 s, System: 228.909 s] Range (min … max): 394.380 s … 411.445 s 10 runs ``` [ Test Plan ] 1. Measure `update-initramfs -u` before the update. 2. Log the content of the initrd before the update: `lsinitramfs /boot/initrd.img` 3. update dracut-install / initramfs-tools-core 4. Measure `update-initramfs -u`. It should be faster (the performance improvements on amd64 should be very small and might be within the measurement uncertainty). 5. Check with lsinitramfs that the content of the newly generated initrd hasn't changed. [ Where problems could occur ] The code that is responsible for including the kernel modules into the initrd is touched. Negative consequences could be that some needed kernel modules will not be included any more (should be covered by the test case) or that building new initrds will fail. The initramfs-tools fix changes how manual_add_modules behaves. `manual_add_modules` does not copy kernel modules, but queues them for being copied when the newly added function `apply_add_modules` is called. I checked all instances of calls to `manual_add_modules` for possible regressions (see https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/comments/15). Only miniramfs needs to be adjusted to also call `apply_add_modules`. But this change could break consumers of the `manual_add_modules` function that are outside of the Ubuntu archive. I googled for `apply_add_modules` but found no public outside users. [ Benchmarks ] Stock noble on a Raspberry Pi Zero 2W: ``` bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] Range (min … max): 409.139 s … 422.632 s 5 runs ``` noble with dracut-install 060+5-1ubuntu3.1 (with linux 6
[Touch-packages] [Bug 2065294] Re: Diagnostics settings flips to Never without any user action
Verified the test plan with gnome-control-
center{,-data,-faces}=1:46.4-0ubuntu0.24.04.1 on Ubuntu 24.04.1 LTS
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie-preferences in
Ubuntu.
https://bugs.launchpad.net/bugs/2065294
Title:
Diagnostics settings flips to Never without any user action
Status in gnome-control-center package in Ubuntu:
Fix Released
Status in whoopsie-preferences package in Ubuntu:
Invalid
Status in gnome-control-center source package in Jammy:
Fix Committed
Status in whoopsie-preferences source package in Jammy:
Invalid
Status in gnome-control-center source package in Noble:
Fix Committed
Status in whoopsie-preferences source package in Noble:
Invalid
Bug description:
[ Impact ]
In GNOME Settings' Diagnostics page, the switch to control automatic
bug reporting to Canonical automatically flips to "Never" after 1
minute of the page being open without interaction
The bug triggered because the DBus service that manages the
automatic-bug-reporting configuration ("whoopsie-preferences") quits after 1
minute of inactivity, and GNOME Settings receives an "invalidation" signal when
that happens.
We are fixing the issue by detecting that the service has quit in which case
we should not refresh the state of the setting.
A further change should be applied to the whoopsie-preferences service
to avoid quitting when there are clients still listening for potential
settings changes.
[ Test Plan ]
* Open GNOME Settings -> Privacy & Security -> Diagnostics
* You should see `Send error reports to Canonical` set to `Manual` by
default.
> If instead it is set to Never, change it now to another option.
* Stay on the settings page for more than 60 seconds
* The setting should have remained the same and *not* have
automatically changed to `Never`.
[ Where problems could occur ]
This patch also tries to re-start the "whoopsie-preferences" daemon
when it automatically stops after 60 seconds, because GNOME Settings
should keep listening for settings changes from external factors. This
should not present any issues, but it's the most "intrusive" part of
the patch.
[ Original Description ]
steps to reproduce.
1. Open Gnome Settings
2. Go to Privacy -> Diagnostics
3. You should see `Send error reports to Canonical` set to Manual by default.
4. Stay on the settings page for some time (maybe <2 mins), the setting will
slip to Never.
You could also try to change the settings to Automatic and stay on the
page, it will also flip to Never within a couple of minutes.
I noticed this on Jammy, Mantic, and Noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2065294/+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 2065294] Re: Diagnostics settings flips to Never without any user action
Verified the test plan with gnome-control-
center{,-data,-faces}=1:41.7-0ubuntu0.22.04.9 on Ubuntu 22.04.5 LTS
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie-preferences in
Ubuntu.
https://bugs.launchpad.net/bugs/2065294
Title:
Diagnostics settings flips to Never without any user action
Status in gnome-control-center package in Ubuntu:
Fix Released
Status in whoopsie-preferences package in Ubuntu:
Invalid
Status in gnome-control-center source package in Jammy:
Fix Committed
Status in whoopsie-preferences source package in Jammy:
Invalid
Status in gnome-control-center source package in Noble:
Fix Committed
Status in whoopsie-preferences source package in Noble:
Invalid
Bug description:
[ Impact ]
In GNOME Settings' Diagnostics page, the switch to control automatic
bug reporting to Canonical automatically flips to "Never" after 1
minute of the page being open without interaction
The bug triggered because the DBus service that manages the
automatic-bug-reporting configuration ("whoopsie-preferences") quits after 1
minute of inactivity, and GNOME Settings receives an "invalidation" signal when
that happens.
We are fixing the issue by detecting that the service has quit in which case
we should not refresh the state of the setting.
A further change should be applied to the whoopsie-preferences service
to avoid quitting when there are clients still listening for potential
settings changes.
[ Test Plan ]
* Open GNOME Settings -> Privacy & Security -> Diagnostics
* You should see `Send error reports to Canonical` set to `Manual` by
default.
> If instead it is set to Never, change it now to another option.
* Stay on the settings page for more than 60 seconds
* The setting should have remained the same and *not* have
automatically changed to `Never`.
[ Where problems could occur ]
This patch also tries to re-start the "whoopsie-preferences" daemon
when it automatically stops after 60 seconds, because GNOME Settings
should keep listening for settings changes from external factors. This
should not present any issues, but it's the most "intrusive" part of
the patch.
[ Original Description ]
steps to reproduce.
1. Open Gnome Settings
2. Go to Privacy -> Diagnostics
3. You should see `Send error reports to Canonical` set to Manual by default.
4. Stay on the settings page for some time (maybe <2 mins), the setting will
slip to Never.
You could also try to change the settings to Automatic and stay on the
page, it will also flip to Never within a couple of minutes.
I noticed this on Jammy, Mantic, and Noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2065294/+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 2080518] Re: /usr/bin/w:11:print_host:print_from:showinfo:main
all autopkgtest regressions have been retried, and then passed. I installed propcps/noble-proposed, and tested in noble vm. root@n-vm-1:~# w 10:25:02 up 4 days, 2:04, 1 user, load average: 0.00, 0.00, 0.00 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT root pts/0-10:212.00s 0.02s ?w root@n-vm-1:~# w -s 10:25:03 up 4 days, 2:04, 1 user, load average: 0.00, 0.00, 0.00 USER TTY FROM IDLE WHAT root pts/0- 3.00s w -s root@n-vm-1:~# w -h root pts/0-10:211.00s 0.02s ?w -h root@n-vm-1:~# w -hs root pts/0- 3.00s w -hs root@n-vm-1:~# w -hfip root pts/0-10:210.00s 0.02s ?2289/2743 w -hfip root@n-vm-1:~# w -hfips root pts/0- 3.00s 2289/2744 w -hfips All these commands run successfully. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2080518 Title: /usr/bin/w:11:print_host:print_from:showinfo:main Status in procps package in Ubuntu: Fix Released Status in procps source package in Noble: Fix Committed Bug description: [Impact] * Running `w -s` crashes. Segmentation fault. It only crashes when there are users in `w` output. [ Test Plan ] * Launch a noble vm. If run `w` doesn't show any user (for example the shell is launched by lxc exec), then run `login -f root` to populate a user in `w` output. * Install the version from -proposed, and run `w -hs`. It shouldn't crash. * Run other `w` options, like without `-s`, and combine `-s` with other options as well. They all shouldn't crash. [ Where problems could occur ] * The backported patch only affects the `w` utility in procps. The tests should cover most options of `w` utility. It may have regressions if we miss some tests for the options. [ Original description ] Running `w -hs` crashes. The Ubuntu Error Tracker has been receiving reports about a problem regarding procps. This problem was most recently seen with package version 2:4.0.4-4ubuntu4, the problem page at https://errors.ubuntu.com/problem/373d37cffbad5aec5447c867001913ba8278a791 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. 917 crashes in the last month on Ubuntu 24.04 makes it #31 on https://errors.ubuntu.com/?release=Ubuntu%2024.04&period=month To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2080518/+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 2083158] Re: Sync python-testtools 2.7.2-2 (main) from Debian unstable (main) to fix FTBFS on oracular
This bug was fixed in the package python-testtools - 2.7.2-2
Sponsored for Olivier Gayot (ogayot)
---
python-testtools (2.7.2-2) unstable; urgency=medium
* Disable failing twisted tests (Closes: #1082697):
- TestAsynchronousDeferredRunTest.test_log_in_details
- TestAsynchronousDeferredRunTest.test_log_to_twisted
-- Thomas Goirand Wed, 25 Sep 2024 09:59:04 +0200
** Tags added: ftbfs
** Changed in: python-testtools (Ubuntu)
Assignee: (unassigned) => Graham Inggs (ginggs)
** Changed in: python-testtools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-testtools in
Ubuntu.
https://bugs.launchpad.net/bugs/2083158
Title:
Sync python-testtools 2.7.2-2 (main) from Debian unstable (main) to
fix FTBFS on oracular
Status in python-testtools package in Ubuntu:
Fix Released
Status in python-testtools package in Debian:
Fix Released
Bug description:
Please sync python-testtools 2.7.2-2 (main) from Debian unstable
(main)
python-testtools 2.7.2-1 currently in oracular FTBFS because the
build-time test-suite fails. This is addressed by Debian debbug
1082697.
FAIL:
testtools.tests.twistedsupport.test_runtest.TestAsynchronousDeferredRunTest.test_log_in_details
--
Traceback (most recent call last):
File "/<>/testtools/tests/twistedsupport/test_runtest.py",
line 743, in test_log_in_details
self.assertThat(
File "/<>/testtools/testcase.py", line 509, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: Differences: [
Differences: [
Differences: {
'twisted-log': '''\
2024-09-15 08:20:13+ [-] foo
2024-09-15 08:20:13+ [-] Main loop terminated.
''' does not end with '''\
foo
'''.: after > on ,
}
]
]
==
FAIL:
testtools.tests.twistedsupport.test_runtest.TestAsynchronousDeferredRunTest.test_log_to_twisted
--
Traceback (most recent call last):
File "/<>/testtools/tests/twistedsupport/test_runtest.py",
line 792, in test_log_to_twisted
self.assertThat(
File "/<>/testtools/testcase.py", line 509, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: Differences: [
len([{'system': '-', 'message': ('foo',), 'time': 1726388413.606103,
'isError': 0, 'log_time': 1726388413.606103, 'log_text': 'foo', 'log_format':
'{log_text}', 'log_level': , 'log_namespace': 'log_legacy',
'log_system': '-', 'format': '%(log_legacy)s', 'log_legacy':
},
{'log_logger': , 'log_level': ,
'log_namespace': 'twisted.internet.base', 'log_source': None, 'log_format':
'Main loop terminated.', 'log_time': 1726388413.6062098, 'message': (), 'time':
1726388413.6062098, 'system': '-', 'format': '%(log_legacy)s', 'log_legacy':
,
'isError': 0}]) != 1: Length mismatch
https://launchpadlibrarian.net/749245792/buildlog_ubuntu-oracular-amd64.python-testtools_2.7.2-1_BUILDING.txt.gz
Changelog entries since current oracular version 2.7.2-1:
python-testtools (2.7.2-2) unstable; urgency=medium
* Disable failing twisted tests (Closes: #1082697):
- TestAsynchronousDeferredRunTest.test_log_in_details
- TestAsynchronousDeferredRunTest.test_log_to_twisted
-- Thomas Goirand Wed, 25 Sep 2024 09:59:04 +0200
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/2083158/+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 2083165] Re: python-debian 0.1.49ubuntu2 FTBFS (rebuild)
** Changed in: python-debian (Ubuntu)
Assignee: (unassigned) => Graham Inggs (ginggs)
** Changed in: python-debian (Ubuntu)
Status: New => In Progress
** Tags added: ftbfs
** Changed in: python-debian (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/2083165
Title:
python-debian 0.1.49ubuntu2 FTBFS (rebuild)
Status in python-debian package in Ubuntu:
Fix Committed
Bug description:
During a rebuild, python-debian failed to build from source:
https://launchpadlibrarian.net/749245152/buildlog_ubuntu-oracular-
amd64.python-debian_0.1.49ubuntu2_BUILDING.txt.gz
dpkg-buildpackage
-
Command: dpkg-buildpackage -us -uc -mLaunchpad Build Daemon
-b -rfakeroot
dpkg-buildpackage.pl: info: source package python-debian
dpkg-buildpackage.pl: info: source version 0.1.49ubuntu2
dpkg-buildpackage.pl: info: source distribution lunar
dpkg-source --before-build .
dpkg-buildpackage.pl: info: host architecture amd64
debian/rules clean
dh clean --with python3 --buildsystem pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py clean
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261:
UserWarning: Unknown distribution option: 'test_suite'
warnings.warn(msg)
Traceback (most recent call last):
File "/<>/setup.py", line 39, in
setup(
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 117, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
146, in setup
_setup_distribution = dist = klass(attrs)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 294, in
__init__
self.metadata.version = self._normalize_version(self.metadata.version)
^^
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 330, in
_normalize_version
normalized = str(Version(version))
File "/usr/lib/python3/dist-packages/packaging/version.py", line 202, in
__init__
raise InvalidVersion(f"Invalid version: '{version}'")
packaging.version.InvalidVersion: Invalid version: '0.1.49ubuntu2+git20240915'
E: pybuild pybuild:389: clean: plugin distutils failed with: exit code=1:
python3.12 setup.py clean
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/2083165/+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 2081604] Re: pk-debconf-helper crashed with SIGSEGV in pk_client_helper_copy_stdout_cb()
@Zixing, thank you for the patch, could you give some explanation about your understanding of the issue and how is the patch addressing the problem? Any chance you could also submit it upstream for review on https://github.com/PackageKit/PackageKit/pulls ? The package is currently in sync with Debian and it would be nice to keep it this way, especially that a bug in the debconf handling probably would also happen there -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2081604 Title: pk-debconf-helper crashed with SIGSEGV in pk_client_helper_copy_stdout_cb() Status in packagekit package in Ubuntu: New Bug description: random crash after installing Ubuntu 24.10 Beta ProblemType: Crash DistroRelease: Ubuntu 24.10 Package: packagekit 1.3.0-1 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 21 21:56:45 2024 ExecutablePath: /usr/libexec/pk-debconf-helper InstallationDate: Installed on 2024-09-21 (0 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240919) JournalErrors: sept. 21 21:56:41 hostname xdg-desktop-por[3252]: Could not find WebExtensions backend: Could not find native messaging host sept. 21 21:56:46 hostname systemd[2292]: pk-debconf-helper.service: Main process exited, code=dumped, status=11/SEGV sept. 21 21:56:46 hostname systemd[2292]: pk-debconf-helper.service: Failed with result 'core-dump'. ProcCmdline: /usr/libexec/pk-debconf-helper ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x77e2f8a5b318:mov0x8(%rax),%rcx PC (0x77e2f8a5b318) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SignalName: SIGSEGV SourcePackage: packagekit StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: pk-debconf-helper crashed with SIGSEGV in g_main_loop_run() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users modified.conffile..etc.dbus-1.system.d.org.freedesktop.PackageKit.conf: [deleted] separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2081604/+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 2081604] Re: pk-debconf-helper crashed with SIGSEGV in pk_client_helper_copy_stdout_cb()
The issue seems to trigger on wayland, attaching the testcase which was pointed out by chat discussion $ pkcon install-local ./noisy-fake-driver_0.6_amd64.deb ** Attachment added: "Deb testcase for the issue" https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2081604/+attachment/5823338/+files/noisy-fake-driver_0.6_amd64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2081604 Title: pk-debconf-helper crashed with SIGSEGV in pk_client_helper_copy_stdout_cb() Status in packagekit package in Ubuntu: New Bug description: random crash after installing Ubuntu 24.10 Beta ProblemType: Crash DistroRelease: Ubuntu 24.10 Package: packagekit 1.3.0-1 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 21 21:56:45 2024 ExecutablePath: /usr/libexec/pk-debconf-helper InstallationDate: Installed on 2024-09-21 (0 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240919) JournalErrors: sept. 21 21:56:41 hostname xdg-desktop-por[3252]: Could not find WebExtensions backend: Could not find native messaging host sept. 21 21:56:46 hostname systemd[2292]: pk-debconf-helper.service: Main process exited, code=dumped, status=11/SEGV sept. 21 21:56:46 hostname systemd[2292]: pk-debconf-helper.service: Failed with result 'core-dump'. ProcCmdline: /usr/libexec/pk-debconf-helper ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x77e2f8a5b318:mov0x8(%rax),%rcx PC (0x77e2f8a5b318) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SignalName: SIGSEGV SourcePackage: packagekit StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: pk-debconf-helper crashed with SIGSEGV in g_main_loop_run() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users modified.conffile..etc.dbus-1.system.d.org.freedesktop.PackageKit.conf: [deleted] separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2081604/+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 2083068] Re: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH >
Tracking Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > here. Which happens due to Depends: python3 | qemu-user | qemu-user-static in libglib2.0-dev:i386 (thanks helmut). i.e. it says python3 needs to be the same architecture, or you need qemu-user to execute bits. For reasons of lazyness I'd propose changing this to: Depends: python3:amd64 [i386] | python3 | qemu-user | qemu-user-static This ensures we do not enter the broken python3:i386 code path. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Triaged => Won't Fix ** Changed in: glib2.0 (Ubuntu) Status: New => Triaged ** Also affects: glib2.0 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2083068 Title: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > Status in glib2.0 package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Won't Fix Status in glib2.0 source package in Noble: New Status in ubuntu-release-upgrader source package in Noble: New Bug description: When trying to upgrade from Ubuntu 22.04.5 LTS to 24.04 LTS, I've got this error: ... "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. The package 'update-manager' is marked for removal but it is in the removal deny list. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. " Update-manager version is 1:22.04.21. All software were updated before upgrade process. Third party repos disabled. How can I upgrade without a fresh install? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.20 ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: GNOME Date: Fri Sep 27 20:54:38 2024 InstallationDate: Installed on 2019-07-12 (1904 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-27 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-27 20:51:16 Requested-By: razvi (1000) End-Date: 2024-09-27 20:51:17 VarLogDistupgradeApttermlog: Log started: 2024-09-27 20:51:16 Log ended: 2024-09-27 20:51:17 VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2083068/+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 2083068] Re: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH >
For oracular is the solution architecture-properties? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2083068 Title: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > Status in glib2.0 package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Won't Fix Status in glib2.0 source package in Noble: New Status in ubuntu-release-upgrader source package in Noble: New Bug description: When trying to upgrade from Ubuntu 22.04.5 LTS to 24.04 LTS, I've got this error: ... "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. The package 'update-manager' is marked for removal but it is in the removal deny list. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. " Update-manager version is 1:22.04.21. All software were updated before upgrade process. Third party repos disabled. How can I upgrade without a fresh install? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.20 ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: GNOME Date: Fri Sep 27 20:54:38 2024 InstallationDate: Installed on 2019-07-12 (1904 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-27 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-27 20:51:16 Requested-By: razvi (1000) End-Date: 2024-09-27 20:51:17 VarLogDistupgradeApttermlog: Log started: 2024-09-27 20:51:16 Log ended: 2024-09-27 20:51:17 VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2083068/+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 2081334] Re: further performance improvement for dracut-install 060
** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2081334 Title: further performance improvement for dracut-install 060 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Noble: Fix Committed Bug description: [ Impact ] This is a follow-up for bug #2065180 implementing the suggestion from comment #44 there. When compared to Ubuntu 23.10, creating intramfs files with update- initramfs takes 2 to 5 times more time on ARM devices. IIUC, dracut-install usage was added to initramfs-tools to speed up the process. But now its way slower. Even running update-initramfs on jammy, which doesn't use dracut-install, is way faster then the time taken on Noble. first bad commit - https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870 Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble) with initramfs-tools 0.142ubuntu25.1 takes over six minutes: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 402.751 s ± 5.592 s [User: 166.316 s, System: 228.909 s] Range (min … max): 394.380 s … 411.445 s 10 runs ``` [ Test Plan ] 1. Measure `update-initramfs -u` before the update. 2. Log the content of the initrd before the update: `lsinitramfs /boot/initrd.img` 3. update dracut-install / initramfs-tools-core 4. Measure `update-initramfs -u`. It should be faster (the performance improvements on amd64 should be very small and might be within the measurement uncertainty). 5. Check with lsinitramfs that the content of the newly generated initrd hasn't changed. [ Where problems could occur ] The code that is responsible for including the kernel modules into the initrd is touched. Negative consequences could be that some needed kernel modules will not be included any more (should be covered by the test case) or that building new initrds will fail. The initramfs-tools fix changes how manual_add_modules behaves. `manual_add_modules` does not copy kernel modules, but queues them for being copied when the newly added function `apply_add_modules` is called. I checked all instances of calls to `manual_add_modules` for possible regressions (see https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/comments/15). Only miniramfs needs to be adjusted to also call `apply_add_modules`. But this change could break consumers of the `manual_add_modules` function that are outside of the Ubuntu archive. I googled for `apply_add_modules` but found no public outside users. [ Benchmarks ] Stock noble on a Raspberry Pi Zero 2W: ``` bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] Range (min … max): 409.139 s … 422.632 s 5 runs ``` noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on 2024-07-01): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 248.054 s ± 5.569 s [User: 67.410 s, System: 169.412 s] Range (min … max): 238.909 s … 257.384 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on 2024-07-11): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 232.001 s ± 5.678 s [User: 55.456 s, System: 166.510 s] Range (min … max): 222.120 s … 239.610 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1011.12 and all updates on 2024-09-19): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Time (mean ± σ): 219.439 s ± 4.869 s [User: 45.626 s, System: 163.172 s] Range (min … max): 213.340 s … 227.411 s 10 runs ``` noble with initramfs-tools 0.142ubuntu25.2 (with dracut-install 060+5-1ubuntu3.2, linux 6.8.0-1012.13, and all updates on 2024-09-30): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 217.160 s ± 4.652 s [User: 45.608 s, System: 159.225 s] Range (min … max): 210.736 s … 225.802 s 10 runs ``` noble with initramfs-tools 0.142ubuntu25.4 (with dracut-install 060+5-1ubuntu3.2, linux 6.8.0-1012.13, and all updates on 2024-09-30): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 204.143 s ± 4.441 s [User: 37.845 s, System: 153.927 s] Range (min … max): 195.729 s … 208.805 s 10 runs ``` [ Reduce m
[Touch-packages] [Bug 2072452] Re: AppArmor denies crun sending signals to containers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: runc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2072452 Title: AppArmor denies crun sending signals to containers Status in alsa-driver package in Ubuntu: Confirmed Status in runc package in Ubuntu: Confirmed Bug description: Environment: k8s 1.30.2, containerd 1.7.12 (package in ubuntu repo) When I do a k8s deployment update, the old pods stay in 'Terminating' status. The /var/log/syslog has the following messages: 2024-07-05T15:52:07.892132+08:00 km kernel: audit: type=1400 audit(1720165927.890:2191): apparmor="DENIED" operation="signal" class="signal" profile="cri-containerd.apparmor.d" pid=134029 comm="runc" requested_mask="receive" denied_mask="receive" signal=kill peer="runc" Workaround: currently I disable the apparmor.service and reboot the system. Info from github: https://github.com/moby/moby/pull/47749/files#diff-4a7aa58be335398fb04f9f1634143e158146b57c6256a2d605f9eb3c3c53d840 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jul 8 09:26:20 2024 InstallationDate: Installed on 2024-07-03 (5 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64 (20240423) SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2072452/+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 2081604] Re: pk-debconf-helper crashed with SIGSEGV in pk_client_helper_copy_stdout_cb()
> @Zixing, thank you for the patch, could you give some explanation about your understanding of the issue and how is the patch addressing the problem? I could not reproduce the issue because I encountered another problem (unable to launch `debconf-communicate`) while reproducing the issue described in this bug report. So, instead, I analyzed the re-tracer output: The code tried to access the `error` variable (a NULL address according to the stack trace). Unfortunately, the `status` variable was "", but we can still try to recover its value. There is also an unfortunate design problem with the reporter bot. It does not disassemble the code segment before the program counter (%pc register), so we must disassemble the binary ourselves to hopefully see where the return value went. 0x77f72292 <+242>: mov-0x438(%rbp),%rdx 0x77f72299 <+249>: lea-0x440(%rbp),%rcx 0x77f722a0 <+256>: call 0x77f64ad0 [0]0x77f722a5 <+261>: cmp$0x1,%eax [1]0x77f722a8 <+264>: jne0x77f72300 0x77f722aa <+266>: mov-0x440(%rbp),%r8 0x77f722b1 <+273>: mov-0x438(%rbp),%rcx 0x77f722b8 <+280>: cmp%rcx,%r8 0x77f722bb <+283>: je 0x77f722e0 0x77f722bd <+285>: lea0x2aa0c(%rip),%rdx# 0x77f9ccd0 0x77f722c4 <+292>: mov$0x10,%esi 0x77f722c9 <+297>: mov%r14,%rdi 0x77f722cc <+300>: xor%eax,%eax 0x77f722ce <+302>: call 0x77f65570 0x77f722d3 <+307>: xor%ebx,%ebx 0x77f722d5 <+309>: jmp0x77f72228 0x77f722da <+314>: nopw 0x0(%rax,%rax,1) 0x77f722e0 <+320>: mov%r8,%rcx 0x77f722e3 <+323>: lea0x27ceb(%rip),%rdx# 0x77f99fd5 0x77f722ea <+330>: mov%r14,%rdi 0x77f722ed <+333>: xor%eax,%eax 0x77f722ef <+335>: mov$0x80,%esi 0x77f722f4 <+340>: call 0x77f65570 0x77f722f9 <+345>: jmp0x77f72223 0x77f722fe <+350>: xchg %ax,%ax [2]0x77f72300 <+352>: mov-0x448(%rbp),%rax 0x77f72307 <+359>: lea0x27ca9(%rip),%rdx# 0x77f99fb7 0x77f7230e <+366>: mov%r14,%rdi 0x77f72311 <+369>: xor%ebx,%ebx 0x77f72313 <+371>: mov$0x10,%esi => 0x77f72318 <+376>: mov0x8(%rax),%rcx 0x77f7231c <+380>: xor%eax,%eax The comparison with G_IO_STATUS_NORMAL (with an integer value of `1`) is made in location [0]; we can be sure that the conditional jump at [1] did not happen, so the control flow must go straight down. The load that happened in [2] has overwritten our return value, so, indeed, we can't see it. However, we can still make an educated guess about what happened after the I/O write operation. You can look at https://docs.gtk.org/glib/enum.IOStatus.html; apparently, "EOF" and "AGAIN" are not handled in this case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2081604 Title: pk-debconf-helper crashed with SIGSEGV in pk_client_helper_copy_stdout_cb() Status in packagekit package in Ubuntu: New Bug description: random crash after installing Ubuntu 24.10 Beta ProblemType: Crash DistroRelease: Ubuntu 24.10 Package: packagekit 1.3.0-1 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 21 21:56:45 2024 ExecutablePath: /usr/libexec/pk-debconf-helper InstallationDate: Installed on 2024-09-21 (0 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240919) JournalErrors: sept. 21 21:56:41 hostname xdg-desktop-por[3252]: Could not find WebExtensions backend: Could not find native messaging host sept. 21 21:56:46 hostname systemd[2292]: pk-debconf-helper.service: Main process exited, code=dumped, status=11/SEGV sept. 21 21:56:46 hostname systemd[2292]: pk-debconf-helper.service: Failed with result 'core-dump'. ProcCmdline: /usr/libexec/pk-debconf-helper ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x77e2f8a5b318:mov0x8(%rax),%rcx PC (0x77e2f8a5b318) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SignalName: SIGSEGV SourcePackage: packagekit StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libg
[Touch-packages] [Bug 2083259] [NEW] Update librsvg to 2.59.1
Public bug reported: Impact - There is a new bugfix release in the stable 2.59.x series https://gitlab.gnome.org/GNOME/librsvg/-/blob/2.59.1/NEWS Other Info - This package has a thorough test suite and minimal autopkgtests ** Affects: librsvg (Ubuntu) Importance: Undecided Status: In Progress ** Tags: oracular -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2083259 Title: Update librsvg to 2.59.1 Status in librsvg package in Ubuntu: In Progress Bug description: Impact - There is a new bugfix release in the stable 2.59.x series https://gitlab.gnome.org/GNOME/librsvg/-/blob/2.59.1/NEWS Other Info - This package has a thorough test suite and minimal autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2083259/+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 2081604] Re: pk-debconf-helper crashed with SIGSEGV in pk_client_helper_copy_stdout_cb()
** Tags removed: rls-oo-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2081604 Title: pk-debconf-helper crashed with SIGSEGV in pk_client_helper_copy_stdout_cb() Status in packagekit package in Ubuntu: New Bug description: random crash after installing Ubuntu 24.10 Beta ProblemType: Crash DistroRelease: Ubuntu 24.10 Package: packagekit 1.3.0-1 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 21 21:56:45 2024 ExecutablePath: /usr/libexec/pk-debconf-helper InstallationDate: Installed on 2024-09-21 (0 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240919) JournalErrors: sept. 21 21:56:41 hostname xdg-desktop-por[3252]: Could not find WebExtensions backend: Could not find native messaging host sept. 21 21:56:46 hostname systemd[2292]: pk-debconf-helper.service: Main process exited, code=dumped, status=11/SEGV sept. 21 21:56:46 hostname systemd[2292]: pk-debconf-helper.service: Failed with result 'core-dump'. ProcCmdline: /usr/libexec/pk-debconf-helper ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x77e2f8a5b318:mov0x8(%rax),%rcx PC (0x77e2f8a5b318) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SignalName: SIGSEGV SourcePackage: packagekit StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: pk-debconf-helper crashed with SIGSEGV in g_main_loop_run() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users modified.conffile..etc.dbus-1.system.d.org.freedesktop.PackageKit.conf: [deleted] separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2081604/+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 2069041] Re: Changing Port in sshd_config requires calling systemctl daemon-reload
** Changed in: openssh (Ubuntu Noble) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2069041 Title: Changing Port in sshd_config requires calling systemctl daemon-reload Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Noble: Triaged Bug description: [Impact] There is currently no comment in the default /etc/ssh/sshd_config explaining that a systemctl daemon-reload is needed for changes to Port etc. to take effect when systemd socket activation is used (the default on Ubuntu). Users may change e.g. Port in /etc/ssh/sshd_config and expect systemctl restart ssh.service to reflect the change, but this will not work. [Test Plan] 1. The proposed fix here is to improve the documentation by adding a comment above the default Port setting in /etc/ssh/sshd_config. Hence, the test is to simply install openssh-server from noble-proposed, and verify that the comment is there. 2. Because the patch changes the default sshd_config, and debian/openssh-server.ucf-md5sum needs to be updated when this happens, an upgrade from noble to oracular should be done after installing openssh-server from noble-proposed. If a debconf prompt is shown, then a mistake was made in recording the checksums. Otherwise, they are correct. [Where problems could occur] There is low technical risk, but we should be sure that the documentation is clear and improves the experience of users. It could be harmful if the documentation accidentally makes things worse, or is just confusing. Also, a packaging quirk of openssh-server is that checksums of the patched sshd_config (along with certain settings tweaked) need to be recorded in debian/openssh-server.ucf-md5sum to avoid unnecessary debconf prompts on upgrades. I have updated those checksums, but if they are incorrent, then in future upgrades users might see an unnecessary debconf prompt about /etc/ssh/sshd_config. [Original Description] Changing the Port directive in sshd_config and restarting ssh.service is without effect, sshd keeps listening to port 22. Also mentioned in https://discourse.ubuntu.com/t/sshd-now-uses-socket- based-activation-ubuntu-22-10-and-later/30189/32 Steps to reproduce: 1. Install Ubuntu 24.04 LTS 2. Change Port directive in /etc/ssh/sshd_config to Port 2233 3. Restart ssh.service 4. Observe sshd still listening to port 22 Expected behaviour: sshd changes port to 2233 Actual behaviour: sshd keeps listening to port 22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2069041/+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 2071815] Re: Investigate ASLR re-randomization being disabled for children
** Also affects: openssh (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu Noble) Importance: Undecided => Medium ** Tags removed: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2071815 Title: Investigate ASLR re-randomization being disabled for children Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Noble: New Bug description: The systemd-socket-activation.patch patch has an Ubuntu delta to fix bug 2011458, but this results in ASLR not being re-randomized for children because the patch delta does "rexec_flag = 0;". This was discovered as part of the CVE-2024-6387 discovery by Qualys, and is mentioned in the disclosure itself: Side note: we discovered that Ubuntu 24.04 does not re-randomize the ASLR of its sshd children (it is randomized only once, at boot time); we tracked this down to the patch below, which turns off sshd's rexec_flag. This is generally a bad idea, but in the particular case of this signal handler race condition, it prevents sshd from being exploitable: the syslog() inside the SIGALRM handler does not call any of the malloc functions, because it is never the very first call to syslog(). This is also mentioned in the release notes of OpenSSH 9.8: Exploitation on non-glibc systems is conceivable but has not been examined. Systems that lack ASLR or users of downstream Linux distributions that have modified OpenSSH to disable per-connection ASLR re-randomisation (yes - this is a thing, no - we don't understand why) may potentially have an easier path to exploitation. We should investigate why that was needed, and if an alternative way of fixing the original bug can be done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2071815/+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 2083068] Re: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH >
** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2083068 Title: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > Status in glib2.0 package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Won't Fix Status in glib2.0 source package in Noble: New Status in ubuntu-release-upgrader source package in Noble: New Bug description: When trying to upgrade from Ubuntu 22.04.5 LTS to 24.04 LTS, I've got this error: ... "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. The package 'update-manager' is marked for removal but it is in the removal deny list. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. " Update-manager version is 1:22.04.21. All software were updated before upgrade process. Third party repos disabled. How can I upgrade without a fresh install? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.20 ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: GNOME Date: Fri Sep 27 20:54:38 2024 InstallationDate: Installed on 2019-07-12 (1904 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-27 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-27 20:51:16 Requested-By: razvi (1000) End-Date: 2024-09-27 20:51:17 VarLogDistupgradeApttermlog: Log started: 2024-09-27 20:51:16 Log ended: 2024-09-27 20:51:17 VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2083068/+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 2073742] Re: [SRU] Enable support for Dalmation Cloud Archive
Hey folks, When will it be available on Noble? I'm still getting `not a valid cloud-archive: 'dalmation'` when trying to add it. Not even `dalmation-staging` is available... Looking forward to play with OpenStack Ansible and the `distro` install method with Noble! Cheers! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2073742 Title: [SRU] Enable support for Dalmation Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Noble: Fix Committed Status in software-properties source package in Oracular: Fix Released Bug description: Please add support for: cloud-archive:dalmation cloud-archive:dalmation-proposed This will also need to be SRU'd back to noble. [Impact] End users have to manually enable the dalmation cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:dalmation sudo add-apt-repository cloud-archive:dalmation-proposed apt policy openstack-release Verify that the expected version is available to "apt policy", and report that version in the SRU verification bug comment. [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2073742/+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 2081334] Re: further performance improvement for dracut-install 060
And verified speed improvement on a Raspberry Pi Zero 2W: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 217.160 s ± 4.652 s[User: 45.608 s, System: 159.225 s] Range (min … max): 210.736 s … 225.802 s10 runs bdrung@zero2w:~$ sudo apt install initramfs-tools=0.142ubuntu25.4 initramfs-tools-bin=0.142ubuntu25.4 initramfs-tools-core=0.142ubuntu25.4 bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 204.143 s ± 4.441 s[User: 37.845 s, System: 153.927 s] Range (min … max): 195.729 s … 208.805 s10 runs ``` ** Description changed: [ Impact ] This is a follow-up for bug #2065180 implementing the suggestion from comment #44 there. When compared to Ubuntu 23.10, creating intramfs files with update- initramfs takes 2 to 5 times more time on ARM devices. IIUC, dracut-install usage was added to initramfs-tools to speed up the process. But now its way slower. Even running update-initramfs on jammy, which doesn't use dracut-install, is way faster then the time taken on Noble. first bad commit - https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870 Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble) with initramfs-tools 0.142ubuntu25.1 takes over six minutes: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 402.751 s ± 5.592 s [User: 166.316 s, System: 228.909 s] Range (min … max): 394.380 s … 411.445 s 10 runs ``` [ Test Plan ] 1. Measure `update-initramfs -u` before the update. 2. Log the content of the initrd before the update: `lsinitramfs /boot/initrd.img` 3. update dracut-install / initramfs-tools-core 4. Measure `update-initramfs -u`. It should be faster (the performance improvements on amd64 should be very small and might be within the measurement uncertainty). 5. Check with lsinitramfs that the content of the newly generated initrd hasn't changed. [ Where problems could occur ] The code that is responsible for including the kernel modules into the initrd is touched. Negative consequences could be that some needed kernel modules will not be included any more (should be covered by the test case) or that building new initrds will fail. The initramfs-tools fix changes how manual_add_modules behaves. `manual_add_modules` does not copy kernel modules, but queues them for being copied when the newly added function `apply_add_modules` is called. I checked all instances of calls to `manual_add_modules` for possible regressions (see https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/comments/15). Only miniramfs needs to be adjusted to also call `apply_add_modules`. But this change could break consumers of the `manual_add_modules` function that are outside of the Ubuntu archive. I googled for `apply_add_modules` but found no public outside users. [ Benchmarks ] Stock noble on a Raspberry Pi Zero 2W: ``` bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] Range (min … max): 409.139 s … 422.632 s 5 runs ``` noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on 2024-07-01): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 248.054 s ± 5.569 s [User: 67.410 s, System: 169.412 s] Range (min … max): 238.909 s … 257.384 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on 2024-07-11): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 232.001 s ± 5.678 s [User: 55.456 s, System: 166.510 s] Range (min … max): 222.120 s … 239.610 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1011.12 and all updates on 2024-09-19): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Time (mean ± σ): 219.439 s ± 4.869 s [User: 45.626 s, System: 163.172 s] Range (min … max): 213.340 s … 227.411 s 10 runs ``` + noble with initramfs-tools 0.142ubuntu25.2 (with dracut-install + 060+5-1ubuntu3.2, linux 6.8.0-1012.13, and all updates on 2024-09-30): + + ``` + bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" + Benchmark 1: update-initramfs -u + Time (mean ± σ): 217.160 s ± 4.652 s [User: 45.608 s, System: 159.225 s] + Range (min … max): 210.736 s … 225.802 s 10 runs + ``` + + noble with initramfs-tools 0.142ubuntu25.4 (with dracut-install + 060+5-1ubuntu3.2, linux 6.8.0-1012.13, and all updates on 2024-09-30): + + ``` + bd
[Touch-packages] [Bug 2065180] Re: performance regression in dracut-install 060
** Description changed: [ Impact ] When compared to Ubuntu 23.10, creating intramfs files with update- initramfs takes 2 to 5 times more time on ARM devices. IIUC, dracut-install usage was added to initramfs-tools to speed up the process. But now its way slower. Even running update-initramfs on jammy, which doesn't use dracut-install, is way faster then the time taken on Noble. first bad commit - https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870 Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble) with initramfs-tools 0.142ubuntu25.1 takes over six minutes: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 402.751 s ± 5.592 s[User: 166.316 s, System: 228.909 s] Range (min … max): 394.380 s … 411.445 s10 runs ``` [ Test Plan ] 1. Measure `update-initramfs -u` before the update. 2. Log the content of the initrd before the update: `lsinitramfs /boot/initrd.img` 3. update dracut-install / initramfs-tools-core 4. Measure `update-initramfs -u`. It should be faster (the performance improvements on amd64 should be very small and might be within the measurement uncertainty). 5. Check with lsinitramfs that the content of the newly generated initrd hasn't changed. [ Where problems could occur ] The code that is responsible for including the kernel modules into the initrd is touched. Negative consequences could be that some needed kernel modules will not be included any more (should be covered by the test case) or that building new initrds will fail. The initramfs-tools fix changes how manual_add_modules behaves. `manual_add_modules` does not copy kernel modules, but queues them for being copied when the newly added function `apply_add_modules` is called. I checked all instances of calls to `manual_add_modules` for possible regressions (see comment #15). Only miniramfs needs to be adjusted to also call `apply_add_modules`. But this change could break consumers of the `manual_add_modules` function that are outside of the Ubuntu archive. I googled for `apply_add_modules` but found no public outside users. [ Benchmarks ] Stock noble on a Raspberry Pi Zero 2W: ``` bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] Range (min … max): 409.139 s … 422.632 s 5 runs ``` noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on 2024-07-01): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 248.054 s ± 5.569 s[User: 67.410 s, System: 169.412 s] Range (min … max): 238.909 s … 257.384 s10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on 2024-07-11): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 232.001 s ± 5.678 s [User: 55.456 s, System: 166.510 s] Range (min … max): 222.120 s … 239.610 s 10 runs ``` noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1011.12 and all updates on 2024-09-19): ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" - Time (mean ± σ): 219.439 s ± 4.869 s[User: 45.626 s, System: 163.172 s] - Range (min … max): 213.340 s … 227.411 s10 runs + Time (mean ± σ): 219.439 s ± 4.869 s[User: 45.626 s, System: 163.172 s] + Range (min … max): 213.340 s … 227.411 s10 runs + ``` + + noble with initramfs-tools 0.142ubuntu25.2 (with dracut-install + 060+5-1ubuntu3.2, linux 6.8.0-1012.13, and all updates on 2024-09-30): + + ``` + bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" + Benchmark 1: update-initramfs -u + Time (mean ± σ): 217.160 s ± 4.652 s [User: 45.608 s, System: 159.225 s] + Range (min … max): 210.736 s … 225.802 s 10 runs + ``` + + noble with initramfs-tools 0.142ubuntu25.4 (with dracut-install + 060+5-1ubuntu3.2, linux 6.8.0-1012.13, and all updates on 2024-09-30): + + ``` + bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" + Benchmark 1: update-initramfs -u + Time (mean ± σ): 204.143 s ± 4.441 s [User: 37.845 s, System: 153.927 s] + Range (min … max): 195.729 s … 208.805 s 10 runs ``` [ Reduce manual_add_modules calls ] Besides making the dracut-install calls faster, group the dracut-install calls. Since the fix in oracular can cause regressions in custom hooks that rely on the current behavior, the SRU takes a safe approach which includes following packages (stating how many dracut-install calls are used): * cryptsetup: 2 -> 1 * lvm2: 8 -> 1 * thin-provisioning-tools: 3 -> 1
[Touch-packages] [Bug 2083165] Re: python-debian 0.1.49ubuntu2 FTBFS (rebuild)
This bug was fixed in the package python-debian - 0.1.49ubuntu3
---
python-debian (0.1.49ubuntu3) oracular; urgency=medium
* Fix FTBFS by ensuring that the PEP440 compliant package version is
available when running dh_auto_clean & dh_auto_configure (LP: #2083165).
-- Olivier Gayot Sun, 29 Sep 2024
20:52:17 +0200
** Changed in: python-debian (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/2083165
Title:
python-debian 0.1.49ubuntu2 FTBFS (rebuild)
Status in python-debian package in Ubuntu:
Fix Released
Bug description:
During a rebuild, python-debian failed to build from source:
https://launchpadlibrarian.net/749245152/buildlog_ubuntu-oracular-
amd64.python-debian_0.1.49ubuntu2_BUILDING.txt.gz
dpkg-buildpackage
-
Command: dpkg-buildpackage -us -uc -mLaunchpad Build Daemon
-b -rfakeroot
dpkg-buildpackage.pl: info: source package python-debian
dpkg-buildpackage.pl: info: source version 0.1.49ubuntu2
dpkg-buildpackage.pl: info: source distribution lunar
dpkg-source --before-build .
dpkg-buildpackage.pl: info: host architecture amd64
debian/rules clean
dh clean --with python3 --buildsystem pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py clean
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261:
UserWarning: Unknown distribution option: 'test_suite'
warnings.warn(msg)
Traceback (most recent call last):
File "/<>/setup.py", line 39, in
setup(
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 117, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
146, in setup
_setup_distribution = dist = klass(attrs)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 294, in
__init__
self.metadata.version = self._normalize_version(self.metadata.version)
^^
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 330, in
_normalize_version
normalized = str(Version(version))
File "/usr/lib/python3/dist-packages/packaging/version.py", line 202, in
__init__
raise InvalidVersion(f"Invalid version: '{version}'")
packaging.version.InvalidVersion: Invalid version: '0.1.49ubuntu2+git20240915'
E: pybuild pybuild:389: clean: plugin distutils failed with: exit code=1:
python3.12 setup.py clean
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/2083165/+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 2083297] [NEW] 5.1 Sound not working via HDMI and internal GPU
Public bug reported: Hello, I've tried Ubuntu 22.04 and now 24.04. Unfortunately the 5.1 sound can be chosen, but does not work. I've also used pavucontrol and tried other solutions to fix it. Issue remains the same. Even the test only gives an audio output for the two audio channels (left/right) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:toni 5257 F pipewire /dev/snd/controlC0: toni 5262 F wireplumber /dev/snd/controlC1: toni 5262 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Tue Oct 1 08:03:50 2024 InstallationDate: Installed on 2024-09-29 (2 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: Gigabyte Technology Co., Ltd. X670E AORUS MASTER PackageArchitecture: all ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2024 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X670E AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF32:bd08/14/2024:br5.35:svnGigabyteTechnologyCo.,Ltd.:pnX670EAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX670EAORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X670 MB dmi.product.name: X670E AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- 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/2083297 Title: 5.1 Sound not working via HDMI and internal GPU Status in alsa-driver package in Ubuntu: New Bug description: Hello, I've tried Ubuntu 22.04 and now 24.04. Unfortunately the 5.1 sound can be chosen, but does not work. I've also used pavucontrol and tried other solutions to fix it. Issue remains the same. Even the test only gives an audio output for the two audio channels (left/right) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:toni 5257 F pipewire /dev/snd/controlC0: toni 5262 F wireplumber /dev/snd/controlC1: toni 5262 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Tue Oct 1 08:03:50 2024 InstallationDate: Installed on 2024-09-29 (2 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: Gigabyte Technology Co., Ltd. X670E AORUS MASTER PackageArchitecture: all ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2024 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X670E AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF32:bd08/14/2024:br5.35:svnGigabyteTechnologyCo.,Ltd.:pnX670EAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX670EAORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X670 MB dmi.product.name: X670E AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To man
[Touch-packages] [Bug 2073742] Re: [SRU] Enable support for Dalmation Cloud Archive
BTW, I also tried (typo?): ``` # add-apt-repository cloud-archive:dalmatian not a valid cloud-archive: 'dalmatian' ``` https://releases.openstack.org/dalmatian/index.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2073742 Title: [SRU] Enable support for Dalmation Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Noble: Fix Committed Status in software-properties source package in Oracular: Fix Released Bug description: Please add support for: cloud-archive:dalmation cloud-archive:dalmation-proposed This will also need to be SRU'd back to noble. [Impact] End users have to manually enable the dalmation cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:dalmation sudo add-apt-repository cloud-archive:dalmation-proposed apt policy openstack-release Verify that the expected version is available to "apt policy", and report that version in the SRU verification bug comment. [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2073742/+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 2073742] Re: [SRU] Enable support for Dalmation Cloud Archive
Never mind... Found it! lol https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/dalmatian- staging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2073742 Title: [SRU] Enable support for Dalmation Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Noble: Fix Committed Status in software-properties source package in Oracular: Fix Released Bug description: Please add support for: cloud-archive:dalmation cloud-archive:dalmation-proposed This will also need to be SRU'd back to noble. [Impact] End users have to manually enable the dalmation cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:dalmation sudo add-apt-repository cloud-archive:dalmation-proposed apt policy openstack-release Verify that the expected version is available to "apt policy", and report that version in the SRU verification bug comment. [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2073742/+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 2083259] Re: Update librsvg to 2.59.1
This bug was fixed in the package librsvg - 2.59.1+dfsg-1 --- librsvg (2.59.1+dfsg-1) unstable; urgency=medium * New upstream release (LP: #2083259) -- Jeremy Bícha Mon, 30 Sep 2024 11:02:55 -0400 ** Changed in: librsvg (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 librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2083259 Title: Update librsvg to 2.59.1 Status in librsvg package in Ubuntu: Fix Released Bug description: Impact - There is a new bugfix release in the stable 2.59.x series https://gitlab.gnome.org/GNOME/librsvg/-/blob/2.59.1/NEWS Other Info - This package has a thorough test suite and minimal autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2083259/+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 2082087] Re: Update gstreamer packages from 1.24.7 to 1.24.8 for oracular
** Changed in: gst-libav1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-ugly1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-python1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2082087 Title: Update gstreamer packages from 1.24.7 to 1.24.8 for oracular Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 1.24 series. It would be helpful to have these fixes in Ubuntu 24.10 before the release. https://gstreamer.freedesktop.org/releases/1.24/#1.24.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/2082087/+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
