[Touch-packages] [Bug 2052324] Re: Gnome not possible run from wsl
It looks like the 'modesetting' Xorg driver is at fault, if we trust the log message suggesting /dev/dri/card0 exists. Please run: sudo apt install drm-info sudo drm_info > drminfo.txt and then attach the resulting text file here. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Summary changed: - Gnome not possible run from wsl + Xorg not possible to run from WSL -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2052324 Title: Xorg not possible to run from WSL Status in xorg-server package in Ubuntu: Incomplete Bug description: there is error xorg.conf (EE) no screens found(EE) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 5.15.133.1-microsoft-standard-WSL2 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: ** (process:4174): WARNING **: 20:44:25.586: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject Error registering local authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject Date: Fri Feb 2 20:44:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lspci-vt: -+-[a214:00]---00.0 Red Hat, Inc. Virtio console \-[:00]- Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 480M ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\initrd.img WSL_ROOT_INIT=1 panic=-1 nr_cpus=4 bonding.max_bonds=0 dummy.numdummies=0 fb_tunnels=none console=hvc0 debug pty.legacy_count=0 ProcModules: SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: ** (process:4187): WARNING **: 20:44:25.696: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject Error registering local authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2052324/+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 2052138] Re: After screen turns off and you turn it back on, weird corruption
** Tags added: amdgpu ** Tags added: flicker suspend-resume ** Summary changed: - After screen turns off and you turn it back on, weird corruption + [amdgpu] After screen turns off and you turn it back on, weird corruption ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2052138 Title: [amdgpu] After screen turns off and you turn it back on, weird corruption Status in linux package in Ubuntu: New Bug description: When the laptop main screen turns off due to inactivity and then you turn it back on, there is a weird corruption. Restart helps. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28 15:37:48 UTC 2023 GCC version: ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 2 10:14:53 2024 DistUpgraded: Fresh install DistroCodename: mantic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:3a58] InstallationDate: Installed on 2024-01-12 (21 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash amd_pstate=guided vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.60 dmi.modalias: dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052138/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
Hi Krister, Fascinating. I'm in New Zealand, so I use ap-southeast-2 in Sydney, Australia for all my instances, and I never gave it any thought that this could depend on how busy EBS is on the availability zone. I'll move my instances to us-west-2. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: In Progress Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: In Progress Status in e2fsprogs source package in Jammy: In Progress Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: In Progress Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2052405] [NEW] Translation error in policykit-1 package
Public bug reported: policykit-1 package have translation error. https://translations.launchpad.net/ubuntu/jammy/+source/policykit-1/+pots/polkit-1/ko/+translate `$(program)'을(를) 관리자 권한으로 실행려면 인증이 필요합니다. -> `$(program)'을(를) 관리자 권한으로 실행하려면 인증이 필요합니다. `$(program)'을(를) $(user) 계정으로 실행려면 인증이 필요합니다. -> `$(program)'을(를) $(user) 계정으로 실행하려면 인증이 필요합니다. ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New -- 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/2052405 Title: Translation error in policykit-1 package Status in policykit-1 package in Ubuntu: New Bug description: policykit-1 package have translation error. https://translations.launchpad.net/ubuntu/jammy/+source/policykit-1/+pots/polkit-1/ko/+translate `$(program)'을(를) 관리자 권한으로 실행려면 인증이 필요합니다. -> `$(program)'을(를) 관리자 권한으로 실행하려면 인증이 필요합니다. `$(program)'을(를) $(user) 계정으로 실행려면 인증이 필요합니다. -> `$(program)'을(를) $(user) 계정으로 실행하려면 인증이 필요합니다. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2052405/+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 2052399] Re: kbd is not built for i386
Tried `apt source --build kbd:i386` but it fails. /bin/ld: kdmapop.o:/tmp/chroots/kbd-1.15.5/src/version.h:8: multiple definition of `progname'; setfont.o:/tmp/chroots/kbd-1.15.5/src/version.h:8: first defined here /bin/ld: kdfontop.o:/tmp/chroots/kbd-1.15.5/src/version.h:8: multiple definition of `progname'; setfont.o:/tmp/chroots/kbd-1.15.5/src/version.h:8: first defined here collect2: error: ld returned 1 exit status make[2]: *** [Makefile:798: setfont] Error 1 make[2]: Leaving directory '/tmp/chroots/kbd-1.15.5/src' make[1]: *** [debian/rules:42: override_dh_auto_build] Error 2 make[1]: Leaving directory '/tmp/chroots/kbd-1.15.5' make: *** [debian/rules:27: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 E: Build command ‘cd kbd-1.15.5 && dpkg-buildpackage -b -uc’ failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2052399 Title: kbd is not built for i386 Status in kbd package in Ubuntu: New Bug description: kbd is not built for i386 which leads to Bug #1463840 dpkg: dependency problems prevent configuration of console-setup-linux: console-setup-linux depends on kbd (>= 0.99-12) | console-tools (>= 1:0.2.3-16); however: Package kbd is not installed. Package console-tools is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2052399/+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 2052399] [NEW] kbd is not built for i386
Public bug reported: kbd is not built for i386 which leads to Bug #1463840 dpkg: dependency problems prevent configuration of console-setup-linux: console-setup-linux depends on kbd (>= 0.99-12) | console-tools (>= 1:0.2.3-16); however: Package kbd is not installed. Package console-tools is not installed. ** Affects: kbd (Ubuntu) Importance: Undecided Status: New ** Tags: i386 jammy noble ** Attachment added: "debootstrap.log" https://bugs.launchpad.net/bugs/2052399/+attachment/5744624/+files/debootstrap.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2052399 Title: kbd is not built for i386 Status in kbd package in Ubuntu: New Bug description: kbd is not built for i386 which leads to Bug #1463840 dpkg: dependency problems prevent configuration of console-setup-linux: console-setup-linux depends on kbd (>= 0.99-12) | console-tools (>= 1:0.2.3-16); however: Package kbd is not installed. Package console-tools is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2052399/+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 2032577] Re: xz crashed with SIGSEGV in lzma_lzma_optimum_normal
Hello, RAM: not ECC, 4x32GB @2133MHz, nothing fancy. It has been happening regularly, often enough to drive me to set up an account here and report it, however it does happen any more. At some point it has stopped. The pc in question is still using the same kernel and the same version of liblzma. I think that at some point after I reported the bug I have switched from wayland to x11, however I may be misremembering. It could also be an irrelevant change (not sure what the link would be), but I will try to verify and switch back to wayland this week and see if the error returns. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2032577 Title: xz crashed with SIGSEGV in lzma_lzma_optimum_normal Status in xz-utils package in Ubuntu: New Bug description: xz segfaults. More details in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379 From Dmesg.txt on that report [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000] ProblemType: Crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 ExecutablePath: /usr/bin/xz ExecutableTimestamp: 1649422298 InstallationDate: Installed on 2021-04-09 (863 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xz-utils 5.2.5-2ubuntu1 ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9 ProcCwd: / ProcEnviron: LC_CTYPE=C.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 SegvAnalysis: Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d PC (0x7f9b3f780c1a) ok source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 0x7f9a90021000-0x7f9a9400 ---p None destination "%r10d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading VMA None Signal: 11 SourcePackage: xz-utils Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago) UserGroups: N/A StacktraceTop: bt_find_func (len_limit=64, pos=9137198, cur=0x7f9a943edc3d "", cur_match=4194304, depth=24, son=son@entry=0x7f9a8afbd010, cyclic_pos=748589, cyclic_size=8388609, matches=0x7f9adc0ec324, len_best=11) at ../../../../src/liblzma/lz/lz_encoder_mf.c:483 lzma_mf_bt4_find (mf=0x7f9a9c70, matches=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:721 lzma_mf_find (mf=mf@entry=0x7f9a9c70, count_ptr=count_ptr@entry=0x7f9adc0ecb94, matches=matches@entry=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:28 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:846 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2032577/+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 2032577] Re: xz crashed with SIGSEGV in lzma_lzma_optimum_normal
Hi, correction to the above. The issue does NOT happen any more. It has been happening regularly, often enough to drive me to set up an account here and report it, however it does **NOT** happen any more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2032577 Title: xz crashed with SIGSEGV in lzma_lzma_optimum_normal Status in xz-utils package in Ubuntu: New Bug description: xz segfaults. More details in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379 From Dmesg.txt on that report [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000] ProblemType: Crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 ExecutablePath: /usr/bin/xz ExecutableTimestamp: 1649422298 InstallationDate: Installed on 2021-04-09 (863 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xz-utils 5.2.5-2ubuntu1 ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9 ProcCwd: / ProcEnviron: LC_CTYPE=C.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 SegvAnalysis: Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d PC (0x7f9b3f780c1a) ok source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 0x7f9a90021000-0x7f9a9400 ---p None destination "%r10d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading VMA None Signal: 11 SourcePackage: xz-utils Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago) UserGroups: N/A StacktraceTop: bt_find_func (len_limit=64, pos=9137198, cur=0x7f9a943edc3d "", cur_match=4194304, depth=24, son=son@entry=0x7f9a8afbd010, cyclic_pos=748589, cyclic_size=8388609, matches=0x7f9adc0ec324, len_best=11) at ../../../../src/liblzma/lz/lz_encoder_mf.c:483 lzma_mf_bt4_find (mf=0x7f9a9c70, matches=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:721 lzma_mf_find (mf=mf@entry=0x7f9a9c70, count_ptr=count_ptr@entry=0x7f9adc0ecb94, matches=matches@entry=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:28 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:846 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2032577/+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 1784135] Re: libicu-dev and libicu-dev:i386 conflict with each other
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1784135 Title: libicu-dev and libicu-dev:i386 conflict with each other Status in icu package in Ubuntu: Confirmed Status in icu package in Debian: Fix Released Bug description: Release is bionic (18.04.1) When trying to install libicu-dev and libicu-dev:i386 together in bionic, the conflict with each other. It is expected that these two libs can be installed together in one system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1784135/+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 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64
** Changed in: cpio (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cpio in Ubuntu. https://bugs.launchpad.net/bugs/2052295 Title: autopkgtest unshare-qemuwrapper failing on amd64 Status in cpio package in Ubuntu: Fix Released Status in sbuild package in Ubuntu: New Status in cpio source package in Noble: Fix Released Status in sbuild source package in Noble: New Status in cpio package in Debian: Fix Released Bug description: While watching Noble openssh migration, I saw this test failing and marking amd64 as regression. Log : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz Relevant part of the log: 1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/ 1565s Setting up cpio (2.15+dfsg-1) ... 1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist 1565s dpkg: error processing package cpio (--configure): 1565s installed cpio package post-installation script subprocess returned error exit status 2 It can be reproduced locally, too. The most recent test working is from 01/08/2024: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz The cpio version in the immediately log above is lower. The same (working) part is: 2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/ 2188s Setting up cpio (2.14+dfsg-1) ... 2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto mode cpio diff : https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+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 2052328] Re: openssh-client encounters MAC algo issue with EL8
Hi, Thanks for reporting this issue. I can't seem to reproduce it though with Oracle Linux v8 running openssh-server-8.0p1-17.el8.x86_64 and an Ubuntu 22.04 client running 1:8.9p1-3ubuntu0.6. Could you perhaps give me a bit more details on how I could reproduce this? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2052328 Title: openssh-client encounters MAC algo issue with EL8 Status in openssh package in Ubuntu: New Bug description: Ubuntu 22.04 system connecting to an Oracle Linux v8 host. The following error occurs regardless of the the MACs specified (or not) in sshd_config: Corrupted MAC on input. ssh_dispatch_run_fatal: Connection to XX.XX.XX.XX port 22: message authentication code incorrect Presumably, this may happen on any RHEL v8 variant. Note that connecting to Enterprise Linux v7 work as well as other Ubuntu hosts. Downgrading to previous version of openssh-client fixes issue. apt install openssh-client=1:8.9p1-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2052328/+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 2016303] Re: Rebuild NSS with support for system-wide config file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nss (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/2016303 Title: Rebuild NSS with support for system-wide config file Status in nss package in Ubuntu: Confirmed Bug description: NSS should be rebuilt with this patch: diff --git a/debian/libnss3.dirs b/debian/libnss3.dirs new file mode 100644 index ..0f796964 --- /dev/null +++ b/debian/libnss3.dirs @@ -0,0 +1 @@ +etc/nss diff --git a/debian/rules b/debian/rules index 5ab1ced0..51bee160 100755 --- a/debian/rules +++ b/debian/rules @@ -128,6 +128,8 @@ override_dh_auto_build: NSS_USE_SYSTEM_SQLITE=1 \ NSS_ENABLE_ECC=1 \ CHECKLOC= \ + POLICY_FILE=pkcs11.txt \ + POLICY_PATH=/etc/nss \ $(TOOLCHAIN) override_dh_auto_clean: The directory could be another one, of course. This will allow us to create a system-wide /etc/nss/pkcs11.txt file which could load the NSS policy module. The upstream documentation is quite poor and outdated, unfortunately: https://firefox-source-docs.mozilla.org/security/nss/legacy/nss_config_options/ https://firefox-source-docs.mozilla.org/security/nss/legacy/pkcs11/module_specs/index.html The current source code is the best documentation, and has a ton of tests that show how to use the policy module: - allow/disallow options: https://git.launchpad.net/ubuntu/+source/nss/tree/nss/lib/pk11wrap/pk11pars.c#n144 - versions and key sizes: https://git.launchpad.net/ubuntu/+source/nss/tree/nss/lib/pk11wrap/pk11pars.c#n437 - other qualifiers for algorithms (which types of signatures): https://git.launchpad.net/ubuntu/+source/nss/tree/nss/lib/pk11wrap/pk11pars.c#n451 - tons of policy tests: https://git.launchpad.net/ubuntu/+source/nss/tree/nss/tests/ssl/sslpolicy.txt and https://git.launchpad.net/ubuntu/+source/nss/tree/nss/tests/policy Here is a sample /etc/nss/pkcs11.txt which enables the policy module with certain values: library= name=Policy NSS=flags=policyOnly,moduleDB config="disallow=ALL allow=HMAC-SHA256:HMAC-SHA1:HMAC-SHA384:HMAC-SHA512:CURVE25519:SECP256R1:SECP384R1:SECP521R1:aes256-gcm:chacha20-poly1305:aes256-cbc:aes128-gcm:aes128-cbc:SHA256:SHA384:SHA512:SHA224:ECDHE-RSA:ECDHE-ECDSA:RSA:DHE-RSA:ECDSA:RSA-PSS:RSA-PKCS:tls-version-min=tls1.2:dtls-version-min=dtls1.2:DH-MIN=2048:DSA-MIN=2048:RSA-MIN=2048" The same config snippet can of course be used in ~/.pki/nssdb/pkcs11.txt or in any of the other many places we have a pkcs11.txt file on the system (hence the need for this build option: to have just one place): - firefox: ~/snap/firefox/common/.mozilla/firefox/pqx65eu1.default/pkcs11.txt - thunderbid: ~/.thunderbird/6mxs87xg.default-release/pkcs11.txt - chrome and system-provided libnss3: ~/.pki/nssdb/pkcs11.txt Note thunderbird ships its own libnss3 (zomg), and would not be affected by this build change (unless it's done in the thunderbird source package too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/2016303/+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