[Touch-packages] [Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
Hello : iznobe@iznobe-PC:~$ sudo nano /etc/fstab iznobe@iznobe-PC:~$ sudo mkdir -pv /Videos/WD8 /Videos/WD8PRO2 mkdir: création du répertoire '/Videos' mkdir: création du répertoire '/Videos/WD8' mkdir: création du répertoire '/Videos/WD8PRO2' iznobe@iznobe-PC:~$ sudo umount -v /Vidéos/WD8 /Vidéos/WD8PRO2 umount: /Vidéos/WD8 démonté umount: /Vidéos/WD8PRO2 démonté iznobe@iznobe-PC:~$ sudo mount -av / : ignoré /boot/efi : déjà monté none : ignoré /datas : déjà monté /media/WD8PRO1 : ignoré /media/Seagate_4T : ignoré /Videos/WD8PRO2 : successfully mounted /Videos/WD8 : successfully mounted /tmp : déjà monté /var/log : déjà monté /home/iznobe/.cache : déjà monté /media/ramdisk : déjà monté iznobe@iznobe-PC:~$ and finally , it works ! iznobe@iznobe-PC:~$ tree /Videos/WD8/.Trash /Videos/WD8/.Trash └── 1000 ├── files │ └── test.odt └── info └── test.odt.trashinfo 3 directories, 2 files iznobe@iznobe-PC:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) Status in glib2.0 package in Ubuntu: New Status in glib2.0 source package in Jammy: New Bug description: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain the message in title. how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . Exactly same file systeme mounted on same directory , with same trash directory is working fine on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+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
Hi AG-Ubrio, the profile that you should check is not the lightdm one, but this: /var/lib/snapd/apparmor/profiles/snap.firefox.firefox It doesn't matter much, though, since this also has the rule /tmp/** mrwlkix, Can you please check in the logs, if you get some apparmor denials when running firefox? You could run the command journalctl -f -t audit then start firefox, and paste here the output from the first command. Also, if you say that the directory is created, it would be interesting to know what are its permissions. -- 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 1983618] Re: New upstream microrelease 2.5.13
This bug was fixed in the package openldap - 2.5.13+dfsg-1ubuntu1 --- openldap (2.5.13+dfsg-1ubuntu1) kinetic; urgency=medium * Merge with Debian unstable (LP: #1983618). Remaining changes: - Enable AppArmor support: + d/apparmor-profile: add AppArmor profile + d/rules: use dh_apparmor + d/control: Build-Depends on dh-apparmor + d/slapd.README.Debian: add note about AppArmor - Enable ufw support: + d/control: suggest ufw. + d/rules: install ufw profile. + d/slapd.ufw.profile: add ufw profile. - d/{rules,slapd.py}: Add apport hook. - d/rules: better regexp to match the Maintainer tag in d/control, needed in the Ubuntu case because of XSBC-Original-Maintainer (Closes #960448, LP #1875697) - Enable SASL/GSSAPI tests. (LP #1976508) + d/control: Update B-D to include required dependencies needed to run SASL/GSSAPI tests during build time, and mark them "!nocheck". Thanks: Andreas Hasenack -- Sergio Durigan Junior Tue, 20 Sep 2022 15:30:47 -0400 ** Changed in: openldap (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1983618 Title: New upstream microrelease 2.5.13 Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Jammy: Fix Released Bug description: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/3PLJDVP7QWTRFHC2GPQTGBLEQFCBUZZ2/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/pipelines/4504 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/RXOSXVLKTIDM4XJUA5EZZ42677JXRHYN/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in bileto and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: https://launchpad.net/~ci-train- ppa-service/+archive/ubuntu/4887/+build/24250107 * Bileto ticket: https://bileto.ubuntu.com/#/ticket/4895 [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. * CVEs fixed by this release: - None. Current versions in supported releases that got updates: openldap | 2.5.12+dfsg-0ubuntu0.22.04.1 | jammy-updates | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 As usual we test and prep from the PPA and then push through SRU/Security as applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1983618/+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 1990448] Re: Show Ubuntu Pro settings
** Also affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1990448 Title: Show Ubuntu Pro settings Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Jammy: New Status in software-properties source package in Kinetic: New Bug description: Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of just Livepatch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+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 1990448] [NEW] Show Ubuntu Pro settings
Public bug reported: Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of just Livepatch. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1990448 Title: Show Ubuntu Pro settings Status in software-properties package in Ubuntu: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Jammy: New Status in software-properties source package in Kinetic: New Bug description: Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of just Livepatch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+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 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status
Possibly this? --- /bin/on_ac_power2019-07-20 16:43:51.0 +0100 +++ ./on_ac_power 2022-09-22 01:44:53.412558622 +0100 @@ -28,6 +28,17 @@ type="$(cat "${FN}/type")" case "${type}" in Mains|USB*|BrickID|Wireless) +# If USB, is it input or output? +# + case "${type}" in + USB*) + if test -r "${FN}/usb_type"; then + usb_type=`cat "${FN}/usb_type"` + case "${usb_type}" in + *PD*) continue;; + esac + fi + esac if [ -r "${FN}/online" ]; then online="$(cat "${FN}/online")" [ "$online" = 1 ] && exit 0 (sorry - the indentation spaces after any + are being eaten) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. https://bugs.launchpad.net/bugs/1980991 Title: /usr/sbin/on_ac_power incorrectly reporting ac power status Status in powermgmt-base package in Ubuntu: Confirmed Status in powermgmt-base source package in Kinetic: Confirmed Bug description: Good afternoon, folks. I believe I discovered a bug in the /usr/sbin/on_ac_power script. I have a Dell OptiPlex 5090 host that has an entry in /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe this is the USB-C power delivery port on the front of the chassis. The issue I'm encountering is that /usr/sbin/on_ac_power is exiting with code 1 which states: (1 (false) if not on AC power) when that isn't the case. This looks to be because of the ucsi-source-psy-USBC000:001 entry reporting the "online" status as 0, presumably because nothing is currently connected to that USB-C port. This causes /usr/sbin/on_ac_power to incorrectly report that the machine isn't connected to AC power and causes other utilities like unattended-upgrades to quit when using the default configuration since it believes the machine isn't connected to AC power. There is a workaround with unattended-upgrades where you can specify it to run regardless of if AC power is connected, but as more and more chassis implement power-delivery USB-C ports I foresee this becoming more of an issue. I'm not sure if it's anything to look into, but I figured I would share my findings. Please let me know if you have any questions or if I can provide any additional information, troubleshooting, or testing. Thanks! -Kevin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+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 1615381] Autopkgtest regression report (apt/1.6.17)
All autopkgtests for the newly accepted apt (1.6.17) for bionic have finished running. The following regressions have been reported in tests triggered by the package: unattended-upgrades/1.1ubuntu1.18.04.14 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+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 1968154] Autopkgtest regression report (apt/1.6.17)
All autopkgtests for the newly accepted apt (1.6.17) for bionic have finished running. The following regressions have been reported in tests triggered by the package: unattended-upgrades/1.1ubuntu1.18.04.14 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Impish: Fix Released Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1974456] Autopkgtest regression report (apt/1.6.17)
All autopkgtests for the newly accepted apt (1.6.17) for bionic have finished running. The following regressions have been reported in tests triggered by the package: unattended-upgrades/1.1ubuntu1.18.04.14 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Bug description: [Impact] bootstrapping a system with apt that fixes #1968154 fails in focal and bionic, as they try to execute the config file that is being removed. This is not a problem on updates, only on new installs, so impact is limited to bootstrapping tools that enable -updates, such as mmdebstrap. [Test case] bootstrapping with -updates enabled can easily be tested with mmdebstrap: mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal for example, on focal: Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 [Regression potential] We remove 5 lines from the shell postinst script, there could be syntax errors? But then we'd see those during upgrades, so practically none. [Original bug report] #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1974223] Re: FTBFS and autopkgtest failure since changes in apt for automatic kernel removal
Hello Olivier, or anyone else affected, Accepted unattended-upgrades into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unattended- upgrades/1.1ubuntu1.18.04.15 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1974223 Title: FTBFS and autopkgtest failure since changes in apt for automatic kernel removal Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Focal: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] Since the following changes in apt have landed in focal-updates (and is currently in bionic-proposed), unattended-upgrades FTBFS and fails autopkgtest on both series: * Revert "Protect currently running kernel at run-time" * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of 2.4.5; including the change to only protect two kernels, not last installed one (LP: #1968154) == FAIL: test_remove_unused_dependencies_new_unused_only (__main__.TestRemoveUnused) -- Traceback (most recent call last): File "./test_remove_unused.py", line 165, in test_remove_unused_dependencies_new_unused_only haystack)) AssertionError: False is not true : Can not find 'Removing unused kernel packages: linux-image-4.05.0-1021-kvm [Test plan] 1. focal: * run autopkgtest against -updates: $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=updates --test-name run-tests -- * try to build the package 2. bionic: * run autopkgtest against -proposed: $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=proposed --test-name run-tests -- * try to build the package [Where problems could occur] * The fix only affects the test-suite (that runs both at build time & autopkgtest time) so the impact should be minimal. Something wrong in the patch would make the unattended package FTBFS or fail autopkgtest but it is already failing ATM. * The new tests dependency on apt can trigger more autopkgtest runs. Since unattended-upgrades has a non-trivial autopkgtest suite, this can have a slight impact on the queues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1989830] Re: vmwgfx_dri.so not built on aarch64
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1989830 Title: vmwgfx_dri.so not built on aarch64 Status in mesa package in Ubuntu: Confirmed Bug description: Ubuntu currently isn't building the vmwgfx_dri.so driver on aarch64 which makes graphics acceleration not work on VMware hypervisors running aarch64. Any Mesa3D version 22.1.4 or higher has full 3D support for the svga device, unfortunately only in: https://gitlab.freedesktop.org/mesa/mesa/-/commit/6e311dd7229b2afb478e65afe2f17d7fb422d01e we've added it to the default/auto compile options, before then it had to be manually enabled. It would be great if mesa packages for 22.10 could build the vmwgfx_dri.so by enabling the svga device in mesa packages. That would make accelerated GL work on aarch64 with VMware products. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1989830/+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 1990429] [NEW] software-properties uses deprecated apt-key
Public bug reported: software-properties still references apt-key, which is deprecated upstream (https://blog.jak-linux.org/2021/06/20/migrating-away-apt- key/): $ grep -r apt-key tests/test_dbus.py:# test apt-key update tests/test_aptauth.py:"/usr/bin/apt-key", tests/test_aptauth.py:stderr="Warning: apt-key is deprecated.\n", debian/changelog: - thus, add-apt-key for PPAs observes https_proxy for key retrieval debian/changelog: - stop using apt-key for installing keys debian/changelog: * Port AptAuth.py from gpg command parsing to apt-key command debian/changelog:- fix incorrect call call to apt-key for the fingerprint, thanks softwareproperties/SoftwareProperties.py:# apt-key stuff softwareproperties/SoftwareProperties.py:""" Run apt-key update """ softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "adv", "--with-colons", "--batch", "--fixed-list-mode", "--list-keys"] softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "--fakeroot", "add", filename] softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "--fakeroot", "update"] softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "--fakeroot", "rm", key] $ apt-key will eventually go away, and software-properties needs to adapt. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: rls-kk-incoming ** Tags added: rls-kk-incoming -- 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/1990429 Title: software-properties uses deprecated apt-key Status in software-properties package in Ubuntu: New Bug description: software-properties still references apt-key, which is deprecated upstream (https://blog.jak-linux.org/2021/06/20/migrating-away-apt- key/): $ grep -r apt-key tests/test_dbus.py:# test apt-key update tests/test_aptauth.py:"/usr/bin/apt-key", tests/test_aptauth.py:stderr="Warning: apt-key is deprecated.\n", debian/changelog: - thus, add-apt-key for PPAs observes https_proxy for key retrieval debian/changelog: - stop using apt-key for installing keys debian/changelog: * Port AptAuth.py from gpg command parsing to apt-key command debian/changelog:- fix incorrect call call to apt-key for the fingerprint, thanks softwareproperties/SoftwareProperties.py:# apt-key stuff softwareproperties/SoftwareProperties.py:""" Run apt-key update """ softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "adv", "--with-colons", "--batch", "--fixed-list-mode", "--list-keys"] softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "--fakeroot", "add", filename] softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "--fakeroot", "update"] softwareproperties/AptAuth.py:cmd = ["/usr/bin/apt-key", "--quiet", "--fakeroot", "rm", key] $ apt-key will eventually go away, and software-properties needs to adapt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990429/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
** Changed in: ubuntu-meta (Ubuntu Jammy) Milestone: ubuntu-22.04.1 => ubuntu-22.04.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Triaged Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Jammy: Confirmed Bug description: With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+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
I don't know if somebody changed something since 2022-05-03 (Comment #6 form @nrbrtx ), but my error message when starting firefox (snap) on Ubuntu Mate 22.04 in a guest session is different: guest-qd9nle@ubrio22:~$ firefox cannot create user data directory: /tmp/guest-qd9nle/snap/firefox/1860: Permission denied I don't understand why there appears this Permission denied, as in /etc/apparmor.d/abstractions/lightdm the permission is: "owner /tmp/** rwlkmix,", so it seems to be ok. And more: the directory /tmp/guest- qd9nle/snap/firefox/1860 is created, despite the message. -- 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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
I tested latest daily build https://cdimage.ubuntu.com/jammy/daily-live/20220920/jammy-desktop-amd64.iso and out of memory stil exist. I hope someone can provide an iso for download with a livesystem and install for jammy with changed compression. Ubuntu 21.10 (out of support) and Fedora 36 works fine. -- 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 1989457] Re: FFE: Enable riscv64 build
This bug was fixed in the package systemd - 251.4-1ubuntu5 --- systemd (251.4-1ubuntu5) kinetic; urgency=medium * enable building systemd-boot for riscv64 (LP: #1989457) -- Heinrich Schuchardt Tue, 13 Sep 2022 13:43:01 +0200 ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1989457 Title: FFE: Enable riscv64 build Status in systemd package in Ubuntu: Fix Released Bug description: The upstream source supports building systemd-boot for the riscv64 architecture. We just haven't enabled it yet in debian/control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989457/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989973] Re: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version
** Tags removed: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1989973 Title: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version Status in vim package in Ubuntu: Fix Released Bug description: In a fresh focal install/container, vim is uninstallable because version 2:8.1.2269-1ubuntu5.8 failed to build for vim, but the `all` packages did succeed. ``` $ docker run -ti --rm arm32v7/ubuntu:focal bash -c 'apt update && apt install vim-tiny' WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/amd64) and no specific platform was requested Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages [1227 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports focal/universe armhf Packages [10.9 MB] Get:7 http://ports.ubuntu.com/ubuntu-ports focal/multiverse armhf Packages [141 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports focal/restricted armhf Packages [10.8 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted armhf Packages [16.9 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe armhf Packages [996 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse armhf Packages [9626 B] Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages [1400 kB] Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe armhf Packages [27.4 kB] Get:14 http://ports.ubuntu.com/ubuntu-ports focal-backports/main armhf Packages [54.7 kB] Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf Packages [1032 kB] Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/multiverse armhf Packages [4730 B] Get:17 http://ports.ubuntu.com/ubuntu-ports focal-security/universe armhf Packages [698 kB] Get:18 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted armhf Packages [16.6 kB] Fetched 17.2 MB in 8s (2274 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 23 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-tiny : Depends: vim-common (= 2:8.1.2269-1ubuntu5.7) but 2:8.1.2269-1ubuntu5.8 is to be installed E: Unable to correct problems, you have held broken packages. ``` Seems to be due to https://launchpad.net/ubuntu/+source/vim/2:8.1.2269-1ubuntu5.8/+build/24478851 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1989973/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
Out of curiosity, would it work if you rename Vidéos into Videos? ** Also affects: glib2.0 (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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) Status in glib2.0 package in Ubuntu: New Status in glib2.0 source package in Jammy: New Bug description: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain the message in title. how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . Exactly same file systeme mounted on same directory , with same trash directory is working fine on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+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 1972939] Re: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes
*** This bug is a duplicate of bug 1990216 *** https://bugs.launchpad.net/bugs/1990216 ** This bug has been marked a duplicate of bug 1990216 backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1972939 Title: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes Status in Release Notes for Ubuntu: New Status in openssl package in Ubuntu: Fix Released Status in tinc package in Ubuntu: Invalid Status in openssl source package in Jammy: Confirmed Status in tinc source package in Jammy: Invalid Bug description: The tinc included in Jammy (1.0.36-2build1 linked with libssl3) cannot connect to tinc nodes running e.g. tinc from Xenial (1.0.26-1). (Tinc from Impish, which is also v1.0.36-2 but is linked to libssl1.1, can connect to these nodes without problems.) The symptom is a log message (on the system running Jammy) during the metadata channel negotiation (with debug level set to 5): Error during initialisation of cipher from tinc_xenial [...] error:0308010C:digital envelope routines::unsupported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1972939/+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 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy
** Changed in: openssl (Ubuntu Jammy) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1990216 Title: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: Confirmed Bug description: OpenSSL upstream implemented a fix for their issue #18359 "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" https://github.com/openssl/openssl/issues/18359 as of libssl3 3.0.4 (and thus it is included in recent libssl3 versions in Kinetic). Could this fix be backported to libssl3 in Jammy? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1990216/+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 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory
** Changed in: cyrus-sasl2 (Ubuntu Jammy) Assignee: (unassigned) => Lena Voytek (lvoytek) ** Changed in: cyrus-sasl2 (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1912256 Title: Missing channel binding prevents authentication to ActiveDirectory Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in openldap package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Jammy: In Progress Status in openldap source package in Jammy: Fix Released Bug description: > Are you uncertain if your issue is really a bug? Effect is an authentication error. Root case is a "missing feature" (see below) and requires updating dependencies, downporting. > If you are certain this is a bug please include the source package the bug is in. It's in the interaction between three libraries: openldap, cyrus-sasl, krb5 > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Broken in 18.04 and also in 20.10 (I guess it's also broken in anything inbetween) > 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libsasl2-modules-gssapi-mit: 2.1.27+dfsg-2ubuntu1 ldap-utils: 2.4.53+dfsg-1ubuntu1.2 libgssapi-krb5-2: 1.17-10ubuntu0.1 > 3) What you expected to happen # kinit $ export LDAPSASL_CBINDING=tls-endpoint $ ldapwhoami -O minssf=0,maxssf=0 -N -Y GSSAPI -H ldaps:// SASL/GSSAPI authentication started SASL username: SASL SSF: 0 u: > 4) What happened instead SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: 80090346: LdapErr: DSID-0C090597, comment: AcceptSecurityContext error, data 80090346, v4563 --- Microsoft ActiveDirectory has "LDAP Channel Binding" and recommends activating this as a required feature. See https://access.redhat.com/articles/4661861 Authentication to any AD DC which has mandatory channel binding fails. Channel binding requires at least an update to cyrus-sasl, which is not in any release as far as I can see: https://github.com/cyrusimap/cyrus- sasl/commit/975edbb69070eba6b035f08776de771a129cfb57 It also needs this commit in openldap: https://git.openldap.org/openldap/openldap/-/commit/3cd50fa8b32a21040a9892e2a8a7a9dfc7541ce6 Which as far as I can tell is v2.5 (branch OPENLDAP_REL_ENG_2_5). RH also mentions it needs up-to-date krb5 libraries, but I can't tell what minimum version this needs. I can build all libraries from source, current master (except for krb5 where I've used 1.18.3) and can confirm that channel binding works when using those libraries. I'm not sure if Samba is affected, but at least adcli, ldap-utils, and I would guess by extension also SSSD and realmd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1912256/+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 1990278] Re: systemd-resolved not included in Ubuntu bootstrap
I plan on reviewing and sponsoring this. ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) ** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/1990278 Title: systemd-resolved not included in Ubuntu bootstrap Status in systemd package in Ubuntu: In Progress Bug description: By default, i.e. with no --variant specified, debootstrap will only pull in packages with Priority: required or important. Before the systemd-resolved package split, resolved would be included because it was shipped with the systemd binary package, which is Priority: important. Currently there is no Priority: set on systemd-resolved, so it is not included with the deafult Ubuntu bootstrap. The systemd-resolved package should have Priority: important to fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990278/+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 1969901] Re: network-manager fails to renew ipv6 address
The test plan looks good - thanks! On reviewing the patch itself, it looks quite complex. We took a look upstream to see if there were any further fixes on the commit being cherry-picked, and found at least one. See https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commits/nm-1-10/src/devices/nm- device.c and commit d017022. This doesn't appear to be incorporated into the fix in Bionic being proposed here. Please could you fully analyze what has occurred upstream to ensure that this patch doesn't have any known issues that have since been fixed upstream? If these are false positives, I'd appreciate an explanation. Thanks! ** Changed in: network-manager (Ubuntu Bionic) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1969901 Title: network-manager fails to renew ipv6 address Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Incomplete Bug description: [Impact] * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is used. * Network manager might kill dhclient(6) and fail to start it again causing the IPv6 address to be lost on a network that uses mixed IPv4/IPV6. The network status will still be seen as online in gnome since ipv4 is still active. The user then have to manually remove the dhcpv6 lease files and restart ipv6 connection/restart network manager to regain IPv6 connectivity. * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version is based on 1.10.6): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f * Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=783391 [Test Plan] The test requires three computers * one computer runing isc dhcpd server (with network configured static) * one computer running patched network manager * one computer running vanilla ubuntu The idea is to execute on an isolated network and trigger the error by changing ip range handed out by the dhcp-server to force a nack response back to the clients. Expected result * patched network keeps dhclient6 alive * vanilla network manager will fail to keep dhclient6 alive in network manager logs dhcp6 will expire and not be restarted ON THE SERVER # Disable app-armor, as it has rules restricting dhcpd aa-teardown # install isc dhcpserver isc-dhcp-server # configure network static sudo nmcli connection modify "${CONNECTION_NAME}" \ ipv4.method "manual" \ ipv4.addresses "192.168.1.1/24" \ ipv4.gateway "192.168.1.254" \ ipv4.dns "192.168.1.1" \ ipv6.method "manual" \ ipv6.addresses "2001:db8:0:1::1/64" \ ipv6.gateway "2001:db8:0:1::ffbb" \ ipv6.dns "2001:db8:0:1::1/64" mkdir -p tmp touch tmp/dhcpd4_a.leases touch tmp/dhcpd4_b.leases touch tmp/dhcpd6_a.leases touch tmp/dhcpd6_b.leases Then it is time to execute dhcpd -f - run in foreground -d - print errors to stderr instead of syslog # Start in separate terminals dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6 dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6 Press ctrl-C to kill servers, then restart with the b configurations dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6 dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6 Then leases to expire (check for clients that kills dhclient) Press ctrl-C to kill servers, then restart with the a configurations ON THE CLIENTS Setup: Configure ipv6 network in settings to use dhcp (using the gui) Test: check that dhcp clients are still running: ps aux|grep dhclient Expected in output one client for dhcpv4 one client for dhcpv6 Also check network manager status : journalctl -u NetworkManager.service journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6 journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4 if dhclient is not running: stop network in gui remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the lease for the client not running. start network in gui if dhclients are running: wait additional ten minutes, repeat from beginning of test [Where problems could occur] * The change is in the dchp lease expiration handling so verify that there is no regression in dhcp renewals on different type of configuration include IPv6 [Other Info] * We have tested this patch on a couple of clients where we have seen this this problem. If this patch is feasible to include in Ubuntu 18.04 we could request more users to test. To manage notifications about this bug go to:
[Touch-packages] [Bug 1989969] Re: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el
I intend to review and sponsor enr0n's fix available in the MP. ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1989969 Title: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el Status in systemd package in Ubuntu: Triaged Bug description: In Kinetic, TEST-36-NUMAPOLICY from upstream-2 fails very frequently on ppc64el. See for example: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/ppc64el/s/systemd/20220908_195425_da51e@/log.gz, and the full kinetic ppc64el history: https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el. It has passed on very few occasions. I have tried to debug this locally but have gotten very little useful information (i.e. not enough to open an upstream bug). For now it is probably best to denylist this test on ppc64el. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990397] [NEW] Screen goes blank after a few seconds of inactivity
Public bug reported: Despite "Never" being selected in the "Screen Blank" section of the "Power" pane of gnome settings. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-1ubuntu1) ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 10:16:49 2022 DistUpgraded: 2022-08-02 22:49:48,677 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-43-generic, x86_64: installed nvidia/515.65.01, 5.19.0-15-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:249c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:22e4] InstallationDate: Installed on 2022-05-05 (138 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20Y5CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-08-03 (49 days ago) dmi.bios.date: 08/26/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N40ET37W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN40ET37W(1.19):bd08/26/2022:br1.19:efr1.16:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i: dmi.product.family: ThinkPad X1 Extreme Gen 4i dmi.product.name: 20Y5CTO1WW dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i dmi.product.version: ThinkPad X1 Extreme Gen 4i dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.1.7-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.1.7-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic possible-manual-nvidia-install regression reproducible third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1990397 Title: Screen goes blank after a few seconds of inactivity Status in xorg package in Ubuntu: New Bug description: Despite "Never" being selected in the "Screen Blank" section of the "Power" pane of gnome settings. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu
[Touch-packages] [Bug 1990315] Re: cannot link against libudev
There is a pkgconfig file shipped with udev itself, which just contains the definition of udev_dir. This is unrelated to the udev development package (libudev-dev). For development purposes, you should be using libudev, e.g. `pkg-config --libs libudev`. The rest sounds related to your build system, or at least not related to systemd or udev. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1990315 Title: cannot link against libudev Status in systemd package in Ubuntu: Invalid Bug description: When building Mesa vulkan drivers I get a lot of those error messages and the build fails: ``` error: undefined symbol: udev_new error: undefined symbol: udev_monitor_get_fd error: undefined symbol: udev_monitor_new_from_netlink error: undefined symbol: udev_monitor_receive_device error: undefined symbol: udev_monitor_unref error: undefined symbol: udev_unref error: undefined symbol: udev_device_unref error: undefined symbol: udev_device_get_property_value error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype error: undefined symbol: udev_monitor_enable_receiving ``` It worked on Ubuntu 21.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990315/+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 1990387] Re: FFE: Mesa 22.2.0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1990387 Title: FFE: Mesa 22.2.0 Status in mesa package in Ubuntu: Confirmed Bug description: Mesa 22.2.0 was released yesterday, a month late. This is an important release which brings support for AMD RDNA3 (together with llvm-15), Intel Arc (aka DG2) etc. Debian unstable has had 22.2.0-rc's since the start, because it was mistakenly uploaded there.. anyway, there was only one regression filed for x86 which is now fixed. Another one is for aarch64/virtio (Debian bug 1020391) and is unclear at this point if it's fixed by the final version or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1990387/+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 1962454] Re: Oops pages show wrong time window in JournalErrors
** Changed in: apport (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: apport (Ubuntu Focal) Status: New => Confirmed -- 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/1962454 Title: Oops pages show wrong time window in JournalErrors Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Confirmed Status in apport source package in Jammy: Confirmed Bug description: [Impact] Oops pages show wrong time window in JournalErrors. For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. [Test Plan] 1. Find a recent crash report from a relevant Ubuntu release on https://errors.ubuntu.com/ If you're looking at https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a relevant instance from the Occurrences list. 2. Now you're on a page starting with https://errors.ubuntu.com/oops/ look at ApportVersion and verify that apport is a recent enough version to contain the proposed fix. If not then go to step 1. 3. Verify the Date field falls within the time range of the JournalErrors entries. Step 3 might fail in the case of there being no system log entries from around the time of the crash. That does not necessarily mean the test plan has failed. Go to step 1 and pick a different crash. Prior to the fix you would almost never find oops pages that would pass the test. After the fix you should find many/most oops pages do pass the test. [Where problems could occur] Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. [Other Info] Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review. * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1962454/+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 1969901] Re: network-manager fails to renew ipv6 address
** Changed in: network-manager (Ubuntu Bionic) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1969901 Title: network-manager fails to renew ipv6 address Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: In Progress Bug description: [Impact] * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is used. * Network manager might kill dhclient(6) and fail to start it again causing the IPv6 address to be lost on a network that uses mixed IPv4/IPV6. The network status will still be seen as online in gnome since ipv4 is still active. The user then have to manually remove the dhcpv6 lease files and restart ipv6 connection/restart network manager to regain IPv6 connectivity. * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version is based on 1.10.6): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f * Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=783391 [Test Plan] The test requires three computers * one computer runing isc dhcpd server (with network configured static) * one computer running patched network manager * one computer running vanilla ubuntu The idea is to execute on an isolated network and trigger the error by changing ip range handed out by the dhcp-server to force a nack response back to the clients. Expected result * patched network keeps dhclient6 alive * vanilla network manager will fail to keep dhclient6 alive in network manager logs dhcp6 will expire and not be restarted ON THE SERVER # Disable app-armor, as it has rules restricting dhcpd aa-teardown # install isc dhcpserver isc-dhcp-server # configure network static sudo nmcli connection modify "${CONNECTION_NAME}" \ ipv4.method "manual" \ ipv4.addresses "192.168.1.1/24" \ ipv4.gateway "192.168.1.254" \ ipv4.dns "192.168.1.1" \ ipv6.method "manual" \ ipv6.addresses "2001:db8:0:1::1/64" \ ipv6.gateway "2001:db8:0:1::ffbb" \ ipv6.dns "2001:db8:0:1::1/64" mkdir -p tmp touch tmp/dhcpd4_a.leases touch tmp/dhcpd4_b.leases touch tmp/dhcpd6_a.leases touch tmp/dhcpd6_b.leases Then it is time to execute dhcpd -f - run in foreground -d - print errors to stderr instead of syslog # Start in separate terminals dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6 dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6 Press ctrl-C to kill servers, then restart with the b configurations dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6 dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6 Then leases to expire (check for clients that kills dhclient) Press ctrl-C to kill servers, then restart with the a configurations ON THE CLIENTS Setup: Configure ipv6 network in settings to use dhcp (using the gui) Test: check that dhcp clients are still running: ps aux|grep dhclient Expected in output one client for dhcpv4 one client for dhcpv6 Also check network manager status : journalctl -u NetworkManager.service journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6 journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4 if dhclient is not running: stop network in gui remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the lease for the client not running. start network in gui if dhclients are running: wait additional ten minutes, repeat from beginning of test [Where problems could occur] * The change is in the dchp lease expiration handling so verify that there is no regression in dhcp renewals on different type of configuration include IPv6 [Other Info] * We have tested this patch on a couple of clients where we have seen this this problem. If this patch is feasible to include in Ubuntu 18.04 we could request more users to test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+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 1990387] [NEW] FFE: Mesa 22.2.0
Public bug reported: Mesa 22.2.0 was released yesterday, a month late. This is an important release which brings support for AMD RDNA3 (together with llvm-15), Intel Arc (aka DG2) etc. Debian unstable has had 22.2.0-rc's since the start, because it was mistakenly uploaded there.. anyway, there was only one regression filed for x86 which is now fixed. Another one is for aarch64/virtio (Debian bug 1020391) and is unclear at this point if it's fixed by the final version or not. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1990387 Title: FFE: Mesa 22.2.0 Status in mesa package in Ubuntu: New Bug description: Mesa 22.2.0 was released yesterday, a month late. This is an important release which brings support for AMD RDNA3 (together with llvm-15), Intel Arc (aka DG2) etc. Debian unstable has had 22.2.0-rc's since the start, because it was mistakenly uploaded there.. anyway, there was only one regression filed for x86 which is now fixed. Another one is for aarch64/virtio (Debian bug 1020391) and is unclear at this point if it's fixed by the final version or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1990387/+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 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status
I have this issue on an Intel NUC (NUC10i357FN). The sysfs entry for the power supply does contain a usb_type entry for it, which contains: [nuc]: cat usb_type [C] PD -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. https://bugs.launchpad.net/bugs/1980991 Title: /usr/sbin/on_ac_power incorrectly reporting ac power status Status in powermgmt-base package in Ubuntu: Confirmed Status in powermgmt-base source package in Kinetic: Confirmed Bug description: Good afternoon, folks. I believe I discovered a bug in the /usr/sbin/on_ac_power script. I have a Dell OptiPlex 5090 host that has an entry in /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe this is the USB-C power delivery port on the front of the chassis. The issue I'm encountering is that /usr/sbin/on_ac_power is exiting with code 1 which states: (1 (false) if not on AC power) when that isn't the case. This looks to be because of the ucsi-source-psy-USBC000:001 entry reporting the "online" status as 0, presumably because nothing is currently connected to that USB-C port. This causes /usr/sbin/on_ac_power to incorrectly report that the machine isn't connected to AC power and causes other utilities like unattended-upgrades to quit when using the default configuration since it believes the machine isn't connected to AC power. There is a workaround with unattended-upgrades where you can specify it to run regardless of if AC power is connected, but as more and more chassis implement power-delivery USB-C ports I foresee this becoming more of an issue. I'm not sure if it's anything to look into, but I figured I would share my findings. Please let me know if you have any questions or if I can provide any additional information, troubleshooting, or testing. Thanks! -Kevin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+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 1989309] Re: [FFe] apparmor 3.1.1 upstream release
** Changed in: apparmor (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1989309 Title: [FFe] apparmor 3.1.1 upstream release Status in apparmor package in Ubuntu: Incomplete Bug description: AppArmor 3.1.1 is the latest upstream version of the apparmor userspace tooling. This includes a large number of bug fixes since the 3.0.7 release which is currently in kinetic, as well as various cleanups and optimisations to the different tools to improve performance and maintainability. The full ChangeLog can be seen at [1]. Upstream does not provide a ChangeLog file, however I have generated one based on the git commit history of apparmor from the 3.0.7 tag to 3.1.1 as: $ git log v3.0.7...v3.1.1 -- > ~/Downloads/apparmor-3.0.7-to-3.1.1-git-log.log This can be seen in the attached file https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617640/+files/apparmor-3.0.7-to-3.1.1-git- log.log TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[2] for AppArmor and the extensive QA Regression Tests[3] for AppArmor as well. This ensures that the various applications that make heavy use of AppArmor (LXD, docker, lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions have been observed. All tests have passed and demonstrated both apparmor and the various applications that use it to be working as expected. BUILD LOGS This is currently uploaded to https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309, build logs can be found on Launchpad at: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+build/24491969 for amd64 etc DEBDIFF The debdiff can be found in the PPA: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+files/apparmor_3.0.7-1ubuntu1_3.1.1-0ubuntu1.diff.gz INSTALL / UPGRADE LOG The apt upgrade log is attached in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617638/+files/apparmor-3.1.1-0ubuntu1-apt- upgrade.log [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.1 [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [3] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+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 1989309] Re: [FFe] apparmor 3.1.1 upstream release
The generated changelog for this release is quite big, so it's not really easily parseable. Do you know of any bigger/important features that are part of this apport release? Would be nice to at least know the overview of how many 'new' things are in there, compared to the huge set of fixes. -- 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/1989309 Title: [FFe] apparmor 3.1.1 upstream release Status in apparmor package in Ubuntu: New Bug description: AppArmor 3.1.1 is the latest upstream version of the apparmor userspace tooling. This includes a large number of bug fixes since the 3.0.7 release which is currently in kinetic, as well as various cleanups and optimisations to the different tools to improve performance and maintainability. The full ChangeLog can be seen at [1]. Upstream does not provide a ChangeLog file, however I have generated one based on the git commit history of apparmor from the 3.0.7 tag to 3.1.1 as: $ git log v3.0.7...v3.1.1 -- > ~/Downloads/apparmor-3.0.7-to-3.1.1-git-log.log This can be seen in the attached file https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617640/+files/apparmor-3.0.7-to-3.1.1-git- log.log TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[2] for AppArmor and the extensive QA Regression Tests[3] for AppArmor as well. This ensures that the various applications that make heavy use of AppArmor (LXD, docker, lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions have been observed. All tests have passed and demonstrated both apparmor and the various applications that use it to be working as expected. BUILD LOGS This is currently uploaded to https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309, build logs can be found on Launchpad at: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+build/24491969 for amd64 etc DEBDIFF The debdiff can be found in the PPA: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+files/apparmor_3.0.7-1ubuntu1_3.1.1-0ubuntu1.diff.gz INSTALL / UPGRADE LOG The apt upgrade log is attached in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617638/+files/apparmor-3.1.1-0ubuntu1-apt- upgrade.log [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.1 [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [3] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+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 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
** Tags added: originate-from-1989447 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1977986 Title: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad Status in OEM Priority Project: New Status in upower package in Ubuntu: New Bug description: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977986/+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 1989309] Re: [FFe] apparmor 3.1.1 upstream release
** Description changed: - Placeholder for preparation of AppArmor 3.1.1 for kinetic. + AppArmor 3.1.1 is the latest upstream version of the apparmor userspace + tooling. + + This includes a large number of bug fixes since the 3.0.7 release which + is currently in kinetic, as well as various cleanups and optimisations + to the different tools to improve performance and maintainability. + + The full ChangeLog can be seen at [1] + + + TESTING + + This has been extensively tested by the security team - this includes + following the documented Ubuntu merges test plan[2] for AppArmor and the + extensive QA Regression Tests[3] for AppArmor as well. This ensures that + the various applications that make heavy use of AppArmor (LXD, docker, + lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions + have been observed. All tests have passed and demonstrated both apparmor + and the various applications that use it to be working as expected. + + + BUILD LOGS + + This is currently uploaded to https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309, build logs can be found on + Launchpad at: + https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+build/24491969 for amd64 etc + + + DEBDIFF + + The debdiff can be found in the PPA: + https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+files/apparmor_3.0.7-1ubuntu1_3.1.1-0ubuntu1.diff.gz + + + INSTALL / UPGRADE LOG + + The apt upgrade log is attached. + + + [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.1 + [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor + [3] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py ** Attachment added: "apparmor-3.1.1-0ubuntu1-apt-upgrade.log" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617638/+files/apparmor-3.1.1-0ubuntu1-apt-upgrade.log ** Description changed: AppArmor 3.1.1 is the latest upstream version of the apparmor userspace tooling. This includes a large number of bug fixes since the 3.0.7 release which is currently in kinetic, as well as various cleanups and optimisations to the different tools to improve performance and maintainability. The full ChangeLog can be seen at [1] - TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[2] for AppArmor and the extensive QA Regression Tests[3] for AppArmor as well. This ensures that - the various applications that make heavy use of AppArmor (LXD, docker, - lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions - have been observed. All tests have passed and demonstrated both apparmor + the various applications that make heavy use of AppArmor (LXD, docker, + lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions + have been observed. All tests have passed and demonstrated both apparmor and the various applications that use it to be working as expected. - BUILD LOGS This is currently uploaded to https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309, build logs can be found on Launchpad at: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+build/24491969 for amd64 etc - DEBDIFF The debdiff can be found in the PPA: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+files/apparmor_3.0.7-1ubuntu1_3.1.1-0ubuntu1.diff.gz - INSTALL / UPGRADE LOG - The apt upgrade log is attached. - + The apt upgrade log is attached in + https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617638/+files/apparmor-3.1.1-0ubuntu1-apt- + upgrade.log [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.1 [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [3] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py ** Description changed: AppArmor 3.1.1 is the latest upstream version of the apparmor userspace tooling. This includes a large number of bug fixes since the 3.0.7 release which is currently in kinetic, as well as various cleanups and optimisations to the different tools to improve performance and maintainability. - The full ChangeLog can be seen at [1] + The full ChangeLog can be seen at [1]. Upstream does not provide a + ChangeLog file, however I have generated one based on the git commit + history of apparmor from the 3.0.7 tag to 3.1.1 as: + + $ git log v3.0.7...v3.1.1 -- > ~/Downloads/apparmor-3.0.7-to-3.1.1-git- + log.log + + This can be seen in the attached file. + TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[2] for AppArmor and the extensive QA Regression Tests[3] for AppArmor as well. This ensures that the various applications that make heavy use of AppArmor (LXD, docker, lxc, dbus, libvirt, snapd etc) have all been exercised and no
[Touch-packages] [Bug 1989309] Re: [FFe] apparmor 3.1.1 upstream release
** Attachment added: "apparmor-3.0.7-to-3.1.1-git-log.log" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617640/+files/apparmor-3.0.7-to-3.1.1-git-log.log ** Description changed: AppArmor 3.1.1 is the latest upstream version of the apparmor userspace tooling. This includes a large number of bug fixes since the 3.0.7 release which is currently in kinetic, as well as various cleanups and optimisations to the different tools to improve performance and maintainability. The full ChangeLog can be seen at [1]. Upstream does not provide a ChangeLog file, however I have generated one based on the git commit history of apparmor from the 3.0.7 tag to 3.1.1 as: $ git log v3.0.7...v3.1.1 -- > ~/Downloads/apparmor-3.0.7-to-3.1.1-git- log.log - This can be seen in the attached file. - + This can be seen in the attached file + https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617640/+files/apparmor-3.0.7-to-3.1.1-git- + log.log TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[2] for AppArmor and the extensive QA Regression Tests[3] for AppArmor as well. This ensures that the various applications that make heavy use of AppArmor (LXD, docker, lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions have been observed. All tests have passed and demonstrated both apparmor and the various applications that use it to be working as expected. BUILD LOGS This is currently uploaded to https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309, build logs can be found on Launchpad at: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+build/24491969 for amd64 etc DEBDIFF The debdiff can be found in the PPA: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+files/apparmor_3.0.7-1ubuntu1_3.1.1-0ubuntu1.diff.gz INSTALL / UPGRADE LOG The apt upgrade log is attached in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617638/+files/apparmor-3.1.1-0ubuntu1-apt- upgrade.log [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.1 [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [3] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py -- 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/1989309 Title: [FFe] apparmor 3.1.1 upstream release Status in apparmor package in Ubuntu: New Bug description: AppArmor 3.1.1 is the latest upstream version of the apparmor userspace tooling. This includes a large number of bug fixes since the 3.0.7 release which is currently in kinetic, as well as various cleanups and optimisations to the different tools to improve performance and maintainability. The full ChangeLog can be seen at [1]. Upstream does not provide a ChangeLog file, however I have generated one based on the git commit history of apparmor from the 3.0.7 tag to 3.1.1 as: $ git log v3.0.7...v3.1.1 -- > ~/Downloads/apparmor-3.0.7-to-3.1.1-git-log.log This can be seen in the attached file https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617640/+files/apparmor-3.0.7-to-3.1.1-git- log.log TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[2] for AppArmor and the extensive QA Regression Tests[3] for AppArmor as well. This ensures that the various applications that make heavy use of AppArmor (LXD, docker, lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions have been observed. All tests have passed and demonstrated both apparmor and the various applications that use it to be working as expected. BUILD LOGS This is currently uploaded to https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309, build logs can be found on Launchpad at: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+build/24491969 for amd64 etc DEBDIFF The debdiff can be found in the PPA: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+files/apparmor_3.0.7-1ubuntu1_3.1.1-0ubuntu1.diff.gz INSTALL / UPGRADE LOG The apt upgrade log is attached in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617638/+files/apparmor-3.1.1-0ubuntu1-apt- upgrade.log [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.1 [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [3] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
I agree with Seb. Behavior is broken, not different. It's not just about printing information; it's the fact that ping is not checking csum, not checking duplicates... Ideally, both this and bug 1551020 should be fixed. But if I'd have to pick only one, this would be the one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Incomplete Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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