[Touch-packages] [Bug 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)
** Also affects: sudo (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1958055 Title: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP) Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Jammy: New Bug description: Running ubuntu-bug as normal user has the correct theme (see screenshots attached to bug #1881640), but running "sudo ubuntu-bug" has a different, non-matching theme (see attached screenshot). This problem can be reproduce by running a KDE application on Ubuntu Desktop (GNOME): 1. Launch ubuntu-22.04-desktop-amd64.iso 2. Install apport-kde 3. Run: /usr/share/apport/apport-kde -f 4. Run: sudo /usr/share/apport/apport-kde -f 5. Compare both windows. They have different icons and font size. Same result with KDE: 1. Use kubuntu-22.04-desktop-amd64.iso 2. Run ubuntu-bug -f 3. Run: sudo ubuntu-bug -f [Analysis] Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme, but XDG_CURRENT_DESKTOP is not in the list of environment variables to preserve (and not in env_keep in /etc/sudoers). On other other hand, sudo preserves the DISPLAY environment variable: $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)' XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 MAIL=/var/mail/root LOGNAME=root USER=root HOME=/root SHELL=/bin/bash [Workaround] Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:04:24 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1958055/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
** Changed in: cyrus-sasl2 (Ubuntu Impish) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Won't Fix Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 source package in Impish: Won't Fix Status in cyrus-sasl2 source package in Jammy: Triaged Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1981672] Re: apt phased out broken code, missing documentation to opt out
** Changed in: apt (Ubuntu) Status: In Progress => Incomplete -- 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/1981672 Title: apt phased out broken code, missing documentation to opt out Status in apt package in Ubuntu: Incomplete Bug description: Having the configuration at https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24 it fails to work. The phased updates get distributed on some hosts anyways for 22.04. Please properly document and test this, and provide a working configuration to opt out from phased updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1983473] Re: update-initramfs -u fails: cannot create directory '/var/tmp/mkinitramfs_38kRbm/cryptroot': File exists
...and I found the culprit: My fiddling around left a file name /usr/share/initramfs-tools/hooks/cryptroot.orig which was executed by update-initramfs too. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1983473 Title: update-initramfs -u fails: cannot create directory '/var/tmp/mkinitramfs_38kRbm/cryptroot': File exists Status in initramfs-tools package in Ubuntu: Invalid Bug description: This is a fresh Ubuntu 22.04 installation in a VM used for debugging bug #1979159. I had modified some files, but checked with "sudo debsums -ac" that I reverted all local changes. The failure still happens after the reboot. $ LANG=C sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic mkdir: cannot create directory '/var/tmp/mkinitramfs_38kRbm/cryptroot': File exists E: /usr/share/initramfs-tools/hooks/cryptroot.orig failed with return 1. update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: cryptsetup-initramfs:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Aug 3 14:08:39 2022 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2022-05-20 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983473/+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 1983473] [NEW] update-initramfs -u fails: cannot create directory '/var/tmp/mkinitramfs_38kRbm/cryptroot': File exists
Public bug reported: This is a fresh Ubuntu 22.04 installation in a VM used for debugging bug #1979159. I had modified some files, but checked with "sudo debsums -ac" that I reverted all local changes. The failure still happens after the reboot. $ LANG=C sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic mkdir: cannot create directory '/var/tmp/mkinitramfs_38kRbm/cryptroot': File exists E: /usr/share/initramfs-tools/hooks/cryptroot.orig failed with return 1. update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: cryptsetup-initramfs:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Aug 3 14:08:39 2022 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2022-05-20 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-package jammy ** Summary changed: - package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück + initramfs-tools 0.140ubuntu13 failed to install/upgrade: update-initramfs fails: cannot create directory '/var/tmp/mkinitramfs_38kRbm/cryptroot': File exists ** Summary changed: - initramfs-tools 0.140ubuntu13 failed to install/upgrade: update-initramfs fails: cannot create directory '/var/tmp/mkinitramfs_38kRbm/cryptroot': File exists + update-initramfs -u fails: cannot create directory '/var/tmp/mkinitramfs_38kRbm/cryptroot': File exists -- 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/1983473 Title: update-initramfs -u fails: cannot create directory '/var/tmp/mkinitramfs_38kRbm/cryptroot': File exists Status in initramfs-tools package in Ubuntu: Invalid Bug description: This is a fresh Ubuntu 22.04 installation in a VM used for debugging bug #1979159. I had modified some files, but checked with "sudo debsums -ac" that I reverted all local changes. The failure still happens after the reboot. $ LANG=C sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic mkdir: cannot create directory '/var/tmp/mkinitramfs_38kRbm/cryptroot': File exists E: /usr/share/initramfs-tools/hooks/cryptroot.orig failed with return 1. update-initramfs: failed for /boot/initrd.img-5.15.0-43-generic with 1. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: cryptsetup-initramfs:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Aug 3 14:08:39 2022 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2022-05-20 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983473/+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 1981672] Re: apt phased out broken code, missing documentation to opt out
I recall/see again a mention of aptitude: aptitude and aptitude-robot are not supported components. They are packages provided by the community as part of the universe repository. While the implementation of phased updates in apt versions prior to 2.4.6 would work there, the current version does not. Implementing phased updates in aptitude for the current algorithm is out of scope, as aptitude does not use the apt resolver where the keep-back is implemented, and a generic API to handle phasing is not yet exposed in apt. Switching to the policy based pinning as documented before should make aptitude respect pinning more, however, aptitude is not a reliable tool that respects your choices like that (its solver will happily suggest solutions violating your wishes; it also generally is too happy to remove packages), so you do not want to use it in an automated setting. ** Also affects: aptitude (Ubuntu) Importance: Undecided Status: New ** Changed in: aptitude (Ubuntu) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu) Status: Incomplete => Triaged ** Changed in: aptitude (Ubuntu) Status: New => Triaged ** Summary changed: - apt phased out broken code, missing documentation to opt out + phased updates API and client for aptitude -- 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/1981672 Title: phased updates API and client for aptitude Status in apt package in Ubuntu: Triaged Status in aptitude package in Ubuntu: Triaged Bug description: Having the configuration at https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24 it fails to work. The phased updates get distributed on some hosts anyways for 22.04. Please properly document and test this, and provide a working configuration to opt out from phased updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1981672] Re: phased updates API and client for aptitude
I have added an aptitude task and set the tasks accordingly to indicate that this is a feature request for aptitude. The needed API will surface at some point in APT due to some refactoring, likely in the 23.04 cycle. aptitude could then consume that API in its resolver and make choices to keep back phased upgrades, however, that is up to the aptitude maintainers upstream. Do note that aptitude is mostly unmaintained these days. Alternatively, aptitude can also enable the policy based variant as that likely works for its solver. That could be SRUed into jammy if somebody wants to provide a patch for that, do the SRU paperwork, and get it sponsored and then work on getting it released. Do note that this option is experimental and may disappear in a future release as we finalize the correct approach. -- 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/1981672 Title: phased updates API and client for aptitude Status in apt package in Ubuntu: Triaged Status in aptitude package in Ubuntu: Triaged Bug description: Having the configuration at https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24 it fails to work. The phased updates get distributed on some hosts anyways for 22.04. Please properly document and test this, and provide a working configuration to opt out from phased updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1978068] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert
The relevant log is: zstd: error 25 : Write error : No space left on device (cannot write compressed block) So you ran out of free space to update your initramfs. ** Summary changed: - package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück + initramfs-tools 0.140ubuntu13 failed to install/upgrade: update-initramfs fails: No space left on device -- 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/1978068 Title: initramfs-tools 0.140ubuntu13 failed to install/upgrade: update- initramfs fails: No space left on device Status in initramfs-tools package in Ubuntu: New Bug description: The error appeared right after login and was caught by the Ubuntu error reporting tool. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: ntfs-3g:amd64: Install libntfs-3g89:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jun 9 09:33:58 2022 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2022-01-17 (142 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all 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.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to jammy on 2022-05-03 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1978068/+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 1981672] Re: apt phased out broken code, missing documentation to opt out
It's documented in the discourse thread (Discourse is where Ubuntu documentation lives) You have not provided evidence that it does not work for you. APT itself has test cases that proof that *it does* work. Note that newer apt versions (2.4.6, 2.5.1) will install more phased updates - as phasing only applies to upgrades, not to new installs, so if you `apt install phased`, you'll get the phased version, regardless of your setting, - or if there is a phased=1 security update and a phased=2 update, you'll get phased=2 even if it's phasing at 0. You can restore previous behavior by setting APT::Get::Phase-Policy to true; but note that this can cause the `apt install` command to fail to install packages, see bug 1979244 for more details. All other phased updates should show as being kept back in the upgrade output. If you want to move this further you'll have to provide one of the following: - A reproducer - A log that shows a phased update being installed that should not be, including the command that installed the update and any debug output Either must be accompanied by a tarball containing: - /etc/apt - /var/lib/dpkg/status - /var/lib/apt You also want to check yourself that - `apt-config dump` shows `APT::Get::Never-Include-Phased-Updates "false";` - `apt-config dump` shows no entry, or a negative one, for `APT::Get::Always-Include-Phased-Updates` If you use update-manager it's not entirely clear how this interacts with the new phasing code in 2.4.6, so you might also/instead have to set `Update-Manager::Never-Include-Phased-Updates "false";` As documented in the discourse post. -- 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/1981672 Title: apt phased out broken code, missing documentation to opt out Status in apt package in Ubuntu: Incomplete Bug description: Having the configuration at https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24 it fails to work. The phased updates get distributed on some hosts anyways for 22.04. Please properly document and test this, and provide a working configuration to opt out from phased updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1981672] Re: phased updates API and client for aptitude
To make it clear, my suggestion for a workaround for jammy would be to
have
_config->CndSet("APT::Get::Phase-Policy", true);
somewhere in the aptitude code. It is unclear to me if aptitude will
break then as phased versions get their pin limited to 1, apt certainly
does if there's a mismatch as in bug 1979244
Anyone doing the SRU will have to analyse that regression potential.
--
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/1981672
Title:
phased updates API and client for aptitude
Status in apt package in Ubuntu:
Triaged
Status in aptitude package in Ubuntu:
Triaged
Bug description:
Having the configuration at
https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
it fails to work.
The phased updates get distributed on some hosts anyways for 22.04.
Please properly document and test this, and provide a working
configuration to opt out from phased updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1910768] Re: apport-collect hangs and makes computer hang
@Tomislav, can you report a separate bug? My gut feeling is that you experienced a different issue (with similar symptoms). @Peter, sadly the stack trace posted only contains threading.py and nothing from apport itself. So I have not enough information to fix this bug without a test case. Can you reproduce the issue and can come up with a test case? ** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1910768 Title: apport-collect hangs and makes computer hang Status in apport package in Ubuntu: Incomplete Bug description: This bug is related to bug 1723558 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1723558) but I could not transfer the generated information. After a crash of bluetoothd (see bug 1910405) I tried to run apport- collect with the bug ID, but the process hangs. After clicking cancel, it makes the computer hang totally, except running teams calls that keep streaming but without interaction possible. All is released when apport is killed manually. The problem also occurs when a crash of the Brave browser causes a call to apport. This bug is generated through ubuntu-bug -w after clicking on the apport-collect window. This second apport process doesn't hang. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.9-0ubuntu7.21 ProcVersionSignature: Ubuntu 5.4.0-58.64~18.04.1-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:29:04 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2019-11-22 (412 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768/+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 1977647] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1977647 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I didn't perform any action to get this crash. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.15.0-33.34-lowlatency 5.15.30 Uname: Linux 5.15.0-33-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marqrdt 676730 F pulseaudio /dev/snd/controlC0: marqrdt 676730 F pulseaudio /dev/snd/controlC1: marqrdt 676730 F pulseaudio CasperMD5CheckResult: pass Date: Tue May 31 11:25:55 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-07-09 (330 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-lowlatency root=/dev/mapper/vgubuntu-root ro threadirqs quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2 RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago) dmi.bios.date: 06/13/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/13/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977647/+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
Re: [Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude
Hi Julian, Julian Andres Klode wrote: > Do note that aptitude is mostly unmaintained these days. I have to object here as well: There's no development currently, but it is _not_ unmaintained. (And the current RC bug in Debian will soon be addressed. I'm just back from holidays.) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- 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/1981672 Title: phased updates API and client for aptitude Status in apt package in Ubuntu: Triaged Status in aptitude package in Ubuntu: Triaged Bug description: Having the configuration at https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24 it fails to work. The phased updates get distributed on some hosts anyways for 22.04. Please properly document and test this, and provide a working configuration to opt out from phased updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1981672] Re: apt phased out broken code, missing documentation to opt out
it appears phased upates are everywhere and not just with proposed repos... so although the bug might be against the wrong package filed (feel free to reassign to somewhere else). there's a bug lacking information how to properly opt out of phased updates. which is pointless to take part of if the automatic bug reporting is disabled/removed. ** Changed in: apt (Ubuntu) Status: Invalid => In Progress -- 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/1981672 Title: apt phased out broken code, missing documentation to opt out Status in apt package in Ubuntu: In Progress Bug description: Having the configuration at https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24 it fails to work. The phased updates get distributed on some hosts anyways for 22.04. Please properly document and test this, and provide a working configuration to opt out from phased updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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
Re: [Touch-packages] [Bug 1981672] Re: apt phased out broken code, missing documentation to opt out
Hi Julian, Julian Andres Klode wrote: > aptitude is not a reliable tool that respects your choices like that > (its solver will happily suggest solutions violating your wishes; it I have to object here. It very well respects the user's wishes and also has a setting where the user can configure it should propose solutions violating holds and forbids. > also generally is too happy to remove packages), Again, this solely depends on your settings. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- 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/1981672 Title: phased updates API and client for aptitude Status in apt package in Ubuntu: Triaged Status in aptitude package in Ubuntu: Triaged Bug description: Having the configuration at https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24 it fails to work. The phased updates get distributed on some hosts anyways for 22.04. Please properly document and test this, and provide a working configuration to opt out from phased updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1703821] Re: Dovecot and Apparmor complains at operation file_inherit
What's the user impact here please? Just noisy logs, or are users impacted in a more meaningful way? The downside here is that a rebuild of apparmor is going to result in virtually every Ubuntu Bionic user having to download and install an update. The vast majority of whom aren't using dovecot, or even those that are don't have this profile enforcing, AIUI. And this is for Bionic which was released over four years ago, with only one person reporting themselves as affected in that time. Is this really worth an SRU? At a minimum, I'd like a proper explanation of user impact please, and then we can reconsider. ** Changed in: apparmor (Ubuntu Bionic) 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/1703821 Title: Dovecot and Apparmor complains at operation file_inherit Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Expired Status in dovecot package in Ubuntu: Fix Released Status in apparmor source package in Bionic: Incomplete Status in dovecot source package in Bionic: Fix Released Bug description: [Impact] Users report that while running dovecot there are some issues reported by AppArmor, specifically regarding "file_inherit" operations: Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400 audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit" profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/sbin/dovecot" Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400 audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit" profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/anvil" This is likely caused by an anonymous socket communication channel between dovecot and anvil. A fix in the dovecot AppArmor policy was already merged upstream in commit 1ce8cd21, which is being backported in this SRU. There was a change upstream that renamed the dovecot profile, so it was necessary to make a small change on the backport to reference the correct profile name. [Test Plan] Clone the qa-regression-testing repo https://git.launchpad.net/qa-regression-testing Setup the machine according to the instructions in the README.multipurpose-vm - specifically the Email section. Run the dovecot tests from the qa-regression-testing repo: python3 ./script test-dovecot.py After running the tests, check dmesg for no DENIED messages: dmesg | grep DENIED [Where problems could occur] This update broadens the dovecot policy, so it won't to cause any issues regarding a behavior that was previously allowed and it is now denied. In addition, the dovecot policy is already in complain mode in bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1703821/+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 1983414] Re: [BPO] dh-python 5.20220403 to focal
** Also affects: dh-python (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: dh-python (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1983414 Title: [BPO] dh-python 5.20220403 to focal Status in dh-python package in Ubuntu: Fix Released Status in dh-python source package in Focal: New Bug description: [Impact] * This is needed to refresh the yt-dlp package as it has support for 'environment markers' * This version could also be useful for other projects as it adds support for pyproject. [Scope] Backport from: * To me it makes sense to backport from jammy (LTS), though the version currently is the same as devel. Backport to: * focal [Other Info] * I have created a test backport in ppa:unit193/staging and have already utilized. [Testing] * focal: [x] Package builds without modification [x] dh-python installs cleanly and runs [?] pybuild-plugin-pyproject installs cleanly and runs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1983414/+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 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
I did some testing to confirm this is present in jammy (the offending code is also in kinetic). I will test the upstream fix soon. ** Tags added: rls-jj-incoming rls-kk-incoming -- 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/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu 22.04 - Linux 5.15.0-40-generic - systemd 249.11-0ubuntu3.3 - util-linux 2.37.2-4ubuntu3 This appears on both Ubuntu 22.04 machines that I have (a hardware machine and a VM). To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1979952/+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 1703821] Re: Dovecot and Apparmor complains at operation file_inherit
Please also fix the bug status for the Ubuntu development release apparmor package task. -- 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/1703821 Title: Dovecot and Apparmor complains at operation file_inherit Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Expired Status in dovecot package in Ubuntu: Fix Released Status in apparmor source package in Bionic: Incomplete Status in dovecot source package in Bionic: Fix Released Bug description: [Impact] Users report that while running dovecot there are some issues reported by AppArmor, specifically regarding "file_inherit" operations: Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400 audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit" profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/sbin/dovecot" Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400 audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit" profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/anvil" This is likely caused by an anonymous socket communication channel between dovecot and anvil. A fix in the dovecot AppArmor policy was already merged upstream in commit 1ce8cd21, which is being backported in this SRU. There was a change upstream that renamed the dovecot profile, so it was necessary to make a small change on the backport to reference the correct profile name. [Test Plan] Clone the qa-regression-testing repo https://git.launchpad.net/qa-regression-testing Setup the machine according to the instructions in the README.multipurpose-vm - specifically the Email section. Run the dovecot tests from the qa-regression-testing repo: python3 ./script test-dovecot.py After running the tests, check dmesg for no DENIED messages: dmesg | grep DENIED [Where problems could occur] This update broadens the dovecot policy, so it won't to cause any issues regarding a behavior that was previously allowed and it is now denied. In addition, the dovecot policy is already in complain mode in bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1703821/+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 1703821] Re: Dovecot and Apparmor complains at operation file_inherit
Bug 1979879 is similar to this, except for samba in Jammy. In both cases, a workaround is trivially available since a user can safely modify the profile directly in /etc. -- 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/1703821 Title: Dovecot and Apparmor complains at operation file_inherit Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Expired Status in dovecot package in Ubuntu: Fix Released Status in apparmor source package in Bionic: Incomplete Status in dovecot source package in Bionic: Fix Released Bug description: [Impact] Users report that while running dovecot there are some issues reported by AppArmor, specifically regarding "file_inherit" operations: Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400 audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit" profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/sbin/dovecot" Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400 audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit" profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/anvil" This is likely caused by an anonymous socket communication channel between dovecot and anvil. A fix in the dovecot AppArmor policy was already merged upstream in commit 1ce8cd21, which is being backported in this SRU. There was a change upstream that renamed the dovecot profile, so it was necessary to make a small change on the backport to reference the correct profile name. [Test Plan] Clone the qa-regression-testing repo https://git.launchpad.net/qa-regression-testing Setup the machine according to the instructions in the README.multipurpose-vm - specifically the Email section. Run the dovecot tests from the qa-regression-testing repo: python3 ./script test-dovecot.py After running the tests, check dmesg for no DENIED messages: dmesg | grep DENIED [Where problems could occur] This update broadens the dovecot policy, so it won't to cause any issues regarding a behavior that was previously allowed and it is now denied. In addition, the dovecot policy is already in complain mode in bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1703821/+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 1979879] Re: Apparmor profile in 22.04 jammy - fails to start when printing enabled
>From an SRU perspective bug 1703821 is similar to this, except for dovecot in Bionic. In both cases, a workaround is trivially available since a user can safely modify the profile directly in /etc. -- 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/1979879 Title: Apparmor profile in 22.04 jammy - fails to start when printing enabled Status in apparmor package in Ubuntu: Invalid Status in samba package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Triaged Status in samba source package in Jammy: Triaged Bug description: See bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1191532 Fix was backported, but the path to samba-bgqd is wrong on 22.04. Currently apparmor profile has it like this: /usr/lib*/samba/samba-bgqd When in fact 22.04 has it on /usr/lib/x86_64-linux-gnu/samba/samba- bgqd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1979879/+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 1900098] Re: software-properties-gtk fails to open with error
I tried reinstalling all the packages, even the python ones and nothing worked. So I read the code in /lib/python3/dist- packages/softwareproperties/gtk/SoftwarePropertiesGtk.py and commenting out line 222 everything worked again!!! self.backend.Reload(); --> # self.backend.Reload(); -- 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/1900098 Title: software-properties-gtk fails to open with error Status in software-properties package in Ubuntu: Expired Bug description: When trying to open software-properties-gtk via Terminal (via GUI: “Settings & Livepatch”) the following error is returned in the terminal and software-properties-gtk does not open. ERROR:dbus.proxies:Introspect error on :1.121:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying 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 211, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.121 was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 08:17:15 2020 InstallationDate: Installed on 2020-10-09 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all 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/1900098/+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 1980210] Re: [SRU] Unable download from store.kde.org with error "invalid number of concurrent streams"
** Changed in: qtbase-opensource-src (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1980210 Title: [SRU] Unable download from store.kde.org with error "invalid number of concurrent streams" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Jammy: Fix Released Bug description: Version: 5.15.3+dfsg-2 Release: Jammy 22.04 In KDE systemsettings or Discover, trying to download new plasma themes or similar assets from store.kde.org results in an error dialogue stating "invalid number of concurrent streams". KDE Bug: https://bugs.kde.org/show_bug.cgi?id=455540 Fixed in KDE Qt patch collection with: https://invent.kde.org/qt/qt/qtbase/-/commit/ec68c541a72bde122a1ab5ba89f41b58c370537f Fixed in Kinetic with: https://launchpad.net/ubuntu/+source/qtbase- opensource-src/5.15.4+dfsg-3ubuntu1 Also fixed in Debian experimental as part on the planned Qt 5.15.5 transition: https://metadata.ftp- master.debian.org/changelogs//main/q/qtbase-opensource-src/qtbase- opensource-src_5.15.5+dfsg-2_changelog The update has also been shipped to our updates and backports PPA, and confirmed to be working by users. [Impact] * Users are unable to download new assets from store.kde.org. This is an important feature for users to be able to easily and safely customise their systems. [Test Plan] * Confirm that you can reproduce the bug with the unpatched Qtbase in the main archive. * Apply the update and test. * Confirm that assets now download without error. * Check a selection of other Qt based applications that access the internet to confirm as mush as is practical that there are not adverse consequences to the update. [Where problems could occur] * We are changing somewhat how Qt responds to these http requests, so some testing of other Qt based applications is desirable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1980210/+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 1966984] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
*** This bug is a duplicate of bug 1969460 *** https://bugs.launchpad.net/bugs/1969460 ** This bug is no longer a duplicate of bug 1968661 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings ** This bug has been marked a duplicate of bug 1969460 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings -- 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/1966984 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in software-properties package in Ubuntu: New Bug description: میخواستم مثل همیشه درایور نصب نشده وای فای برودکم 802.11 رو نصب کنم نمیدونم چرا تو این نسخه از ابونتو این مشکل هست که نمیشه درایور برودکم رو دانلود و نصبش کنم ولی تو نسخه های قبل این مشکل نبود تا تیک گزینه نصب رو میزنم ارور میدهدانلود نمیکنه من واقعا این نسخه ابونتو رو دوست دارم و به دوستانممم توصیه میکنم اما متسفانه بعد از نصب درایور های اینترنت وای فای و بلوتوث برودکم رو نصب نمیکنه من با اینترنت همراه با کمک کابل یو اس بی هستم الان و مشکل اینترنتی ندارم با تشکر ممنون از تیم خوبتون ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.21 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 21:20:41 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1422, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1966984/+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 1968661] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
*** This bug is a duplicate of bug 1969460 *** https://bugs.launchpad.net/bugs/1969460 ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1969460 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings -- 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/1968661 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in software-properties package in Ubuntu: Confirmed Bug description: Software & Updates > Additional Drivers > Realtek Semiconductor Co., Ltd:RTL8821CE 802.11ac PCIe Wireless Network Adapter When I select Do not use the device to Using DKMS source for the Realtek ... this error happens. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 09:35:48 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-29 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1422, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968661/+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 1843829] Re: sudoers: admin group has permissions, but does not exist by default
** Changed in: sudo (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1843829 Title: sudoers: admin group has permissions, but does not exist by default Status in sudo package in Ubuntu: Triaged Bug description: Hello I had reported this earlier but my account shows no bugs reported so here I try again. On Ubuntu going back for a while now and also including the newest release /etc/sudoers contains the below lines on a default install %admin ALL=(ALL) ALL The problem is that the admin group doesn't exist by default so if a user with the name of admin was created they would be in a group of their own name. It looks like you guys might be using an account named adm instead of admin? This is also causing other bugs to be reported. It may seem silly as adding a user requires elevated permissions. If someone doesn't know about this behaviour or a user is allowed to create an admin named account through a script they are just a short sudo su away from controlling a system. I'd recommend commenting out the /etc/sudoers line or adding an admin group to /etc/group or changing the admin in sudoers to adm if that is what you are trying to do. Aaron Ringo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1843829/+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 1983481] Re: Can't report totem crash with ubuntu-bug
** Package changed: totem (Ubuntu) => apport (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1983481
Title:
Can't report totem crash with ubuntu-bug
Status in apport package in Ubuntu:
New
Bug description:
When totem crashes and I try to report the crash with ubuntu-bug, one
of two things happens:
1) Sometimes after the dialog pops up and I click the "Send" button,
ubuntu-bug immediately exits without doing anything:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
jik@jik5:~$
2) Sometimes I get a stack trace before it exits:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
jik@jik5:~$
Either way, my browser doesn't open to launchpad as it should after
ubuntu-bug posts a report.
This makes it difficult, to say the least, to report a totem crash
properly.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem-common 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 3 10:35:28 2022
InstallationDate: Installed on 2019-01-02 (1308 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
LogAlsaMixer:
Simple mixer control 'Line',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [15.00dB] [on]
PackageArchitecture: all
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1983481/+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 1983529] [NEW] No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4)
You have been subscribed to a public bug: Not sure if it's relevant, but there are some errors in dmesg: $ sudo dmesg | grep audio [ 14.290226] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 14.440430] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 14.445129] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 14.445811] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 14.445861] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 14.448966] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 15.467232] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 15.467478] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 15.467479] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 15.467484] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 15.478062] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.478066] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.478068] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.478073] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 15.584074] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.584079] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.584080] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.591457] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.591461] sof-audio-pci-intel-tgl :00:1f.3: warn: topology ABI is more recent than kernel [ 15.624250] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [ 15.643720] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 15.643726] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 15.643727] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 15.643728] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [ 15.643729] snd_hda_codec_realtek ehdaudio0D0:inputs: [ 15.643730] snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 Because of those ABI warnings, I tried building the latest mainline kernel from source, and the ABI warnings went away, but I still have no sound. $ sudo dmesg | grep audio # On latest upstream kernel [ 17.519958] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 17.804900] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 17.805661] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 17.806225] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 17.806265] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 17.808071] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 21.844005] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 21.844263] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 21.844264] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 21.844267] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 21.853970] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.853971] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.853979] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 21.961252] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.961255] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.967719] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.979145] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 21.979147] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 21.979148] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 21.979149] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [ 21.979150] snd_hda_codec_realtek ehdaudio0D0:inputs: [ 21.979151] snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 Please let me know if any further information might be helpful. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset
[Touch-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
This message doesn't seem to affect anything, from what I can tell.
Here's a technical analysis.
The system call, sched_setattr, is being made in glib's
g_system_thread_get_scheduler_settings. It gets the current scheduling
settings, and then tests to make sure it can set them on the same
thread. This call is performed when the thread pool is being created,
so that the initial scheduler settings can be recorded and applied to
future threads. (If that's not possible, then glib has a different
mechanism that it will use instead.)
In the Linux kernel, __sched_setscheduler (which does the work for
sched_setattr) tests to see if the user is trying to do anything that
requires the SYS_NICE capability. There are several tests it runs, all
wrapped together:
/* Simplified version of the relevant kernel code */
if (!capable(CAP_SYS_NICE)) {
if (new_nice < old_nice)
return -EPERM;
if (is_rt_policy(new_policy)) {
if (new_policy != old_policy)
return -EPERM;
if (new_priority > old_priority && new_priority > rlim_rtprio)
return -EPERM;
}
if (is_dl_policy(new_policy))
return -EPERM;
/* and so on */
}
All these are guarded by one check to see if the process is allowed to
make changes that require CAP_SYS_NICE. This capability check is
performed regardless of whether the app actually is trying to do
something that requires CAP_SYS_NICE. (In this case, it's not trying
to, but the check is made regardless.)
Ok, now we've outlined the components, so I'll paint the bigger picture.
glib is testing to see if it can save and restore the scheduling
parameters, albeit with no changes. The kernel checks to see if the
process has the SYS_NICE capability. apparmor sees that the program
doesn't have that capability, denies it, and logs an audit message. But
the kernel continues, and determines that the program isn't trying to do
anything that needs SYS_NICE after all. The kernel tells glib that
everything is fine, and glib finishes setting up the thread pool.
At no point does anything even attempt to make any actual changes to the
scheduling parameters. cups_browsed doesn't want to renice itself.
It's just that, as part of the startup process, the SYS_NICE capability
is tested, even though it's ultimately not needed.
Personally, I like Jamie's suggestion: mute the message using a "deny"
rule, since it's understood and not causing any ill effects.
If users want to do this before it gets integrated (and I suggest it
gets upstreamed to Debian, where that file is introduced), then create a
file named /etc/apparmor.d/local/usr.sbin.cups-browsed with the contents
"deny capability sys_nice," (including the comma).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1897369
Title:
apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
Status in cups package in Ubuntu:
Confirmed
Bug description:
In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
`/usr/sbin/cups-browsed` to change its nice value.
$ sudo dmesg | grep apparmor
[541870.509461] audit: type=1400 audit(1600898428.089:60):
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed"
pid=62030 comm="cups-browsed" capability=23 capname="sys_nice"
[628298.779668] audit: type=1400 audit(1600984854.115:61):
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed"
pid=66850 comm="cups-browsed" capability=23 capname="sys_nice"
[714667.424963] audit: type=1400 audit(1601071220.527:62):
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed"
pid=76828 comm="cups-browsed" capability=23 capname="sys_nice"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
I lost all sound devices recently using Kubuntu 22.04 and the 5.18 kernel on my Legion 7 16ACHg6. Following this guide restored my devices: https://pipewire-debian.github.io/pipewire-debian/ Note: I installed all of the recommended wireplumber and BT options as well as the pipewire packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1983481] [NEW] Can't report totem crash with ubuntu-bug
You have been subscribed to a public bug:
When totem crashes and I try to report the crash with ubuntu-bug, one of
two things happens:
1) Sometimes after the dialog pops up and I click the "Send" button,
ubuntu-bug immediately exits without doing anything:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
jik@jik5:~$
2) Sometimes I get a stack trace before it exits:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
jik@jik5:~$
Either way, my browser doesn't open to launchpad as it should after
ubuntu-bug posts a report.
This makes it difficult, to say the least, to report a totem crash
properly.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem-common 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 3 10:35:28 2022
InstallationDate: Installed on 2019-01-02 (1308 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
LogAlsaMixer:
Simple mixer control 'Line',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 15 [100%] [15.00dB] [on]
PackageArchitecture: all
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
--
Can't report totem crash with ubuntu-bug
https://bugs.launchpad.net/bugs/1983481
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to apport in Ubuntu.
--
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 1966640] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
*** This bug is a duplicate of bug 1969460 *** https://bugs.launchpad.net/bugs/1969460 ** This bug is no longer a duplicate of bug 1968661 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings ** This bug has been marked a duplicate of bug 1969460 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings -- 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/1966640 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in software-properties package in Ubuntu: New Bug description: Changing Options in "additional Drivers" crashed the Program ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 09:33:57 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1418, in on_driver_selection_changed pkg = self.apt_cache[pkg_name] TypeError: Expected a string or a pair of strings UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1966640/+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 1966578] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
*** This bug is a duplicate of bug 1969460 *** https://bugs.launchpad.net/bugs/1969460 ** This bug is no longer a duplicate of bug 1968661 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings ** This bug has been marked a duplicate of bug 1969460 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings -- 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/1966578 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in software-properties package in Ubuntu: New Bug description: Try to install rtl8821ce-dkms ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia rtl8821ce ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 11:01:32 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1422, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1966578/+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 1967327] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
*** This bug is a duplicate of bug 1969460 *** https://bugs.launchpad.net/bugs/1969460 ** This bug is no longer a duplicate of bug 1968661 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings ** This bug has been marked a duplicate of bug 1969460 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings -- 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/1967327 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in software-properties package in Ubuntu: New Bug description: Unable to use Broadcom 802.11 Linux STA wireless driver. When it gets clicked "Using Broadcom 802.11..." an error pop up come out. Have restarted the computer before, unfortunately the problem persist. Ubuntu version used: 22.04 daily build ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 23:05:59 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-31 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1422, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1967327/+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 1966521] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
*** This bug is a duplicate of bug 1969460 *** https://bugs.launchpad.net/bugs/1969460 ** This bug is no longer a duplicate of bug 1968661 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings ** This bug has been marked a duplicate of bug 1969460 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings -- 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/1966521 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in software-properties package in Ubuntu: New Bug description: RTL8821CE802 PCIe Wireless DKMS impossible de sélectionner ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 21:33:15 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1422, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1966521/+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 1966566] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
*** This bug is a duplicate of bug 1969460 *** https://bugs.launchpad.net/bugs/1969460 ** This bug is no longer a duplicate of bug 1968661 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings ** This bug has been marked a duplicate of bug 1969460 software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings -- 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/1966566 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in software-properties package in Ubuntu: New Bug description: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings GPU is GTX 980 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 26 23:21:27 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1422, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1966566/+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 1983529] Re: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4)
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1983529 Title: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4) Status in alsa-driver package in Ubuntu: New Bug description: Not sure if it's relevant, but there are some errors in dmesg: $ sudo dmesg | grep audio [ 14.290226] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 14.440430] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 14.445129] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 14.445811] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 14.445861] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 14.448966] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 15.467232] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 15.467478] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 15.467479] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 15.467484] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 15.478062] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.478066] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.478068] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.478073] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 15.584074] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.584079] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.584080] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.591457] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.591461] sof-audio-pci-intel-tgl :00:1f.3: warn: topology ABI is more recent than kernel [ 15.624250] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [ 15.643720] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 15.643726] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 15.643727] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 15.643728] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [ 15.643729] snd_hda_codec_realtek ehdaudio0D0:inputs: [ 15.643730] snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 Because of those ABI warnings, I tried building the latest mainline kernel from source, and the ABI warnings went away, but I still have no sound. $ sudo dmesg | grep audio # On latest upstream kernel [ 17.519958] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 17.804900] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 17.805661] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 17.806225] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 17.806265] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 17.808071] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 21.844005] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 21.844263] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 21.844264] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 21.844267] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 21.853970] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.853971] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.853979] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 21.961252] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.961255] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.967719] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.979145] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 21.979147] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 21.979148] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 21.979149] snd_hda_codec_realtek ehdaudio0D0:
[Touch-packages] [Bug 1322843] Re: foregrounding a sudo'd vim will sometimes break terminal state
The upstream patch got applied as commit b121da2e21cabd2793fc423d84ceddd919fd6e47 and was released in sudo 1.8.11. Therefore this bug is fixed since Ubuntu 16.04 (xenial). ** Changed in: sudo (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1322843 Title: foregrounding a sudo'd vim will sometimes break terminal state Status in sudo: Unknown Status in sudo package in Ubuntu: Fix Released Bug description: See this bug: http://www.sudo.ws/bugs/show_bug.cgi?id=649 Started on Ubuntu/Trusty since it has a sudo after 1.8.7, (precise has 1.8.3). Steps to reproduce: - take a local machine with a recent sudo (after 1.8.7) - sudo vi - ^Z (control-Z) - fg - repeat ^Z and fg until the fg fails and the screen is partially cleared - now a second fg wil open vim with a broken terminal state: arrow keys will render the escape sequences and other nastiness Fix is provided upstream, but author is currently figuring out why it breaks. Cheers, Walter Doekes OSSO B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1322843/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
As with comment #41, #44, and #45, has the decision been made to fix
grub2's memory issues or just the compression level change that was with
initramfs (as I believe it was a choice made to increase Raspberry Pie
boot times)?
--
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: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test
[Touch-packages] [Bug 491352] Re: Patch for incorrect charset in notification emails
Hi, I tried to check all sudo bugs with attached patches. Sadly the upstream bug link is broken. So I cannot follow-up the upstream progress. The git history revealed no reference to bug number 457. Looking at the upstream code, I found following in lib/eventlog/eventlog.c: #if defined(HAVE_NL_LANGINFO) && defined(CODESET) locale = setlocale(LC_ALL, NULL); if (locale[0] != 'C' || locale[1] != '\0') (void) fprintf(mail, "\nContent-Type: text/plain; charset=\"%s\"\nContent-Transfer-Encoding: 8bit", nl_langinfo(CODESET)); #endif /* HAVE_NL_LANGINFO && CODESET */ So I assume that it was fixed upstream. This code snippet was introduced in commit bd1ca79cca827a92e904f022e49df121931d4ff5 and was part of sudo 1.9.4 which landed in Ubuntu 22.04 (jammy). If my assumption is wrong, please reopen this bug report. ** Changed in: sudo (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/491352 Title: Patch for incorrect charset in notification emails Status in sudo: Unknown Status in sudo package in Ubuntu: Fix Released Bug description: Binary package hint: sudo sudo uses strftime() to generate the date string in the notification mails sent to administrators when something fishy happens. strftime() generates the date according to locale env vars. This could result in date strings containing arbitrary characters in arbitrary charsets (think UTF-8 in far eastern languages). By default, email messages are us-ascii. sudo does no conversion of the data returned by strftime (which is in the user's current charset) to the default us-ascii charset. This causes non-ascii dates to come through as garbage. Solution: 1. stop using strftime. The code actually has the strftime code in a IFDEF, remove that whole ifdef, and use ctime, which is ascii. 2. insert charset information into the notification email. add header (Content-Type: text/plain; charset="") and (Content-Transfer-Encoding: 8bit). downside of solution 2: 1. 8bit transfer encoding is required. 8bit is not strictly supported by SMTP, although is supported by most MTA's, probably all MTA's in the Ubuntu repo. 2. Also, since the strftime uses the locale of the user, it could represent the date in some language unreadable by the sysadmin (who receives the notification, but does not necessarily read the same language as the user who committed whatever offense). ctime() always represents the date in English ASCII. I think we can safely assume the large majority of sysadmins out there can read English ASCII? I've attached a patch to only use ctime in notification emails and logging. Since launch pad only allows one attachment at time of bug creation, I'll try attach the other patch after I've submitted this. Here's hoping I can do that. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/491352/+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 501204] Re: sudo syntax error in /etc/sudoers due to #-- comment
Thanks for reporting this issue and for providing steps to reproduce. I tried to reproduce it on Ubuntu 22.04 (jammy) and added a "#--ariel--#" comment line to my sudoers file. sudo correctly ignore it. So I mark this bug as fixed. ** Changed in: sudo (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/501204 Title: sudo syntax error in /etc/sudoers due to #-- comment Status in sudo package in Ubuntu: Fix Released Bug description: Binary package hint: sudo I put a few comments in /etc/sudoers where the '#' comment char is succeeded with -- as in: #--ariel--# result: sudo won't work anymore. $ sudo echo OK >>> /etc/sudoers: syntax error near line 9 <<< >>> /etc/sudoers: syntax error near line 27 <<< sudo: parse error in /etc/sudoers near line 9 sudo: no valid sudoers sources found, quitting putting a space between the '#' and '--' solves the problem. Comments should start with '#' only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/501204/+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 1915789] Re: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
** Changed in: sudo (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915789 Title: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set Status in sudo package in Ubuntu: Fix Released Bug description: After upgrading sudo from 1.9.4p2-2ubuntu3 to 1.9.5p2-2ubuntu1, it no longer works. $ sudo sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set The file permission of /usr/bin/sudo seems to have been messed up. $ ls -l /usr/bin/sudo -rwsr-xr-x 1 2001 2501 190952 2021-02-10 19:42 /usr/bin/sudo System information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 Codename: hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915789/+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 1843829] Re: sudoers: admin group has permissions, but does not exist by default
** Summary changed: - Incorrect Sudo configuration + sudoers: admin group has permissions, but does not exist by default ** Changed in: sudo (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1843829 Title: sudoers: admin group has permissions, but does not exist by default Status in sudo package in Ubuntu: Triaged Bug description: Hello I had reported this earlier but my account shows no bugs reported so here I try again. On Ubuntu going back for a while now and also including the newest release /etc/sudoers contains the below lines on a default install %admin ALL=(ALL) ALL The problem is that the admin group doesn't exist by default so if a user with the name of admin was created they would be in a group of their own name. It looks like you guys might be using an account named adm instead of admin? This is also causing other bugs to be reported. It may seem silly as adding a user requires elevated permissions. If someone doesn't know about this behaviour or a user is allowed to create an admin named account through a script they are just a short sudo su away from controlling a system. I'd recommend commenting out the /etc/sudoers line or adding an admin group to /etc/group or changing the admin in sudoers to adm if that is what you are trying to do. Aaron Ringo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1843829/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
In case it's relevant...
I bricked my old PC while trying to work around this bug(!). After
putting the same RAM and plugging the same monitor into a new machine,
the bug does not occur. So the trigger for the bug was more to do with
the old machine's firmware.
--
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: https://github.com/os369510/grub2/tree/lp1842320
*
[Touch-packages] [Bug 1843829] Re: sudoers: admin group has permissions, but does not exist by default
Thanks for reporting this issue. Since you need to be root to create a new user, this can probably not be used directly as exploit. But I agree that creating a user "admin" should not create one that is in the admin group. So either removing this configuration line or create a admin group by default. In the latter case, adduser will fail to create a admin user. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1843829 Title: sudoers: admin group has permissions, but does not exist by default Status in sudo package in Ubuntu: Triaged Bug description: Hello I had reported this earlier but my account shows no bugs reported so here I try again. On Ubuntu going back for a while now and also including the newest release /etc/sudoers contains the below lines on a default install %admin ALL=(ALL) ALL The problem is that the admin group doesn't exist by default so if a user with the name of admin was created they would be in a group of their own name. It looks like you guys might be using an account named adm instead of admin? This is also causing other bugs to be reported. It may seem silly as adding a user requires elevated permissions. If someone doesn't know about this behaviour or a user is allowed to create an admin named account through a script they are just a short sudo su away from controlling a system. I'd recommend commenting out the /etc/sudoers line or adding an admin group to /etc/group or changing the admin in sudoers to adm if that is what you are trying to do. Aaron Ringo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1843829/+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 1910768] Re: apport-collect hangs and makes computer hang
I see a similar (same?) issue: if I say a bug is display-related, apport collecting problem information hangs ~20% through the process and neither "Cancel" nor (x) can stop the process. Cancel in the parent window helps. This is on 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1910768 Title: apport-collect hangs and makes computer hang Status in apport package in Ubuntu: Confirmed Bug description: This bug is related to bug 1723558 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1723558) but I could not transfer the generated information. After a crash of bluetoothd (see bug 1910405) I tried to run apport- collect with the bug ID, but the process hangs. After clicking cancel, it makes the computer hang totally, except running teams calls that keep streaming but without interaction possible. All is released when apport is killed manually. The problem also occurs when a crash of the Brave browser causes a call to apport. This bug is generated through ubuntu-bug -w after clicking on the apport-collect window. This second apport process doesn't hang. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.9-0ubuntu7.21 ProcVersionSignature: Ubuntu 5.4.0-58.64~18.04.1-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:29:04 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2019-11-22 (412 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Yes, grub will be fixed eventually, but we are blocked by the security
update not being out yet. This is not a blocker for enabling upgrades to
22.04.1, as it only affects a small number of systems and grub fixes
itself by using the previous kernel version if the new one fails.
--
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 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible
** Changed in: initramfs-tools (Debian) Status: Unknown => 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/1950996 Title: Missing all modules for usb nics in initrd which makes PXE boot impossible Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Confirmed Status in initramfs-tools source package in Hirsute: Confirmed Status in initramfs-tools source package in Impish: Won't Fix Status in initramfs-tools source package in Jammy: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: initrd taken from the live iso for PXE boot does not contain USB NIC drivers which makes PXE installation/netboot impossible via usb. This is the case on 20.04 server iso (both hwe and normal kernel/initrd) and desktop iso. "kernel/drivers/net/usb" is empty and needs to be included in the initramfs build. As most modern thin laptops lack physical rj45 ethernet this is a big issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18 Uname: Linux 5.8.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 16:47:45 2021 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+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 1315559] Re: UpgradeStatus can be incorrect
** Changed in: apport (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1315559
Title:
UpgradeStatus can be incorrect
Status in apport package in Ubuntu:
Triaged
Bug description:
In the general hook for ubuntu there is the following code:
log = '/var/log/dist-upgrade/main.log'
if os.path.exists(log):
mtime = os.stat(log).st_mtime
human_mtime = time.strftime('%Y-%m-%d', time.gmtime(mtime))
delta = time.time() - mtime
# Would be nice if this also showed which release was originally
installed
report['UpgradeStatus'] = 'Upgraded to %s on %s (%d days ago)' %
(release_codename, human_mtime, delta / 86400)
else:
report['UpgradeStatus'] = 'No upgrade log present (probably fresh
install)'
This does no checking of main.log to see if the upgrade was actually
successful, so if someone is reporting a bug about a failed upgrade of
ubuntu-release-upgrader they'll have a confusing 'UpgradeStatus' of
today for the previous release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1315559/+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 1593407] Re: Guest session cannot run snaps
That was firefox packaged as a deb, right? This issue is specifically with snaps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1593407 Title: Guest session cannot run snaps Status in Light Display Manager: Confirmed Status in Snappy: Confirmed Status in Ubuntu MATE: Confirmed Status in Desktop: New Status in firefox package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Xenial: Confirmed Status in lightdm source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Bug description: I'm using Ubuntu 16.04. The guest session cannot execute snaps, because of a permission error. The LightDM's guest session AppArmor profile is not allowing access to /snap and other needed files and folders. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1853115] Re: localauthority.conf - AdminIdentities: unix-group is ignored
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: policykit-1 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1853115 Title: localauthority.conf - AdminIdentities: unix-group is ignored Status in policykit-1 package in Ubuntu: Confirmed Bug description: Allowed users and groups as admins for pkexec are defined in: /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin As you can see, I added unix-group:localadmin My user is localadmin-user1 who is in the local group localadmin. It does not matter if I create a new configuration file /etc/polkit-1/localauthority.conf.d/99-myadmins.conf or expand the original 51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin If I add the user himself instead of his group localadmin the user is listed the allowed list for pkexec. [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-user:localadmin-user1 How to reproduce: - create local user and group (here: localadmin) - add unix-group:localadmin to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user in group localadmin is not listed - add unix-user:localadmin-user1 to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user localadmin-user1 is listed Kubuntu 19.10 policykit-10.105-26ubuntu1 SSSD for system authorization including domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1853115/+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 1853115] Re: localauthority.conf - AdminIdentities: unix-group is ignored
I am experiencing the same issue on Ubuntu 20.04.4 with the below polkit config, where sysapp is an LDAP group, and we are using SSSD for LDAP login to our machines. # This file is managed by Puppet. DO NOT EDIT. [Configuration] AdminIdentities=unix-group:sysapp;unix-group:sudo;unix-group:admin When attempting to install software via GUI (snap-store) or update packages, the GUI prompt only accepts authorisation from users in the 'sudo' or 'admin' groups. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1853115 Title: localauthority.conf - AdminIdentities: unix-group is ignored Status in policykit-1 package in Ubuntu: Confirmed Bug description: Allowed users and groups as admins for pkexec are defined in: /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin As you can see, I added unix-group:localadmin My user is localadmin-user1 who is in the local group localadmin. It does not matter if I create a new configuration file /etc/polkit-1/localauthority.conf.d/99-myadmins.conf or expand the original 51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin If I add the user himself instead of his group localadmin the user is listed the allowed list for pkexec. [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-user:localadmin-user1 How to reproduce: - create local user and group (here: localadmin) - add unix-group:localadmin to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user in group localadmin is not listed - add unix-user:localadmin-user1 to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user localadmin-user1 is listed Kubuntu 19.10 policykit-10.105-26ubuntu1 SSSD for system authorization including domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1853115/+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 580801] Re: Default /etc/sudoers file overwrites /etc/sudoers.d for 'admin' users
Thanks for reporting this bug. It should not have happened that your patch got unaddressed for so long. I checked /etc/sudoers in Ubuntu 22.04 and it is correct there: the last line is "@includedir /etc/sudoers.d". So I mark this bug as fixed. ** Changed in: sudo (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/580801 Title: Default /etc/sudoers file overwrites /etc/sudoers.d for 'admin' users Status in sudo: Opinion Status in sudo package in Ubuntu: Fix Released Bug description: Binary package hint: sudo I was trying to make truecrypt to mount encrypted container without asking my user's password after I provided my truecrypt password and found out that I need to modify my 'sudo' configuration. After reading bit more about sudo configuration I found out that custom configuration should be placed in '/etc/sudoers.d' instead of modifying the default '/etc/sudoers' file. I found out that my custom setting did not worked any user who is member of the group 'admin', but worked find for any other user. I found that last line '%admin ALL=(ALL) ALL' in default '/etc/sudoers' file overwrites any setting set in '/etc/sudoers.d'. I fixed it by moving the '#includedir /etc/sudoers.d' to be the last line. I am attaching my patch. I think that this should be fixed in default configuration file because I believe this file will get overwritten during the next 'sudo' upgrade. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: sudo 1.7.2p1-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Fri May 14 20:05:14 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: sudo VisudoCheck: /etc/sudoers: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/580801/+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
