[Touch-packages] [Bug 1993800]
This is an autogenerated message for OBS integration: This bug (1204267) was mentioned in https://build.opensuse.org/request/show/1157115 Backports:SLE-15-SP5 / llvm17 -- 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/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: Fix Released Status in llvm-toolchain-15 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in llvm-toolchain-15 package in openSUSE: Fix Released Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+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 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12
** Changed in: rich (Debian) Status: Confirmed => Fix Released -- 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/2049369 Title: autopkg tests ignored for migration of python3-defaults adding 3.12 Status in cython package in Ubuntu: New Status in cython-legacy package in Ubuntu: New Status in ipykernel package in Ubuntu: New Status in ironic-python-agent package in Ubuntu: New Status in jupyter-client package in Ubuntu: New Status in numpy package in Ubuntu: New Status in python-memory-profiler package in Ubuntu: New Status in python-oslo.versionedobjects package in Ubuntu: Fix Released Status in python-urllib3 package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in rich package in Ubuntu: New Status in sphinx-autoapi package in Ubuntu: New Status in vcr.py package in Ubuntu: New Status in cython package in Debian: Confirmed Status in cython-legacy package in Debian: New Status in ipykernel package in Debian: New Status in jupyter-client package in Debian: Confirmed Status in numpy package in Debian: New Status in python-memory-profiler package in Debian: New Status in python-urllib3 package in Debian: Fix Released Status in rich package in Debian: Fix Released Status in sphinx-autoapi package in Debian: Fix Released Status in vcr.py package in Debian: Fix Released Bug description: autopkg tests ignored for migration of python3-defaults adding 3.12: These are the autopkg tests for packages, which we'll ignore for the initial migration of python3-defaults adding 3.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2056194] Re: Networking broken in early boot on Oracle Native instances due to MTU settings
This bug was fixed in the package cloud-init - 24.1.1-0ubuntu1
---
cloud-init (24.1.1-0ubuntu1) noble; urgency=medium
* Upstream snapshot based on 24.1.1.
List of changes from upstream can be found at
https://raw.githubusercontent.com/canonical/cloud-init/24.1.1/ChangeLog
- Bugs fixed in this snapshot: (LP: #2056439, #2056460, #2055077)
(LP: #2056194)
-- Brett Holman Mon, 11 Mar 2024 21:09:37
-0600
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
--
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/2056194
Title:
Networking broken in early boot on Oracle Native instances due to MTU
settings
Status in cloud-images:
New
Status in cloud-init package in Ubuntu:
Fix Released
Status in initramfs-tools package in Ubuntu:
Fix Committed
Bug description:
BACKGROUND:
cloud-init-local.service runs before networking has started. On non-
Oracle platforms, before networking has come up, cloud-init will
create an ephemeral connection to the cloud's IMDS using DHCP to
retrieve instance metadata. On Oracle, this normally isn't necessary
as we boot with connectivity to the IMDS out of the box. This can be
seen in the following Jammy instance using an SR-IOV NIC:
2024-03-05 14:09:05,351 - url_helper.py[DEBUG]: [0/1] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent'
: 'Cloud-Init/23.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
2024-03-05 14:09:05,362 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup,
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/',
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'headers': {'User-Agent': 'Cloud-Init/23
.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}} configuration
2024-03-05 14:09:05,368 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
Notice the "Skip ephemeral DHCP setup, instance has connectivity".
This means that cloud-init has determined that it already has
connectivity and doesn't need to do any additional setup to retrieve
data from the IMDS.
We can also see the same behavior on a Noble paravirtualized instance:
2024-03-01 20:51:33,482 - url_helper.py[DEBUG]: [0/1] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-01 20:51:33,488 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
2024-03-01 20:51:33,488 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup,
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/',
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
2024-03-01 20:51:33,489 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-01 20:51:33,500 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
2024-03-01 20:51:33,501 - util.py[DEBUG]: Writing to
/run/cloud-init/cloud-id-oracle - wb: [644] 7 bytes
PROBLEM:
On a Noble instance using Hardware-assisted (SR-IOV) networking, this
is not working. cloud-init-local.service no longer has immediate
connectivity to the IMDS. Since it cannot connect, in then attempts to
create an ephemeral connection to the IMDS using DHCP. It is able to
obtain a DHCP lease, but then when it tries to connect to the IMDS,
the call just hangs. The call has no timeout, so this results in an
instance that cannot be logged into even via the serial console
because cloud-init is blocking the rest of boot. A simple cloud-init
workaround is to add something along the lines of `timeout=2` to
https://github.com/canonical/cloud-
init/blob/main/cloudinit/sources/DataSourceOracle.py#L349 . This
allows cloud-init to boot. Looking at the logs, we can see that cloud-
init is unable to connect to the IMDS:
[Touch-packages] [Bug 2057710] Re: Accountsservice FTBFS on noble
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2057710 Title: Accountsservice FTBFS on noble Status in accountsservice package in Ubuntu: New Bug description: package version 23.13.9-2ubuntu FTBFS on all architectures. This is because of an invalid test This has been resolved upstream - see the attached debdiff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2057710/+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
The only focal autopkgtest that really has me confused in the python2.7 failure. This is due to a unit test that fails. The strange thing is that this unit test actually fails in the Jammy autopkgtest, but the Jammy autopkgtest passes anyways. It has always been like this. You will see 1643s FAIL: test_customize_compiler (distutils.tests.test_sysconfig.SysconfigTestCase) 1643s -- 1643s Traceback (most recent call last): 1643s File "/usr/lib/python2.7/distutils/tests/test_sysconfig.py", line 110, in test_customize_compiler 1643s 'env_cc --sc-cflags --env-cflags --env-cppflags') 1643s AssertionError: 'env_cc -fno-strict-aliasing --env-cflags --env-cppflags' != 'env_cc --sc-cflags --env-cflags --env-cppflags' Which has always been like this - my patch did not cause this change. I think this should be safe to ignore simply because the package has always been like this, and if it is an issue we should've found a bug for it by now. I tried to see if the Debian autopkgtest also sees this behavior, but unfortunately those logs have been removed due to the retention policy. I'm curious if the change I am doing will fix this unit test... So I created a PPA with the change enabled by default and will come back when the results are ready. -- 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: Fix Committed Status in python2.7 source package in Jammy: Fix Committed 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 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 gcc 3. Create test files # mkdir testprog # cd testprog # cat >setup.py
[Touch-packages] [Bug 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/2057687 Title: systemctl hibernate error: "Call to Hibernate failed: Invalid argument" Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped working. Trying to hibernate: systemctl hibernate I get: Call to Hibernate failed: Invalid argument systemctl status systemd-hibernate.service - × systemd-hibernate.service - Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static) Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 1min 33s ago Docs: man:systemd-hibernate.service(8) Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate (code=exited, status=1/FAILURE) Main PID: 4473 (code=exited, status=1/FAILURE) CPU: 5ms мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting systemd-hibernate.service - Hibernate... мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location to hibernate to: Invalid argument мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'. мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start systemd-hibernate.service - Hibernate. -- Previous version (254.x) worked: swapfile(on EXT4 fs) is used to hibernate/resume, resume with resume_offset kernel parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+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 2056496] Re: [FFe] AppArmor 4.0-beta2 + prompting support for noble
Uploaded to noble-proposed yesterday https://launchpad.net/ubuntu/+source/apparmor/4.0.0~beta2-0ubuntu3 ** Changed in: apparmor (Ubuntu) Status: Triaged => Fix Committed -- 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/2056496 Title: [FFe] AppArmor 4.0-beta2 + prompting support for noble Status in apparmor package in Ubuntu: Fix Committed Bug description: AppArmor 4.0-beta2 contains fixes that prevented AppArmor 4.0-beta1 from landing pre feature freeze. Landing AppArmor 4.0-beta's will enable us to more easily track upstream bug fixes, and is needed to support network rules in prompting. The addition of the prompting patch on top of AppArmor 4.0 is required to support snapd prompting in general for both file and network rules. Currently the prompting patch is not part of the upstream release but is part of the vendored apparmor in snapd. In ordered for snapd to be able to vendor the noble release of apparmor it requires support for prompting. The prompting patch is a straight rebase to AppArmor 4.0 of the patch that has been in testing in snapd prompting for more than six months. Changes from 4.0.0~alpha4-0ubuntu1 (current noble) version Beta1 added three additional features that were not present in alpha4 (current Noble). • support for fine grained (address based) IPv4 and IPv6 mediation (required for prompting to support networking). • aa-notify support message filters to reduce notifications • aa-logprof/genprof support for mount rules None of these features affect existing policy, which will continue to function under the abi that it was developed under. This can be seen in the regression testing below. I addition to the 3 features introduced in Beta1, Beta1 and Beta2 add several bug fixes the most important are highlighted below with the full list available in the upstream release notes, available at https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_4.0-beta1 and https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_4.0-beta2 • new unconfined profiles in support of unprivileged user namespace mediation https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626 ∘ nautalus, devhelp, element-desktop, epiphany, evolution, keybase, opam • fix policy generation for non-af_inet rules (MR:1175) • Fix race when reading proc files (AABUG:355, MR:1157) • handle unprivileged_userns transition in userns tests (MR:1146) • fix usr-merge failures on exec and regex tests (MR:1146) This proposed change has been tested via the QA Regression Testing project, in particular with the specific test added in https://git.launchpad.net/qa-regression- testing/commit/?id=6f2c5ab7c8659174adac772ce0e894328bb5045d The output of a test run is in the attached qrt.output file. Of which the summary is below Ran 62 tests in 811.542s OK (skipped=3) apparmor_4.0.0~beta2-0ubuntu3 has been installed on several up to date (as of March 7) noble systems. Boot/Reboot and regression tests have been done, against different kernel versions. 6.8.0-11-generic #11-Ubuntu 6.5.0-14-generic #14-Ubuntu 6.7.0 (upstream custom build) 6.8-rc3 (upstream custom build) The changelog is available here https://launchpad.net/~apparmor-dev/+archive/ubuntu/apparmor-devel/+files/apparmor_4.0.0~beta2-0ubuntu3_source.changes The prepared package is available via the ppa https://launchpad.net/~apparmor-dev/+archive/ubuntu/apparmor-ffe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056496/+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 2057605] Re: update-initramfs fails: /usr/share/initramfs-tools/hooks/fsck failed with return 1
Thank you for taking the time to report this bug and helping to make Ubuntu better and for providing the correct logs to further troubleshoot the issue. Things went south after `ldd /sbin/fsck.ext4` leading to `/lib/libgcwrap.so`. Can you provide the output of the `ldd /sbin/fsck.ext4` command? On a clean focal chroot the output of the command looks like this: ``` $ ldd /sbin/fsck.ext4 linux-vdso.so.1 (0x7ffd483c4000) libext2fs.so.2 => /lib/x86_64-linux-gnu/libext2fs.so.2 (0x776e7776c000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x776e77765000) libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x776e7770e000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x776e77705000) libe2p.so.2 => /lib/x86_64-linux-gnu/libe2p.so.2 (0x776e776fa000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x776e77508000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x776e774e3000) /lib64/ld-linux-x86-64.so.2 (0x776e77828000) ``` ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- 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/2057605 Title: update-initramfs fails: /usr/share/initramfs-tools/hooks/fsck failed with return 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 initramfs-tools: Installed: 0.136ubuntu6.7 Candidate: 0.136ubuntu6.7 Version table: *** 0.136ubuntu6.7 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.136ubuntu6 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages sudo apt-get install linux-image-5.4.0-173-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-modules-5.4.0-173-generic Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-173-generic The following NEW packages will be installed: linux-image-5.4.0-173-generic linux-modules-5.4.0-173-generic 0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded. Need to get 25.5 MB of archives. After this operation, 92.5 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-modules-5.4.0-173-generic amd64 5.4.0-173.191 [15.0 MB] Get:2 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-5.4.0-173-generic amd64 5.4.0-173.191 [10.5 MB] Fetched 25.5 MB in 2s (12.1 MB/s) Selecting previously unselected package linux-modules-5.4.0-173-generic. (Reading database ... 77620 files and directories currently installed.) Preparing to unpack .../linux-modules-5.4.0-173-generic_5.4.0-173.191_amd64.deb ... Unpacking linux-modules-5.4.0-173-generic (5.4.0-173.191) ... Selecting previously unselected package linux-image-5.4.0-173-generic. Preparing to unpack .../linux-image-5.4.0-173-generic_5.4.0-173.191_amd64.deb ... Unpacking linux-image-5.4.0-173-generic (5.4.0-173.191) ... Setting up linux-modules-5.4.0-173-generic (5.4.0-173.191) ... Setting up linux-image-5.4.0-173-generic (5.4.0-173.191) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-173-generic I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-173-generic Processing triggers for linux-image-5.4.0-173-generic (5.4.0-173.191) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-173-generic + PREREQ= + prereqs + echo + exit 0 + PREREQ= + [ ! -x /sbin/fsck ] + . /usr/share/initramfs-tools/scripts/functions + . /usr/share/initramfs-tools/hook-functions + + sort get_fsck_types + get_fsck_type_fstab / root + uniq + _read_fstab_entry / + echo MNT_FSNAME= + echo MNT_DIR= + echo MNT_TYPE= + [ -f /etc/fstab ] + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ / = / ] + [ -n ] + echo MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72" + echo MNT_DIR=/ + echo MNT_TYPE=ext4 + echo MNT_PASS=0 + break 2 + eval MNT_FSNAME= MNT_DIR= MNT_TYPE= MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72" MNT_DIR=/ MNT_TYPE=ext4 MNT_PASS=0 + MNT_FSNAME= + MNT_DIR= + MNT_TYPE= + MNT_FSNAME=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + MNT_DIR=/ + MNT_TYPE=ext4 + MNT_PASS=0 + [ / = / ] + [ / = / ] + resolve_device UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + DEV=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + local orig=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + blkid -l -t
[Touch-packages] [Bug 2056696] Re: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors
The thunderbird fallback notification bug is here, so this *might* be a dupe: https://bugs.launchpad.net/bugs/2056481 -- 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/2056696 Title: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors Status in snapd: New Status in apparmor package in Ubuntu: New Bug description: OS: Kubuntu Noble 24.04 Alpha (two-day old install) snapd version: 2.61.2 Affected Snaps: firefox, thunderbird, element-desktop Steps to reproduce: # For Firefox: 1. Open the Firefox Snap. 2. Open https://www.bennish.net/web-notifications.html. 3. Click "Authorize" and allow the website to send notifications. 4. Click "Show". Expected result: A notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: The notification shows up in the upper-right corner of the display, improperly themed and obviously generated by Firefox as a fallback. # For Thunderbird: 1. Open the Thunderbird Snap. 2. Ensure you are connected to an email account. 3. Unfocus the Thunderbird window. 4. Wait for an email to come through. Expected result: When the email comes through, a notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: The notification shows up improperly themed and obviously generated by Thunderbird as a fallback. # For Element: 1. Open the Element Snap. Expected result: An apptray indicator should appear in the system tray with the Element logo. Actual result: No such indicator appears. 2. Log in, ask someone to ping you, then unfocus the window and wait for the ping to come through. Expected result: A notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: No notification appears at all. Additional information: Based on the output of snappy-debug, this appears to be AppArmor related, at least for element-desktop (but presumably for the others too). Of note are some of the following log entries: ``` = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="ListActivatableNames" mask="send" name="org.freedesktop.DBus" pid=2950 label="snap.element-desktop.element-desktop" peer_label="unconfined" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/modules/kwalletd5" interface="org.kde.KWallet" member="isEnabled" mask="send" name="org.kde.kwalletd5" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=1762 peer_label="unconfined" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/modules/kwalletd5" interface="org.kde.KWallet" member="close" mask="send" name="org.kde.kwalletd5" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=1762 peer_label="unconfined" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/StatusNotifierItem" interface="org.freedesktop.DBus.Properties" member="GetAll" name=":1.45" mask="receive" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=2394 peer_label="plasmashell" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_signal" bus="session" path="/StatusNotifierItem" interface="org.kde.StatusNotifierItem" member="NewToolTip" mask="send" name="org.freedesktop.DBus" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=2394 peer_label="plasmashell" DBus access ``` Booting with `apparmor=0` set on the kernel command line fixes the issue with Element (apptray indicator appears, notifications show up). Obviously this is not a solution, but it does isolate AppArmor as being at least partially at fault. This issue seems to be somewhat similar to https://forum.snapcraft.io/t/dbus-related-apparmor-denials/37422, however it seems as if Element is trying to hit the right paths and interfaces and is still being denied (based on looking at the info in https://github.com/snapcore/snapd/blob/master/interfaces/builtin/desktop_legacy.go and comparing the paths and interfaces there with the paths and interfaces shown by snappy-debug. I talked about this issue with Erich Eickmeyer and he mentioned that it occurred after a Plasma update. This doesn't make a great deal of sense to me, and I suspect possibly some other component of the affected systems happened to get updated at the same time (perhaps the snapd Snap), but it's definitely worth mentioning. An example of one of Thunderbird's fallback
[Touch-packages] [Bug 2057710] [NEW] Accountsservice FTBFS on noble
Public bug reported: package version 23.13.9-2ubuntu FTBFS on all architectures. This is because of an invalid test This has been resolved upstream - see the attached debdiff ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Patch added: "addtest.patch" https://bugs.launchpad.net/bugs/2057710/+attachment/5755358/+files/addtest.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2057710 Title: Accountsservice FTBFS on noble Status in accountsservice package in Ubuntu: New Bug description: package version 23.13.9-2ubuntu FTBFS on all architectures. This is because of an invalid test This has been resolved upstream - see the attached debdiff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2057710/+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 2057605] Re: update-initramfs fails: /usr/share/initramfs-tools/hooks/fsck failed with return 1
** Package changed: ubuntu => initramfs-tools (Ubuntu) -- 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/2057605 Title: update-initramfs fails: /usr/share/initramfs-tools/hooks/fsck failed with return 1 Status in initramfs-tools package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 initramfs-tools: Installed: 0.136ubuntu6.7 Candidate: 0.136ubuntu6.7 Version table: *** 0.136ubuntu6.7 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.136ubuntu6 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages sudo apt-get install linux-image-5.4.0-173-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-modules-5.4.0-173-generic Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-173-generic The following NEW packages will be installed: linux-image-5.4.0-173-generic linux-modules-5.4.0-173-generic 0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded. Need to get 25.5 MB of archives. After this operation, 92.5 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-modules-5.4.0-173-generic amd64 5.4.0-173.191 [15.0 MB] Get:2 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-5.4.0-173-generic amd64 5.4.0-173.191 [10.5 MB] Fetched 25.5 MB in 2s (12.1 MB/s) Selecting previously unselected package linux-modules-5.4.0-173-generic. (Reading database ... 77620 files and directories currently installed.) Preparing to unpack .../linux-modules-5.4.0-173-generic_5.4.0-173.191_amd64.deb ... Unpacking linux-modules-5.4.0-173-generic (5.4.0-173.191) ... Selecting previously unselected package linux-image-5.4.0-173-generic. Preparing to unpack .../linux-image-5.4.0-173-generic_5.4.0-173.191_amd64.deb ... Unpacking linux-image-5.4.0-173-generic (5.4.0-173.191) ... Setting up linux-modules-5.4.0-173-generic (5.4.0-173.191) ... Setting up linux-image-5.4.0-173-generic (5.4.0-173.191) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-173-generic I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-173-generic Processing triggers for linux-image-5.4.0-173-generic (5.4.0-173.191) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-173-generic + PREREQ= + prereqs + echo + exit 0 + PREREQ= + [ ! -x /sbin/fsck ] + . /usr/share/initramfs-tools/scripts/functions + . /usr/share/initramfs-tools/hook-functions + + sort get_fsck_types + get_fsck_type_fstab / root + uniq + _read_fstab_entry / + echo MNT_FSNAME= + echo MNT_DIR= + echo MNT_TYPE= + [ -f /etc/fstab ] + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ / = / ] + [ -n ] + echo MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72" + echo MNT_DIR=/ + echo MNT_TYPE=ext4 + echo MNT_PASS=0 + break 2 + eval MNT_FSNAME= MNT_DIR= MNT_TYPE= MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72" MNT_DIR=/ MNT_TYPE=ext4 MNT_PASS=0 + MNT_FSNAME= + MNT_DIR= + MNT_TYPE= + MNT_FSNAME=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + MNT_DIR=/ + MNT_TYPE=ext4 + MNT_PASS=0 + [ / = / ] + [ / = / ] + resolve_device UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + DEV=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + local orig=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + blkid -l -t UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 -o device + DEV=/dev/md127 + [ -e /dev/md127 ] + echo /dev/md127 + MNT_FSNAME=/dev/md127 + get_fstype /dev/md127 + local FS FSTYPE + FS=/dev/md127 + blkid -o value -s TYPE /dev/md127 + FSTYPE=ext4 + echo ext4 + return 0 + get_fsck_type_fstab /usr /usr + _read_fstab_entry /usr + echo MNT_FSNAME= + echo MNT_DIR= + echo MNT_TYPE= + [ -f /etc/fstab ] + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ / = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ /var = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ /home = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ swap = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ swap = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ /boot/efi = /usr ] + MNT_DIR= + read -r
[Touch-packages] [Bug 2057605] [NEW] update-initramfs fails: /usr/share/initramfs-tools/hooks/fsck failed with return 1
You have been subscribed to a public bug: lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 initramfs-tools: Installed: 0.136ubuntu6.7 Candidate: 0.136ubuntu6.7 Version table: *** 0.136ubuntu6.7 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.136ubuntu6 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages sudo apt-get install linux-image-5.4.0-173-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-modules-5.4.0-173-generic Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-173-generic The following NEW packages will be installed: linux-image-5.4.0-173-generic linux-modules-5.4.0-173-generic 0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded. Need to get 25.5 MB of archives. After this operation, 92.5 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-modules-5.4.0-173-generic amd64 5.4.0-173.191 [15.0 MB] Get:2 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-5.4.0-173-generic amd64 5.4.0-173.191 [10.5 MB] Fetched 25.5 MB in 2s (12.1 MB/s) Selecting previously unselected package linux-modules-5.4.0-173-generic. (Reading database ... 77620 files and directories currently installed.) Preparing to unpack .../linux-modules-5.4.0-173-generic_5.4.0-173.191_amd64.deb ... Unpacking linux-modules-5.4.0-173-generic (5.4.0-173.191) ... Selecting previously unselected package linux-image-5.4.0-173-generic. Preparing to unpack .../linux-image-5.4.0-173-generic_5.4.0-173.191_amd64.deb ... Unpacking linux-image-5.4.0-173-generic (5.4.0-173.191) ... Setting up linux-modules-5.4.0-173-generic (5.4.0-173.191) ... Setting up linux-image-5.4.0-173-generic (5.4.0-173.191) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-173-generic I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-173-generic Processing triggers for linux-image-5.4.0-173-generic (5.4.0-173.191) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-173-generic + PREREQ= + prereqs + echo + exit 0 + PREREQ= + [ ! -x /sbin/fsck ] + . /usr/share/initramfs-tools/scripts/functions + . /usr/share/initramfs-tools/hook-functions + + sort get_fsck_types + get_fsck_type_fstab / root + uniq + _read_fstab_entry / + echo MNT_FSNAME= + echo MNT_DIR= + echo MNT_TYPE= + [ -f /etc/fstab ] + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ / = / ] + [ -n ] + echo MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72" + echo MNT_DIR=/ + echo MNT_TYPE=ext4 + echo MNT_PASS=0 + break 2 + eval MNT_FSNAME= MNT_DIR= MNT_TYPE= MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72" MNT_DIR=/ MNT_TYPE=ext4 MNT_PASS=0 + MNT_FSNAME= + MNT_DIR= + MNT_TYPE= + MNT_FSNAME=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + MNT_DIR=/ + MNT_TYPE=ext4 + MNT_PASS=0 + [ / = / ] + [ / = / ] + resolve_device UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + DEV=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + local orig=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + blkid -l -t UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 -o device + DEV=/dev/md127 + [ -e /dev/md127 ] + echo /dev/md127 + MNT_FSNAME=/dev/md127 + get_fstype /dev/md127 + local FS FSTYPE + FS=/dev/md127 + blkid -o value -s TYPE /dev/md127 + FSTYPE=ext4 + echo ext4 + return 0 + get_fsck_type_fstab /usr /usr + _read_fstab_entry /usr + echo MNT_FSNAME= + echo MNT_DIR= + echo MNT_TYPE= + [ -f /etc/fstab ] + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ / = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ /var = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ /home = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ swap = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ swap = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ /boot/efi = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ -f /etc/fstab.d/*.fstab ] + eval MNT_FSNAME= MNT_DIR= MNT_TYPE= + MNT_FSNAME= + MNT_DIR= + MNT_TYPE= + [ /usr = ] + fsck_types=ext4 + [ -z ext4 ] + copy_exec /sbin/fsck + local src target x nonoptlib ret + src=/sbin/fsck + target=/sbin/fsck + copy_file binary /sbin/fsck /sbin/fsck + local type src target link_target + type=binary + src=/sbin/fsck + target=/sbin/fsck + [ -f /sbin/fsck ] + [ -d /var/tmp/mkinitramfs_dK1Mgz//sbin/fsck ] + target=/usr/sbin/fsck + [ -e /var/tmp/mkinitramfs_dK1Mgz//usr/sbin/fsck ] + mkdir -p
[Touch-packages] [Bug 2057704] Re: jackd2 FTBFS due to waflib incompatible with Python 3.12
The jackd2 maintainer is a friend of mine, I'll let him know about this bug. :) Edit: He already fixed it. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/2057704 Title: jackd2 FTBFS due to waflib incompatible with Python 3.12 Status in jackd2 package in Ubuntu: New Bug description: jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF build system inside. The upstream has already fixed the issue in a recent commit, we need to introduce this as a patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2057704/+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 2057704] Re: jackd2 FTBFS due to waflib incompatible with Python 3.12
** Merge proposal linked: https://code.launchpad.net/~liushuyu-011/ubuntu/+source/jackd2/+git/jackd2/+merge/462267 ** Changed in: jackd2 (Ubuntu) Assignee: (unassigned) => Zixing Liu (liushuyu-011) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/2057704 Title: jackd2 FTBFS due to waflib incompatible with Python 3.12 Status in jackd2 package in Ubuntu: New Bug description: jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF build system inside. The upstream has already fixed the issue in a recent commit, we need to introduce this as a patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2057704/+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 2054609] Re: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ntp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: Confirmed Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-02-25 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-97-fips x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+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 2038925] Re: Many hangs during apt full-upgrade
They sometimes happen when updating and installing packages. I haven't seen them happen when reinstalling packages, but I rarely reinstall packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038925 Title: Many hangs during apt full-upgrade Status in apt package in Ubuntu: New Bug description: Since upgrading to Ubuntu 23.10, running "apt full-upgrade" has resulted in many hangs of up to a minute or so during the upgrade procedure. These seem to happen at random and unpredictable steps during the upgrade. Running it just now, it hung for around a minute on this line: Installing new version of config file /etc/lsb-release ... At around the same time, the following was logged to /var/log/syslog, which may or may not be related: 2023-10-10T06:38:33.162713-07:00 albatross hud-service[3499]: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface “com.canonical.dbusmenu” on object at path /org/ayatana/bamf/window/73400498" It then hung again for about a minute at: Setting up apport (2.27.0-0ubuntu5) ... but nothing was logged to syslog. These hangs did not happen on 23.04. I appreciate that this is all a bit vague, so am happy to do further debugging if someone can advise me what to do. I also appreciate that apt might not be the correct package to file this bug against - feel free to reassign it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 10 06:41:34 2023 InstallationDate: Installed on 2020-07-14 (1183 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: apt UpgradeStatus: Upgraded to mantic on 2023-09-16 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2038925/+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 2057704] [NEW] jackd2 FTBFS due to waflib incompatible with Python 3.12
Public bug reported: jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF build system inside. The upstream has already fixed the issue in a recent commit, we need to introduce this as a patch. ** Affects: jackd2 (Ubuntu) Importance: Undecided Assignee: Zixing Liu (liushuyu-011) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/2057704 Title: jackd2 FTBFS due to waflib incompatible with Python 3.12 Status in jackd2 package in Ubuntu: New Bug description: jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF build system inside. The upstream has already fixed the issue in a recent commit, we need to introduce this as a patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2057704/+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 2038925] Re: Many hangs during apt full-upgrade
Do these freezes occur when updating, installing and reinstalling packages too? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038925 Title: Many hangs during apt full-upgrade Status in apt package in Ubuntu: New Bug description: Since upgrading to Ubuntu 23.10, running "apt full-upgrade" has resulted in many hangs of up to a minute or so during the upgrade procedure. These seem to happen at random and unpredictable steps during the upgrade. Running it just now, it hung for around a minute on this line: Installing new version of config file /etc/lsb-release ... At around the same time, the following was logged to /var/log/syslog, which may or may not be related: 2023-10-10T06:38:33.162713-07:00 albatross hud-service[3499]: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface “com.canonical.dbusmenu” on object at path /org/ayatana/bamf/window/73400498" It then hung again for about a minute at: Setting up apport (2.27.0-0ubuntu5) ... but nothing was logged to syslog. These hangs did not happen on 23.04. I appreciate that this is all a bit vague, so am happy to do further debugging if someone can advise me what to do. I also appreciate that apt might not be the correct package to file this bug against - feel free to reassign it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 10 06:41:34 2023 InstallationDate: Installed on 2020-07-14 (1183 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: apt UpgradeStatus: Upgraded to mantic on 2023-09-16 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2038925/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Before I saw your post about the environment variable, I edited the profile in /etc/apparmor.d/firefox to reflect /opt/firefox. If I launch from a mate desktop icon, or from the menu, all is well. If I click on a link, from say an email, I get the tab crashed bug again. Is there a way to work around this? I'm using Thunderbird, installed the same way, for my email. -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2057700] [NEW] On Bluetooth mode whenI open layout to volume on Kubuntu sound gone after clsoe to volume layour on right left icon.
Public bug reported: When I click to volume icon on left down on kde ubuntu bluetooth sound gone when I close to volume layout sound come back. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: fox1403 F pulseaudio /dev/snd/controlC1: fox1403 F pulseaudio /dev/snd/pcmC1D6c: fox1403 F...m pulseaudio /dev/snd/controlC0: fox1403 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Mar 12 22:47:22 2024 InstallationDate: Installed on 2024-03-10 (2 days ago) InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2024 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0GT7NV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd01/05/2024:br1.12:efr1.4:svnDellInc.:pnDellG167630:pvr:rvnDellInc.:rn0GT7NV:rvrA00:cvnDellInc.:ct10:cvr:sku0BFA: dmi.product.family: GSeries dmi.product.name: Dell G16 7630 dmi.product.sku: 0BFA dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2057700 Title: On Bluetooth mode whenI open layout to volume on Kubuntu sound gone after clsoe to volume layour on right left icon. Status in pulseaudio package in Ubuntu: New Bug description: When I click to volume icon on left down on kde ubuntu bluetooth sound gone when I close to volume layout sound come back. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: fox1403 F pulseaudio /dev/snd/controlC1: fox1403 F pulseaudio /dev/snd/pcmC1D6c: fox1403 F...m pulseaudio /dev/snd/controlC0: fox1403 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Mar 12 22:47:22 2024 InstallationDate: Installed on 2024-03-10 (2 days ago) InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2024 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0GT7NV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd01/05/2024:br1.12:efr1.4:svnDellInc.:pnDellG167630:pvr:rvnDellInc.:rn0GT7NV:rvrA00:cvnDellInc.:ct10:cvr:sku0BFA: dmi.product.family: GSeries dmi.product.name: Dell G16 7630 dmi.product.sku: 0BFA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2057700/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
Xavier - do you happen to have the /etc/apt/sources.list.d/ubuntu.sources that was on your machine for the failed upgrade attempt? ** Also affects: python-apt (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu Mantic) Importance: Undecided => High ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
This appears to be a bug in python-apt. It fails to parse .sources files which contain a comment paragraph which is not connect to a source stanza (I think). I.e., this first scenario is fine: root@mantic:~# cat /etc/apt/sources.list.d/ubuntu.sources # This comment is OK. Types: deb URIs: http://archive.ubuntu.com/ubuntu Suites: mantic mantic-updates Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg root@mantic:~# python3 Python 3.11.6 (main, Oct 8 2023, 05:06:43) [GCC 13.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from aptsources.sourceslist import SourcesList >>> for e in SourcesList(deb822=True): ... print(str(e)) ... # This comment is OK. Types: deb URIs: http://archive.ubuntu.com/ubuntu Suites: mantic mantic-updates Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg >>> As opposed to this, which fails: root@mantic:~# cat /etc/apt/sources.list.d/ubuntu.sources # This comment is NOT OK. # This comment is OK. Types: deb URIs: http://archive.ubuntu.com/ubuntu Suites: mantic mantic-updates Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg root@mantic:~# python3 Python 3.11.6 (main, Oct 8 2023, 05:06:43) [GCC 13.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from aptsources.sourceslist import SourcesList >>> for e in SourcesList(deb822=True): ... print(str(e)) ... WARNING:root:could not open file '/etc/apt/sources.list.d/ubuntu.sources': Unable to parse section data >>> -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2053228] Re: software-properties-gtk does not start
BTW: pressing the "Revert" button tries to launch "dbus-launch", but in
my Noble system it wasn't installed. I had to manually install
"dbus-x11" to have it. Maybe it should be included in the
dependencies...
--
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/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Triaged
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
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: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2053228] Re: software-properties-gtk does not start
Anyway, the "Revert" button does nothing... so there is something else
that has to be done.
--
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/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Triaged
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
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: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2026757] Re: dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates
Yes, still happens with 2.90-0ubuntu0.22.04.1. It is a problem with the upstream code as far as I can tell from dnsmasq, not the ubuntu package build itself. Message: Process 1671294 (dnsmasq) of user 65534 dumped core. Found module linux-vdso.so.1 with build-id: 975d8292a19f8c241322ae7eb151b63f4f01d8e2 Found module ld-linux-x86-64.so.2 with build-id: 15921ea631d9f36502d20459c43e5c85b7d6ab76 Found module libc.so.6 with build-id: c289da5071a3399de893d2af81d6a30c62646e1e Found module dnsmasq with build-id: aa89f97a7ccd45a1c50674eb7d5da473d605d476 Stack trace of thread 1671294: #0 0x7fbd66ca29fc __pthread_kill_implementation (libc.so.6 + 0x969fc) #1 0x7fbd66c4e476 __GI_raise (libc.so.6 + 0x42476) #2 0x7fbd66c347f3 __GI_abort (libc.so.6 + 0x287f3) #3 0x7fbd66c95676 __libc_message (libc.so.6 + 0x89676) #4 0x7fbd66caccfc malloc_printerr (libc.so.6 + 0xa0cfc) #5 0x7fbd66caea44 _int_free (libc.so.6 + 0xa2a44) #6 0x7fbd66cb1453 __GI___libc_free (libc.so.6 + 0xa5453) #7 0x555899cd1a32 dhcp_netid_free (dnsmasq + 0x16a32) #8 0x555899cdc001 clear_dynamic_conf (dnsmasq + 0x21001) #9 0x555899ce58af clear_cache_and_reload (dnsmasq + 0x2a8af) #10 0x555899cc5ad7 async_event (dnsmasq + 0xaad7) #11 0x7fbd66c35d90 __libc_start_call_main (libc.so.6 + 0x29d90) #12 0x7fbd66c35e40 __libc_start_main_impl (libc.so.6 + 0x29e40) #13 0x555899cc6375 _start (dnsmasq + 0xb375) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2026757 Title: dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates Status in Ironic: Triaged Status in neutron: New Status in dnsmasq package in Ubuntu: Invalid Status in dnsmasq source package in Jammy: Incomplete Status in dnsmasq source package in Kinetic: Won't Fix Status in dnsmasq source package in Lunar: Invalid Status in dnsmasq source package in Mantic: Invalid Bug description: The Ironic project's CI has been having major blocking issues moving to utilizing Ubuntu Jammy and with some investigation we were able to isolate the issues down to the dhcp updates causing dnsmasq to crash on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds similar to an issue known about to the dnsmasq maintainers, where dnsmasq would crash with updates occurring due to configuration refresh[0]. This resulted in us upgrading dnsmasq to the version which ships with Ubuntu Lunar. Which was no better. Dnsmasq still crashed upon record updates for addresses and ports getting configuration added/changed/removed. We later downgraded to the version of dnsmasq shipped in Ubuntu Focal, and dnsmasq stopped crashing and appeared stable enough to utilize for CI purposes. ** Kernel log from Ubuntu Jammy Package ** [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000] [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000] [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000] [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000] [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000] [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83
[Touch-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15
** Changed in: fontconfig (Ubuntu) Status: Triaged => Fix Committed ** Changed in: fonts-noto-color-emoji (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2054924 Title: color emoji are broken with fontconfig 2.15 Status in Fontconfig: Fix Released Status in fontconfig package in Ubuntu: Fix Committed Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fontconfig package in Debian: Fix Released Bug description: The Noto Color Emoji font is no longer used to show emoji. Many emoji no longer show and the few that do are not in color. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2052930] Re: liblocale-gettext-perl autopkgtests fail against glibc 2.39
** Changed in: glibc (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblocale-gettext-perl in Ubuntu. https://bugs.launchpad.net/bugs/2052930 Title: liblocale-gettext-perl autopkgtests fail against glibc 2.39 Status in glibc package in Ubuntu: Invalid Status in liblocale-gettext-perl package in Ubuntu: Fix Committed Bug description: The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with the following errors: autopkgtest [15:27:03]: test autodep8-perl-build-deps: [--- 243s t/bind.t ... 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s t/frconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:02 2024 243s # Current time GMT: Wed Feb 7 15:27:02 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/frconvert.t at line 22 243s # t/frconvert.t line 22 is: ok(0); 243s Failed 1/1 subtests 243s t/jaconvert.t .. 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s test 243s not ok 1 243s # Failed test 1 in t/jaconvert.t at line 23 243s # t/jaconvert.t line 23 is: ok(0); 243s Failed 1/1 subtests 243s t/raw.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s not ok 1 243s # Failed test 1 in t/raw.t at line 14 243s # t/raw.t line 14 is: ok(0); 243s Failed 1/1 subtests 243s t/use.t 243s 1..1 243s # Running under perl version 5.036000 for linux 243s # Current time local: Wed Feb 7 15:27:03 2024 243s # Current time GMT: Wed Feb 7 15:27:03 2024 243s # Using Test.pm version 1.31 243s ok 1 243s ok 243s 243s Test Summary Report 243s --- 243s t/frconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/jaconvert.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s t/raw.t (Wstat: 0 Tests: 1 Failed: 1) 243s Failed test: 1 243s Files=5, Tests=5, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.09 cusr 0.07 csys = 0.20 CPU) 243s Result: FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2052930/+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 2057687] [NEW] systemctl hibernate error: "Call to Hibernate failed: Invalid argument"
Public bug reported: After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped working. Trying to hibernate: systemctl hibernate I get: Call to Hibernate failed: Invalid argument systemctl status systemd-hibernate.service - × systemd-hibernate.service - Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static) Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 1min 33s ago Docs: man:systemd-hibernate.service(8) Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate (code=exited, status=1/FAILURE) Main PID: 4473 (code=exited, status=1/FAILURE) CPU: 5ms мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting systemd-hibernate.service - Hibernate... мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location to hibernate to: Invalid argument мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'. мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start systemd-hibernate.service - Hibernate. -- Previous version (254.x) worked: swapfile(on EXT4 fs) is used to hibernate/resume, resume with resume_offset kernel parameters. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/2057687 Title: systemctl hibernate error: "Call to Hibernate failed: Invalid argument" Status in systemd package in Ubuntu: New Bug description: After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped working. Trying to hibernate: systemctl hibernate I get: Call to Hibernate failed: Invalid argument systemctl status systemd-hibernate.service - × systemd-hibernate.service - Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static) Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 1min 33s ago Docs: man:systemd-hibernate.service(8) Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate (code=exited, status=1/FAILURE) Main PID: 4473 (code=exited, status=1/FAILURE) CPU: 5ms мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting systemd-hibernate.service - Hibernate... мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location to hibernate to: Invalid argument мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'. мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start systemd-hibernate.service - Hibernate. -- Previous version (254.x) worked: swapfile(on EXT4 fs) is used to hibernate/resume, resume with resume_offset kernel parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+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 2053228] Re: software-properties-gtk does not start
The attachment "patch.diff" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Triaged
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
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: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2053228] Re: software-properties-gtk does not start
New patch that takes into account the _deb822 format.
** Patch added: "patch.diff"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+attachment/5755308/+files/patch.diff
--
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/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Triaged
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
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: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2057684] [NEW] Backport a fix from Pulseaudio 17 to fix playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients
Public bug reported: This is a request for a backport of an existing bug fix, present in the recent Pulseaudio version 17 upstream release, to the outdated Pulseaudio 16 releases in jammy - noble. Affects: Ubuntu 22.04.0 LTS and all later versions. The fix fixes an annoying start of playback timing bug that affects my own software package octave-psychtoolbox-3 (part of Ubuntu universe), see https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374 which uses GStreamer for video and audio playback. Psychtoolbox is a very popular toolkit for neuroscience and related medical research, with Ubuntu as the recommended target distribution. It requires high reliability in audio and video presentation timing, so the bug described in the various links below is serious to our users. The bug also in the same way affects other media applications in Ubuntu which play back audio via the default (auto-plugged) pulseaudiosink GStreamer plugin. See GStreamer bug report https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The GStreamer bug turned out to be a pulseaudio client library bug (in libpulse.so.0). Any native pulseaudio client is affected, even if pipewire is used as desktop sound server in recent Ubuntu releases, given that many audio applications still access pipewire via its pulseaudio frontend (package pipewire-pulse). See pipewire bug https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399 The bug in libpulse.so.0, reported against Pulseaudio 16 in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has been fixed for the Pulseaudio 17 release. See the following merge request for the following trivial one-liner patch that would need to be backported to Ubuntu's current implementation: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs I hoped that Pulseaudio 17 would be included in Debian in time for integration into Ubuntu 24.04-LTS, but apparently not much maintenance of pulseaudio is happening on the Debian side at the moment. Given that this bug affects all Ubuntu versions since Ubuntu 22.04-LTS, I'd ask kindly for a backport, ideally for Pulseaudio 15.99.1 in 22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at least for the upcoming 24.04-LTS. Alternatively it would have been great to get Pulseaudio upgraded to version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but apparently that is too late now, according to https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476 Thanks, -mario ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: gstreamer pipewire pulseaudio sound timing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2057684 Title: Backport a fix from Pulseaudio 17 to fix playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients Status in pulseaudio package in Ubuntu: New Bug description: This is a request for a backport of an existing bug fix, present in the recent Pulseaudio version 17 upstream release, to the outdated Pulseaudio 16 releases in jammy - noble. Affects: Ubuntu 22.04.0 LTS and all later versions. The fix fixes an annoying start of playback timing bug that affects my own software package octave-psychtoolbox-3 (part of Ubuntu universe), see https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374 which uses GStreamer for video and audio playback. Psychtoolbox is a very popular toolkit for neuroscience and related medical research, with Ubuntu as the recommended target distribution. It requires high reliability in audio and video presentation timing, so the bug described in the various links below is serious to our users. The bug also in the same way affects other media applications in Ubuntu which play back audio via the default (auto-plugged) pulseaudiosink GStreamer plugin. See GStreamer bug report https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The GStreamer bug turned out to be a pulseaudio client library bug (in libpulse.so.0). Any native pulseaudio client is affected, even if pipewire is used as desktop sound server in recent Ubuntu releases, given that many audio applications still access pipewire via its pulseaudio frontend (package pipewire-pulse). See pipewire bug https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399 The bug in libpulse.so.0, reported against Pulseaudio 16 in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has been fixed for the Pulseaudio 17 release. See the following merge request for the following trivial one-liner patch that would need to be backported to Ubuntu's current implementation: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs I
[Touch-packages] [Bug 2057671] Re: Rename the ubuntu-advantage-tools package
** Description changed: From ubuntu-advantage-tools v31, it has been renamed to ubuntu-pro- client. The current package is now a transitional package pointing to - ubuntu-pro-client. wsl-pro-service depends on ubuntu-advantage-tool thus - we should rename the dependency to ubuntu-pro-client to avoid having the - transitional package as a dependency. + ubuntu-pro-client. software-properties depends on ubuntu-advantage-tool + thus we should rename the dependency to ubuntu-pro-client to avoid + having the transitional package as a dependency. -- 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/2057671 Title: Rename the ubuntu-advantage-tools package Status in software-properties package in Ubuntu: New Bug description: From ubuntu-advantage-tools v31, it has been renamed to ubuntu-pro- client. The current package is now a transitional package pointing to ubuntu-pro-client. software-properties depends on ubuntu-advantage- tool thus we should rename the dependency to ubuntu-pro-client to avoid having the transitional package as a dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2057671/+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 2057671] Re: Rename the ubuntu-advantage-tools package
** Merge proposal linked: https://code.launchpad.net/~calvinmwadime/ubuntu/+source/software-properties/+git/software-properties/+merge/462237 -- 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/2057671 Title: Rename the ubuntu-advantage-tools package Status in software-properties package in Ubuntu: New Bug description: From ubuntu-advantage-tools v31, it has been renamed to ubuntu-pro- client. The current package is now a transitional package pointing to ubuntu-pro-client. wsl-pro-service depends on ubuntu-advantage-tool thus we should rename the dependency to ubuntu-pro-client to avoid having the transitional package as a dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2057671/+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 2057671] [NEW] Rename the ubuntu-advantage-tools package
Public bug reported: >From ubuntu-advantage-tools v31, it has been renamed to ubuntu-pro- client. The current package is now a transitional package pointing to ubuntu-pro-client. wsl-pro-service depends on ubuntu-advantage-tool thus we should rename the dependency to ubuntu-pro-client to avoid having the transitional package as a dependency. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- 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/2057671 Title: Rename the ubuntu-advantage-tools package Status in software-properties package in Ubuntu: New Bug description: From ubuntu-advantage-tools v31, it has been renamed to ubuntu-pro- client. The current package is now a transitional package pointing to ubuntu-pro-client. wsl-pro-service depends on ubuntu-advantage-tool thus we should rename the dependency to ubuntu-pro-client to avoid having the transitional package as a dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2057671/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
A workaround is to set the environment variable MOZ_ASSUME_USER_NS=0. You can run it as: env MOZ_ASSUME_USER_NS=0 /home/bob/Downloads/firefox/firefox --name=firefox-nightly %u -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
I confirmed the patch matches the upstream changes and builds find. I see the bug description ([Test] section) was updated to mention pairing of 7 audio and 2 non-audio devices. That pairing test needs to be re-run with the final binaries, once they are build in the archive, as per the usual SRU process. Sponsoring for Mantic & Jammy, unsubscribing sponsors. The status is already set to "In Progress". https://launchpad.net/ubuntu/mantic/+queue?queue_state=1_text=pulseaudio https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=pulseaudio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Jammy: In Progress Status in pulseaudio source package in Mantic: In Progress Status in pulseaudio source package in Noble: Fix Committed Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my change only affects bluetooth audio devices, it will not bring any impact to non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices and 2 non-audio devices: BT audio devices (pairing, connection, re-connection, playback and capture all worked well): PLT_BBTGO2 (headset) Xiaomi Air3 SE (headset) Crusher Wireless (headset) SOAIY S18 (sound box) HK Soho Wireless (headset) Thinkplus XT99 (headset) Wl-1000X (headset) BT non-audio devices (pairing, connection, re-connection, key input all worked well): BT3.0 Keyboard The Pinao 2 keyboard [Where problems could occur] This change will impact bt headset negotiation process in the pulseaudio, so the possiblity of regression is limited to bt headset, it could make the bt headset fail to connect, but this possibility is very low, we tested the patch with different bt headset and bt speaker, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2053228] Re: software-properties-gtk does not start
While the patch makes the application run it also breaks the
functionality it's patching for deb822 sources by just ignoring them.
More work is needed and I do have it scheduled for this pulse
--
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/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Triaged
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
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: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2053228] Re: software-properties-gtk does not start
A quick patch.
** Patch added: "patch.diff"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+attachment/5755261/+files/patch.diff
--
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/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Triaged
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
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: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure
** No longer affects: pygobject (Ubuntu) ** Changed in: gobject-introspection (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/2056753 Title: pygobject FTBFS on armhf: time_t build test failure Status in GObject Introspection: New Status in gobject-introspection package in Ubuntu: Fix Committed Status in gobject-introspection package in Debian: New Bug description: pygobject fails to build on armhf, the only Ubuntu 32-bit architecture that has done the time_t transition. test_gi.py runs a time_t test that I believe is using functions in glib2.0 Test log excerpt tests/test_gi.py ... [ 21%] . --- stderr --- Fatal Python error: Aborted Current thread 0xf785e020 (most recent call first): File "/<>/tests/test_gi.py", line 579 in test_time_t_in File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod File "/usr/lib/python3.12/unittest/case.py", line 634 in run File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__ File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in runtest File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in pytest_runtest_call File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in from_call File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in call_runtest_hook File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in call_and_report File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in runtestprotocol File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in pytest_runtest_protocol File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in pytest_runtestloop File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in wrap_session File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in pytest_cmdline_main File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 in main File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 in console_main File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in File "", line 88 in _run_code File "", line 198 in _run_module_as_main Full build log == https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 2056739] Re: apparmor="DENIED" operation="open" class="file" profile="virt-aa-helper" name="/etc/gnutls/config"
Yes, will do I added both reference you provided to the upstream merge commit and all fixes/closes references will be going into the changelog. -- 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/2056739 Title: apparmor="DENIED" operation="open" class="file" profile="virt-aa- helper" name="/etc/gnutls/config" Status in apparmor package in Ubuntu: In Progress Status in chrony package in Ubuntu: Won't Fix Status in gnutls28 package in Ubuntu: Won't Fix Status in libvirt package in Ubuntu: Won't Fix Status in apparmor source package in Noble: In Progress Status in chrony source package in Noble: Won't Fix Status in gnutls28 source package in Noble: Won't Fix Status in libvirt source package in Noble: Won't Fix Bug description: Christian summarizes this after the great reports by Martin: gnutls started to ship forceful disables in pkg/import/3.8.1-4ubuntu3 and added more later. Due to that anything linked against gnutls while being apparmor isolated now hits similar denials, preventing the desired effect of the config change BTW. I think for safety we WANT to always allow this access, otherwise people will subtly not have crypto control about the more important (those isolated) software. Because after the denial I'd expect this to not really disable it in the program linked to gnutls (details might vary depending what they really use gnutls for). I do not nkow of a gnutls abstraction to use, but TBH I'm afraid now fixing a few but leaving this open in some others not spotted. I'd therefore suggest, but we need to discuss, to therefore change it in /etc/apparmor.d/abstractions/base. Therefore I'm adding gnutls (and Adrien) as well as apparmor to the bug tasks. --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Merely booting current noble cloud image with "chrony" installed causes this: audit: type=1400 audit(1710152842.540:107): apparmor="DENIED" operation="open" class="file" profile="/usr/sbin/chronyd" name="/etc/gnutls/config" pid=878 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Running any VM in libvirt causes a new AppArmor violation in current noble. This is a regression, this didn't happen in any previous release. Reproducer: virt-install --memory 50 --pxe --virt-type qemu --os-variant alpinelinux3.8 --disk none --wait 0 --name test1 (This is the simplest way to create a test VM. But it's form or shape doesn't matter at all). Results in lots of audit: type=1400 audit(1710146677.570:108): apparmor="DENIED" operation="open" class="file" profile="virt-aa-helper" name="/etc/gnutls/config" pid=1480 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 libvirt-daemon 10.0.0-2ubuntu1 apparmor 4.0.0~alpha4-0ubuntu1 libgnutls30:amd64 3.8.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056739/+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 2057490] [NEW] Crash during upgrade from Jammy/Mantic to Noble
Public bug reported: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "mantic-noble-ubuntu-mate_network-manager_crash.zip" https://bugs.launchpad.net/bugs/2057490/+attachment/5755245/+files/mantic-noble-ubuntu-mate_network-manager_crash.zip ** Summary changed: - Crash during upgrade from Mantic to Noble + Crash during upgrade from Jammy/Mantic to Noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble Status in network-manager package in Ubuntu: New Bug description: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+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 2056739] Re: apparmor="DENIED" operation="open" class="file" profile="virt-aa-helper" name="/etc/gnutls/config"
** Changed in: chrony (Ubuntu) Status: New => Won't Fix ** Changed in: gnutls28 (Ubuntu) Status: New => Won't Fix ** Changed in: libvirt (Ubuntu) Status: New => Won't Fix -- 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/2056739 Title: apparmor="DENIED" operation="open" class="file" profile="virt-aa- helper" name="/etc/gnutls/config" Status in apparmor package in Ubuntu: In Progress Status in chrony package in Ubuntu: Won't Fix Status in gnutls28 package in Ubuntu: Won't Fix Status in libvirt package in Ubuntu: Won't Fix Status in apparmor source package in Noble: In Progress Status in chrony source package in Noble: Won't Fix Status in gnutls28 source package in Noble: Won't Fix Status in libvirt source package in Noble: Won't Fix Bug description: Christian summarizes this after the great reports by Martin: gnutls started to ship forceful disables in pkg/import/3.8.1-4ubuntu3 and added more later. Due to that anything linked against gnutls while being apparmor isolated now hits similar denials, preventing the desired effect of the config change BTW. I think for safety we WANT to always allow this access, otherwise people will subtly not have crypto control about the more important (those isolated) software. Because after the denial I'd expect this to not really disable it in the program linked to gnutls (details might vary depending what they really use gnutls for). I do not nkow of a gnutls abstraction to use, but TBH I'm afraid now fixing a few but leaving this open in some others not spotted. I'd therefore suggest, but we need to discuss, to therefore change it in /etc/apparmor.d/abstractions/base. Therefore I'm adding gnutls (and Adrien) as well as apparmor to the bug tasks. --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Merely booting current noble cloud image with "chrony" installed causes this: audit: type=1400 audit(1710152842.540:107): apparmor="DENIED" operation="open" class="file" profile="/usr/sbin/chronyd" name="/etc/gnutls/config" pid=878 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Running any VM in libvirt causes a new AppArmor violation in current noble. This is a regression, this didn't happen in any previous release. Reproducer: virt-install --memory 50 --pxe --virt-type qemu --os-variant alpinelinux3.8 --disk none --wait 0 --name test1 (This is the simplest way to create a test VM. But it's form or shape doesn't matter at all). Results in lots of audit: type=1400 audit(1710146677.570:108): apparmor="DENIED" operation="open" class="file" profile="virt-aa-helper" name="/etc/gnutls/config" pid=1480 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 libvirt-daemon 10.0.0-2ubuntu1 apparmor 4.0.0~alpha4-0ubuntu1 libgnutls30:amd64 3.8.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056739/+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 2056739] Re: apparmor="DENIED" operation="open" class="file" profile="virt-aa-helper" name="/etc/gnutls/config"
FYI - submitted as https://gitlab.com/apparmor/apparmor/-/merge_requests/1178 @John if merged, would you mind adding a bug-ref to the Ubuntu upload changelog so this bug 2056739 closes? Given that there seems to be some agreement to fix this in apparmor, I'll set the other tasks to "Won't Fix" ** Changed in: libvirt (Ubuntu Noble) Status: New => Won't Fix ** Changed in: gnutls28 (Ubuntu Noble) Status: New => Won't Fix ** Changed in: chrony (Ubuntu Noble) Status: New => Won't Fix ** Changed in: apparmor (Ubuntu Noble) Status: New => In Progress -- 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/2056739 Title: apparmor="DENIED" operation="open" class="file" profile="virt-aa- helper" name="/etc/gnutls/config" Status in apparmor package in Ubuntu: In Progress Status in chrony package in Ubuntu: New Status in gnutls28 package in Ubuntu: New Status in libvirt package in Ubuntu: New Status in apparmor source package in Noble: In Progress Status in chrony source package in Noble: Won't Fix Status in gnutls28 source package in Noble: Won't Fix Status in libvirt source package in Noble: Won't Fix Bug description: Christian summarizes this after the great reports by Martin: gnutls started to ship forceful disables in pkg/import/3.8.1-4ubuntu3 and added more later. Due to that anything linked against gnutls while being apparmor isolated now hits similar denials, preventing the desired effect of the config change BTW. I think for safety we WANT to always allow this access, otherwise people will subtly not have crypto control about the more important (those isolated) software. Because after the denial I'd expect this to not really disable it in the program linked to gnutls (details might vary depending what they really use gnutls for). I do not nkow of a gnutls abstraction to use, but TBH I'm afraid now fixing a few but leaving this open in some others not spotted. I'd therefore suggest, but we need to discuss, to therefore change it in /etc/apparmor.d/abstractions/base. Therefore I'm adding gnutls (and Adrien) as well as apparmor to the bug tasks. --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Merely booting current noble cloud image with "chrony" installed causes this: audit: type=1400 audit(1710152842.540:107): apparmor="DENIED" operation="open" class="file" profile="/usr/sbin/chronyd" name="/etc/gnutls/config" pid=878 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Running any VM in libvirt causes a new AppArmor violation in current noble. This is a regression, this didn't happen in any previous release. Reproducer: virt-install --memory 50 --pxe --virt-type qemu --os-variant alpinelinux3.8 --disk none --wait 0 --name test1 (This is the simplest way to create a test VM. But it's form or shape doesn't matter at all). Results in lots of audit: type=1400 audit(1710146677.570:108): apparmor="DENIED" operation="open" class="file" profile="virt-aa-helper" name="/etc/gnutls/config" pid=1480 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 libvirt-daemon 10.0.0-2ubuntu1 apparmor 4.0.0~alpha4-0ubuntu1 libgnutls30:amd64 3.8.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056739/+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 2057467] Re: my external monitor screen keeps going blank intermittently
Thanks for the bug report. This is a common problem and is almost always
due to a bad connection or low quality cable. Please try unplugging and
replugging the cable at both ends. If that doesn't solve it then please
try a different cable. For better performance and reliability on a
Lenovo G50-70, I would recommend using the HDMI port instead of VGA.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2057467
Title:
my external monitor screen keeps going blank intermittently
Status in linux package in Ubuntu:
Incomplete
Bug description:
I have connected a samsung exnternal monitor to my laptop via VGA cable.
But the screen frequently goes blank, I have tried updating the graphics
drivers but of no use. Please help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 12 13:10:05 2024
DistUpgraded: 2024-02-05 14:12:41,366 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: nvidia/470.239.06, 6.5.0-25-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16]
(rev 0b) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c]
InstallationDate: Installed on 2022-11-10 (488 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
MonitorsUser.xml: 59.96
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-25-generic
root=UUID=d786cdef-a41c-4f13-8357-af62bee963a6 ro i915.enable_dc=0
intel_idle.max_cstate=2
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2024-02-05 (36 days ago)
dmi.bios.date: 10/20/2014
dmi.bios.release: 0.29
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ACN29WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5A2
dmi.board.vendor: LENOVO
dmi.board.version: NANANANANO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-70
dmi.ec.firmware.release: 0.29
dmi.modalias:
dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:br0.29:efr0.29:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:skuLENOVO_MT_20351_BU_idea_FM_LenovoG50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 20351
dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
dmi.product.version: Lenovo G50-70
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057467/+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 2057467] [NEW] my external monitor screen keeps going blank intermittently
Public bug reported:
I have connected a samsung exnternal monitor to my laptop via VGA cable.
But the screen frequently goes blank, I have tried updating the graphics
drivers but of no use. Please help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 12 13:10:05 2024
DistUpgraded: 2024-02-05 14:12:41,366 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: nvidia/470.239.06, 6.5.0-25-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev
0b) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c]
InstallationDate: Installed on 2022-11-10 (488 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
MonitorsUser.xml: 59.96
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-25-generic
root=UUID=d786cdef-a41c-4f13-8357-af62bee963a6 ro i915.enable_dc=0
intel_idle.max_cstate=2
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2024-02-05 (36 days ago)
dmi.bios.date: 10/20/2014
dmi.bios.release: 0.29
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ACN29WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5A2
dmi.board.vendor: LENOVO
dmi.board.version: NANANANANO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-70
dmi.ec.firmware.release: 0.29
dmi.modalias:
dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:br0.29:efr0.29:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:skuLENOVO_MT_20351_BU_idea_FM_LenovoG50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 20351
dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
dmi.product.version: Lenovo G50-70
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2057467
Title:
my external monitor screen keeps going blank intermittently
Status in xorg package in Ubuntu:
New
Bug description:
I have connected a samsung exnternal monitor to my laptop via VGA cable.
But the screen frequently goes blank, I have tried updating the graphics
drivers but of no use. Please help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 12 13:10:05 2024
DistUpgraded: 2024-02-05 14:12:41,366 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: nvidia/470.239.06, 6.5.0-25-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16]
(rev 0b) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c]
InstallationDate: Installed on 2022-11-10 (488 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
MonitorsUser.xml: 59.96
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-25-generic
root=UUID=d786cdef-a41c-4f13-8357-af62bee963a6 ro i915.enable_dc=0
intel_idle.max_cstate=2
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2024-02-05 (36 days ago)
dmi.bios.date: 10/20/2014
