[Touch-packages] [Bug 1992930] Re: chromium won't launch at nenu when installed; lubuntu kinetic
2029.529767] audit: type=1400 audit(1665727989.480:369): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4554 comm="firefox" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2029.788432] audit: type=1400 audit(1665727989.740:370): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4573 comm="firefox" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.216633] audit: type=1400 audit(1665727991.169:371): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4617 comm="xdg-settings" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.226352] audit: type=1400 audit(1665727991.177:372): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4618 comm="dbus-send" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.226369] audit: type=1400 audit(1665727991.177:373): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4619 comm="cut" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.431479] audit: type=1400 audit(1665727991.385:374): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4690 comm="xdg-settings" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.438386] audit: type=1400 audit(1665727991.389:375): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4691 comm="dbus-send" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.338418] kauditd_printk_skb: 10 callbacks suppressed [ 2291.338425] audit: type=1400 audit(1665728251.317:386): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/meta/snap.yaml" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.401821] audit: type=1400 audit(1665728251.381:387): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/doc/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.401839] audit: type=1400 audit(1665728251.381:388): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.401849] audit: type=1400 audit(1665728251.381:389): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.401919] audit: type=1400 audit(1665728251.381:390): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/doc/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.697486] audit: type=1400 audit(1665728251.673:391): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/meta/snap.yaml" pid=5013 comm="snap-exec" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.820941] audit: type=1400 audit(1665728251.797:392): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/cups/" pid=5013 comm="snap-exec" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.853434] audit: type=1400 audit(1665728251.829:393): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/lib/snapd/void/" pid=5013 comm="desktop-launch" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.878977] audit:
[Touch-packages] [Bug 1992667] Re: Application windows invisible (on DG2 graphics)
you'll have a new mesa backport from kinetic to jammy in ppa:canonical-x/x-staging soon, once all the build-deps are in order -- 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/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in linux-oem-6.0 source package in Jammy: New Status in mesa source package in Jammy: New Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Won't Fix -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Fix Released Status in HWE Next: Fix Released Status in X.Org X server: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Invalid Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1714178/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
needs also spirv-llvm-translator-14 to build libclc-15, or s-l-t-15 plus spirv-headers backported ** Also affects: spirv-llvm-translator-14 (Ubuntu) Importance: Undecided Status: New ** Changed in: directx-headers (Ubuntu Jammy) Status: New => In Progress ** Changed in: libdrm (Ubuntu Jammy) Status: New => In Progress ** Changed in: llvm-toolchain-15 (Ubuntu Jammy) Status: New => In Progress ** Changed in: mesa (Ubuntu Jammy) Status: New => In Progress ** Changed in: spirv-llvm-translator-14 (Ubuntu) Status: New => Invalid ** Changed in: spirv-llvm-translator-14 (Ubuntu Jammy) Status: New => In Progress -- 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/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: In Progress Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-llvm-translator-14 source package in Jammy: In Progress Bug description: WIP directx-headers libdrm llvm-15 mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1992667] Re: Application windows invisible (on DG2 graphics)
the backports in jammy mesa are likely somewhat buggy although some demos etc work fine, 22.2 should work better OOTB ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in linux-oem-6.0 source package in Jammy: New Status in mesa source package in Jammy: New Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1971712] Re: Add support for Intel DG2
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- 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/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: In Progress Status in mesa source package in Jammy: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1992930] Re: chromium won't launch at nenu when installed; lubuntu kinetic
fox.firefox" name="/var/lib/snapd/void/" pid=4469 comm="dbus-send" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2029.529767] audit: type=1400 audit(1665727989.480:369): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4554 comm="firefox" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2029.788432] audit: type=1400 audit(1665727989.740:370): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4573 comm="firefox" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.216633] audit: type=1400 audit(1665727991.169:371): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4617 comm="xdg-settings" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.226352] audit: type=1400 audit(1665727991.177:372): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4618 comm="dbus-send" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.226369] audit: type=1400 audit(1665727991.177:373): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4619 comm="cut" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.431479] audit: type=1400 audit(1665727991.385:374): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4690 comm="xdg-settings" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.438386] audit: type=1400 audit(1665727991.389:375): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4691 comm="dbus-send" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.338418] kauditd_printk_skb: 10 callbacks suppressed [ 2291.338425] audit: type=1400 audit(1665728251.317:386): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/meta/snap.yaml" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.401821] audit: type=1400 audit(1665728251.381:387): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/doc/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.401839] audit: type=1400 audit(1665728251.381:388): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.401849] audit: type=1400 audit(1665728251.381:389): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.401919] audit: type=1400 audit(1665728251.381:390): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/doc/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.697486] audit: type=1400 audit(1665728251.673:391): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/meta/snap.yaml" pid=5013 comm="snap-exec" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.820941] audit: type=1400 audit(1665728251.797:392): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/cups/" pid=5013 comm="snap-exec" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.853434] audit: type=1400 audit(1665728251.829:393): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/lib/snapd/void/" pid=5013 comm="desktop-launch" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.878977] audit: type=1400 audit(1665728251.857:394): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/lib/snapd/void/" pid=5048 comm="date" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.883639] audit: type=1400 audit(1665728251.861:395): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/lib/snapd/void/" pid=5050 comm="getent" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apparmor 3.0.7-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: LXQt Date: Fri Oct 14 06:12:40 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Daily amd64 (20221013) ProcKernelCmdline: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- SourcePackage: apparmor Syslog: Oct 14 05:40:44 lubuntu dbus-daemon[1290]: [system] AppArmor D-Bus mediation is enabled Oct 14 05:41:54 lubuntu dbus-daemon[1747]: [session uid=999 pid=1747] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1992930/+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 1992930] Re: chromium won't launch at nenu when installed; lubuntu kinetic
refox" name="/var/lib/snapd/void/" pid=4469 comm="dbus-send" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2029.529767] audit: type=1400 audit(1665727989.480:369): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4554 comm="firefox" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2029.788432] audit: type=1400 audit(1665727989.740:370): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4573 comm="firefox" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.216633] audit: type=1400 audit(1665727991.169:371): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4617 comm="xdg-settings" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.226352] audit: type=1400 audit(1665727991.177:372): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4618 comm="dbus-send" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.226369] audit: type=1400 audit(1665727991.177:373): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4619 comm="cut" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.431479] audit: type=1400 audit(1665727991.385:374): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4690 comm="xdg-settings" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.438386] audit: type=1400 audit(1665727991.389:375): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4691 comm="dbus-send" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.338418] kauditd_printk_skb: 10 callbacks suppressed [ 2291.338425] audit: type=1400 audit(1665728251.317:386): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/meta/snap.yaml" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.401821] audit: type=1400 audit(1665728251.381:387): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/doc/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.401839] audit: type=1400 audit(1665728251.381:388): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.401849] audit: type=1400 audit(1665728251.381:389): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.401919] audit: type=1400 audit(1665728251.381:390): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/doc/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.697486] audit: type=1400 audit(1665728251.673:391): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/meta/snap.yaml" pid=5013 comm="snap-exec" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.820941] audit: type=1400 audit(1665728251.797:392): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/cups/" pid=5013 comm="snap-exec" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.853434] audit: type=1400 audit(1665728251.829:393): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/lib/snapd/void/" pid=5013 comm="desktop-launch" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.878977] audit: type=1400 audit(1665728251.857:394): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/lib/snapd/void/" pid=5048 comm="date" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.883639] audit: type=1400 audit(1665728251.861:395): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/lib/snapd/void/" pid=5050 comm="getent" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apparmor 3.0.7-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: LXQt Date: Fri Oct 14 06:12:40 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Daily amd64 (20221013) ProcKernelCmdline: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- SourcePackage: apparmor Syslog: Oct 14 05:40:44 lubuntu dbus-daemon[1290]: [system] AppArmor D-Bus mediation is enabled Oct 14 05:41:54 lubuntu dbus-daemon[1747]: [session uid=999 pid=1747] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1992930/+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 1992930] [NEW] chromium won't launch at nenu when installed; lubuntu kinetic
quot; name="/var/lib/snapd/void/" pid=4573 comm="firefox" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.216633] audit: type=1400 audit(1665727991.169:371): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4617 comm="xdg-settings" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.226352] audit: type=1400 audit(1665727991.177:372): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4618 comm="dbus-send" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.226369] audit: type=1400 audit(1665727991.177:373): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4619 comm="cut" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.431479] audit: type=1400 audit(1665727991.385:374): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4690 comm="xdg-settings" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2031.438386] audit: type=1400 audit(1665727991.389:375): apparmor="DENIED" operation="getattr" class="file" profile="snap.firefox.firefox" name="/var/lib/snapd/void/" pid=4691 comm="dbus-send" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.338418] kauditd_printk_skb: 10 callbacks suppressed [ 2291.338425] audit: type=1400 audit(1665728251.317:386): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/meta/snap.yaml" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.401821] audit: type=1400 audit(1665728251.381:387): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/doc/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.401839] audit: type=1400 audit(1665728251.381:388): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.401849] audit: type=1400 audit(1665728251.381:389): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.401919] audit: type=1400 audit(1665728251.381:390): apparmor="DENIED" operation="getattr" class="file" profile="snap-update-ns.chromium" name="/run/user/999/doc/" pid=5038 comm="5" requested_mask="r" denied_mask="r" fsuid=999 ouid=999 [ 2291.697486] audit: type=1400 audit(1665728251.673:391): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/meta/snap.yaml" pid=5013 comm="snap-exec" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.820941] audit: type=1400 audit(1665728251.797:392): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/cups/" pid=5013 comm="snap-exec" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.853434] audit: type=1400 audit(1665728251.829:393): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/lib/snapd/void/" pid=5013 comm="desktop-launch" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.878977] audit: type=1400 audit(1665728251.857:394): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/lib/snapd/void/" pid=5048 comm="date" requested_mask="r" denied_mask="r" fsuid=999 ouid=0 [ 2291.883639] audit: type=1400 audit(1665728251.861:395): apparmor="DENIED" operation="getattr" class="file" profile="snap.chromium.chromium" name="/var/lib/snapd/voi
[Touch-packages] [Bug 1992727] Re: package linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1992727 Title: package linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: it just said it want to report a problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 13 07:00:41 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-01-09 (641 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-50-generic 5.15.0-50.56~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992727/+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 1991975] Re: dev file system is mounted without nosuid or noexec
Just a heads-up that SGX has been deprecated by Intel: https://edc.intel.com/content/www/us/en/design/ipla/software- development-platforms/client/platforms/alder-lake-desktop/12th- generation-intel-core-processors-datasheet-volume-1-of-2/004/deprecated- technologies/ === The processor has deprecated the following technologies and they are no longer supported: Intel® Memory Protection Extensions (Intel® MPX) Branch Monitoring Counters Hardware Lock Elision (HLE), part of Intel® TSX-NI Intel® Software Guard Extensions (Intel® SGX) Intel® TSX-NI Power Aware Interrupt Routing (PAIR) === I think we shouldn't put too much weight on SGX support in making this decision. Thanks -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: In Progress Status in systemd source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in systemd source package in Jammy: Invalid Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon
[Touch-packages] [Bug 1992688] Re: firefox deb not installed
This bug was fixed in the package ubuntu-meta - 1.497 --- ubuntu-meta (1.497) kinetic; urgency=medium * Refreshed dependencies * Added firefox to desktop-minimal-recommends [amd64 arm64 armhf], desktop-recommends [amd64 arm64 armhf] as it provides dpkg alternatives for x-www-browser and gnome-www-browser. (LP: #1992688) -- Brian Murray Thu, 13 Oct 2022 14:37:15 -0700 ** Changed in: ubuntu-meta (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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1992688] Re: firefox deb not installed
I'm going to do the ubuntu-meta upload so we can get this in ASAP. ** Changed in: ubuntu-meta (Ubuntu) Assignee: Olivier Tilloy (osomon) => Brian Murray (brian-murray) -- 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/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: In Progress Status in firefox source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1990588] Re: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 1
It seems like for some reason systemd-machine-id-setup was not unpacked correctly? It's trying to link against libsystemd-shared-245.so, which is from focal. It should be linking against libsystemd-shared-249.so instead. It's called in systemd.postinst, so by that point the new version of the binary should be in place. Does this issue persist? If so, what does `which systemd-machine-id-setup` say? Is it possible you have another version of the binary installed somewhere? ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Tags removed: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1990588 Title: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 Status in systemd package in Ubuntu: Incomplete Bug description: updating from server 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd 249.11-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 22 19:00:53 2022 ErrorMessage: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 InstallationDate: Installed on 2020-07-28 (786 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel IC4GG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=8859cc64-d58f-4403-a3dc-284744628c34 ro rootflags=subvol=@ debian-installer/language=es keyboard-configuration/layoutcode?=es consoleblank=60 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: systemd Title: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 UpgradeStatus: Upgraded to focal on 2022-09-22 (0 days ago) dmi.bios.date: 07/03/2012 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 63K dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: IC4GG dmi.board.vendor: Intel dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr63K:bd07/03/2012:br0.1:svnIntel:pnIC4GG:pvr0.1:rvnIntel:rnIC4GG:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:skuSystemSKUNumber: dmi.product.family: ChiefRiver System dmi.product.name: IC4GG dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel mtime.conffile..etc.systemd.logind.conf: 2020-10-22T18:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990588/+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 1992688] Re: firefox deb not installed
** Also affects: ubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu Jammy) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: ubuntu-meta (Ubuntu Jammy) Importance: Undecided => High -- 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/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: In Progress Status in firefox source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1992688] Re: firefox deb not installed
** Merge proposal linked: https://code.launchpad.net/~osomon/ubuntu-seeds/+git/ubuntu/+merge/431530 -- 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/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: In Progress Status in firefox source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1992688] Re: firefox deb not installed
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: ubuntu-meta (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => High -- 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/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: In Progress Status in firefox source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1988548] Re: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy
** Changed in: zlib (Ubuntu) Assignee: (unassigned) => Rodrigo Figueiredo Zaiden (rodrigo-zaiden) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1988548 Title: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy Status in zlib package in Ubuntu: Confirmed Bug description: There is a crictical security issue with zlib tracked here [1] The newest version in bionic [2] already has a security patch for it but the one in the focal [3] (and jammy) does not. As can be seen from their respective changelogs in the right hand side panel. Since zlib is loaded by lots of software, e.g. the apache weg server, this could be a problem. It seems that focal, jammy and bionic use the same base zlib version (1.2.11), so maybe the patch there could be recycled? I was asked to create a bug here after asking it as question here [4]. Thank you very much for your hard work! [1] CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-37434 [2] Bionic Package: https://packages.ubuntu.com/bionic/zlib1g [3] Focal Package: https://packages.ubuntu.com/focal/zlib1g [4] Original Question: https://answers.launchpad.net/ubuntu/+source/zlib/+question/703010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1988548/+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 1992844] [NEW] apt download retries do not start at the 'root' but the redirect
Public bug reported: I am running apt with exactly one source and with the retries=3 option that became standard. ~ $ cat /etc/apt/sources.list.d/raspi.list deb http://raspbian.raspberrypi.org/raspbian bullseye main ~ $ apt --version apt 2.2.4 (arm64) $ sudo apt-get -oAcquire::ForceIPv6=true -oAcquire::Retries=3 install --reinstall adduser Now the host of the repo will reply with a mirror selection (i.e. http 302 redirect). It so happens that the mirror selected is a ipv4 mirror and my machine is a ipv6 only machine, so there is no possible dns resolution. (force ipv6 was a trial, has no effect on my machine which is ipv6 only) Apt tries again 3 times, but only at the location of the redirect. For my understanding it should start at the original source, so it has a chance of getting a _different_ 302 redirect. Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt. Ign:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf adduser all 3.118 Ign:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf adduser all 3.118 Ign:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf adduser all 3.118 Fehl:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf adduser all 3.118 Beim Auflösen von »ftp.agdsn.de:http« ist etwas Schlimmes passiert (-5 - Zu diesem Hostnamen gehört keine Adresse). E: Fehlschlag beim Holen von http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian/pool/main/a/adduser/adduser_3.118_all.deb Beim Auflösen von »ftp.agdsn.de:http« ist etwas Schlimmes passiert (-5 - Zu diesem Hostnamen gehört keine Adresse). [ something wicked happened, no address for this hostname ] E: Einige Archive konnten nicht heruntergeladen werden; vielleicht »apt-get update« ausführen oder mit »--fix-missing« probieren? ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1992844 Title: apt download retries do not start at the 'root' but the redirect Status in apt package in Ubuntu: New Bug description: I am running apt with exactly one source and with the retries=3 option that became standard. ~ $ cat /etc/apt/sources.list.d/raspi.list deb http://raspbian.raspberrypi.org/raspbian bullseye main ~ $ apt --version apt 2.2.4 (arm64) $ sudo apt-get -oAcquire::ForceIPv6=true -oAcquire::Retries=3 install --reinstall adduser Now the host of the repo will reply with a mirror selection (i.e. http 302 redirect). It so happens that the mirror selected is a ipv4 mirror and my machine is a ipv6 only machine, so there is no possible dns resolution. (force ipv6 was a trial, has no effect on my machine which is ipv6 only) Apt tries again 3 times, but only at the location of the redirect. For my understanding it should start at the original source, so it has a chance of getting a _different_ 302 redirect. Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt. Ign:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf adduser all 3.118 Ign:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf adduser all 3.118 Ign:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf adduser all 3.118 Fehl:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf adduser all 3.118 Beim Auflösen von »ftp.agdsn.de:http« ist etwas Schlimmes passiert (-5 - Zu diesem Hostnamen gehört keine Adresse). E: Fehlschlag beim Holen von http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian/pool/main/a/adduser/adduser_3.118_all.deb Beim Auflösen von »ftp.agdsn.de:http« ist etwas Schlimmes passiert (-5 - Zu diesem Hostnamen gehört keine Adresse). [ something wicked happened, no address for this hostname ] E: Einige Archive konnten nicht heruntergeladen werden; vielleicht »apt-get update« ausführen oder mit »--fix-missing« probieren? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992844/+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 1992690] Re: Fix large thumbnails with Nautilus
** Changed in: glib2.0 (Debian) Status: New => Fix Released -- 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/1992690 Title: Fix large thumbnails with Nautilus Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 package in Debian: Fix Released Bug description: Impact -- Copying this report from Debian. I have a 4K monitor with 175% fractional scaling. Nautilus 43 broke hi-dpi thumbnailing [1], and goes into an infinite loop trying to create x-large and xx-large thumbnails, consuming CPU forever. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1992690/+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 1992701] Re: Issue with opening module dependency file
What happens if you reboot after the kernel is upgraded? ** Changed in: kmod (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1992701 Title: Issue with opening module dependency file Status in kmod package in Ubuntu: Incomplete Bug description: Tested on: Trusty, Xenial (used as recovery system) I'm unable to manage (modprobe, insmod) modules due following error: "modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'" I don't know why, but it seem like in the libkmod.c was a bug that attempt to load an old kernel after it got upgraded (replaced with) a newer one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1992701/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
** Changed in: llvm-toolchain-15 (Ubuntu Jammy) Status: New => Invalid -- 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/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in llvm-toolchain-15 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-15 source package in Jammy: Invalid Status in mesa source package in Jammy: Confirmed Status in llvm-toolchain-15 source package in Kinetic: Fix Released Status in mesa source package in Kinetic: Confirmed Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1980386/+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 1980805] Re: Backport packages for 20.04.5 HWE stack
** Changed in: llvm-toolchain-13 (Ubuntu) Status: New => Invalid -- 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/1980805 Title: Backport packages for 20.04.5 HWE stack Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mesa-amber package in Ubuntu: Invalid Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-13 source package in Focal: Fix Committed Status in mesa source package in Focal: New Status in mesa-amber source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.5 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: pci-id updates, some minor api updates mesa: a new major release, but we'll pull the final stable release of 22.0.x series, so there shouldn't be any regressions left at that point mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI drivers that were removed from main mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1980805/+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 1969671] Re: Misspelled Ukrainian cities in tzdata
This bug was fixed in the package tzdata - 2022e-0ubuntu1 --- tzdata (2022e-0ubuntu1) kinetic; urgency=medium * New upstream releases (LP: #1992692): - Palestine transitions are now Saturdays at 02:00. This means 2022 falls back 10-29 at 02:00, not 10-28 at 01:00. - Simplify three Ukraine zones into one. (LP: #1969671) - Jordan and Syria switch from +02/+03 with DST to year-round +03. * Update the ICU timezone data to 2022d, as 2022e isn't available yet * debian/tzdata.config: convert Europe/Uzhgorod and Europe/Zaporozhye into Europe/Kyiv. * debian/tzdata.templates: Remove Uzhgorod and Zaporozhye -- Benjamin Drung Wed, 12 Oct 2022 21:26:34 +0200 ** Changed in: tzdata (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1969671 Title: Misspelled Ukrainian cities in tzdata Status in tzdata package in Ubuntu: Fix Released Bug description: When user is prompted to choose a city in the region 'Europe' they have a choice of 4 cities in Ukraine: 23. Kiev -> should be Kyiv 46. Simferopol - > OK 54. Uzhgorod -> should be Uzhhorod 62. Zaporozhye -> should be Zaporizhzhia The 'should be' variant is the only correct transliteration from Ukrainian into English. Possible useful pieces of ubuntu-bug report (run in a headless ubuntu/latest docker image): DistroRelease: Ubuntu 20.04 Package: tzdata 2022a-0ubuntu0.20.04 Tags: focal PackageArchitecture: all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1969671/+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 1992692] Re: tzdata 2022e release
This bug was fixed in the package tzdata - 2022e-0ubuntu1 --- tzdata (2022e-0ubuntu1) kinetic; urgency=medium * New upstream releases (LP: #1992692): - Palestine transitions are now Saturdays at 02:00. This means 2022 falls back 10-29 at 02:00, not 10-28 at 01:00. - Simplify three Ukraine zones into one. (LP: #1969671) - Jordan and Syria switch from +02/+03 with DST to year-round +03. * Update the ICU timezone data to 2022d, as 2022e isn't available yet * debian/tzdata.config: convert Europe/Uzhgorod and Europe/Zaporozhye into Europe/Kyiv. * debian/tzdata.templates: Remove Uzhgorod and Zaporozhye -- Benjamin Drung Wed, 12 Oct 2022 21:26:34 +0200 ** Changed in: tzdata (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1992692 Title: tzdata 2022e release Status in tzdata package in Ubuntu: Fix Released Bug description: New timezone data, with the following timezones impacted: - Palestine transitions are now Saturdays at 02:00. This means 2022 falls back 10-29 at 02:00, not 10-28 at 01:00. - Simplify three Ukraine zones into one. - Jordan and Syria switch from +02/+03 with DST to year-round +03. icu update to 2022e: https://unicode- org.atlassian.net/browse/ICU-22178 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+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 1979352] Re: system frozen after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1979352] Re: system frozen after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1979352] Re: system frozen after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: acpid (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1979352] Re: system frozen after sleep
Maybe related to this https://github.com/mate-desktop/mate- desktop/issues/519 ** Bug watch added: github.com/mate-desktop/mate-desktop/issues #519 https://github.com/mate-desktop/mate-desktop/issues/519 -- 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/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1990742] Re: screen not consistently locking when lid is closed
** Tags removed: foundations-triage-discuss -- 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/1990742 Title: screen not consistently locking when lid is closed Status in systemd package in Ubuntu: Incomplete Bug description: I have GNOME configured to lock the screen when the screen is blanked, and to blank the screen when the lid is closed: org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank' org.gnome.desktop.screensaver lock-delay uint32 0 org.gnome.desktop.screensaver lock-enabled true This worked fine in Jammy: whenever my screen was unlocked and I closed my laptop lid, it locked immediately, i.e., if I immediately reopened my lid, the screen was locked. After having just upgraded to Kinetic, however, sometimes when I close the lid it locks as described above, and sometimes it just... doesn't, i.e., when I open the lid again the screen is unlocked and I can just keep working. I have been unable to determine what the factors are which control whether the screen locks when I close the lid. There is a moderate security implication here, as it's problematic for someone's screen not to lock when they think that it did. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 17:57:37 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1135 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990742/+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 1992692] Re: tzdata 2022e release
** Changed in: tzdata (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1992692 Title: tzdata 2022e release Status in tzdata package in Ubuntu: Fix Committed Bug description: New timezone data, with the following timezones impacted: - Palestine transitions are now Saturdays at 02:00. This means 2022 falls back 10-29 at 02:00, not 10-28 at 01:00. - Simplify three Ukraine zones into one. - Jordan and Syria switch from +02/+03 with DST to year-round +03. icu update to 2022e: https://unicode- org.atlassian.net/browse/ICU-22178 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1992692/+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 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
ifupdown is in universe these days, so I'll unsubscribe foundations. ** Tags removed: foundations-triage-discuss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Jammy: Triaged Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
Thanks! I didn't test it, but formally it LGTM. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync: Fix Released Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Jammy: Triaged Bug description: [Impact] This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime as being "newer" implying they would need to be transfered/sync'ed where in fact they are "uptodate". This breaks users' scripts depending on "is newer" to signal that files need to be sync'ed when in fact, they don't need to be. [Test Plan] Steps to reproduce: 1. Create a local file: $ touch foo 2. Check if rsync would transfer it using the --update option: $ rsync -avv --update foo . If the regression is present, "foo is newer" would be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is newer total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 61 bytes received 96 bytes 314.00 bytes/sec total size is 0 speedup is 0.00 ``` If the updated package is installed (from -proposed), "foo is uptodate" should be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is uptodate total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 60 bytes received 106 bytes 332.00 bytes/sec total size is 0 speedup is 0.00 ``` [Regression potential] The patch changes the behavior of --update so if something goes wrong, it could break backup/sync jobs. To mitiate that, manual testing of rsync with and without the --update option was done in addition to the quick [Test Plan] outlined above. Please note the patch restores the behavior from before version 3.2.3 and has been integrated by upstream in September 2021. It also is in Kinetic where no visible regression was observed. [Original description] rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. The bug was fixed upstream in June 2020: https://github.com/WayneD/rsync/issues/98 $ touch foo $ rsync --update --info=skip foo foo foo is newer<=== THIS IS NOT CORRECT - A file can't be newer than itself. Obviously a file should not be listed as newer than itself. Another way: $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1965076/+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 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
Hi, I can also confirm that fwupd Version 1.7.9-1~22.04.1 fixes this issue for jammy. After installing the patched version, the service starts and runs as expected. I'm sorry that I can not provide tests for focal, since I already updated all my machines.. Thank you all imker -- 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/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in OEM Priority Project: Confirmed Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Fix Committed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Won't Fix Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Fix Committed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
Here's a bit more information about the service failure: -- Logs begin at Sun 2022-09-25 00:05:05 UTC, end at Thu 2022-09-29 12:03:20 UTC. -- Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd-remount-fs[74]: mount: /: can't find LABEL=cloudimg-rootfs. Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd-remount-fs[59]: /bin/mount for / exited with exit status 1. Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'. Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd[1]: Failed to start Remount Root and Kernel File Systems. FAIL This makes me think it's bug 1576341 again. According to the git history, that patch was not carried in Ubuntu past 2019. I will try to find out if we ever attempted to upstream the change. ** Tags removed: foundations-triage-discuss ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
Thanks Paride for the feedback, here's a refreshed debdiff! ** Patch removed: "rsync_3.2.3-8ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+attachment/5623548/+files/rsync_3.2.3-8ubuntu4.debdiff ** Patch added: "rsync_3.2.3-8ubuntu3.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+attachment/5623978/+files/rsync_3.2.3-8ubuntu3.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync: Fix Released Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Jammy: Triaged Bug description: [Impact] This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime as being "newer" implying they would need to be transfered/sync'ed where in fact they are "uptodate". This breaks users' scripts depending on "is newer" to signal that files need to be sync'ed when in fact, they don't need to be. [Test Plan] Steps to reproduce: 1. Create a local file: $ touch foo 2. Check if rsync would transfer it using the --update option: $ rsync -avv --update foo . If the regression is present, "foo is newer" would be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is newer total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 61 bytes received 96 bytes 314.00 bytes/sec total size is 0 speedup is 0.00 ``` If the updated package is installed (from -proposed), "foo is uptodate" should be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is uptodate total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 60 bytes received 106 bytes 332.00 bytes/sec total size is 0 speedup is 0.00 ``` [Regression potential] The patch changes the behavior of --update so if something goes wrong, it could break backup/sync jobs. To mitiate that, manual testing of rsync with and without the --update option was done in addition to the quick [Test Plan] outlined above. Please note the patch restores the behavior from before version 3.2.3 and has been integrated by upstream in September 2021. It also is in Kinetic where no visible regression was observed. [Original description] rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. The bug was fixed upstream in June 2020: https://github.com/WayneD/rsync/issues/98 $ touch foo $ rsync --update --info=skip foo foo foo is newer<=== THIS IS NOT CORRECT - A file can't be newer than itself. Obviously a file should not be listed as newer than itself. Another way: $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1965076/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken
There was no change in the fonts-dejavu package between Focal -> Jammy. ** Also affects: gnome-font-viewer (Ubuntu) Importance: Undecided Status: New ** Changed in: fonts-dejavu (Ubuntu) Status: New => Invalid ** Tags removed: foundations-triage-discuss ** Tags added: jj-rls-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fonts-dejavu package in Ubuntu: Invalid Status in gnome-font-viewer package in Ubuntu: New Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken
I was unable to recreate this bug using these packages: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with additional characters (extra variants) ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME ** Attachment added: "Screenshot from 2022-10-13 08-26-26.png" https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+attachment/5623977/+files/Screenshot%20from%202022-10-13%2008-26-26.png ** Changed in: gnome-font-viewer (Ubuntu) Importance: Undecided => Low ** Tags removed: jj-rls-incoming ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fonts-dejavu package in Ubuntu: Invalid Status in gnome-font-viewer package in Ubuntu: New Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1969671] Re: Misspelled Ukrainian cities in tzdata
Fix committed in 2022e-0ubuntu1 ** Changed in: tzdata (Ubuntu) Status: New => Fix Committed ** Changed in: tzdata (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1969671 Title: Misspelled Ukrainian cities in tzdata Status in tzdata package in Ubuntu: Fix Committed Bug description: When user is prompted to choose a city in the region 'Europe' they have a choice of 4 cities in Ukraine: 23. Kiev -> should be Kyiv 46. Simferopol - > OK 54. Uzhgorod -> should be Uzhhorod 62. Zaporozhye -> should be Zaporizhzhia The 'should be' variant is the only correct transliteration from Ukrainian into English. Possible useful pieces of ubuntu-bug report (run in a headless ubuntu/latest docker image): DistroRelease: Ubuntu 20.04 Package: tzdata 2022a-0ubuntu0.20.04 Tags: focal PackageArchitecture: all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1969671/+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 1992472] Re: APT hooks do not respect the -q option
** Tags removed: foundations-triage-discuss -- 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/1992472 Title: APT hooks do not respect the -q option Status in apt package in Ubuntu: Triaged Bug description: ubuntu-advantage-tools recently used an APT Cli hook (AptCli::Hooks::Upgrade) to add a message to the output. We were asked in https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+bug/1992026/comments/9 to honor the -q (-qq, -qqq) option of APT upgrade, and hide the output. However, the hook does not expose this option, so there is nothing we can do from our side. APT could either treat those messages based on the "quietness" defined when running the command, or expose the flag somehow so we could configure our message to respect it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992472/+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 1990200] Re: goa-daemon crashed with SIGABRT
error tracker entry is https://errors.ubuntu.com/problem/595467fba803f55fea2dfef4bb4b3a77a787e18e ** Tags added: rls-kk-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990200/+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 1992822] Re: /usr/libexec/goa-daemon:6:g_assertion_message:g_assertion_message_expr:finish_call:rest_proxy_call_sync:get_identity_sync
*** This bug is a duplicate of bug 1990200 *** https://bugs.launchpad.net/bugs/1990200 ** This bug has been marked a duplicate of bug 1990200 goa-daemon crashed with SIGABRT -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1992822 Title: /usr/libexec/goa- daemon:6:g_assertion_message:g_assertion_message_expr:finish_call:rest_proxy_call_sync:get_identity_sync Status in gnome-online-accounts package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-online-accounts. This problem was most recently seen with package version 3.46.0-1, the problem page at https://errors.ubuntu.com/problem/595467fba803f55fea2dfef4bb4b3a77a787e18e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1992822/+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 1992822] [NEW] /usr/libexec/goa-daemon:6:g_assertion_message:g_assertion_message_expr:finish_call:rest_proxy_call_sync:get_identity_sync
*** This bug is a duplicate of bug 1990200 *** https://bugs.launchpad.net/bugs/1990200 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-online-accounts. This problem was most recently seen with package version 3.46.0-1, the problem page at https://errors.ubuntu.com/problem/595467fba803f55fea2dfef4bb4b3a77a787e18e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic kylin-22.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1992822 Title: /usr/libexec/goa- daemon:6:g_assertion_message:g_assertion_message_expr:finish_call:rest_proxy_call_sync:get_identity_sync Status in gnome-online-accounts package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-online-accounts. This problem was most recently seen with package version 3.46.0-1, the problem page at https://errors.ubuntu.com/problem/595467fba803f55fea2dfef4bb4b3a77a787e18e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1992822/+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 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date
** Tags removed: foundations-triage-discuss ** Tags added: foundations-todo -- 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/1992513 Title: apt will not install nvidia-driver-470-server if nvidia- driver-450-server is installed and out of date Status in apt package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Status in nvidia-graphics-drivers-470-server package in Ubuntu: New Bug description: apt/jammy apt will refuse to install nvidia-driver-470-server if nvidia-driver-450-server is installed *and* out of date. I can reproduce this by disabling all but the jammy release pocket, installing the old n-d-450-s from there, and then enabling updates and trying to install n-v-470-s (where a new n-d-450-s is available): # libnvidia-gl-450-server has an update available root@dannf-apt-jammy:/var/cache# apt install --dry-run libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes Reading package lists... Done Building dependency tree... Done 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: libnvidia-common-450-server : Conflicts: libnvidia-common libnvidia-common-470-server : Conflicts: libnvidia-common E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+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 1990200] Re: goa-daemon crashed with SIGABRT
Impact: I miss new events because I no longer get calendar notifications because the calendar does not sync anymore when that happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990200/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
Stumbled on this in Triage and I did a quick review of the debdiff (thanks for preparin it!). The patch cherry-picking LGTM, but I think we want ubuntu3.1 in the d/changelog version string. Also the DEP-3 headers could have a Bug: line pointing to the upstream bug [1]. [1] https://github.com/WayneD/rsync/issues/98 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync: Fix Released Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Jammy: Triaged Bug description: [Impact] This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime as being "newer" implying they would need to be transfered/sync'ed where in fact they are "uptodate". This breaks users' scripts depending on "is newer" to signal that files need to be sync'ed when in fact, they don't need to be. [Test Plan] Steps to reproduce: 1. Create a local file: $ touch foo 2. Check if rsync would transfer it using the --update option: $ rsync -avv --update foo . If the regression is present, "foo is newer" would be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is newer total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 61 bytes received 96 bytes 314.00 bytes/sec total size is 0 speedup is 0.00 ``` If the updated package is installed (from -proposed), "foo is uptodate" should be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is uptodate total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 60 bytes received 106 bytes 332.00 bytes/sec total size is 0 speedup is 0.00 ``` [Regression potential] The patch changes the behavior of --update so if something goes wrong, it could break backup/sync jobs. To mitiate that, manual testing of rsync with and without the --update option was done in addition to the quick [Test Plan] outlined above. Please note the patch restores the behavior from before version 3.2.3 and has been integrated by upstream in September 2021. It also is in Kinetic where no visible regression was observed. [Original description] rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. The bug was fixed upstream in June 2020: https://github.com/WayneD/rsync/issues/98 $ touch foo $ rsync --update --info=skip foo foo foo is newer<=== THIS IS NOT CORRECT - A file can't be newer than itself. Obviously a file should not be listed as newer than itself. Another way: $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1965076/+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 1992105] Re: missing httpform plugin for saslauthd
Hi Amit, Ubuntu 22.04 is currently sticking with version 2.1.27 + security and feature updates to maintain consistency and stability. Ubuntu 22.10, which is fully releasing soon, uses 2.1.28 though. The package will be actively maintained in 22.04 until 2027 but may not experience many version bumps. Ah I haven't activated ARM64 on the ppa, I'll do that now. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1992105 Title: missing httpform plugin for saslauthd Status in cyrus-sasl2 package in Ubuntu: In Progress Status in cyrus-sasl2 source package in Jammy: In Progress Status in cyrus-sasl2 source package in Kinetic: In Progress Bug description: Hi, we noticed missing httpform plugin for saslauthd. We are migrating from Centos. == On Centos (Notice the httpform at the end) /usr/sbin/saslauthd -v saslauthd 2.1.26 authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap httpform == On Ubuntu jammy /usr/sbin/saslauthd -v saslauthd 2.1.27 authentication mechanisms: sasldb getpwent kerberos5 pam rimap shadow ldap == Potential fix add the "--enable-httpform" flag to the sasl2-bin package build ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: sasl2-bin 2.1.27+dfsg2-3ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Oct 6 14:54:13 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: cyrus-sasl2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1992105/+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 1991553] Re: can't add a private PPA
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- 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/1991553 Title: can't add a private PPA Status in software-properties package in Ubuntu: Confirmed Bug description: As per today's discussion in ~is : add-apt-repository has a bug when adding a private PPA. Quoting ~cjwatson : === It asks Launchpad for all your personal archive subscriptions _that have tokens_. But `Person:+archivesubscriptions` also shows subscriptions without tokens - the token is generated when you click on Viewt here for the first time. Instead, `add-apt-repository` should call `getArchiveSubscriptionURL` (not `getArchiveSubscriptionURLs`) for the archive it's interested in. That generates tokens on-demand. Either it will get an HTTP 401, or it will get a URL which it can parse for the username and password. === Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1991553/+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 1990200] Re: goa-daemon crashed with SIGABRT
** Changed in: gnome-online-accounts (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990200/+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 1990200] Re: goa-daemon crashed with SIGABRT
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990200/+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 1992504] Re: Update libsoup to 2.74.3
This bug was fixed in the package libsoup2.4 - 2.74.3-1 --- libsoup2.4 (2.74.3-1) unstable; urgency=medium * New upstream release (LP: #1992504) * Drop 3 test patches applied in new release -- Jeremy Bicha Tue, 11 Oct 2022 15:28:32 -0400 ** Changed in: libsoup2.4 (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 libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1992504 Title: Update libsoup to 2.74.3 Status in libsoup2.4 package in Ubuntu: Fix Released Bug description: New upstream bugfix release in the stable libsoup 2.74 series https://gitlab.gnome.org/GNOME/libsoup/-/blob/2.74.3/NEWS https://gitlab.gnome.org/GNOME/libsoup/-/compare/2.74.2...2.74.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1992504/+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 329455] Re: canberra-gtk-pl seg fault
Once I have faced this issue and I searched on google and got the solution. So you should try on google Regards https://almotion.net//";>Alight Motion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/329455 Title: canberra-gtk-pl seg fault Status in libcanberra package in Ubuntu: New Bug description: Gnome crashed on me and took me back to the login prompt. Messages file shows this: Feb 14 10:45:03 ubuntudesktop bonobo-activation-server (reece-7936): could not associate with desktop session: Failed to connect to socket /tmp/dbus-dXvoGakMY9: Connection refused Feb 14 10:45:04 ubuntudesktop kernel: [829984.836630] mtrr: type mismatch for e000,1000 old: write-back new: write-combining Feb 14 10:45:23 ubuntudesktop pulseaudio[8049]: ltdl-bind-now.c: Failed to find original dlopen loader. Feb 14 10:45:23 ubuntudesktop pulseaudio[8051]: pid.c: Stale PID file, overwriting. Feb 14 10:45:23 ubuntudesktop pulseaudio[8051]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted Feb 14 10:45:23 ubuntudesktop pulseaudio[8051]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted Feb 14 10:45:33 ubuntudesktop kernel: [830013.327147] canberra-gtk-pl[8099]: segfault at 929dcd0 ip b727584d sp b7012f10 error 6 in libpulse.so.0.4.1[b7236000+4e000] I have no idea what else to provide - let me know and I'll provide it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/329455/+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] new apparmor features for 3.0.7
** Changed in: apparmor (Ubuntu) Status: Triaged => Fix Released -- 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] new apparmor features for 3.0.7 Status in apparmor package in Ubuntu: Fix Released Bug description: We propose two new features for 3.0.7 Apparmor: 1. parser support for user namespace mediation. Since the last kernel update with commit https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next&id=30bce26855c9171f8dee74d93308fd506730c914 Ubuntu 22.10 mediates user namespaces which allows for confined applications to have unprivileged user namespace creation, instead of disabling it completely. If we want applications to have this ability, then we need to add support on the parser, which is a feature we are introducing. Bug 1990064 is an example caused by this. 2. userspace support for posix message queue mediation Kernel also has POSIX message queue mediation with commit https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master- next&id=44f28e2ccee2000c7da971876dd003d38a8232d8 which indicates that if admins want to allow legitimate use of POSIX message queues, then they will need the support of userspace tools. We are also adding a fix for Bug 1990692 which will make the AppArmor profiles for samba to be up to date with upstream. TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[1] for AppArmor and the extensive QA Regression Tests[2] 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/~georgiag/+archive/ubuntu/apparmor-kinetic-ffe, build logs can be found on Launchpad at: https://launchpad.net/~georgiag/+archive/ubuntu/test2/+build/24518253 for amd64 DEBDIFF The debdiff can be found in the PPA: https://launchpadlibrarian.net/626954017/apparmor_3.0.7-1ubuntu1_3.0.7-1ubuntu2.diff.gz INSTALL / UPGRADE LOG The apt upgrade log is attached in: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5620824/+files/apparmor-3.0.7-1ubuntu2-apt-upgrade.log [1] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [2] 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 1972654] Re: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable
ACK from the security team to sync from unstable. Please make sure the policy overrides in policykit-desktop-privileges still work or are converted to their equivalent JS before doing so. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental
policykit-1 121+compat0.1-5 is now in Debian Unstable. Could I get a clear answer from the Ubuntu Security Team if this is acceptable to autosync when Ubuntu 23.04 development opens? ** Tags added: block-proposed ** Summary changed: - [security review] Sync policykit-1 0.120-6 (main) from Debian experimental + [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable ** Description changed: - Please sync policykit-1 0.120-6 (main) from Debian experimental + Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for + Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: - https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6 + https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. It appears the Debian maintainer is considering switching Debian to the updated version in time for the next Debian Stable release (so uploading to unstable later this year). - - My requested deadline is August 25, Ubuntu 22.10 Feature Freeze. ** Description changed: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. - - It appears the Debian maintainer is considering switching Debian to the - updated version in time for the next Debian Stable release (so uploading - to unstable later this year). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1971712] Re: Add support for Intel DG2
you need to use i915.force_probe until maybe 6.2, but other than that it works quite well for the most part even in 6.0 -- 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/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: In Progress Status in mesa source package in Jammy: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1992667] Re: Application windows invisible (on DG2 graphics)
I've managed to reproduce this bug on an Arc A380 and Arc A770 GPU. I've attached the requested lspci output for the A770. Ubuntu 22.04 has already received a mesa update with backported patches for DG2 support: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1971712 I haven't tried 22.10 yet, but I will do so in the coming days. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+attachment/5623860/+files/lspci.txt -- 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/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
Indeed there are no crashes after version 42.x -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: Fix Released Status in gtk+3.0 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1989803] Re: Adjust apport for the new Ubuntu debuginfod service
** Tags added: cetest -- 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/1989803 Title: Adjust apport for the new Ubuntu debuginfod service Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: With the new Ubuntu debuginfod service (https://debuginfod.ubuntu.com), and with the prospect of having the system automatically fetch debuginfo from the internet without user intervention, it is necessary to adjust apport to cope with this scenario. I had a conversation with bdmurray and he was concerned that having a debuginfod-enabled GDB generate the corefiles that are eventually submitted to Ubuntu can be a problem. My proposed solution is to disable GDB's debuginfod support when collecting the corefile. This should keep things as is and not disturb the retrace service. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1989803/+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
