[Touch-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes
Not a regression, or at least an intended regression (ie. it is doing exactly what is intended). This is exactly what has been talked about for 6+ months. unprivileged user_namespaces are going away, but instead of the big system level sysctl we can allow them on a per application basis. The only question is whether we default this off for 22.10 With the current kernel there are two options for dealing with this 1. for applications that don't have CAP_SYS_ADMIN confine the application if it needs to use user namespaces 2. set the sysctl apparmor_restrict_unprivileged_userns to 0 Its possible we could set this option in the kernel to default N. But it HAS to change soon. unprivileged usernamespaces have been used as part of the exploit chain in multiple attacks over the last several years. Debian defaults them off with the sysctl, and this gives them a potential option to move forward. I will re-iterate, unprivieged user_namespaces are going away, this is a requirement. -- 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/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1990064] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1990064 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** 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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1990064] Re: unconfined profile denies userns_create for chromium based processes
This sounds like a kernel regression. The commit you link to is for SELinux, which is not enabled by default in Ubuntu, so I doubt it is that specifically - instead I suspect this is due to the following commit: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master- next=30bce26855c9171f8dee74d93308fd506730c914 The logic here: int aa_profile_ns_perm(struct aa_profile *profile, struct common_audit_data *sa, u32 request) { ... if (profile_unconfined(profile)) { if (!unprivileged_userns_restricted || ns_capable_noaudit(current_user_ns(), CAP_SYS_ADMIN)) return 0; aad(sa)->info = "User namespace creation restricted"; /* fall through to below allows complain mode to override */ } else { struct aa_ruleset *rules = list_first_entry(>rules, typeof(*rules), list); aa_state_t state; state = RULE_MEDIATES(rules, aad(sa)->class); if (!state) /* TODO: add flag to complain about unmediated */ return 0; perms = *aa_lookup_perms(>policy, state); } aa_apply_modes_to_perms(profile, ); return aa_check_perms(profile, , request, sa, audit_ns_cb); } Seems to indicate that all unconfined processes that do not have CAP_SYS_ADMIN will be denied the ability to use user namespaces - this feels like a definite regression / policy change within the kernel itself. Should the kernel instead be built with CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS=n ? Or is this code not doing what it was intended to do. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1989973] Re: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version
Seems to have not quite done it still took 0.3 seconds :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1989973 Title: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version Status in vim package in Ubuntu: New Bug description: In a fresh focal install/container, vim is uninstallable because version 2:8.1.2269-1ubuntu5.8 failed to build for vim, but the `all` packages did succeed. ``` $ docker run -ti --rm arm32v7/ubuntu:focal bash -c 'apt update && apt install vim-tiny' WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/amd64) and no specific platform was requested Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages [1227 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports focal/universe armhf Packages [10.9 MB] Get:7 http://ports.ubuntu.com/ubuntu-ports focal/multiverse armhf Packages [141 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports focal/restricted armhf Packages [10.8 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted armhf Packages [16.9 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe armhf Packages [996 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse armhf Packages [9626 B] Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages [1400 kB] Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe armhf Packages [27.4 kB] Get:14 http://ports.ubuntu.com/ubuntu-ports focal-backports/main armhf Packages [54.7 kB] Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf Packages [1032 kB] Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/multiverse armhf Packages [4730 B] Get:17 http://ports.ubuntu.com/ubuntu-ports focal-security/universe armhf Packages [698 kB] Get:18 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted armhf Packages [16.6 kB] Fetched 17.2 MB in 8s (2274 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 23 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-tiny : Depends: vim-common (= 2:8.1.2269-1ubuntu5.7) but 2:8.1.2269-1ubuntu5.8 is to be installed E: Unable to correct problems, you have held broken packages. ``` Seems to be due to https://launchpad.net/ubuntu/+source/vim/2:8.1.2269-1ubuntu5.8/+build/24478851 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1989973/+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 1989973] Re: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version
** Tags added: foundations-todo ** Changed in: vim (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1989973 Title: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version Status in vim package in Ubuntu: New Bug description: In a fresh focal install/container, vim is uninstallable because version 2:8.1.2269-1ubuntu5.8 failed to build for vim, but the `all` packages did succeed. ``` $ docker run -ti --rm arm32v7/ubuntu:focal bash -c 'apt update && apt install vim-tiny' WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/amd64) and no specific platform was requested Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages [1227 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports focal/universe armhf Packages [10.9 MB] Get:7 http://ports.ubuntu.com/ubuntu-ports focal/multiverse armhf Packages [141 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports focal/restricted armhf Packages [10.8 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted armhf Packages [16.9 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe armhf Packages [996 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse armhf Packages [9626 B] Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages [1400 kB] Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe armhf Packages [27.4 kB] Get:14 http://ports.ubuntu.com/ubuntu-ports focal-backports/main armhf Packages [54.7 kB] Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf Packages [1032 kB] Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/multiverse armhf Packages [4730 B] Get:17 http://ports.ubuntu.com/ubuntu-ports focal-security/universe armhf Packages [698 kB] Get:18 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted armhf Packages [16.6 kB] Fetched 17.2 MB in 8s (2274 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 23 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-tiny : Depends: vim-common (= 2:8.1.2269-1ubuntu5.7) but 2:8.1.2269-1ubuntu5.8 is to be installed E: Unable to correct problems, you have held broken packages. ``` Seems to be due to https://launchpad.net/ubuntu/+source/vim/2:8.1.2269-1ubuntu5.8/+build/24478851 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1989973/+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 1989973] Re: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version
Argh that shouldn't have happened. I've retried both the builds (it looks like they failed because of infrastructure issues), hopefully that will fix it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1989973 Title: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version Status in vim package in Ubuntu: New Bug description: In a fresh focal install/container, vim is uninstallable because version 2:8.1.2269-1ubuntu5.8 failed to build for vim, but the `all` packages did succeed. ``` $ docker run -ti --rm arm32v7/ubuntu:focal bash -c 'apt update && apt install vim-tiny' WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/amd64) and no specific platform was requested Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages [1227 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports focal/universe armhf Packages [10.9 MB] Get:7 http://ports.ubuntu.com/ubuntu-ports focal/multiverse armhf Packages [141 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports focal/restricted armhf Packages [10.8 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted armhf Packages [16.9 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe armhf Packages [996 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse armhf Packages [9626 B] Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages [1400 kB] Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe armhf Packages [27.4 kB] Get:14 http://ports.ubuntu.com/ubuntu-ports focal-backports/main armhf Packages [54.7 kB] Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf Packages [1032 kB] Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/multiverse armhf Packages [4730 B] Get:17 http://ports.ubuntu.com/ubuntu-ports focal-security/universe armhf Packages [698 kB] Get:18 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted armhf Packages [16.6 kB] Fetched 17.2 MB in 8s (2274 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 23 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-tiny : Depends: vim-common (= 2:8.1.2269-1ubuntu5.7) but 2:8.1.2269-1ubuntu5.8 is to be installed E: Unable to correct problems, you have held broken packages. ``` Seems to be due to https://launchpad.net/ubuntu/+source/vim/2:8.1.2269-1ubuntu5.8/+build/24478851 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1989973/+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 1989292] Re: package openssh-server 1:8.9p1-3 failed to install/upgrade: »installiertes openssh-server-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zur
It's unclear to me how the comment about the kernel panic and the openssh upgrade failing are related to me, I'm afraid. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1989292 Title: package openssh-server 1:8.9p1-3 failed to install/upgrade: »installiertes openssh-server-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in openssh package in Ubuntu: Incomplete Bug description: when starting the system it shows the following: [ 0.578926]--- [end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0) ]--- ProblemType: Package DistroRelease: Ubuntu 22.04 Package: openssh-server 1:8.9p1-3 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Sep 8 13:40:54 2022 ErrorMessage: »installiertes openssh-server-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: openssh Title: package openssh-server 1:8.9p1-3 failed to install/upgrade: »installiertes openssh-server-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to jammy on 2022-09-08 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1989292/+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 1971409] Re: value_copy: Assertion `arg->contents != nullptr' failed.
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474 tracks the update of gdb to the 12.1 final release. You could try installing gdb from jammy-proposed and see if that helps? ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971409 Title: value_copy: Assertion `arg->contents != nullptr' failed. Status in gdb package in Ubuntu: Confirmed Bug description: When debugging RP2040 with vscode this assert makes gdb crash. This is a new assert, that wasn't present in gdb 11. The fix is easy, replace `if (!value_lazy (val))` to `if (!value_lazy (val) && arg->contents != nullptr) `. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409/+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 1971474] Re: SRU: Update gdb to the final 12.1 release in 22.04 LTS
** Changed in: gdb (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971474 Title: SRU: Update gdb to the final 12.1 release in 22.04 LTS Status in gdb package in Ubuntu: Invalid Status in gdb source package in Jammy: Fix Committed Bug description: Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are: - updated gnulib library - Fix for PR mi/29002 (Windows only) - gdb: fix 'remote show FOO-packet' aliases - various testsuite fixes - fixing compiler warnings - Fix bug in Ada number lexing - Remove "Ada Settings" node from the manual - Handle TLS variable lookups when using separate debug files. - PR 28980: gdb: don't copy entirely optimized out values in value_copy - gdb/mi: fix use after free of frame_info causing spurious notifications Comparing the test results between the two builds doesn't show any regression on any architecture. Also tested with a test rebuild of main, see LP: #1970233. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474/+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 1761341] Re: lsb_release crashed with ValueError in (): could not convert string to float: '6.06 LTS'
Ioanna are you going to take care of preparing patches for fixing the stable releases? I marked the overall/kinetic task as fix released as you say the bug is no longer present there. ** Changed in: lsb (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1761341 Title: lsb_release crashed with ValueError in (): could not convert string to float: '6.06 LTS' Status in lsb package in Ubuntu: Fix Released Status in lsb source package in Bionic: Confirmed Status in lsb source package in Focal: Confirmed Status in lsb source package in Jammy: Confirmed Bug description: [Description] In some cases lsb_release script can crash with the following trace : Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 356, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 246, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '6.06 LTS The root cause of this is that function get_distro_info() while parsing the '/usr/share/distro-info/ubuntu.csv' and expects to find a float at the beginning of each line, instead it find a string ("6.06 LTS"). There is a fix for this bug upstream: https://salsa.debian.org/debian/lsb/-/commit/4b36f9d31c00233ea20415542633729ab3799e61 and is already in kinetic. [Test Case] The easier way to reproduce this bug is to hack /usr/share/pyshared/lsb_release.py file change the get_distro_info definition from def get_distro_info(origin='Debian'): to def get_distro_info(origin='Ubuntu'): and run $ lsb_release Traceback (most recent call last): File "/usr/bin/lsb_release", line 25, in import lsb_release File "/usr/lib/python3/dist-packages/lsb_release.py", line 58, in get_distro_info() File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '6.06 LTS' A detailed analysis on how this bug can happen in a real life scenario can be found in comment #3. [Regression Potential] The fix changes the way get_distro_info function parses the csv file and instead of expecting a float at the beginning of the line, it now expects a string and isolates the numerical part. The regression potential is small and would affect the behavior of lsb_release executable. [Other] Debian bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980566 Fix : https://salsa.debian.org/debian/lsb/-/commit/4b36f9d31c00233ea20415542633729ab3799e61 Affected releases : Jammy, Focal, Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1761341/+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 1989969] Re: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el
** Changed in: systemd (Ubuntu) Status: New => Triaged ** Tags added: foundations-todo -- 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/1989969 Title: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el Status in systemd package in Ubuntu: Triaged Bug description: In Kinetic, TEST-36-NUMAPOLICY from upstream-2 fails very frequently on ppc64el. See for example: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/ppc64el/s/systemd/20220908_195425_da51e@/log.gz, and the full kinetic ppc64el history: https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el. It has passed on very few occasions. I have tried to debug this locally but have gotten very little useful information (i.e. not enough to open an upstream bug). For now it is probably best to denylist this test on ppc64el. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989969/+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 1981622] Re: mtd device must be supplied (device name is empty)
I don't see an upload for focal either in the unapproved queue or in proposed. Am I confused? resetting the status for focal to in progress in any case. ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => In Progress -- 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/1981622 Title: mtd device must be supplied (device name is empty) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Jammy: Fix Committed Bug description: [WORKAROUND] This will NOT fix a system that is not booting, because the "mtd device must be supplied (device name is empty)" message is not the cause of failed boots. This work around is only for those who are annoyed by the error message, but are otherwise not experiencing any issues. If you are not able to boot your system, but you see this error message, please open a separate bug with your journalctl and dmesg logs. # cp /{lib,etc}/systemd/system/systemd-pstore.service # sed -i 's/modprobe@mtdpstore.service //' /etc/systemd/system/systemd-pstore.service # systemctl daemon-reload [Impact] Due to mtdpstore not being properly configured as a pstore backend, when systemd-pstore.service tries to load the module, users get the following error in dmesg: [ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore... [ 18.462685] mtd device must be supplied (device name is empty) This is a distracting error for users trying to diagnose other system issues, especially if their system does not boot after a kernel crash and this is the only message displayed on the console. [Test Plan] * Force a kernel crash to populate /sys/fs/pstore, thus causing systemd-pstore.service to start on the subsequent boot: # echo 1 > /proc/sys/kernel/sysrq # echo 1 > /proc/sys/kernel/panic # echo c > /proc/sysrq-trigger * When the system reboots, observe the error in dmesg: # dmesg | grep mtd [Where problems could occur] If a system was relying on this pstore backend, and mtdpstore is built as a module, it is possible for systemd-pstore.service to trigger before mtdpstore is loaded, causing systemd-pstore to not copy the contents of /sys/fs/pstore. Note however that before the patched introduced as a result of bug 1978079, systemd-pstore.service would not attempt to load *any* kernel modules. [Original Description] After updating my 22.04 system (possibly caused by Systemd update). And now booting, dmesg has two errors: 'mtd device must be supplied (device name is empty)'. See line 8 and 134 in the included logfile. The system are booting as it should though, and the system are working like it should no errors at all. Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in systemd? I have an EFI mounted at boot but it isn't used because I have installed my system in legacy BIOS mode. Is this maybe the culprit? I could ignore the message but it isn't nice though. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1990081] [NEW] Computer continually sends audio to bluetooth headphones
Public bug reported: Pipewire/BlueZ is constantly sending audio data to Bluetooth headphones even when no audio is playing. This causes three problems: 1. Prevents any other device sending audio to the headphones when Bluetooth multipoint connection is use. 2. Additional battery drain on a laptop due to unnecessary Bluetooth traffic. 3. Additional battery drain on the headphones for the same reason. The first problem is the primary reason for creating this bug report, it can prevent the headphones from being used with two devices simultaneously (e.g. computer and mobile phone) when only one device plays audio at any one time (a so-called 'multipoint connection'). The issue can be easily diagnosed by running 'sudo btmon' and noticing that very similar packets are continually being transmitted, even when no audio is being played, likely representing silence encoded as Bluetooth A2DP packets. When audio is played via the computer, these packets look like encoded data (the audio encoded as Bluetooth A2DP packets). Sometimes this does not cause an issue, it all depends on what connection the headphones deem as the primary connection, if the computer is deemed the priority then the silence being continually transmitted prevents audio from the other connected device being heard. If the other connected device is deemed the priority then its audio will be heard instead and the silence from the computer ignored. Note that Android works properly in this aspect: when no audio is playing, it does not continually send audio packets to the headphones allowing the other device to play audio correctly, irrespective of which device is deemed the priority by the headphones. $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 richard@richard-dell:~ $ sudo apt-cache policy bluez bluez: Installed: 5.64-0ubuntu1 Candidate: 5.64-0ubuntu1 Version table: *** 5.64-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status richard@richard-dell:~ $ sudo apt-cache policy pipewire-media-session pipewire-media-session: Installed: 0.4.1.r11.ga870086-2~ubuntu22.04 Candidate: 0.4.1.r11.ga870086-2~ubuntu22.04 Version table: *** 0.4.1.r11.ga870086-2~ubuntu22.04 500 500 https://ppa.launchpadcontent.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 0.4.1-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages richard@richard-dell:~ $ sudo apt-cache policy pipewire-pulse pipewire-pulse: Installed: 0.3.58-1~ubuntu22.04 Candidate: 0.3.58-1~ubuntu22.04 Version table: *** 0.3.58-1~ubuntu22.04 500 500 https://ppa.launchpadcontent.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 0.3.48-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages richard@richard-dell:~ $ sudo apt-cache policy pipewire-audio-client-libraries pipewire-audio-client-libraries: Installed: (none) Candidate: 0.3.58-1~ubuntu22.04 Version table: 0.3.58-1~ubuntu22.04 500 500 https://ppa.launchpadcontent.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main amd64 Packages 500 https://ppa.launchpadcontent.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status 0.3.48-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages $ bluetoothctl info Device 80:C7:55:FB:B1:4E (public) Name: RB-M700B Alias: RB-M700B Class: 0x00240404 Icon: audio-headset Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (---0099-aabbccddeeff) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1990081 Title: Computer continually sends audio to bluetooth headphones Status in bluez package in Ubuntu: New Bug description: Pipewire/BlueZ is constantly sending audio data to Bluetooth headphones even when no audio is playing. This causes three problems: 1. Prevents any other device sending
[Touch-packages] [Bug 1990064] [NEW] unconfined profile denies userns_create for chromium based processes
Public bug reported: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: New Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1989626] Re: UIFe: fonts-noto-color-emoji & other updates for Unicode 15
** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google released their updated fonts-noto-color-emoji Friday. We also need to update glib so that new non-emoji Unicode characters are handled correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. UI affecting packages fonts-noto-color-emoji glib2.0 Other packages needed but don't affect UI - - node-unicode-data utf8proc + node-unicode-property-aliases + node-unicode-property-aliases-ecmascript + node-unicode-property-value-aliases + node-unicode-property-value-aliases-ecmascript + node-unicode-data which will start a small transition + node-esutils + node-json5 + node-regenerate-unicode-properties + node-regexpu-core + node-regjsparser maybe more universe packages Declined changes harfbuzz - doesn't appear to be a critical need and our kinetic version is too old. harfbuzz will be updated for Ubuntu 23.04 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1989626 Title: UIFe: fonts-noto-color-emoji & other updates for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Triaged Bug description: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google released their updated fonts-noto-color-emoji Friday. We also need to update glib so that new non-emoji Unicode characters are handled correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. UI affecting packages fonts-noto-color-emoji glib2.0 Other packages needed but don't affect UI - utf8proc node-unicode-property-aliases node-unicode-property-aliases-ecmascript node-unicode-property-value-aliases node-unicode-property-value-aliases-ecmascript node-unicode-data which will start a small transition node-esutils node-json5 node-regenerate-unicode-properties node-regexpu-core node-regjsparser maybe more universe packages Declined changes harfbuzz - doesn't appear to be a critical need and our kinetic version is too old. harfbuzz will be updated for Ubuntu 23.04 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List:
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Unfortunately the steps in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/89 aren't working for me (I'm a professional developer, am confident i've followed the steps properly, have tried three times) Does anyone else have any other workarounds? -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code:
[Touch-packages] [Bug 1990056] Re: Logrotate fails on never installed tomcat (catalina) log rotate
To add, when run manually (restart) runs just fine. Logrotates and logrotates. fyi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1990056 Title: Logrotate fails on never installed tomcat (catalina) log rotate Status in logrotate package in Ubuntu: New Bug description: Hi, I get error: error: error opening /var/log/tomcat9/catalina.out: Permission denied logrotate.service: Main process exited, code=exited, status=1/FAILURE logrotate.service: Failed with result 'exit-code'. Logrotate fails on tomcat(catalina) log rotate. I have never had tomcat installed in this machine. System: Description:Ubuntu 22.04.1 LTS Release:22.04 logrotate: Installed: 3.19.0-1ubuntu1.1 Candidate: 3.19.0-1ubuntu1.1 Version table: *** 3.19.0-1ubuntu1.1 500 500 http://fi.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 3.19.0-1ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu jammy/main amd64 Packages SH ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: logrotate 3.19.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 18 12:07:15 2022 InstallationDate: Installed on 2021-09-28 (354 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: logrotate UpgradeStatus: Upgraded to jammy on 2022-04-22 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1990056/+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 1990056] [NEW] Logrotate fails on never installed tomcat (catalina) log rotate
Public bug reported: Hi, I get error: error: error opening /var/log/tomcat9/catalina.out: Permission denied logrotate.service: Main process exited, code=exited, status=1/FAILURE logrotate.service: Failed with result 'exit-code'. Logrotate fails on tomcat(catalina) log rotate. I have never had tomcat installed in this machine. System: Description:Ubuntu 22.04.1 LTS Release:22.04 logrotate: Installed: 3.19.0-1ubuntu1.1 Candidate: 3.19.0-1ubuntu1.1 Version table: *** 3.19.0-1ubuntu1.1 500 500 http://fi.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 3.19.0-1ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu jammy/main amd64 Packages SH ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: logrotate 3.19.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 18 12:07:15 2022 InstallationDate: Installed on 2021-09-28 (354 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: logrotate UpgradeStatus: Upgraded to jammy on 2022-04-22 (148 days ago) ** Affects: logrotate (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 logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1990056 Title: Logrotate fails on never installed tomcat (catalina) log rotate Status in logrotate package in Ubuntu: New Bug description: Hi, I get error: error: error opening /var/log/tomcat9/catalina.out: Permission denied logrotate.service: Main process exited, code=exited, status=1/FAILURE logrotate.service: Failed with result 'exit-code'. Logrotate fails on tomcat(catalina) log rotate. I have never had tomcat installed in this machine. System: Description:Ubuntu 22.04.1 LTS Release:22.04 logrotate: Installed: 3.19.0-1ubuntu1.1 Candidate: 3.19.0-1ubuntu1.1 Version table: *** 3.19.0-1ubuntu1.1 500 500 http://fi.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 3.19.0-1ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu jammy/main amd64 Packages SH ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: logrotate 3.19.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 18 12:07:15 2022 InstallationDate: Installed on 2021-09-28 (354 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: logrotate UpgradeStatus: Upgraded to jammy on 2022-04-22 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1990056/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
$ journalctl --disk-usage Archived and active journals take up 624.0M in the file system. -- 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/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GU_G731GU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
https://bugs.launchpad.net/ubuntu/+source/module-init-tools/+bug/240553 $ sudo rmmod evbug [sudo] password for hannu: $ -- 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/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GU_G731GU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
Same here, recent upgrade message appears. -- 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/1981622 Title: mtd device must be supplied (device name is empty) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Jammy: Fix Committed Bug description: [WORKAROUND] This will NOT fix a system that is not booting, because the "mtd device must be supplied (device name is empty)" message is not the cause of failed boots. This work around is only for those who are annoyed by the error message, but are otherwise not experiencing any issues. If you are not able to boot your system, but you see this error message, please open a separate bug with your journalctl and dmesg logs. # cp /{lib,etc}/systemd/system/systemd-pstore.service # sed -i 's/modprobe@mtdpstore.service //' /etc/systemd/system/systemd-pstore.service # systemctl daemon-reload [Impact] Due to mtdpstore not being properly configured as a pstore backend, when systemd-pstore.service tries to load the module, users get the following error in dmesg: [ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore... [ 18.462685] mtd device must be supplied (device name is empty) This is a distracting error for users trying to diagnose other system issues, especially if their system does not boot after a kernel crash and this is the only message displayed on the console. [Test Plan] * Force a kernel crash to populate /sys/fs/pstore, thus causing systemd-pstore.service to start on the subsequent boot: # echo 1 > /proc/sys/kernel/sysrq # echo 1 > /proc/sys/kernel/panic # echo c > /proc/sysrq-trigger * When the system reboots, observe the error in dmesg: # dmesg | grep mtd [Where problems could occur] If a system was relying on this pstore backend, and mtdpstore is built as a module, it is possible for systemd-pstore.service to trigger before mtdpstore is loaded, causing systemd-pstore to not copy the contents of /sys/fs/pstore. Note however that before the patched introduced as a result of bug 1978079, systemd-pstore.service would not attempt to load *any* kernel modules. [Original Description] After updating my 22.04 system (possibly caused by Systemd update). And now booting, dmesg has two errors: 'mtd device must be supplied (device name is empty)'. See line 8 and 134 in the included logfile. The system are booting as it should though, and the system are working like it should no errors at all. Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in systemd? I have an EFI mounted at boot but it isn't used because I have installed my system in legacy BIOS mode. Is this maybe the culprit? I could ignore the message but it isn't nice though. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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