[Bug 2065721] [NEW] PCI/MSI: Prevent MSI hardware interrupt number truncation
Public bug reported: While calculating the hardware interrupt number for a MSI interrupt, the higher bits (i.e. from bit-5 onwards a.k.a domain_nr >= 32) of the PCI domain number gets truncated because of the shifted value casting to return type of pci_domain_nr() which is 'int'. This for example is resulting in same hardware interrupt number for devices 0019:00:00.0 and 0039:00:00.0. To address this cast the PCI domain number to 'irq_hw_number_t' before left shifting it to calculate the hardware interrupt number. Please note that this fixes the issue only on 64-bit systems and doesn't change the behavior for 32-bit systems i.e. the 32-bit systems continue to have the issue. Since the issue surfaces only if there are too many PCIe controllers in the system which usually is the case in modern server systems and they don't tend to run 32-bit kernels. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065721 Title: PCI/MSI: Prevent MSI hardware interrupt number truncation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2065721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064549] [NEW] pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin permission before access.")
Public bug reported:
The controller has several register bits describing access control
information for a given GPIO pin. When SCR_SEC_[R|W]EN is unset, it
means we have full read/write access to all the registers for given GPIO
pin. When SCR_SEC[R|W]EN is set, it means we need to further check the
accompanying SCR_SEC_G1[R|W] bit to determine read/write access to all
the registers for given GPIO pin.
This check was previously declaring that a GPIO pin was accessible
only if either of the following conditions were met:
- SCR_SEC_REN + SCR_SEC_WEN both set
or
- SCR_SEC_REN + SCR_SEC_WEN both set and
SCR_SEC_G1R + SCR_SEC_G1W both set
Update the check to properly handle cases where only one of
SCR_SEC_REN or SCR_SEC_WEN is set.
** Affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064549
Title:
pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin
permission before access.")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2064549/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039117] Re: Intermittent problem accessing TPM during 22.04 boot
I encountered the same issue recently and attempted to build systemd from source and patch the retry behavior from #24906, but I failed to make it work. Instead, I modified systemd-cryptsetup-generator to include retry behavior into the generated unit files for the encrypted volumes, which has worked for me. I've written up the details here: https://gist.github.com/bnabholz/86e4a6a8a8af9b66fff121e8a7a053fe It is a little hacky but works for me, until I can upgrade to 24.04 which will have a systemd that contains the proper fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039117 Title: Intermittent problem accessing TPM during 22.04 boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2039117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063461] [NEW] Perf-stat tool does not support ipc and ipc_rate monitoring on NVIDIA Grace system
Public bug reported: PROBLEM: While trying to monitor the ipc group for using perf-stat tool, despite it being supported, I get the following errors: $ sudo perf list | grep ipc ipc ipc_rate retired_ipc spec_ipc $ sudo -S perf stat -a -M ipc -- sudo -S stress-ng --cpu 0 -t 10s Error: The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (instructions). /bin/dmesg | grep -i perf may provide additional information. $ sudo -S perf stat -a -M ipc_rate -- sudo -S stress-ng --cpu 0 -t 10s Error: The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (instructions). /bin/dmesg | grep -i perf may provide additional information. However, I can get the groups retired_ipc and spec_ipc to work: $ sudo -S perf stat -a -M retired_ipc -- sudo -S stress-ng --cpu 0 -t 10s Value 0 contains non-numeric: ' ' Performance counter stats for 'system wide': 96,818,964 INST_RETIRED # 0.58 retired_ipc 166,601,455 CPU_CYCLES 0.013516186 seconds time elapsed $ sudo -S perf stat -a -M spec_ipc -- sudo -S stress-ng --cpu 0 -t 10s Value 0 contains non-numeric: ' ' Performance counter stats for 'system wide': 91,053,297 INST_SPEC# 0.58 spec_ipc 156,558,810 CPU_CYCLES 0.009877355 seconds time elapsed SOLUTION: Please accept the pull request which cherry-picks the following two upstream commits: d43f5491210197196458c1454f2be0eb66d3e4d1 perf vendor events arm64: Update stall_slot workaround for N2 r0p3 4473949074c35072f598bd525ae51d5455f05745 perf vendor events arm64: Update N2 and V2 metrics and events using Arm telemetry repo ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063461 Title: Perf-stat tool does not support ipc and ipc_rate monitoring on NVIDIA Grace system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2063461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
This does appear to fix the issue for me on 22.4.04 LTS sudo add-apt-repository ppa:vanvugt/mutter sudo apt update Then upgrade mutter-common, libmutter-10-0 and gir1.1-mutter-10 (I'm not certain if all 3 of these are required or not). This will get you version 42.9-0ubuntu7 Reboot !! (required) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061900] Re: apply NVIDIA patches April 6-16, 2024
** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061900 Title: apply NVIDIA patches April 6-16, 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2061900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061900] [NEW] apply NVIDIA patches April 6-16, 2024
Public bug reported: Apply NVIDIA patches April 6-16, 2024: NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3115016 NVIDIA: SAUCE: enable handling of macronix block protection https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3114006 PCI: dwc: Restore MSI Receiver mask during resume https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3116302 ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061900 Title: apply NVIDIA patches April 6-16, 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2061900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048942] Re: Openvswitch matching broken for nat packets in the related state
Fixed by linux 6.5.0-27.28 ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048942 Title: Openvswitch matching broken for nat packets in the related state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060327] [NEW] Reapply the linux-nvidia kernel config options from the 5.15 and 6.5 kernels
Public bug reported: There are a number of configuration options that were set in the 5.15. and 6.5 nvidia kernels. When the 6.8 based linux-nvidia kernel was created those config options were not brought forward. This patch set brings them into the 6.8 kernel. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060327 Title: Reapply the linux-nvidia kernel config options from the 5.15 and 6.5 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2060327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060337] [NEW] apply NVIDIA patches Mar 22 - April 5, 2024
Public bug reported: NVIDIA patches Mar 22 - April 5, 2024. NVIDIA tracking details soc/tegra: fuse: Remove security_mode fuse from keepout list https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107228 soc/tegra: fuse: Update Tegra234 nvmem keepout list https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107227 arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107255 arm64: defconfig: Enable DMATEST https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3105125 PCI: tegra194: Fix probe path for Endpoint mode https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3104622 arm64: configs: enable hidraw https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3103367 ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060337 Title: apply NVIDIA patches Mar 22 - April 5, 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2060337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059814] [NEW] Enable GDS in the 6.8 based linux-nvidia kernel
Public bug reported: GDS enables a direct data path for direct memory access (DMA) transfers between GPU memory and storage, which avoids a bounce buffer through the CPU. This direct path increases system bandwidth and decreases the latency and utilization load on the CPU. This functionality has been enabled in all previous kernel versions and needs to be in this kernel so there is no loss of functionality for users. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059814 Title: Enable GDS in the 6.8 based linux-nvidia kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2059814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059178] Re: Pull request to fully enable nvidia-fs NVMe support
** Changed in: linux-nvidia-6.5 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059178 Title: Pull request to fully enable nvidia-fs NVMe support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2059178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059178] [NEW] Pull request to fully enable nvidia-fs NVMe support
Public bug reported: This pull request addresses a missing patch which fully enables GDS functionality using NVMe devices. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059178 Title: Pull request to fully enable nvidia-fs NVMe support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2059178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058706] [NEW] Tegra234 SD card corruption after rebooting some number of times
Public bug reported: The SD card is being observed to get corrupted after some number of reboots, e.g. often in the neighborhood of 10-50 iterations. ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058706 Title: Tegra234 SD card corruption after rebooting some number of times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058550] [NEW] apply nvidia-tegra patches 2024 Mar 9-20
Public bug reported: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra and linux-nvida-tegra-igx). ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058550 Title: apply nvidia-tegra patches 2024 Mar 9-20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056498] Re: Kernel crash in amd gpu driver
The above crash was happening with large downloads of img files or git clones of large repositories (Ubuntu kernels) over wifi. I have changed to hard wired ethernet and I've not been able to reproduce it. With Wifi it's been very reproduceable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056498 Title: Kernel crash in amd gpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2056498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056594] [NEW] apply nvidia-tegra patches 2024 Mar 8
Public bug reported: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra and linux-nvida-tegra-igx). ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056594 Title: apply nvidia-tegra patches 2024 Mar 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056498] [NEW] Kernel crash in amd gpu driver
Public bug reported: Mar 7 19:07:10 ripper kernel: [9.873519] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-YpKOvT/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4 Mar 7 19:07:10 ripper kernel: [9.873531] index 7 is out of range for type 'ATOM_Polaris_SCLK_Dependency_Record [1]' Mar 7 19:07:10 ripper kernel: [9.873538] CPU: 4 PID: 849 Comm: systemd-udevd Not tainted 6.5.0-17-generic #17~22.04.1-Ubuntu Mar 7 19:07:10 ripper kernel: [9.873542] Hardware name: LENOVO 30E1S3VV00/1046, BIOS S07KT45A 01/20/2022 Mar 7 19:07:10 ripper kernel: [9.873544] Call Trace: Mar 7 19:07:10 ripper kernel: [9.873545] Mar 7 19:07:10 ripper kernel: [9.873547] dump_stack_lvl+0x48/0x70 Mar 7 19:07:10 ripper kernel: [9.873551] dump_stack+0x10/0x20 Mar 7 19:07:10 ripper kernel: [9.873554] __ubsan_handle_out_of_bounds+0xc6/0x110 Mar 7 19:07:10 ripper kernel: [9.873560] smu7_get_pp_table_entry_callback_func_v1+0x9b7/0xa00 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.873897] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.873900] ? vi_pcie_rreg+0x6e/0x90 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874187] ? __pfx_smu7_get_pp_table_entry_callback_func_v1+0x10/0x10 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874515] get_powerplay_table_entry_v1_0+0xf8/0x490 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874842] smu7_get_pp_table_entry_v1+0x41/0x4c0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875169] smu7_get_pp_table_entry+0x3d/0x50 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875495] psm_init_power_state_table+0x161/0x250 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875826] hwmgr_hw_init+0xe3/0x1e0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876150] pp_hw_init+0x16/0x50 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876484] amdgpu_device_ip_init+0x48d/0x960 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876749] amdgpu_device_init+0x9a2/0x1150 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877014] amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877278] amdgpu_pci_probe+0x182/0x450 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877541] local_pci_probe+0x47/0xb0 Mar 7 19:07:10 ripper kernel: [9.877545] pci_call_probe+0x55/0x190 Mar 7 19:07:10 ripper kernel: [9.877550] pci_device_probe+0x84/0x120 Mar 7 19:07:10 ripper kernel: [9.877553] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.877557] really_probe+0x1cc/0x430 Mar 7 19:07:10 ripper kernel: [9.877560] __driver_probe_device+0x8c/0x190 Mar 7 19:07:10 ripper kernel: [9.877563] driver_probe_device+0x24/0xd0 Mar 7 19:07:10 ripper kernel: [9.877566] __driver_attach+0x10b/0x210 Mar 7 19:07:10 ripper kernel: [9.877569] ? __pfx___driver_attach+0x10/0x10 Mar 7 19:07:10 ripper kernel: [9.877572] bus_for_each_dev+0x8d/0xf0 Mar 7 19:07:10 ripper kernel: [9.877576] driver_attach+0x1e/0x30 Mar 7 19:07:10 ripper kernel: [9.877579] bus_add_driver+0x127/0x240 Mar 7 19:07:10 ripper kernel: [9.877583] driver_register+0x5e/0x130 Mar 7 19:07:10 ripper kernel: [9.877586] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877849] __pci_register_driver+0x62/0x70 Mar 7 19:07:10 ripper kernel: [9.877852] amdgpu_init+0x69/0xff0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.878111] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878114] do_one_initcall+0x5e/0x340 Mar 7 19:07:10 ripper kernel: [9.878120] do_init_module+0x68/0x260 Mar 7 19:07:10 ripper kernel: [9.878123] load_module+0xb85/0xcd0 Mar 7 19:07:10 ripper kernel: [9.878128] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878131] ? security_kernel_post_read_file+0x75/0x90 Mar 7 19:07:10 ripper kernel: [9.878136] init_module_from_file+0x96/0x100 Mar 7 19:07:10 ripper kernel: [9.878139] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878142] ? init_module_from_file+0x96/0x100 Mar 7 19:07:10 ripper kernel: [9.878149] idempotent_init_module+0x11c/0x2b0 Mar 7 19:07:10 ripper kernel: [9.878155] __x64_sys_finit_module+0x64/0xd0 Mar 7 19:07:10 ripper kernel: [9.878159] do_syscall_64+0x5b/0x90 Mar 7 19:07:10 ripper kernel: [9.878161] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878164] ? ksys_mmap_pgoff+0x120/0x270 Mar 7 19:07:10 ripper kernel: [9.878167] ? __secure_computing+0x89/0xf0 Mar 7 19:07:10 ripper kernel: [9.878170] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878173] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878176] ? exit_to_user_mode_prepare+0x30/0xb0 Mar 7 19:07:10 ripper kernel: [9.878179] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878181] ? syscall_exit_to_user_mode+0x37/0x60 Mar 7
[Bug 2056486] [NEW] apply nvidia-tegra patches 2024 Mar 1-7
Public bug reported: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra and linux-nvida-tegra-igx). ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056486 Title: apply nvidia-tegra patches 2024 Mar 1-7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055712] [NEW] Pull-request to address bug in mm/page_alloc.c
Public bug reported: The current calculation of min_free_kbytes only uses ZONE_DMA and ZONE_NORMAL pages,but the ZONE_MOVABLE zone->_watermark[WMARK_MIN] will also divide part of min_free_kbytes.This will cause the min watermark of ZONE_NORMAL to be too small in the presence of ZONE_MOVEABLE. __GFP_HIGH and PF_MEMALLOC allocations usually don't need movable zone pages, so just like ZONE_HIGHMEM, cap pages_min to a small value in __setup_per_zone_wmarks(). On my testing machine with 16GB of memory (transparent hugepage is turned off by default, and movablecore=12G is configured) The following is a comparative test data of watermark_min no patchadd patch ZONE_DMA1 8 ZONE_DMA32 151 709 ZONE_NORMAL 233 1113 ZONE_MOVABLE1434128 min_free_kbytes 72887326 ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055712 Title: Pull-request to address bug in mm/page_alloc.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2055712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055468] [NEW] apply nvidia-tegra patches 2024 Feb 6-29
Public bug reported: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra and linux-nvida-tegra-igx). ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055468 Title: apply nvidia-tegra patches 2024 Feb 6-29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2055468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055060] [NEW] Pull-request: Apply mm/mglru patches to fix soft lockup
Public bug reported: [ 1918.995157] watchdog: BUG: soft lockup - CPU#0 stuck for 1725s! [kswapd0:42] [ 1919.002366] Modules linked in: raid10 raid456 libcrc32c async_raid6_recov async_memcpy async_pq async_xor xor xor_neon async_tx raid6_pq raid1 raid0 multipath linear scsi_dh_alua scsi_dh_emc scsi_dh_rdac nvme nvme_core nvme_common [ 1919.023319] CPU: 0 PID: 42 Comm: kswapd0 Tainted: G L 6.5.0-1011-nvidia #11-Ubuntu [ 1919.032483] Hardware name: NVIDIA Grace Hopper x4 P4496/UT2.1 DP Chassis, BIOS 01.02.00 20240120 [ 1919.042180] pstate: 8349 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) [ 1919.049300] pc : __rcu_read_unlock+0x10/0x70 [ 1919.053666] lr : shrink_many+0x280/0x468 [ 1919.057675] sp : 80008149bb70 [ 1919.061060] x29: 80008149bb70 x28: 3ddfa600 x27: deee387571e0 [ 1919.068366] x26: deee383154f8 x25: 0001 x24: 301c90bf4400 [ 1919.075671] x23: x22: x21: 301c90bf4400 [ 1919.082975] x20: 02d3 x19: 80008149bd68 x18: [ 1919.090281] x17: x16: x15: [ 1919.097585] x14: x13: x12: [ 1919.104890] x11: x10: x9 : deee355c2008 [ 1919.112195] x8 : 80008149bde0 x7 : x6 : 0020 [ 1919.119500] x5 : 0001 x4 : x3 : [ 1919.126804] x2 : x1 : 0001 x0 : 301c90bf4400 [ 1919.134109] Call trace: [ 1919.136606] __rcu_read_unlock+0x10/0x70 [ 1919.140615] lru_gen_shrink_node+0x180/0x218 [ 1919.144979] shrink_node+0x400/0x470 [ 1919.148633] balance_pgdat+0x2c8/0x810 [ 1919.152464] kswapd+0x12c/0x268 [ 1919.155672] kthread+0x104/0x110 [ 1919.158970] ret_from_fork+0x10/0x20 [ 1942.995157] watchdog: BUG: soft lockup - CPU#0 stuck for 1747s! [kswapd0:42] [ 1943.002366] Modules linked in: raid10 raid456 libcrc32c async_raid6_recov async_memcpy async_pq async_xor xor xor_neon async_tx raid6_pq raid1 raid0 multipath linear scsi_dh_alua scsi_dh_emc scsi_dh_rdac nvme nvme_core nvme_common [ 1943.023319] CPU: 0 PID: 42 Comm: kswapd0 Tainted: G L 6.5.0-1011-nvidia #11-Ubuntu [ 1943.032483] Hardware name: NVIDIA Grace Hopper x4 P4496/UT2.1 DP Chassis, BIOS 01.02.00 20240120 [ 1943.042180] pstate: 6349 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) [ 1943.049300] pc : lru_gen_shrink_node+0x60/0x218 [ 1943.053932] lr : lru_gen_shrink_node+0x1b8/0x218 [ 1943.058651] sp : 80008149bbf0 [ 1943.062037] x29: 80008149bbf0 x28: 3ddfa600 x27: deee387571e0 [ 1943.069342] x26: deee383154f8 x25: 80008149bde0 x24: 07c0 [ 1943.076647] x23: 0001 x22: x21: 3ddfe600 [ 1943.083952] x20: 3ddfa600 x19: 80008149bd68 x18: [ 1943.091257] x17: x16: x15: [ 1943.098562] x14: x13: x12: [ 1943.105867] x11: x10: x9 : deee359e4bb8 [ 1943.113172] x8 : 80008149bde0 x7 : x6 : [ 1943.120477] x5 : x4 : x3 : [ 1943.127782] x2 : x1 : x0 : 301c90bf4400 [ 1943.135086] Call trace: [ 1943.137583] lru_gen_shrink_node+0x60/0x218 [ 1943.141858] shrink_node+0x400/0x470 [ 1943.145511] balance_pgdat+0x2c8/0x810 [ 1943.149342] kswapd+0x12c/0x268 [ 1943.152551] kthread+0x104/0x110 [ 1943.155849] ret_from_fork+0x10/0x20 ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055060 Title: Pull-request: Apply mm/mglru patches to fix soft lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2055060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055057] [NEW] Pull-request: apply upstream patch to reject events meant for other PMUs
Public bug reported: Coresight PMU driver didn't reject events meant for other PMUs. This caused some of the Core PMU events disappearing from the output of "perf list". In addition, trying to run e.g. $ perf stat -e r2 sleep 1 made Coresight PMU driver to handle the event instead of letting Core PMU driver to deal with it. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055057 Title: Pull-request: apply upstream patch to reject events meant for other PMUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2055057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054984] [NEW] Pull request: Enable support of ETE and TRBE in ACPI environment.
Public bug reported: This series enables detection of ACPI based TRBE devices via a stand alone purpose built representative platform device. But as a pre-requisite this changes coresight_platform_data structure assignment for the TRBE device. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054984 Title: Pull request: Enable support of ETE and TRBE in ACPI environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2054984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
After testing kernel 5.18.0 from mainline, the issue does appear resolved -- the system will boot with "pci=nocrs" and the touchpad, touchscreen function. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059947] Re: xvfb-run munges stdout and stderr together
This bug is still present in xvfb 2:1.20.13-1ubuntu1~20.04.2. It prevents us from using `xvfb-run` when we need to disambiguate STDOUT and STDERR. I'm not familiar with the problem of autopkgtests, but is this still an issue? Can autopkgtests be fixed? If we're an impasse, does it make sense to turn this into a feature request to add a flag to change the redirection behavior? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059947 Title: xvfb-run munges stdout and stderr together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1059947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968430] Re: tripwire --init Segmentation Fault
** Description changed: lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 - apt-cache policy tripwire + apt-cache policy tripwire tripwire: Installed: 2.4.3.7-3 Candidate: 2.4.3.7-3 Version table: *** 2.4.3.7-3 500 500 http://ca.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status tripwire --init Please enter your local passphrase: Parsing policy file: /etc/tripwire/tw.pol Generating the database... *** Processing Unix File System *** Software interrupt forced exit: Segmentation Fault Segmentation fault (core dumped) The partial output of /var/crash/_usr_sbin_tripwire.0.crash ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Sat Apr 9 12:36:13 2022 DistroRelease: Ubuntu 21.10 ExecutablePath: /usr/sbin/tripwire ExecutableTimestamp: 1587715517 ProcCmdline: tripwire ProcCwd: /var/crash ProcEnviron: - SHELL=/bin/bash - LANGUAGE=en_CA:en - LANG=en_CA.UTF-8 - TERM=xterm-256color - PATH=(custom, user) + SHELL=/bin/bash + LANGUAGE=en_CA:en + LANG=en_CA.UTF-8 + TERM=xterm-256color + PATH=(custom, user) ProcMaps: - 0040-00401000 r--p 08:01 4600708 /usr/sbin/tripwire - 00401000-0066d000 r-xp 1000 08:01 4600708 /usr/sbin/tripwire - 0066d000-00706000 r--p 0026d000 08:01 4600708 /usr/sbin/tripwire - 00707000-0071c000 r--p 00306000 08:01 4600708 /usr/sbin/tripwire - 0071c000-00722000 rw-p 0031b000 08:01 4600708 /usr/sbin/tripwire - 00722000-00729000 rw-p 00:00 0 - 0122f000-0129a000 rw-p 00:00 0 [heap] - 7f7fb4e8b000-7f7fb4f8b000 rw-p 00:00 0 - 7f7fb4f8b000-7f7fb4f8c000 r--p 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 - 7f7fb4f8c000-7f7fb4fb4000 r-xp 1000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 - 7f7fb4fb4000-7f7fb4fbe000 r--p 00029000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 - 7f7fb4fbe000-7f7fb4fc r--p 00032000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 - 7f7fb4fc-7f7fb4fc2000 rw-p 00034000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 - 7f7fb4fc2000-7f7fb4fea000 r--p 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 - 7f7fb4fea000-7f7fb517e000 r-xp 00028000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 - 7f7fb517e000-7f7fb51d6000 r--p 001bc000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 - 7f7fb51d6000-7f7fb51d7000 ---p 00214000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 - 7f7fb51d7000-7f7fb51db000 r--p 00214000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 - 7f7fb51db000-7f7fb51dd000 rw-p 00218000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 - 7f7fb51dd000-7f7fb51ea000 rw-p 00:00 0 - 7f7fb51ea000-7f7fb51eb000 r--p 08:01 4589711 /usr/lib/x86_64-linux-gnu/libnss_files.so.2 - 7f7fb51eb000-7f7fb51ec000 r-xp 1000 08:01 4589711 /usr/lib/x86_64-linux-gnu/libnss_files.so.2 - 7f7fb51ec000-7f7fb51ed000 r--p 2000 08:01 4589711 /usr/lib/x86_64-linux-gnu/libnss_files.so.2 - 7f7fb51ed000-7f7fb51ee000 r--p 2000 08:01 4589711 /usr/lib/x86_64-linux-gnu/libnss_files.so.2 - 7f7fb51ee000-7f7fb51ef000 rw-p 3000 08:01 4589711 /usr/lib/x86_64-linux-gnu/libnss_files.so.2 - 7f7fb5208000-7f7fb520f000 r--s 08:01 5248344 /usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache - 7f7fb520f000-7f7fb578 r--p 08:01 4588564 /usr/lib/locale/locale-archive - 7f7fb578-7f7fb57e2000 rw-p 00:00 0 - 7ffdd4834000-7ffdd4855000 rw-p 00:00 0 [stack] - 7ffdd48b3000-7ffdd48b7000 r--p 00:00 0 [vvar] - 7ffdd48b7000-7ffdd48b9000 r-xp 00:00 0 [vdso] - ff60-ff601000 --xp 00:00 0 [vsyscall] + 0040-00401000 r--p 08:01 4600708 /usr/sbin/tripwire + 00401000-0066d000 r-xp 1000 08:01 4600708 /usr/sbin/tripwire + 0066d000-00706000 r--p 0026d000 08:01 4600708 /usr/sbin/tripwire + 00707000-0071c000 r--p 00306000 08:01 4600708 /usr/sbin/tripwire + 0071c000-00722000 rw-p 0031b000 08:01 4600708 /usr/sbin/tripwire + 00722000-00729000 rw-p 00:00 0 + 0122f000-0129a000 rw-p 00:00 0 [heap] + 7f7fb4e8b000-7f7fb4f8b000 rw-p 00:00 0 + 7f7fb4f8b000-7f7fb4f8c000 r--p 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 + 7f7fb4f8c000-7f7fb4fb4000 r-xp 1000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 + 7f7fb4fb4000-7f7fb4fbe000 r--p 00029000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 + 7f7fb4fbe000-7f7fb4fc r--p 00032000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 + 7f7fb4fc-7f7fb4fc2000 rw-p 00034000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 + 7f7fb4fc2000-7f7fb4fea000 r--p 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 + 7f7fb4fea000-7f7fb517e000 r-xp 00028000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 +
[Bug 1968178] Re: Jemboss 6.6.0+dfsg-9ubuntu1 failed to launch
UPDATE: suddenly jEmboss started with no errors, thanks guys! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968178 Title: Jemboss 6.6.0+dfsg-9ubuntu1 failed to launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emboss/+bug/1968178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
After a clean install of Ubuntu 22.04, I have the same issue on an Acer Spin 5 SP513-54N-74V2. Installing and booting into kernel 5.13.19 works fine and resolves the issue. With kernel 5.15 and no "pci=nocrs," the error seems to be i2c_designware: failed to claim resource. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968434] [NEW] Output Device shows only Dummy Output
Public bug reported: Audio was working yesterday. I turned on my computer today and the only output device is Dummy Output. Running aplay -l output is aplay: device_list:276: no soundcards found. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 12:04:59 2022 InstallationDate: Installed on 2021-05-24 (319 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2802 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2802:bd10/21/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-04-09T11:38:59.731560 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968434 Title: Output Device shows only Dummy Output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1968434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968430] Re: tripwire --init Segmentation Fault
** Description changed: lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 - apt-cache policy tripwire + apt-cache policy tripwire tripwire: - Installed: 2.4.3.7-3 - Candidate: 2.4.3.7-3 - Version table: - *** 2.4.3.7-3 500 - 500 http://ca.archive.ubuntu.com/ubuntu impish/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2.4.3.7-3 + Candidate: 2.4.3.7-3 + Version table: + *** 2.4.3.7-3 500 + 500 http://ca.archive.ubuntu.com/ubuntu impish/universe amd64 Packages + 100 /var/lib/dpkg/status tripwire --init - Please enter your local passphrase: + Please enter your local passphrase: Parsing policy file: /etc/tripwire/tw.pol Generating the database... *** Processing Unix File System *** Software interrupt forced exit: Segmentation Fault Segmentation fault (core dumped) + + The partial output of /var/crash/_usr_sbin_tripwire.0.crash + + ProblemType: Crash + Architecture: amd64 + CrashCounter: 1 + Date: Sat Apr 9 12:36:13 2022 + DistroRelease: Ubuntu 21.10 + ExecutablePath: /usr/sbin/tripwire + ExecutableTimestamp: 1587715517 + ProcCmdline: tripwire + ProcCwd: /var/crash + ProcEnviron: + SHELL=/bin/bash + LANGUAGE=en_CA:en + LANG=en_CA.UTF-8 + TERM=xterm-256color + PATH=(custom, user) + ProcMaps: + 0040-00401000 r--p 08:01 4600708 /usr/sbin/tripwire + 00401000-0066d000 r-xp 1000 08:01 4600708 /usr/sbin/tripwire + 0066d000-00706000 r--p 0026d000 08:01 4600708 /usr/sbin/tripwire + 00707000-0071c000 r--p 00306000 08:01 4600708 /usr/sbin/tripwire + 0071c000-00722000 rw-p 0031b000 08:01 4600708 /usr/sbin/tripwire + 00722000-00729000 rw-p 00:00 0 + 0122f000-0129a000 rw-p 00:00 0 [heap] + 7f7fb4e8b000-7f7fb4f8b000 rw-p 00:00 0 + 7f7fb4f8b000-7f7fb4f8c000 r--p 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 + 7f7fb4f8c000-7f7fb4fb4000 r-xp 1000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 + 7f7fb4fb4000-7f7fb4fbe000 r--p 00029000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 + 7f7fb4fbe000-7f7fb4fc r--p 00032000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 + 7f7fb4fc-7f7fb4fc2000 rw-p 00034000 08:01 4589666 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 + 7f7fb4fc2000-7f7fb4fea000 r--p 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 + 7f7fb4fea000-7f7fb517e000 r-xp 00028000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 + 7f7fb517e000-7f7fb51d6000 r--p 001bc000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 + 7f7fb51d6000-7f7fb51d7000 ---p 00214000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 + 7f7fb51d7000-7f7fb51db000 r--p 00214000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 + 7f7fb51db000-7f7fb51dd000 rw-p 00218000 08:01 4589689 /usr/lib/x86_64-linux-gnu/libc.so.6 + 7f7fb51dd000-7f7fb51ea000 rw-p 00:00 0 + 7f7fb51ea000-7f7fb51eb000 r--p 08:01 4589711 /usr/lib/x86_64-linux-gnu/libnss_files.so.2 + 7f7fb51eb000-7f7fb51ec000 r-xp 1000 08:01 4589711 /usr/lib/x86_64-linux-gnu/libnss_files.so.2 + 7f7fb51ec000-7f7fb51ed000 r--p 2000 08:01 4589711 /usr/lib/x86_64-linux-gnu/libnss_files.so.2 + 7f7fb51ed000-7f7fb51ee000 r--p 2000 08:01 4589711 /usr/lib/x86_64-linux-gnu/libnss_files.so.2 + 7f7fb51ee000-7f7fb51ef000 rw-p 3000 08:01 4589711 /usr/lib/x86_64-linux-gnu/libnss_files.so.2 + 7f7fb5208000-7f7fb520f000 r--s 08:01 5248344 /usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache + 7f7fb520f000-7f7fb578 r--p 08:01 4588564 /usr/lib/locale/locale-archive + 7f7fb578-7f7fb57e2000 rw-p 00:00 0 + 7ffdd4834000-7ffdd4855000 rw-p 00:00 0 [stack] + 7ffdd48b3000-7ffdd48b7000 r--p 00:00 0 [vvar] + 7ffdd48b7000-7ffdd48b9000 r-xp 00:00 0 [vdso] + ff60-ff601000 --xp 00:00 0 [vsyscall] + ProcStatus: + Name: tripwire + Umask: 0022 + State: S (sleeping) + Tgid: 1711201 + Ngid: 0 + Pid: 1711201 + PPid: 1709566 + TracerPid: 0 + Uid: 0 0 0 0 + Gid: 0 0 0 0 + FDSize: 256 + Groups: 0 + NStgid: 1711201 + NSpid: 1711201 + NSpgid: 1711201 + NSsid: 1709566 + VmPeak: 13280 kB + VmSize: 13280 kB + VmLck: 0 kB + VmPin: 0 kB + VmHWM: 4452 kB + VmRSS: 4452 kB + RssAnon: 848 kB + RssFile: 3604 kB + RssShmem: 0 kB + VmData: 1968 kB + VmStk: 132 kB + VmExe: 2480 kB + VmLib: 1788 kB + VmPTE: 60 kB + VmSwap: 0 kB + HugetlbPages: 0 kB + CoreDumping: 1 + THP_enabled: 1 + Threads: 1 + SigQ: 0/14973 + SigPnd: + ShdPnd: + SigBlk: + SigIgn: 1000 + SigCgt: 418000fc + CapInh: + CapPrm: 01ff + CapEff: 01ff + CapBnd: 01ff + CapAmb: + NoNewPrivs: 0 + Seccomp: 0 + Seccomp_filters: 0 + Speculation_Store_Bypass: not vulnerable + SpeculationIndirectBranch: always enabled
[Bug 1968430] [NEW] tripwire --init Segmentation Fault
Public bug reported: lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 apt-cache policy tripwire tripwire: Installed: 2.4.3.7-3 Candidate: 2.4.3.7-3 Version table: *** 2.4.3.7-3 500 500 http://ca.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status tripwire --init Please enter your local passphrase: Parsing policy file: /etc/tripwire/tw.pol Generating the database... *** Processing Unix File System *** Software interrupt forced exit: Segmentation Fault Segmentation fault (core dumped) ** Affects: emboss (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968430 Title: tripwire --init Segmentation Fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emboss/+bug/1968430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968178] [NEW] Jemboss 6.6.0+dfsg-9ubuntu1 failed to launch
Public bug reported: lsb_release -rd Description:Ubuntu 21.10 Release:21.10 apt-cache policy jemboss jemboss: Installed: 6.6.0+dfsg-9ubuntu1 Candidate: 6.6.0+dfsg-9ubuntu1 Version table: *** 6.6.0+dfsg-9ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu impish/universe i386 Packages 100 /var/lib/dpkg/status I installed jemboss with apt, aptitude, synaptic apt install jemboss Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: ca-certificates-java default-jre default-jre-headless dialign emboss emboss-data emboss-lib fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni libhpdf-2.3.0 openjdk-11-jre openjdk-11-jre-headless primer3 Suggested packages: emboss-doc emboss-test embassy clustalw fonts-ipafont-gothic fonts-ipafont-mincho fonts-wqy-microhei | fonts-wqy-zenhei ncbi-epcr The following NEW packages will be installed: ca-certificates-java default-jre default-jre-headless dialign emboss emboss-data emboss-lib fonts-dejavu-extra java-common jemboss libatk-wrapper-java libatk-wrapper-java-jni libhpdf-2.3.0 openjdk-11-jre openjdk-11-jre-headless primer3 0 upgraded, 16 newly installed, 0 to remove and 0 not upgraded. Need to get 113 MB of archives. After this operation, 684 MB of additional disk space will be used. Do you want to continue? [Y/n] and when I launch it fails: java -version openjdk version "11.0.14.1" 2022-02-08 OpenJDK Runtime Environment (build 11.0.14.1+1-Ubuntu-0ubuntu1.20.04) OpenJDK 64-Bit Server VM (build 11.0.14.1+1-Ubuntu-0ubuntu1.20.04, mixed mode, sharing) brad@rudy:/etc/emboss$ jemboss brad@rudy:/etc/emboss$ Exception in thread "main" java.lang.NumberFormatException: multiple points at java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1914) at java.base/jdk.internal.math.FloatingDecimal.parseFloat(FloatingDecimal.java:122) at java.base/java.lang.Float.parseFloat(Float.java:455) at org.emboss.jemboss.JembossParams.checkDesktopSupport(JembossParams.java:1408) at org.emboss.jemboss.JembossParams.(JembossParams.java:352) at org.emboss.jemboss.Jemboss.(Jemboss.java:102) at org.emboss.jemboss.Jemboss.main(Jemboss.java:397) java Thanks, Brad ** Affects: emboss (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968178 Title: Jemboss 6.6.0+dfsg-9ubuntu1 failed to launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emboss/+bug/1968178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958934] Re: laptop does not respond to keyboard or mouse input
** Package changed: ubuntu => xfce4-screensaver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958934 Title: laptop does not respond to keyboard or mouse input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1958934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958934] Re: laptop does not respond to keyboard or mouse input
If xfce screensaver lock screen is disabled, the issue goes away. When enabled it comes back -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958934 Title: laptop does not respond to keyboard or mouse input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958934] [NEW] laptop does not respond to keyboard or mouse input
Public bug reported: Dell Vostro 15 7510 :lsb_release -crid Distributor ID: Ubuntu Description:Ubuntu 21.10 Release:21.10 Codename: impish Sporadically the laptop does not respond to keyboard or mouse input. The cursor still shows up. This may be associated with waking up from suspend. I can still get to a terminal with Ctl-Fn-Alt-F1. I see this in kern.log at about the time of the issue: Jan 24 11:54:58 brad-dell kernel: [14615.288956] PM: suspend exit Jan 24 11:55:02 brad-dell kernel: [14619.411849] wlp0s20f3: authenticate with 9c:3d:cf:71:af:77 Jan 24 11:55:02 brad-dell kernel: [14619.420838] wlp0s20f3: send auth to 9c:3d:cf:71:af:77 (try 1/3) Jan 24 11:55:02 brad-dell kernel: [14619.502877] wlp0s20f3: authenticated Jan 24 11:55:02 brad-dell kernel: [14619.505396] wlp0s20f3: associate with 9c:3d:cf:71:af:77 (try 1/3) Jan 24 11:55:02 brad-dell kernel: [14619.511548] wlp0s20f3: RX AssocResp from 9c:3d:cf:71:af:77 (capab=0x11 status=0 aid=6) Jan 24 11:55:02 brad-dell kernel: [14619.519475] wlp0s20f3: associated Jan 24 11:55:02 brad-dell kernel: [14619.582017] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready Jan 24 11:56:58 brad-dell kernel: [14735.585403] kauditd_printk_skb: 17 callbacks suppressed Jan 24 11:56:58 brad-dell kernel: [14735.585409] audit: type=1400 audit(1643050618.988:28): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/osrelease" pid=714 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Jan 24 11:56:58 brad-dell kernel: [14735.585544] audit: type=1400 audit(1643050618.988:29): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/1/environ" pid=714 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Jan 24 11:56:58 brad-dell kernel: [14735.585554] audit: type=1400 audit(1643050618.988:30): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/cmdline" pid=714 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Jan 24 11:57:52 brad-dell kernel: [14788.932312] ACPI Error: Thread 3295223488 cannot release Mutex [ECMX] acquired by thread 3475299392 (20210331/exmutex-378) Jan 24 11:57:52 brad-dell kernel: [14788.932333] Jan 24 11:57:52 brad-dell kernel: [14788.932336] No Local Variables are initialized for Method [_Q66] Jan 24 11:57:52 brad-dell kernel: [14788.932337] Jan 24 11:57:52 brad-dell kernel: [14788.932339] No Arguments are initialized for method [_Q66] Jan 24 11:57:52 brad-dell kernel: [14788.932340] Jan 24 11:57:52 brad-dell kernel: [14788.932345] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20210331/psparse-529) ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958934 Title: laptop does not respond to keyboard or mouse input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952818] Re: Fails to suspend
I think this has been fixed by updating the OS to Xubuntu 21.10 (& associated kernel) & the Bios to 1.3.0. I also had to keep the sleep mode in s2idle -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952818 Title: Fails to suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952818] [NEW] Fails to suspend
Public bug reported: Occasionally my laptop fails to suspend with a lid close. I always get this message in syslog or kernal.log: kernel: [ 1947.276485] ACPI: button: The lid device is not compliant to SW_LID. But it usually continues and suspends successfully. This time there was nothing in syslog, kern.log, or dmesg after the SW_LID message. It also never locks the screen either, & this time there was a msg on the screen after I opened it up about failing to lock the screen. Description:Ubuntu 21.04 Release:21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brad 1280 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Nov 30 18:51:44 2021 InstallationDate: Installed on 2021-11-20 (10 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) MachineType: Dell Inc. Vostro 15 7510 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=a07e9fdf-df33-4257-913f-9fe9f42e08a9 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-41-generic N/A linux-backports-modules-5.11.0-41-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-11-29 (1 days ago) dmi.bios.date: 10/14/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0J0MWF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd10/14/2021:br1.2:svnDellInc.:pnVostro157510:pvr:sku0A82:rvnDellInc.:rn0J0MWF:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15 7510 dmi.product.sku: 0A82 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952818 Title: Fails to suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944397] Re: hdmi broken on 5.13.0-1007-raspi
** Changed in: linux-raspi (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944397 Title: hdmi broken on 5.13.0-1007-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929892] Re: [TGL] enable USB-dw3
We get this for free with the move to a 5.13 based focal:linux-intel kernel. ** Changed in: intel Status: New => Invalid ** Changed in: linux-intel (Ubuntu) Status: In Progress => Invalid ** Changed in: intel Assignee: (unassigned) => Brad Figg (brad-figg) ** Changed in: linux-intel (Ubuntu) Assignee: Hsuan-Yu Lin (shanelin) => Brad Figg (brad-figg) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929892 Title: [TGL] enable USB-dw3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929901] Re: [EHL][TGL] EDAC support
This commit already exists in the focal:linux-intel intel-5.13-next. ** Changed in: intel Status: New => Fix Committed ** Changed in: intel Assignee: (unassigned) => Brad Figg (brad-figg) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929901 Title: [EHL][TGL] EDAC support To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938678] Re: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H
** Tags added: lookout-canyon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938678 Title: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938408] Re: [ehl] board does not support soft reboot
** Summary changed: - EHL board does not support soft reboot + [ehl] board does not support soft reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938408 Title: [ehl] board does not support soft reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938413] Re: [ehl] Shutdown hangs on board
** Summary changed: - Shutdown hangs on EHL board + [ehl] Shutdown hangs on board -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: [ehl] Shutdown hangs on board To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938413] Re: Shutdown hangs on EHL board
** Changed in: intel Status: New => Fix Committed ** Tags added: lookout-canyon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: Shutdown hangs on EHL board To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929902] Re: [EHL] enable USB-dw3
** Changed in: intel Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929902 Title: [EHL] enable USB-dw3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938408] Re: EHL board does not support soft reboot
** Changed in: intel Status: New => Fix Committed ** Tags added: lookout-canyon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938408 Title: EHL board does not support soft reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939449] Re: Ubuntu Pro UA fails to enable fips-updates on 20.04
Thanks sincerely for the detailed response. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939449 Title: Ubuntu Pro UA fails to enable fips-updates on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1939449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939449] Re: Ubuntu Pro UA fails to enable fips-updates on 20.04
Searching AWS marketplace I see that for Ubuntu 18, there are: - Ubuntu Pro FIPS 18.04 LTS (offered by Canonical Group Ltd) - Ubuntu Pro 18.04 LTS (offered by Amazon Web Services) But for Ubuntu 20.04, a "Pro FIPS" variety does not exist, only Ubuntu Pro 20.04 LTS. This is confusing from a user perspective. - Why are there two separate AMIs if Ubuntu Pro is supposed to include the fips modules enabled through UA in the first place? - Why can `fips` or `fips-updates` not be enabled using the Ubuntu Pro 20.04 LTS image? - Why is an Ubuntu Pro FIPS 20.04 LTS missing entirely? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939449 Title: Ubuntu Pro UA fails to enable fips-updates on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1939449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939449] [NEW] Ubuntu Pro UA fails to enable fips-updates on 20.04
Public bug reported: Using AWS AMI: ami-0193aa0a9df84a08b Attempting to enable fips-updates with the ua command line tool fails with error that apt "Unable to locate package ubuntu-aws-fips." Canonical has told me directly 20.04 is now FIPS 140-2 Level 1 certified. Output: ubuntu@ip-xx-xx-xx-xx:~$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 ubuntu@ip-xx-xx-xx-xx:~$ ua version 27.2.2~20.04.1 ubuntu@ip-xx-xx-xx-xx:~$ sudo ua status --all SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis yes disabled Center for Internet Security Audit Tools esm-apps yes disabled UA Apps: Extended Security Maintenance (ESM) esm-infra yes disabled UA Infra: Extended Security Maintenance (ESM) fips yes disabled NIST-certified core packages fips-updates yes disabled NIST-certified core packages with priority security updates livepatch yes disabled Canonical Livepatch service Enable services with: ua enable Account: Subscription: Valid until: -12-31 00:00:00+00:00 Technical support level: essential ubuntu@ip-xx-xx-xx-xx:~$ sudo ua --debug enable fips-updates DEBUG: Executed with sys.argv: ['/usr/bin/ua', '--debug', 'enable', 'fips-updates'] This will install the FIPS core packages and will include priority updates with security fixes. Are you sure? (y/N) y DEBUG: Writing file: /var/lib/ubuntu-advantage/private/machine-access-fips-updates DEBUG: Writing file: /etc/apt/preferences.d/ubuntu-fips-updates DEBUG: Ran cmd: apt-cache policy, rc: 0 stderr: b'' DEBUG: Writing file: /etc/apt/sources.list.d/ubuntu-fips-updates.list DEBUG: Writing file: /etc/apt/auth.conf.d/90ubuntu-advantage DEBUG: Exporting GPG key /usr/share/keyrings/ubuntu-advantage-fips.gpg Updating package lists DEBUG: Ran cmd: apt-get update, rc: 0 stderr: b'' DEBUG: Reading file: /var/lib/ubuntu-advantage/private/machine-token.json Installing FIPS Updates packages DEBUG: Failed running command 'apt-get install --assume-yes --allow-downgrades -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" ubuntu-aws-fips' [exit(100)]. Message: E: Unable to locate package ubuntu-aws-fips DEBUG: Failed running command 'apt-get install --assume-yes --allow-downgrades -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" ubuntu-aws-fips' [exit(100)]. Message: E: Unable to locate package ubuntu-aws-fips Retrying 3 more times. DEBUG: Failed running command 'apt-get install --assume-yes --allow-downgrades -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" ubuntu-aws-fips' [exit(100)]. Message: E: Unable to locate package ubuntu-aws-fips DEBUG: Failed running command 'apt-get install --assume-yes --allow-downgrades -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" ubuntu-aws-fips' [exit(100)]. Message: E: Unable to locate package ubuntu-aws-fips Retrying 2 more times. DEBUG: Failed running command 'apt-get install --assume-yes --allow-downgrades -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" ubuntu-aws-fips' [exit(100)]. Message: E: Unable to locate package ubuntu-aws-fips DEBUG: Failed running command 'apt-get install --assume-yes --allow-downgrades -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" ubuntu-aws-fips' [exit(100)]. Message: E: Unable to locate package ubuntu-aws-fips Retrying 1 more times. DEBUG: Failed running command 'apt-get install --assume-yes --allow-downgrades -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" ubuntu-aws-fips' [exit(100)]. Message: E: Unable to locate package ubuntu-aws-fips DEBUG: Reading file: /etc/apt/auth.conf.d/90ubuntu-advantage Updating package lists DEBUG: Ran cmd: apt-get update, rc: 0 stderr: b'' Could not enable FIPS Updates. DEBUG: Reading file: /var/lib/ubuntu-advantage/notices.json DEBUG: Removing file: /var/lib/ubuntu-advantage/notices.json ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939449 Title: Ubuntu Pro UA fails to enable fips-updates on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1939449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900076] Re: file globbing broken on armhf
See upstream cmake issue: https://gitlab.kitware.com/cmake/cmake/-/issues/20568 ** Bug watch added: gitlab.kitware.com/cmake/cmake/-/issues #20568 https://gitlab.kitware.com/cmake/cmake/-/issues/20568 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900076 Title: file globbing broken on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1900076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Can someone point me to where you can download the previous version? rpcbind_0.2.3-0.6ubuntu0.18.04.1_amd64.deb I can't locate it. Brad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] Re: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Hi, This bug is affecting our NIS server. Can someone post where to download the updated rpcbind package for Ubuntu 18.04.5? rpcbind is crashing repeatedly. Jun 10 14:35:08 systemd[1]: rpcbind.service: Main process exited, code=dumped, status=6/ABRT Jun 10 14:35:08 systemd[1]: rpcbind.service: Failed with result 'core-dump'. Jun 10 14:35:08 systemd[1]: rpcbind.service: Service hold-off time over, scheduling restart. Jun 10 14:35:08 systemd[1]: rpcbind.service: Scheduled restart job, restart counter is at 10. Jun 10 14:35:08 systemd[1]: Stopped RPC bind portmap service. Jun 10 14:35:08 systemd[1]: Starting RPC bind portmap service... Thank you. Brad Zoltick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1926506] Re: An unresolvable problem occurred while calculating the upgrade.
Thanks for the reply - but too late! I resolved the issue by removing python and all dependencies, then re-installing the same. It was ugly, but got me going again. On 5/14/21 5:31 PM, Brian Murray wrote: > Thanks for taking the time to report this upgrade failure. There is > currently a new version of the release upgrader available in -proposed > which may resolve the error you've encountered. Please run the following > command to test the new version of the upgrader: > >do-release-upgrade -p > > Please lets us know the results in this bug report. Thanks again and > good luck! > > ** Changed in: ubuntu-release-upgrader (Ubuntu) > Status: New => Incomplete > > ** Tags added: lp-1928397 > -- Brad Smart mailto:bsmar...@afo.net Home Phone: 734-971-7425 GVoice: 516-277-6278 (text and voice mail) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926506 Title: An unresolvable problem occurred while calculating the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926506] [NEW] An unresolvable problem occurred while calculating the upgrade.
Public bug reported: root@myubuntu:/var/log/dist-upgrade# grep -i broken apt.log Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Starting pkgProblemResolver with broken count: 28 Starting 2 pkgProblemResolver with broken count: 28 Broken dpkg:amd64 Breaks on libapt-pkg5.0:amd64 < 1.6.13 @ii mK > (< 1.7~b) Broken libuno-sal3:amd64 Breaks on uno-libs3:amd64 < 6.0.7-0ubuntu0.18.04.10 @ii mK > Broken gnome-settings-daemon-common:amd64 Breaks on gnome-settings-daemon-schemas:amd64 < 3.28.1-0ubuntu1.3 @ii mK > (< 3.30.1.2-2~) Broken libldb2:amd64 Breaks on libldb1:amd64 < 2:1.2.3-1ubuntu0.2 @ii mK > (< 2:2~) Broken python2:amd64 Breaks on python:amd64 < 2.7.15~rc1-1 @ii gK > (< 2.7.15-2) Broken python2-minimal:amd64 Breaks on python-minimal:amd64 < 2.7.15~rc1-1 @ii gK > (< 2.7.15-2) Broken libpython2-stdlib:amd64 Breaks on libpython-stdlib:amd64 < 2.7.15~rc1-1 @ii gK > (< 2.7.15-2) Broken libhfstospell10:amd64 Conflicts on libhfstospell:amd64 < none @un H > Broken libsensors-config:amd64 Conflicts on libsensors4:amd64 < 1:3.4.0-4 @ii mK > Broken libmailutils6:amd64 Conflicts on libmailutils5:amd64 < 1:3.4-1 @ii mK Ib > Broken python-crypto:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > (< 2.8) Broken fwupdate:amd64 Breaks on fwupdate-signed:amd64 < 12-7~ubuntu18.04.3 @ii mK > Broken fwupdate:amd64 Breaks on libfwup1:amd64 < 12-3bionic2 @ii mK > (< 12-5) Broken python-tdb:amd64 Depends on libtdb1:amd64 < 1.3.15-2 -> 1.4.2-3build1 @ii umU > (= 1.3.15-2) Broken python-ldb:amd64 Depends on libldb1:amd64 < 2:1.2.3-1ubuntu0.2 @ii mR > (= 2:1.2.3-1ubuntu0.2) Broken libedata-book-1.2-25:amd64 Depends on libebackend-1.2-10:amd64 < 3.28.5-0ubuntu0.18.04.3 -> 3.36.4-0ubuntu1 @ii umU > (= 3.28.5-0ubuntu0.18.04.3) Broken python-is-python2:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Broken libsnmp30:amd64 Depends on libsensors4:amd64 < 1:3.4.0-4 @ii mR > (>= 1:3.0.0) Broken python-samba:amd64 Depends on python-ldb:amd64 < 2:1.2.3-1ubuntu0.2 @ii mR > (>= 1.1.2~) Broken libapt-inst2.0:amd64 Depends on libapt-pkg5.0:amd64 < 1.6.13 @ii mR > (>= 1.1~exp9) Broken libcupscgi1:amd64 Depends on libcups2:amd64 < 2.2.7-1ubuntu2.8 -> 2.3.1-9ubuntu1.1 @ii umU > (= 2.2.7-1ubuntu2.8) Broken libcupsppdc1:amd64 Depends on libcups2:amd64 < 2.2.7-1ubuntu2.8 -> 2.3.1-9ubuntu1.1 @ii umU > (= 2.2.7-1ubuntu2.8) Broken idle-python3.6:amd64 Depends on python3.6-tk:amd64 < none @un H > Broken libedata-cal-1.2-28:amd64 Depends on libebackend-1.2-10:amd64 < 3.28.5-0ubuntu0.18.04.3 -> 3.36.4-0ubuntu1 @ii umU > (= 3.28.5-0ubuntu0.18.04.3) Broken libcupsmime1:amd64 Depends on libcups2:amd64 < 2.2.7-1ubuntu2.8 -> 2.3.1-9ubuntu1.1 @ii umU > (= 2.2.7-1ubuntu2.8) Broken libebook-1.2-19:amd64 Depends on libedata-book-1.2-25:amd64 < 3.28.5-0ubuntu0.18.04.3 @ii mR > (= 3.28.5-0ubuntu0.18.04.3) Broken libept1.5.0:amd64 Depends on libapt-pkg5.0:amd64 < 1.6.13 @ii mR > (>= 1.1~exp9) Broken libpolkit-backend-1-0:amd64 Depends on libpolkit-gobject-1-0:amd64 < 0.105-20ubuntu0.18.04.5 -> 0.105-26ubuntu1 @ii umU > (= 0.105-20ubuntu0.18.04.5) Broken python-is-python2:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Broken python-is-python2:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Broken python-is-python2:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Broken python-is-python2:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Broken python-is-python2:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Broken python-is-python2:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Broken python-is-python2:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Broken python-is-python2:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Broken python-is-python2:amd64 Depends on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 15:54:40 2021 InstallationDate: Installed on 2018-10-01 (940 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-04-28 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926506
[Bug 1917409] Re: neutron-l3-agents won't become active
*** This bug is a duplicate of bug 1883089 *** https://bugs.launchpad.net/bugs/1883089 As the fix this was a duplicate of has been abandoned, can this still be addressed somehow? Is there anything I can do to move this forward? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917409 Title: neutron-l3-agents won't become active To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1917409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918029] [NEW] Pi400 Night Light
Public bug reported: On the Raspberry Pi 400 the Night Light mode for the display seems to have no effect. The display remains the same bright colour even when the night light filter is enabled. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-1016.19-raspi 5.8.18 Uname: Linux 5.8.0-1016-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 6 20:02:05 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1680x1050M@60 smsc95xx.macaddr=DC:A6:32:E5:00:72 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash RebootRequiredPkgs: gnome-shell SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918029 Title: Pi400 Night Light To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1918029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912752] Re: linux-uc20-efi: megaraid_sas required in the initrd
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912752 Title: linux-uc20-efi: megaraid_sas required in the initrd To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914898] Re: Unable to upgrade to Ubuntu 20.04
My /var/log/dist-upgrade/main.log ends: 2021-02-06 22:02:23,299 WARNING Can't mark 'ubuntu-desktop' for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) Am I supposed to somehow remove/disable ubuntu-desktop before I can upgrade? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914898 Title: Unable to upgrade to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1914898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914898] [NEW] Unable to upgrade to Ubuntu 20.04
Public bug reported: While attempting to upgrade (with the GUI) I get this error message: " Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. " It doesn't actually tell me what the problem is. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 5.3.0-7648.41~1586790036~18.04~600aeb5~dev-generic 5.3.18 Uname: Linux 5.3.0-7648-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 22:02:54 2021 InstallationDate: Installed on 2018-08-26 (896 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-02-07 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914898 Title: Unable to upgrade to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1914898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908894] Re: USB controllers disconnects after random time
I've been having the same issue since building a new system a couple months ago. The frequency is inconsistent, but rarely happens more than once per day. Sometimes I'll lose my keyboard mid-sentence, and other times I won't be able to unlock the system in the morning. Oddly, my USB mouse (a Razer Naga) always still works, and the side buttons which act as a number pad also always work. However, by USB hub loses power, and neither it nor my keyboard ever regain power or functionality when re-plugging or switching ports. It's always fixed by a reboot. I'm on a Threadripper 3990x with an ASUS ROG Zenith II Extreme motherboard. Here's the snippet from /var/log/syslog: Jan 14 19:37:19 amaranth systemd[1]: fprintd.service: Succeeded. Jan 14 19:38:44 amaranth kernel: [37857.592954] xhci_hcd :49:00.3: Mismatch between completed Set TR Deq Ptr command & xHCI internal state. Jan 14 19:38:44 amaranth kernel: [37857.592957] xhci_hcd :49:00.3: ep deq seg = 3ccd0405, deq ptr = 6daebfd1 Jan 14 19:38:45 amaranth kernel: [37858.593779] xhci_hcd :49:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0035 address=0x0 flags=0x] Jan 14 19:38:50 amaranth kernel: [37863.667171] xhci_hcd :49:00.3: xHCI host not responding to stop endpoint command. Jan 14 19:38:50 amaranth kernel: [37863.667178] xhci_hcd :49:00.3: xHCI host controller not responding, assume dead Jan 14 19:38:50 amaranth kernel: [37863.667220] xhci_hcd :49:00.3: HC died; cleaning up Jan 14 19:38:50 amaranth kernel: [37863.667255] usb 9-3: USB disconnect, device number 2 Jan 14 19:38:50 amaranth kernel: [37863.667258] usb 9-3.1: USB disconnect, device number 4 Jan 14 19:38:50 amaranth kernel: [37863.667447] usb 10-3: USB disconnect, device number 2 Jan 14 19:38:50 amaranth kernel: [37863.667449] usb 10-3.2: USB disconnect, device number 4 Jan 14 19:38:50 amaranth kernel: [37863.667451] usb 10-3.2.4: USB disconnect, device number 5 Jan 14 19:38:50 amaranth kernel: [37863.668402] usb 10-4: USB disconnect, device number 3 Jan 14 19:38:50 amaranth kernel: [37863.735579] usb 9-3.2: USB disconnect, device number 6 Jan 14 19:38:50 amaranth kernel: [37863.735581] usb 9-3.2.3: USB disconnect, device number 7 Jan 14 19:38:50 amaranth acpid: input device has been disconnected, fd 17 Jan 14 19:38:50 amaranth acpid: input device has been disconnected, fd 8 Jan 14 19:38:50 amaranth acpid: input device has been disconnected, fd 9 Jan 14 19:38:50 amaranth kernel: [37863.979627] usb 9-3.2.4: USB disconnect, device number 9 Jan 14 19:38:50 amaranth kernel: [37863.979630] usb 9-3.2.4.4: USB disconnect, device number 10 Jan 14 19:38:50 amaranth kernel: [37864.076604] usb 9-4: USB disconnect, device number 3 Jan 14 19:38:50 amaranth kernel: [37864.076833] usb 9-5: USB disconnect, device number 5 Jan 14 19:38:50 amaranth acpid: input device has been disconnected, fd 7 Jan 14 19:38:50 amaranth acpid: input device has been disconnected, fd 10 Jan 14 19:38:50 amaranth kernel: [37864.231560] usb 9-6: USB disconnect, device number 8 Jan 14 19:38:50 amaranth acpid: input device has been disconnected, fd 11 Jan 14 19:38:50 amaranth acpid: input device has been disconnected, fd 12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908894 Title: USB controllers disconnects after random time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893274] Re: Certbot will stop working for 23, 847 users with upcoming Let's Encrypt deprecation
Thank you for resolving this well before Let's Encrypt's brownouts! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893274 Title: Certbot will stop working for 23,847 users with upcoming Let's Encrypt deprecation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1893274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893274] Re: Certbot will stop working for 23, 847 users with upcoming Let's Encrypt deprecation
Testing this is pretty tricky because it's specific to the setup of Let's Encrypt's production ACMEv1 endpoint which no longer lets people create accounts or obtain certificates for new domains and we hardcoded the server URL. The way I'd test it is: 1. Obtain a real, trusted certificate from Let's Encrypt's production ACMEv2 endpoint. This is the default server for Certbot. 2. Run a command like `sudo sed -i 's/acme-v02/acme-v01/g' /etc/letsencrypt/renewal/*` to change the saved `server` value from ACMEv2 to ACMEv1. 3. Run `sudo certbot renew --force-renewal`. Pre-patch, Certbot should crash because it tries to use ACMEv1 (and an account doesn't exist), but post-patch it should switch to ACMEv2 and successfully renew the certificate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893274 Title: Certbot will stop working for 23,847 users with upcoming Let's Encrypt deprecation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1893274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893274] Re: Certbot will stop working for 23, 847 users with upcoming Let's Encrypt deprecation
> Brad, I'd appreciate your review wrt. your comment in https://bugs.launchpad.net/ubuntu/+source/python-certbot- nginx/+bug/1875471/comments/8 please. AIUI, I'm not breaking python- certbot-apache itself, just its tests, right? In other words, with my proposed fix I'm just moving a test failure from python-certbot to python-certbot-apache? I think it's even better than that. The change you made to Certbot's tests should have no effect on any other package. The tests for python- certbot-apache should still be broken as described at https://bugs.launchpad.net/ubuntu/+source/python-certbot- apache/+bug/1876934, but this change shouldn't add any new failures there. The concern about this change that I tried to express at https://bugs.launchpad.net/ubuntu/+source/python-certbot- nginx/+bug/1875471/comments/8 is we're deleting unit tests for the class certbot.plugins.common.TLSSNI01 while keeping it around and used in python-certbot-apache including for users at runtime. The test file you modified was previously completely broken though and you fixed it allowing the other tests there to run so in general I think it's an improvement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893274 Title: Certbot will stop working for 23,847 users with upcoming Let's Encrypt deprecation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1893274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885030] Re: [Intel] Add Error Disconnect Recover support
The following evaluation was done in early May In summary, EDR is brand new in upstream kernels and to my knowledge has not been exercised in-house at Canonical, and may be difficult to test due to a lack of systems with EDR functionality in their firmware. I am unsure as to what the state of regression testing is with regards to this type of PCI functionality. Some followup patches and discussion after the original EDR submission are below. To be clear, these are not part of the request from Nvidia. These are upstream followups to the EDR patch set, and are indicative of the final state of this functionality still being in flux. https://lore.kernel.org/linux-pci/1588272369-2145-1-git-send-email-jonathan.derr...@intel.com/ The above is unapplied upstream; it is proposed to fix an issue with the negotiation between the operating system and firmware for control for DPC, and as of 1 May 2020 is pending waiting for https://lore.kernel.org/linux-pci/67af2931705bed9a588b5a39d369cb70b9942190.1587925636.git.sathyanarayanan.kuppusw...@linux.intel.com/ to be sorted out. This patch (which is applied upstream to pci git tree for merging in 5.8) relates to how the operating system and firmware negotiate control of AER and DPC via the "firmware first" bit in the ACPI HEST vs. using the _OSC ACPI method. Prior to this patch, the ACPI HEST
[Bug 1885030] Re: [Intel] Add Error Disconnect Recover support
Based on this evaluation we have no plans at this time to backport these patches to the Focal 5.4 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885030 Title: [Intel] Add Error Disconnect Recover support To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1885030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842107] Re: [EHL][OSE] I2C implementation
These commits are in the 20.04 release kernel. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: intel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842107 Title: [EHL][OSE] I2C implementation To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842142] Re: [EHL][OSE] SPI implementation
This commit is in the released 20.04 kernel ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: intel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842142 Title: [EHL][OSE] SPI implementation To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842142] Re: [EHL][OSE] SPI implementation
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842142 Title: [EHL][OSE] SPI implementation To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842107] Re: [EHL][OSE] I2C implementation
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842107 Title: [EHL][OSE] I2C implementation To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
Thanks again for quickly helping with this issue everyone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875471 Title: python3-certbot-nginx is incompatible with its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876296] Re: Broken CURL operations
Works for me as of latest version. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876296 Title: Broken CURL operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dub/+bug/1876296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747499] Re: 98-reboot-required and Interaction with livepatch
I agree with comment #4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747499 Title: 98-reboot-required and Interaction with livepatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
I tested the proposed package successfully without any issues. I also examined the changes to our upstream files included in the package they are what I expected. It's our 0.40.0 certbot-nginx package with one test change backported from a newer version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875471 Title: python3-certbot-nginx is incompatible with its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
The package I tested was python3-certbot-nginx 0.40.0-0ubuntu0.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875471 Title: python3-certbot-nginx is incompatible with its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876296] Re: Broken CURL operations
Same problem here, I submitted a diff bug report, but this was what I was getting at. It's interesting because it doesn't appear on this version in other distros. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876296 Title: Broken CURL operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dub/+bug/1876296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
Fantastic! Thanks again Andreas. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875471 Title: python3-certbot-nginx is incompatible with its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
To offer one other option based on my previous comments while trying to keep things simple, I think in the short term you could also go with: d) Update just python-certbot-nginx to 0.40.0 and apply this patch to python-certbot-nginx's tests: https://gist.github.com/bmw/e4f13e17d1f4647c9d6be730c7ec3512. This change is the only changes to the files shipped in the nginx package from https://github.com/certbot/certbot/commit/4abd81e2186eddc67551d61a8260440bd177d18d. This option would fix the user facing problems in the nginx plugin and its tests without modifying any other packages. In the long term, I'm personally in favor of updating things as much as we can and doing as little backporting of commits as possible, but I'm fine with any of the approaches in the short term. I'll start looking into the test failures now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875471 Title: python3-certbot-nginx is incompatible with its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
I think changing the build-dep to python3-idna << 2.9 is acceptable. It looks like we hit a similar problem with the last SRU and I described the problem and how to fix the specific issue at the time at https://bugs.launchpad.net/ubuntu/+source/python- acme/+bug/1836823/comments/23. In this case, allowing python3-idna 2.8 should be fine because Focal has python3-requests 2.22.0 and the constraints that version of requests puts on idna are "idna>=2.5,<2.9" which can be seen at https://github.com/psf/requests/blob/v2.22.0/setup.py#L46. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875471 Title: python3-certbot-nginx is incompatible with its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
Thanks a lot for quickly working on this issue Andreas. Applying that commit to python-certbot 0.40.0-1 in addition to the python-certbot-nginx changes would fix both python-certbot and python- certbot-nginx's tests, however, it would break python-certbot-apache in normal usage outside of tests because it removes certbot.plugins.common.TLSSNI01 which is being used by python-certbot- apache 0.39.0-1 (despite it sending deprecation warnings every time the plugin references the object). This class in Certbot is meant to help plugins handle ACME TLSSNI01 objects, however, its implementation doesn't reference them itself. The problem occurs in the tests for this class in certbot/plugins/common_test.py where these ACME TLSSNI01 objects are created and this testing code is reused in python-certbot-nginx to help it test itself. Because of this, I don't really suspect there to be any future problems with certbot.plugins.common.TLSSNI01, however, the TLSSNI test failures in all of python-certbot, python-certbot-apache, and python-certbot- nginx may continue to be annoying in the future. To fix this, I think we have a few options. If we just wanted to fix python-certbot-nginx's tests and leave python- certbot and python-certbot-apache's untouched with broken tests, you could just apply the changes to certbot-nginx from https://github.com/certbot/certbot/commit/4abd81e2186eddc67551d61a8260440bd177d18d. That's a massive commit, however, the relevant changes to nginx are quite small and only to certbot- nginx/certbot_nginx/tests/http_01_test.py. If we want to try to fix python-certbot's tests now, you could skip these additional python-certbot-nginx changes described in my last paragraph and instead just take the test changes from the commit you found of https://github.com/certbot/certbot/commit/4b488614cf7749c8139c11f0983fe4b71e29827f. I have mixed feelings about this because while it solves some immediate problems, it removes all tests of certbot.plugins.common.TLSSNI01 while keeping the code which is needed to do unless you want to also update python-certbot-apache. If you are also hesitant to leave certbot.plugins.common.TLSSNI01 around without tests and would like to remove it and apply the full commit, you'd need to apply the changes to certbot-apache from https://github.com/certbot/certbot/commit/de6b56bec02881d5a63173aedb670b24d847f72d. If you want to fix python-certbot-apache's tests now, you could apply the changes to python-certbot-apache's tests from https://github.com/certbot/certbot/commit/63d673a3e04de4a64d18483a2f0df55c6a6c4198. This is all a lot backports, many of which require us to apply a subset of the changes from different commits, but things are honestly kind of a mess right now with the mix of 0.x and 1.x components. Again, a final option here would be to update all of these packages to any 1.x version and if the package's dependencies are satisfied, it should all just work, however, that'd come with the backwards incompatible changes I described in my previous post. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875471 Title: python3-certbot-nginx is incompatible with its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875471] Re: python3-certbot-nginx is incompatible with its dependencies
At the risk of sending the discussion in this issue off topic, I looked into other potential problems with the Certbot packages in Focal/Groovy since they've been being held back. I'm happy to move this discussion somewhere else if people prefer. In the current state in Focal/Groovy, the tests we include in our packages are broken for at least python-certbot, python-certbot-apache, and python-certbot-nginx. The python-certbot-dns-* packages themselves are working, but I didn't verify whether or not the tests are. I can if people think that's important. Only python-certbot-nginx is actually broken in Focal from a user perspective though which I described above. The reason for most of these problems is that these tests/packages were relying on parts of python-acme's API which has been removed in recent versions. A version of python-acme with these changes has already been pushed to Focal/Groovy causing the problem. In one case at https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#python-certbot though, I saw a different but similar problem with python-certbot where its proposed update had removed components being used by the old, packaged version of python- certbot-apache. For Groovy, if possible, I'd recommend upgrading all of python-certbot, python-certbot-apache, and python-certbot-nginx together to their latest versions and ignoring failures caused by testing older versions with these new packages. Again, many of the failures being seen are already present in the current packages and none of them will exist when everything is updated to a newer version. For Focal, while I'd love for all Certbot components to be >=1.0, doing this will cause a number of backwards incompatible changes. From our changelog, those are: * Certbot's `config_changes` subcommand has been removed * `certbot.plugins.common.TLSSNI01` has been removed. * The functions `certbot.plugins.common.Installer.view_config_changes`, `certbot.reverter.Reverter.view_config_changes`, and `certbot.util.get_systemd_os_info` have been removed * Certbot's `register --update-registration` subcommand has been removed * When possible, default to automatically configuring the webserver so all requests redirect to secure HTTPS access. This is mostly relevant when running Certbot in non-interactive mode. Previously, the default was to not redirect all requests. All of these changes are things warned about in the current version of our packages in Focal and are to minor aspects to our functionality. If these changes seem acceptable considering our SRU exception, how new Focal is, and the benefit we'll have of making it easier to update these packages going forward since they'll have made it through our API/UI changes and to Certbot 1.0, I'd recommend updating Groovy and then moving these packages to Focal. If these changes do not seem acceptable, I'd recommend taking one of the two paths I described in my previous post to fix python-certbot-nginx in Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875471 Title: python3-certbot-nginx is incompatible with its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875471] [NEW] python3-certbot-nginx is incompatible with its dependencies
Public bug reported: This issue only affects version 0.39.0-1 of the python-certbot-nginx package in Ubuntu 20.04. To reproduce the problem, install python3-certbot-nginx and run a command like: sudo certbot -d example.org --agree-tos --staging --register-unsafely- without-email --nginx This command will fail and the relevant output is: AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01' The problem here is python-certbot-nginx contains references to code in python-acme that has been removed. This problem makes python-certbot- nginx completely unable to obtain certificates. As the upstream maintainer of this package, I'll suggest two ways to fix this problem: 1. Update python-certbot-nginx to our 0.40.0 release. The benefit of this is it sticks to well tested versions of our software rather than making potentially error prone backports. Certbot has an SRU exception which can be seen at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot. The diff of code upstream between 0.39.0 and 0.40.0 if you all want to take this route can be see at https://gist.github.com/bmw/a88429687f4aed13e300fafdad85ce30. 2. You can manually backport minimal fixes. The only changes that should required from the above gist are the changes to: * certbot_nginx/configurator.py * certbot_nginx/tests/configurator_test.py While I have essentially no knowledge of creating .debs myself, please let me know if you have any questions resolving this, want help testing proposed packages, etc. ** Affects: python-certbot-nginx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875471 Title: python3-certbot-nginx is incompatible with its dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-nginx/+bug/1875471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873515] [NEW] Timeout when adding dependencies to project
Public bug reported: Dub cannot find dependencies at https://code.dlang.org this is the main registry. Works fine using the snap package 'dub'. Issue doesn't appear on 18.04 using a different version of dub. Version of dub downloaded from https://dlang.org/ works. I expect it to resolve dependencies and build my project. Output of lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 Output of apt-cache policy dub dub: Installed: 1.19.0-1build2 Candidate: 1.19.0-1build2 Version table: *** 1.19.0-1build2 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status Output of 'dub' when running 'dub build --verbose' using latest bindbc-sdl v0.16.0 (https://code.dlang.org/packages/bindbc-sdl) at time of writing: Using dub registry url 'https://code.dlang.org/' Refreshing local packages (refresh existing: true)... Looking for local package map at /var/lib/dub/packages/local-packages.json Looking for local package map at /home/ubuntu/.dub/packages/local-packages.json Looking for local package map at /home/ubuntu/testing/.dub/packages/local-packages.json Note: Failed to determine version of package testing at .. Assuming ~master. Refreshing local packages (refresh existing: false)... Looking for local package map at /var/lib/dub/packages/local-packages.json Looking for local package map at /home/ubuntu/.dub/packages/local-packages.json Looking for local package map at /home/ubuntu/testing/.dub/packages/local-packages.json Version selection for dependency bindbc-sdl (bindbc-sdl) of testing is missing. Missing dependency bindbc-sdl ~>0.16.0 of testing Refreshing local packages (refresh existing: false)... Looking for local package map at /var/lib/dub/packages/local-packages.json Looking for local package map at /home/ubuntu/.dub/packages/local-packages.json Looking for local package map at /home/ubuntu/testing/.dub/packages/local-packages.json Version selection for dependency bindbc-sdl (bindbc-sdl) of testing is missing. Missing dependency bindbc-sdl ~>0.16.0 of testing Checking for missing dependencies. Search for versions of bindbc-sdl (1 package suppliers) Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback package supplier registry at https://code-mirror.dlang.io/ failed with 'Failed to download https://code-mirror.dlang.io/api/packages/infos?packages=%5B%22bindbc-sdl%22%5D_dependencies=true=true'. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Package supplier registry at https://code.dlang.org/ failed with 'HTTP request returned status code 0 ()', trying fallbacks. Fallback registry at https://dub-registry.herokuapp.com/ succeeded Return for bindbc-sdl: [0.7.0, 0.6.1, 0.6.0, 0.5.1, 0.5.0, 0.4.1, 0.4.0, 0.3.0, 0.2.0, 0.1.0, ~master] Unresolvable dependencies to package bindbc-sdl: testing ~master depends on bindbc-sdl ~>0.16.0 ** Affects: dub (Ubuntu) Importance: Undecided Status: New -- You
[Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
I believe if got the exfat-fuse filesystem when I installed exfat-tools in order to mkexfatfs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
If I take the exfat flashdrive to a 20.04 system that does not have exfat-utils/exfat-fuse on it, it works exactly as I expect and mounts as an exfat filesystem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
exfat-utils that is -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866721] Re: Unable to use microphone in chrome
Not really no. Between this bug and https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853008 I was forced to remove chromium-browser and snapd from my system entirely and switch to the Google chrome binaries. Snap was also causing other issues on my system since for some reason the snap version of docker got installed and started interfering with my docker-ce installation from the docker apt repository. It's clearly not ready for prime-time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866721 Title: Unable to use microphone in chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866721] [NEW] Unable to use microphone in chrome
Public bug reported: Running Ubuntu 19.10 and the chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 package I am unable to use my microphone with sites that support it, such as discord. I can hear audio from websites like Youtube, but sites that want to use my microphone fail to do so, even though I give permission. I've tested with Hubs by Mozilla, Discord and https://www.onlinemictest.com/ All three properly prompt for permission, but then act as if I refused to give it when choose "allow". If I start chrome from the command line, when this happens I see this in the output [73233:73233:0309/165624.013771:ERROR:pulse_util.cc(300)] pa_operation is nullptr. The https://www.onlinemictest.com/ reports "Microphone not authorized. Please check your media permissions settings." My microphone works fine in Firefox. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866721 Title: Unable to use microphone in chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866132] [NEW] Overview window placement hides some windows in some multi-monitor configs
Public bug reported: I created an extensive report here: https://gitlab.gnome.org/GNOME/mutter/issues/1087 Basically if you have a portrait mode monitor that has a larger vertical resolution than the primary monitor, the primary monitor appears to place the overview previews as if it had that larger vertical resolution, and therefore some overview previews get pushed off the bottom of the monitor. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866132 Title: Overview window placement hides some windows in some multi-monitor configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1866132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Wow. This is all remarkably chill for a bug that boils down to "Chrome can't launch external apps". I just started a new job and I'm trying to set up ubuntu 19.10 as my primary desktop and I'm being blocked by this. Both slack and zoom fail to launch because of this. It also means that apps that want to use Google to authenticate, and thus launch chrome to run the google login and then get a URL callback don't work (Slack in particular). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864303] Re: Removing the e1000e module causes a crash
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864303 Title: Removing the e1000e module causes a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862682] Re: iSCSI-target: Deleting a LUN hangs in the kernel
** Package changed: linux-meta-hwe (Ubuntu) => linux-hwe (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862682 Title: iSCSI-target: Deleting a LUN hangs in the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1862682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle
If we think that single patch is a solution then can we get a test kernel with that patch made available for confirmation and then get that submitted so it can go into a official 20.04 kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853044 Title: 5.3.0-23-generic causes fans to spin when idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862028] [NEW] Focal uses the exfat fuse filesystem even though there is support in the kernel
Public bug reported: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858182] Re: Add support for Rizon 3900 Series Processors by updating to a newer kernel version
@ryan The kernel SRU workflow project is a special project that is only used for internal processes. Your bug should have been filed against the ubuntu/linux project which I have now fixed. Also note that we closely follow upstream stable releases and automatically pick them up. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858182 Title: Add support for Rizon 3900 Series Processors by updating to a newer kernel version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845886] Re: Enable GVE driver on GCP/GKE kernels
*** This bug is a duplicate of bug 1855992 *** https://bugs.launchpad.net/bugs/1855992 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845886 Title: Enable GVE driver on GCP/GKE kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856469] [NEW] GIMP 2.10 Crashed retrieving photo from server
Public bug reported: ``` GNU Image Manipulation Program version 2.10.14 git-describe: GIMP_2_10_12-511-ga4f55d6c7e C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) using babl version 0.1.72 (compiled against version 0.1.72) using GEGL version 0.4.18 (compiled against version 0.4.18) using GLib version 2.56.4 (compiled against version 2.56.4) using GdkPixbuf version 2.36.11 (compiled against version 2.36.11) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.40.14 (compiled against version 1.40.14) using Fontconfig version 2.12.6 (compiled against version 2.12.6) using Cairo version 1.15.10 (compiled against version 1.15.10) ``` > fatal error: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 18688 - Thread 18688 # [New LWP 18690] [New LWP 18692] [New LWP 18693] [New LWP 18696] [New LWP 19672] [New LWP 19674] [New LWP 22675] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [34m---[34m[1m[regs] [0m [32mRAX:[0m 0xFE00 [32mRBX:[0m 0x0014 [32mRCX:[0m 0x7F4B2200E384 [32mRDX:[0m 0x0100 [1m[4m[31mo d I t s Z a P c [0m [32mRSI:[0m 0x7FFFE4FBA750 [32mRDI:[0m 0x0014 [32mRBP:[0m 0x7FFFE4FBA750 [32mRSP:[0m 0x7FFFE4FBA360 [32mRIP:[0m 0x7F4B2200E384 [32mR8 :[0m 0x [32mR9 :[0m 0x [32mR10:[0m 0x [32mR11:[0m 0x0246 [32mR12:[0m 0x0100 [32mR13:[0m 0x55FF7D0A54D0 [32mR14:[0m 0x [32mR15:[0m 0x4900 [32mCS:[0m 0033 [32mDS:[0m [32mES:[0m [32mFS:[0m [32mGS:[0m [32mSS:[0m 002B[0m [36m[0m[34m---[34m[1m[code] [0m=> 0x7f4b2200e384 <__libc_read+68>: cmprax,0xf000 0x7f4b2200e38a <__libc_read+74>: ja 0x7f4b2200e3c4 <__libc_read+132> 0x7f4b2200e38c <__libc_read+76>: movedi,r8d 0x7f4b2200e38f <__libc_read+79>: movQWORD PTR [rsp+0x8],rax 0x7f4b2200e394 <__libc_read+84>: call 0x7f4b2200e060 <__pthread_disable_asynccancel> 0x7f4b2200e399 <__libc_read+89>: movrax,QWORD PTR [rsp+0x8] 0x7f4b2200e39e <__libc_read+94>: addrsp,0x10 0x7f4b2200e3a2 <__libc_read+98>: poprbx [34m- [0m0x7f4b2200e384 in __libc_read (fd=0x14, buf=0x7fffe4fba750, nbytes=0x100) at ../sysdeps/unix/sysv/linux/read.c:27 Id Target Id Frame * 1Thread 0x7f4b26e3ee00 (LWP 18688) "gimp-2.10" 0x7f4b2200e384 in __libc_read (fd=0x14, buf=0x7fffe4fba750, nbytes=0x100) at ../sysdeps/unix/sysv/linux/read.c:27 2Thread 0x7f4b184c8700 (LWP 18690) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7f4b15b85700 (LWP 18692) "gmain" 0x7f4b21d20bf9 in __GI___poll (fds=0x55ff79cdd2a0, nfds=0x2, timeout=0x) at ../sysdeps/unix/sysv/linux/poll.c:29 4Thread 0x7f4b15384700 (LWP 18693) "gdbus" 0x7f4b21d20bf9 in __GI___poll (fds=0x55ff7ddd87d0, nfds=0x4, timeout=0x) at ../sysdeps/unix/sysv/linux/poll.c:29 5Thread 0x7f4af0ccf700 (LWP 18696) "async" syscall () at
[Bug 1851749] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303661/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851749] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303657/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
