[Bug 1961738] Re: UBSAN: shift-out-of-bounds in .../intel_opregion.c:388:15
** Tags added: i915 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961738 Title: UBSAN: shift-out-of-bounds in .../intel_opregion.c:388:15 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1961738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961121] Re: Not able to enter s2idle state on AMD platforms
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => Alex Hung (alexhung) ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961121 Title: Not able to enter s2idle state on AMD platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913964] Re: Stacer crashes randomly on start
Sorry I can't reproduce this on 22.04 LTS... I'll try to try it on 20.04 LTS when I find one... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913964 Title: Stacer crashes randomly on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stacer/+bug/1913964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961738] Re: UBSAN: shift-out-of-bounds in .../intel_opregion.c:388:15
Fixed upstream it seems: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915/display/intel_opregion.c?h=v5.17-rc5=ea958422291de248b9e2eaaeea36004e84b64043 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4800 https://gitlab.freedesktop.org/drm/intel/-/issues/4800 ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/4800 Importance: Unknown Status: Unknown ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Description changed: - This seems to happen at boot on all 11th gen Intel systems: + This seems to happen at boot on all 11th gen Intel systems I've seen. + But also on a 10th gen Intel system seen in other bug reports. [1.778960] [1.778964] UBSAN: shift-out-of-bounds in /build/linux-aa0B4d/linux-5.15.0/drivers/gpu/drm/i915/display/intel_opregion.c:388:15 [1.778967] shift exponent 37 is too large for 32-bit type 'unsigned int' [1.778969] CPU: 5 PID: 374 Comm: systemd-udevd Not tainted 5.15.0-18-generic #18-Ubuntu [1.778970] Hardware name: Microsoft Corporation Surface Laptop 4/Surface Laptop 4, BIOS 10.300.141 06/17/2021 [1.778971] Call Trace: [1.778972] [1.778973] show_stack+0x52/0x58 [1.778977] dump_stack_lvl+0x4a/0x5f [1.778979] dump_stack+0x10/0x12 [1.778980] ubsan_epilogue+0x9/0x45 [1.778981] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xe9 [1.778983] ? icl_ddi_tc_is_clock_enabled+0x4d/0xc0 [i915] [1.779060] intel_opregion_notify_encoder.cold+0x2b/0x45 [i915] [1.779129] intel_sanitize_encoder+0x1e2/0x270 [i915] [1.779187] intel_modeset_setup_hw_state+0x322/0x680 [i915] [1.779236] ? drm_modeset_lock_all_ctx+0x151/0x1c0 [drm] [1.779253] ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0x90 [drm] [1.779265] intel_modeset_init_nogem+0x2a8/0x510 [i915] [1.779315] ? intel_irq_postinstall+0x38b/0x680 [i915] [1.779358] i915_driver_probe+0x1b7/0x470 [i915] [1.779395] ? mutex_lock+0x13/0x40 [1.779399] i915_pci_probe+0x58/0x140 [i915] [1.779435] local_pci_probe+0x48/0x90 [1.779438] pci_device_probe+0x115/0x1f0 [1.779439] really_probe+0x21b/0x420 [1.779442] __driver_probe_device+0x115/0x190 [1.779444] driver_probe_device+0x23/0xc0 [1.779445] __driver_attach+0xbd/0x1d0 [1.779447] ? __device_attach_driver+0x110/0x110 [1.779448] bus_for_each_dev+0x7c/0xc0 [1.779450] driver_attach+0x1e/0x20 [1.779452] bus_add_driver+0x135/0x200 [1.779453] driver_register+0x95/0xf0 [1.779454] __pci_register_driver+0x68/0x70 [1.779455] i915_register_pci_driver+0x23/0x30 [i915] [1.779488] i915_init+0x3b/0xfc [i915] [1.779534] ? 0xc1229000 [1.779535] do_one_initcall+0x46/0x1d0 [1.779539] ? kmem_cache_alloc_trace+0x19e/0x2e0 [1.779543] do_init_module+0x62/0x280 [1.779545] load_module+0xac9/0xbb0 [1.779546] __do_sys_finit_module+0xbf/0x120 [1.779548] __x64_sys_finit_module+0x18/0x20 [1.779549] do_syscall_64+0x59/0xc0 [1.779551] ? do_syscall_64+0x69/0xc0 [1.779552] ? do_syscall_64+0x69/0xc0 [1.779553] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.779555] RIP: 0033:0x7f0a61a13a3d [1.779557] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 53 0f 00 f7 d8 64 89 01 48 [1.779558] RSP: 002b:7ffcfe9e0748 EFLAGS: 0246 ORIG_RAX: 0139 [1.779560] RAX: ffda RBX: 5601776d2090 RCX: 7f0a61a13a3d [1.779561] RDX: RSI: 7f0a61ba8441 RDI: 0017 [1.779561] RBP: 0002 R08: R09: 0002 [1.779562] R10: 0017 R11: 0246 R12: 7f0a61ba8441 [1.779562] R13: 5601776cd450 R14: 5601777f7d60 R15: 5601777f8e30 [1.779564] [1.779564] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: dan1364 F pipewire-media- - dan1365 F pulseaudio - /dev/snd/seq:dan1363 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC0: dan1364 F pipewire-media- + dan1365 F pulseaudio
[Bug 1961738] [NEW] UBSAN: shift-out-of-bounds in .../intel_opregion.c:388:15
Public bug reported: This seems to happen at boot on all 11th gen Intel systems I've seen. But also on a 10th gen Intel system seen in other bug reports. [1.778960] [1.778964] UBSAN: shift-out-of-bounds in /build/linux-aa0B4d/linux-5.15.0/drivers/gpu/drm/i915/display/intel_opregion.c:388:15 [1.778967] shift exponent 37 is too large for 32-bit type 'unsigned int' [1.778969] CPU: 5 PID: 374 Comm: systemd-udevd Not tainted 5.15.0-18-generic #18-Ubuntu [1.778970] Hardware name: Microsoft Corporation Surface Laptop 4/Surface Laptop 4, BIOS 10.300.141 06/17/2021 [1.778971] Call Trace: [1.778972] [1.778973] show_stack+0x52/0x58 [1.778977] dump_stack_lvl+0x4a/0x5f [1.778979] dump_stack+0x10/0x12 [1.778980] ubsan_epilogue+0x9/0x45 [1.778981] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xe9 [1.778983] ? icl_ddi_tc_is_clock_enabled+0x4d/0xc0 [i915] [1.779060] intel_opregion_notify_encoder.cold+0x2b/0x45 [i915] [1.779129] intel_sanitize_encoder+0x1e2/0x270 [i915] [1.779187] intel_modeset_setup_hw_state+0x322/0x680 [i915] [1.779236] ? drm_modeset_lock_all_ctx+0x151/0x1c0 [drm] [1.779253] ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0x90 [drm] [1.779265] intel_modeset_init_nogem+0x2a8/0x510 [i915] [1.779315] ? intel_irq_postinstall+0x38b/0x680 [i915] [1.779358] i915_driver_probe+0x1b7/0x470 [i915] [1.779395] ? mutex_lock+0x13/0x40 [1.779399] i915_pci_probe+0x58/0x140 [i915] [1.779435] local_pci_probe+0x48/0x90 [1.779438] pci_device_probe+0x115/0x1f0 [1.779439] really_probe+0x21b/0x420 [1.779442] __driver_probe_device+0x115/0x190 [1.779444] driver_probe_device+0x23/0xc0 [1.779445] __driver_attach+0xbd/0x1d0 [1.779447] ? __device_attach_driver+0x110/0x110 [1.779448] bus_for_each_dev+0x7c/0xc0 [1.779450] driver_attach+0x1e/0x20 [1.779452] bus_add_driver+0x135/0x200 [1.779453] driver_register+0x95/0xf0 [1.779454] __pci_register_driver+0x68/0x70 [1.779455] i915_register_pci_driver+0x23/0x30 [i915] [1.779488] i915_init+0x3b/0xfc [i915] [1.779534] ? 0xc1229000 [1.779535] do_one_initcall+0x46/0x1d0 [1.779539] ? kmem_cache_alloc_trace+0x19e/0x2e0 [1.779543] do_init_module+0x62/0x280 [1.779545] load_module+0xac9/0xbb0 [1.779546] __do_sys_finit_module+0xbf/0x120 [1.779548] __x64_sys_finit_module+0x18/0x20 [1.779549] do_syscall_64+0x59/0xc0 [1.779551] ? do_syscall_64+0x69/0xc0 [1.779552] ? do_syscall_64+0x69/0xc0 [1.779553] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.779555] RIP: 0033:0x7f0a61a13a3d [1.779557] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 53 0f 00 f7 d8 64 89 01 48 [1.779558] RSP: 002b:7ffcfe9e0748 EFLAGS: 0246 ORIG_RAX: 0139 [1.779560] RAX: ffda RBX: 5601776d2090 RCX: 7f0a61a13a3d [1.779561] RDX: RSI: 7f0a61ba8441 RDI: 0017 [1.779561] RBP: 0002 R08: R09: 0002 [1.779562] R10: 0017 R11: 0246 R12: 7f0a61ba8441 [1.779562] R13: 5601776cd450 R14: 5601777f7d60 R15: 5601777f8e30 [1.779564] [1.779564] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1364 F pipewire-media- dan1365 F pulseaudio /dev/snd/seq:dan1363 F pipewire CasperMD5CheckResult: pass CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Tue Feb 22 15:11:13 2022 InstallationDate: Installed on 2022-02-14 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220214) MachineType: Microsoft Corporation Surface Laptop 4 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=6f840793-70c0-4fc9-b509-2f18ca9665ac ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220217.git6342082c-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2021 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 10.300.141
[Bug 1961739] [NEW] PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform
Public bug reported: With bug 1957026, suspend/resume using rtc and power button work as expected, but PS/2 or USB keyboard still do not work well as an wakeup source. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: amd oem-priority originate-from-1961616 ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Tags added: amd oem-priority originate-from-1961616 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961739 Title: PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913964] Re: Stacer crashes randomly on start
** Changed in: stacer (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913964 Title: Stacer crashes randomly on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stacer/+bug/1913964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957050] Re: [MIR] suitesparse-graphblas
Seems this is not enough and it’s again in the graph: o suitesparse-graphblas: libgraphblas-dev libgraphblas-doc libgraphblas6 [Reverse-Depends: Rescued from suitesparse-graphblas, libgraphblas-dev] [Reverse-Recommends: libsuitesparse-dev] Seb, if you have some spare cycle, mind having another look? Let’s reuse this bug to track it. ** Changed in: suitesparse-graphblas (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: suitesparse-graphblas (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957050 Title: [MIR] suitesparse-graphblas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/suitesparse-graphblas/+bug/1957050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961023] Re: [MIR] glade
This is still appearing on the component mismatch list. Seb, do you mind having another look? o glade: gir1.2-gladeui-2.0 libgladeui-2-13 libgladeui-common libgladeui-dev libgladeui-doc MIR: #1961023 (Fix Released) [MIR] glade [Reverse-Depends: Rescued from glade, libgladeui-2-13, libhandy-1-dev] I wonder if the graph/detection is not broken for those use cases since we can have -dev packages in universe, which is when things started to be looking weird. However, it still worths a double check. Someone needs to take time at some point to figure out all those false positives, if they are as such. I’m reusing this bug to track the work. ** Changed in: glade (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: glade (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961023 Title: [MIR] glade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glade/+bug/1961023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961737] Re: package grub-common 2.04-1ubuntu47 failed to install/upgrade: il sottoprocesso installato pacchetto grub-common script post-installation ha restituito lo stato di errore 1
boh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961737 Title: package grub-common 2.04-1ubuntu47 failed to install/upgrade: il sottoprocesso installato pacchetto grub-common script post- installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1961737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961737] [NEW] package grub-common 2.04-1ubuntu47 failed to install/upgrade: il sottoprocesso installato pacchetto grub-common script post-installation ha restituito lo stato di errore 1
Public bug reported: boh ProblemType: Package DistroRelease: Ubuntu 21.10 Package: grub-common 2.04-1ubuntu47 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 21 16:32:42 2022 ErrorMessage: il sottoprocesso installato pacchetto grub-common script post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2021-01-27 (390 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=6878c379-4a46-45c3-9272-17100668e821 ro quiet splash Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: grub2 Title: package grub-common 2.04-1ubuntu47 failed to install/upgrade: il sottoprocesso installato pacchetto grub-common script post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961737 Title: package grub-common 2.04-1ubuntu47 failed to install/upgrade: il sottoprocesso installato pacchetto grub-common script post- installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1961737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959110] Re: pl2303 serial adapter no longer recognized
Awesome! Thanks for checking, I will close this bug with Fix-released. For those who are still having issue with this device, please feel free to open a new bug report. ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: Incomplete => 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/1959110 Title: pl2303 serial adapter no longer recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959420] debdiff_s390-tools_2.17_to_2.20.diff
Default Comment by Bridge ** Attachment added: "debdiff_s390-tools_2.17_to_2.20.diff" https://bugs.launchpad.net/bugs/1959420/+attachment/5562617/+files/debdiff_s390-tools_2.17_to_2.20.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959420 Title: [22.04 FEAT] Upgrade s390utils/s390-tools to latest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959110] Re: pl2303 serial adapter no longer recognized
Good morning. I can confirm my pl2303 devices work in Ubuntu-5.13.0-30.33. Thanks /Fredrik -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959110 Title: pl2303 serial adapter no longer recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959420] Re: [22.04 FEAT] Upgrade s390utils/s390-tools to latest version
Uploaded another updated debdiff that now includes the three patches from LP#1959965 that were made available over night. debdiff for version bump from 2.17 to 2.20 (including LP#1959965) ** Patch removed: "debdiff_s390-tools_2.17_to_2.20.diff" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1959420/+attachment/5562572/+files/debdiff_s390-tools_2.17_to_2.20.diff ** Patch added: "debdiff for version bump from 2.17 to 2.20 (including LP#1959965)" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1959420/+attachment/5562616/+files/debdiff_s390-tools_2.17_to_2.20.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959420 Title: [22.04 FEAT] Upgrade s390utils/s390-tools to latest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961645] Re: QEMU packages have circular dependencies
Oh wow!!! :) Just as I said, q-b-e should also list qemu-utils as one of the alternatives. This is the problem here, not the long list of other alternatives you're trying to remove, but the single alternative - qemu- utils - which is missing here. This one I'll fix right away. That's really an interesting case here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961645 Title: QEMU packages have circular dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1961645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961645] Re: QEMU packages have circular dependencies
Actually this is fixed quite long time ago (but not in any released stable version), in this commit: commit 15bf92b50ca51e078575587bf0f26085d1ecbf88 Author: Michael Tokarev Date: Wed Aug 18 16:43:23 2021 +0300 d/control: reformat Depends for qemu-block-extra, do not include -xen version there, mark -x390x as ubuntu-only, and allow qemu-utils to satisfy the dependency -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961645 Title: QEMU packages have circular dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1961645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915130] Re: libnfsidmap-regex package broken in current LTS release (focal)
would be great if you could test https://packages.debian.org/source/experimental/nfs-utils -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915130 Title: libnfsidmap-regex package broken in current LTS release (focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnfsidmap-regex/+bug/1915130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881733] Re: Cannot access repository page: "FrozenError"
Instead of using the debian package to install redmine install from subversion https://www.redmine.org/projects/redmine/wiki/Download use 4.2.3 Using instructions here: https://www.redmine.org/projects/redmine/wiki/redmineinstall 4.2 has support fully for ruby 2.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881733 Title: Cannot access repository page: "FrozenError" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redmine/+bug/1881733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961645] Re: QEMU packages have circular dependencies
The point that really concerns me is the disk usage. I just want to install qemu-utils, not qemu-system-x86. In my opinion qemu-utils and qemu-system-x86 are applications and qemu- block-extra are libraries. Applications depend on libraries, but not vice versa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961645 Title: QEMU packages have circular dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1961645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961733] Re: Jammy on ZFS: Ubiquity installer creates efi partition, then uses existing efi partition on another drive
** Bug watch added: Email to cjwatson@canonical # mailto:cjwat...@canonical.com ** Also affects: ubiquity via mailto:cjwat...@canonical.com 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/1961733 Title: Jammy on ZFS: Ubiquity installer creates efi partition, then uses existing efi partition on another drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubiquity/+bug/1961733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from
** Changed in: gjs (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-gjs-1.71.2 fixed-upstream ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1960898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961697] Re: Transaction ID collisions cause slow DNS lookups in getaddrinfo
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glibc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961697 Title: Transaction ID collisions cause slow DNS lookups in getaddrinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961733] [NEW] Jammy on ZFS: Ubiquity installer creates efi partition, then uses existing efi partition on another drive
Public bug reported: Expected: Ubiquity would create efi partition, `/dev/nvme2n1p1`, on installation drive for Ubuntu, `/dev/nvme2n1`, and use the Ubiquity-created partition for installing efi bootloader `/etc/fstab` would reflect the installation of efi bootloader on partition created for efi, `/dev/nvme2n1p1` on installation drive, `/dev/nvme2n1`, mount appropriate partition at `/boot/efi` on startup, and direct future invocations of `grub-mkconfig` accordingly. Actual: Ubiquity created the efi partition on the installation drive, `/dev/nvme2n1p1`, and presumably installed grub/efi on the newly created partition, but somehow referenced a different efi partition in the system, `/dev/nvme0n1p1`, when creating `/etc/fstab`. Having targeted this other existing efi partition in `/etc/fstab`, `/dev/nvme0n1p1`, all subsequent `grub-mkconfig` invocations were targeting this other efi partition on a separate drive, `/dev/nvme0n1p1`, instead of the partition created by Ubiquity for efi, `/dev/nvme2n1p1` on the drive where it installed Ubuntu (the one where efi was "supposed" to be located). Note `/var/log/installer/syslog` suggests grub was installed to Ubuntu installation drive without issue: ``` Feb 17 20:10:14 ubuntu grub-installer: info: Installing grub on '/dev/nvme2n1' Feb 17 20:10:14 ubuntu grub-installer: info: grub-install does not support --no-floppy Feb 17 20:10:14 ubuntu grub-installer: info: Running chroot /target grub-install --force --target x86_64-efi "/dev/nvme2n1" Feb 17 20:10:14 ubuntu grub-installer: Installing for x86_64-efi platform. Feb 17 20:10:15 ubuntu grub-installer: Installation finished. No error reported. Feb 17 20:10:15 ubuntu grub-installer: info: grub-install ran successfully ``` However, `/etc/fstab` shows that `/dev/nvme2n1p1` is not the efi partition, `/dev/nvme0n1p1` is: ``` # # /boot/efi was on /dev/nvme0n1p1 during installation UUID=B045-5C3B /boot/efi vfatumask=0022,fmask=0022,dmask=0022 0 1 /boot/efi/grub /boot/grub nonedefaults,bind 0 0 UUID=584b9b78-7d8d-4a5a-9263-d6f6a48adc6b noneswapsw 0 0 ``` Steps: On computer with >= two hard drives, the opposite drive targeted for installation having a previous linux installation and existing (leftover) efi partition: Boot jammy installer USB Select install Select ZFS as filesystem Wipe installation target drive Proceed through installer as normal (no special conditions) reboot check `/etc/fstab` to find opposite drive used for Ubuntu has been configured for efi partition Background: I started investigating this situation when I noticed there was no history entry in my grub menu for the zfs snapshots taken by `zsys`. Finally tracked down that it was because efi had been put on another drive, but not until exhausting several other possibilities. Initially thought it was an issue with `zsys` not creating snapshot entries. When I determined `zsys` was working I thought it might be `/etc/grub.d/10_linux_zfs` not identifying the snapshots. Turns out it was the installer the whole time, although I am not sure why grub cannot create history entries in a grub menu on an efi partition of a different drive, so perhaps there is additionally an issue with grub. However, I am assuming that because of the automatic entry created in `/etc/fstab`, Ubiquity was most likely responsible for choosing the other drive for efi, despite what its logs say. Ubiquity should probably use the partition it creates for efi instead of using one from another drive, therefore I think this is a reasonable bug to report. This is similar to issue: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1890453 However, I created a new issue since bug 1890453 involves a Macintosh installation, while my case involves choosing the ZFS option in Ubiquity installer, so I was not sure if my issue specific to the ZFS option, or theirs specific to being installed on a Mac. Long story short, had Ubiquity configured `/etc/fstab` for the partition it made for grub/efi, history entry would have been present in grub menu. Once I changed `/etc/fstab` to use the partition Ubiquity created for efi, the history menu appeared and was able to be viewed and utilized as normal. There is a very long comment on Github zsys repo here regarding the steps I went through to debug - it is missing the part where I investigated `/var/log/installer/syslog`, as I only became aware of that log's existence after coming to file this bug, so it is missing the assumption that the misconfiguration was only in `/etc/fstab` and not the installer using the wrong drive altogether: https://github.com/ubuntu/zsys/issues/223 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/var/log/installer contents - including syslog and partman" https://bugs.launchpad.net/bugs/1961733/+attachment/5562615/+files/installer-logs.tar.gz -- You
[Bug 1955325] Re: Firefox cannot open files in /usr/local/share/doc
** Summary changed: - Firefox cannot open files in /usr/local/doc + Firefox cannot open files in /usr/local/share/doc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955325 Title: Firefox cannot open files in /usr/local/share/doc To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1955325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959712] Re: [SRU] Add iSCSI support to HPE 3PAR driver for Primera 4.2 and higher
Thanks Nobuto for response. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959712 Title: [SRU] Add iSCSI support to HPE 3PAR driver for Primera 4.2 and higher To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1959712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961697] Re: Transaction ID collisions cause slow DNS lookups in getaddrinfo
** Attachment added: "glibc backtrace from hang" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+attachment/5562613/+files/glibc_backtrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961697 Title: Transaction ID collisions cause slow DNS lookups in getaddrinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961697] Re: Transaction ID collisions cause slow DNS lookups in getaddrinfo
** Attachment added: "Packet capture showing DNS queries with same txnid" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+attachment/5562612/+files/dns_same_txid.pcap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961697 Title: Transaction ID collisions cause slow DNS lookups in getaddrinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961697] [NEW] Transaction ID collisions cause slow DNS lookups in getaddrinfo
Public bug reported: When resolving DNS names with getaddrinfo(), I have seen this hang for 5 seconds and then retry and succeed. The issue is that glibc will issue a both an A and query on the same socket, and in some circumstances they can be sent with the same DNS transaction ID as well. I verified this with a packet capture; in the packet capture, I saw the A and queries for a name be made with the same DNS transaction ID, get responses, do nothing for five seconds, and then send the same DNS query again. On the glibc side, I confirmed that it's blocked waiting for the DNS response by interrupting it with gdb, even though the packet capture shows the response has well and truly arrived. I've attached a packet capture & a backtrace of the glibc hang. I believe this is the same issue reported in these places: * In RHEL: https://bugzilla.redhat.com/show_bug.cgi?id=1904153 * Also RHEL: https://bugzilla.redhat.com/show_bug.cgi?id=1903880 * Upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=26600 The environment I noticed this bug in was: * Docker for Mac on an arm64 m1 Macbook * Docker for Mac Linux kernel version is 5.10.76-linuxkit * Linux is also arm64, not emulated * Container with the buggy DNS environment is Ubuntu bionic (also arm64, not emulated) * Glibc 2.27-3ubuntu1.4 However one of the redhat reporters noticed this issue in m6 series EC2 instances in AWS. A patch has been provided upstream for this issue: https://sourceware.org/pipermail/libc-alpha/2020-September/117547.html I applied the upstream patch to glibc 2.27-3ubuntu1.4 and rebuilt the package, and the problem went away. I've attached the exact patch I applied, since I had to work through some conflicts. So, I think that patch just needs to be backported to Bionic and (I think) Focal as well. Is that reasonable? Thanks! ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Patch added: "upstream patch with conflicts resolved for 2.27" https://bugs.launchpad.net/bugs/1961697/+attachment/5562611/+files/resolv-txnid-collision.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961697 Title: Transaction ID collisions cause slow DNS lookups in getaddrinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961645] Re: QEMU packages have circular dependencies
nope, you're wrong. qemu-block-extra is a set of plugins. This package is useless without one of the other binary packages which can load these plugins. This is one of qemu-system-foo, AND qemu-utils - that's the set of packages q-b-e should depend on in order to actually work. And speaking of qemu-utils - it looks like this one is missing in the list of dep alternatives. On the other hand, qemu-system-* does not depend on its plugins, the plugins are optional. And I've no idea why ubuntu makess this a hard dependency - on debian this is just recommends, - or else q-b-e should not be a separate package to begin with, the plugins can be complied into the other binary packages just fine. BTW, putting this logic aside: what's wrong with circular dependencies? Note this is all the same source, so it's easy to fulfill the deps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961645 Title: QEMU packages have circular dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1961645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938964] Re: icmp_redirect from selftests fails on F/kvm (unary operator expected)
This test is not failing with "unary operator expected" anymore on B-ibm-5.4.0-1015.16~18.04.1 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938964 Title: icmp_redirect from selftests fails on F/kvm (unary operator expected) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1938964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959110] Re: pl2303 serial adapter no longer recognized
Hello,
the fix mentioned in comment #3:
dcf097e7d21f ("USB: serial: pl2303: fix GL type detection")
Has already landed in the Ubuntu 5.13 Impish tree:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-impish.git/commit/?id=77f82bf386d90b9b8e30ca0449177d8fcc3f06b6
With version:
$ git tag --contains 77f82bf386d90b9b8e30ca0449177d8fcc3f06b6
Ubuntu-5.13.0-21.21
Ubuntu-5.13.0-22.22
Ubuntu-5.13.0-23.23
Ubuntu-5.13.0-24.24
Ubuntu-5.13.0-25.26
Ubuntu-5.13.0-26.27
Ubuntu-5.13.0-27.29
Ubuntu-5.13.0-28.31
Ubuntu-5.13.0-29.32
Ubuntu-5.13.0-30.33
Ubuntu-5.13.0-31.34
So apparently this is not the one.
However the fix mentioned in the bug description:
aa5721a9 ("USB: serial: pl2303: fix GC type detection")
Has landed on 5.13 Impish tree as well:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-impish.git/commit/?id=4e1c49e9822a81d05f0518b78968681b8b95c13e
With version:
$ git tag --contain 4e1c49e9822a81d05f0518b78968681b8b95c13e
Ubuntu-5.13.0-29.32
Ubuntu-5.13.0-30.33
Ubuntu-5.13.0-31.34
Please upgrade your kernel to give the latest Ubuntu 5.13 Impish kernel a try
and check if this can solve your problem.
Thanks!
** Changed in: linux-signed-hwe-5.13 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959110
Title:
pl2303 serial adapter no longer recognized
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959110/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827735] Re: DBus/MPRIS2: Totem says it is "Paused" even the stream has ended "Stopped"
** Changed in: totem 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/1827735 Title: DBus/MPRIS2: Totem says it is "Paused" even the stream has ended "Stopped" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1827735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961645] Re: QEMU packages have circular dependencies
The attachment "0001-remove-circular-dependencies.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961645 Title: QEMU packages have circular dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1961645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955667] Re: installation failed
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955667 Title: installation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1955667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946834] Re: Merge multipath-tools from Debian unstable for 22.04
This bug was fixed in the package multipath-tools - 0.8.8-1ubuntu1
---
multipath-tools (0.8.8-1ubuntu1) jammy; urgency=medium
* Merge with Debian unstable (LP: #1946834, #1961136). Remaining changes:
- d/p/enable-find-multipaths.patch: re-enable find_multipaths by
default -- see the removed 'add_find-multipaths.patch' (LP 1463046)
- d/p/kpartx-Improve-finding-loopback-device-by-file.patch: Improve
finding loopback devices (LP 1747044)
- d/multipath.conf: Install friendly names multipath.conf by default,
instead of generating it in every installer.
- debian/multipath-tools.dm-mpath-lvm.udev: Adjust initramfs integration
for new udev rules
- Remove d/initramfs/local-top (redundant with other initramfs scripts):
+ init-top: take over loading modules (dm-multipath and SCSI device
handlers); move the missing dm-emc there (now scsi-dh-emc; see
BTS 567014).
+ d/rules: do not install local-top anymore.
+ remove d/initramfs/local-top
- debian/initramfs/hooks: Add dm-queue-length: users may want to
change from the default selector and should be able to do so.
(LP 1673350)
- multipath initramfs fixes for booting from multipathed devices:
+ d/initramfs/hooks: also copy wwids file on the installed
system to ensure all paths come up on boot. (LP 1479929)
+ d/initramfs/hooks: install multipathd and required
directories.
+ d/initramfs/hooks: copy multipath udev rules to initramfs
+ d/initramfs/hooks: do not copy kpartx rules to initramfs
+ d/initramfs/local-bottom: remember to stop multipathd.
+ d/initramfs/local-premount: wait for udev to settle before
the call to resolve_device() in local_mount_root(), so the
by-uuid/ symlinks have a chance to be updated by the
multipath udev rules (LP 1503286).
+ d/initramfs/local-premount: Run multipath with -B so not to
assign names nor change /etc/multipath/bindings during
initramfs (LP 1561103)
+ d/rules: install d/initramfs/local-bottom
+ d/rules: install d/initramfs/local-premount
- debian/initramfs/local-bottom: wait for the multipathd unix
socket to close, so to avoid multipathd.socket unit failure.
(LP 1682178)
- Split kpartx initramfs bits into kpartx-boot for dmraid (LP 941874)
+ d/initramfs/kpartx.hook
+ d/kpartx-boot.postinst
+ d/kpartx-boot.postrm
+ d/control: Add kpartx-boot package for dmraid
+ d/rules: Install kpartx initramfs hook
- d/rules: Move udev rules to priority 95, because rules that load
modules should be >90.
- Don't build the multipath-tools binary package on i386; we only want
kpartx.
* Dropped changes:
- Use stable wwn-* names in autopkgtest that work with or without
friendly names, as scsi-${DM_NAME} is not a stable symlink name.
[ Included in 0.8.8-1 ]
- debian/tests/tgtbasedmpaths: Add sleep to allow for device creation
[ Included in 0.8.8-1 ]
- d/p/kpartx_more_loopback_fixes.patch: fix loopback mounted files
some more: since we stat() the loopback device node, we can't rely
on S_ISREG() tests to handle this case, and should look at the
device itself instead. (LP 1543430)
[ Applied upstream in 0.8.6 ]
- d/p/no-start-in-containers.patch: Do not attempt to start
multipath-tools in containers, should switch for on-demand udev/socket
based activation in the future. (LP 1823093)
[ Applied upstream in 0.8.7 ]
- d/t/control: use allow-stderr for kpartx-file-loopback, the new
gdisks version displays warnings on stderr now.
[ Fixed in 0.8.8-1 ]
* Added changes:
- d/t/kpartx-file-loopback: silence kpartx messages to stderr
- d/rules: remove -Bsymbolic-functions from LDFLAGS
-- Athos Ribeiro Mon, 21 Feb 2022
18:18:27 -0300
** Changed in: multipath-tools (Ubuntu)
Status: In Progress => 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/1946834
Title:
Merge multipath-tools from Debian unstable for 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1946834/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961136] Re: Syslog shows "multipathd[3142]: failed to increase buffer size" in Ubuntu 22.04
This bug was fixed in the package multipath-tools - 0.8.8-1ubuntu1
---
multipath-tools (0.8.8-1ubuntu1) jammy; urgency=medium
* Merge with Debian unstable (LP: #1946834, #1961136). Remaining changes:
- d/p/enable-find-multipaths.patch: re-enable find_multipaths by
default -- see the removed 'add_find-multipaths.patch' (LP 1463046)
- d/p/kpartx-Improve-finding-loopback-device-by-file.patch: Improve
finding loopback devices (LP 1747044)
- d/multipath.conf: Install friendly names multipath.conf by default,
instead of generating it in every installer.
- debian/multipath-tools.dm-mpath-lvm.udev: Adjust initramfs integration
for new udev rules
- Remove d/initramfs/local-top (redundant with other initramfs scripts):
+ init-top: take over loading modules (dm-multipath and SCSI device
handlers); move the missing dm-emc there (now scsi-dh-emc; see
BTS 567014).
+ d/rules: do not install local-top anymore.
+ remove d/initramfs/local-top
- debian/initramfs/hooks: Add dm-queue-length: users may want to
change from the default selector and should be able to do so.
(LP 1673350)
- multipath initramfs fixes for booting from multipathed devices:
+ d/initramfs/hooks: also copy wwids file on the installed
system to ensure all paths come up on boot. (LP 1479929)
+ d/initramfs/hooks: install multipathd and required
directories.
+ d/initramfs/hooks: copy multipath udev rules to initramfs
+ d/initramfs/hooks: do not copy kpartx rules to initramfs
+ d/initramfs/local-bottom: remember to stop multipathd.
+ d/initramfs/local-premount: wait for udev to settle before
the call to resolve_device() in local_mount_root(), so the
by-uuid/ symlinks have a chance to be updated by the
multipath udev rules (LP 1503286).
+ d/initramfs/local-premount: Run multipath with -B so not to
assign names nor change /etc/multipath/bindings during
initramfs (LP 1561103)
+ d/rules: install d/initramfs/local-bottom
+ d/rules: install d/initramfs/local-premount
- debian/initramfs/local-bottom: wait for the multipathd unix
socket to close, so to avoid multipathd.socket unit failure.
(LP 1682178)
- Split kpartx initramfs bits into kpartx-boot for dmraid (LP 941874)
+ d/initramfs/kpartx.hook
+ d/kpartx-boot.postinst
+ d/kpartx-boot.postrm
+ d/control: Add kpartx-boot package for dmraid
+ d/rules: Install kpartx initramfs hook
- d/rules: Move udev rules to priority 95, because rules that load
modules should be >90.
- Don't build the multipath-tools binary package on i386; we only want
kpartx.
* Dropped changes:
- Use stable wwn-* names in autopkgtest that work with or without
friendly names, as scsi-${DM_NAME} is not a stable symlink name.
[ Included in 0.8.8-1 ]
- debian/tests/tgtbasedmpaths: Add sleep to allow for device creation
[ Included in 0.8.8-1 ]
- d/p/kpartx_more_loopback_fixes.patch: fix loopback mounted files
some more: since we stat() the loopback device node, we can't rely
on S_ISREG() tests to handle this case, and should look at the
device itself instead. (LP 1543430)
[ Applied upstream in 0.8.6 ]
- d/p/no-start-in-containers.patch: Do not attempt to start
multipath-tools in containers, should switch for on-demand udev/socket
based activation in the future. (LP 1823093)
[ Applied upstream in 0.8.7 ]
- d/t/control: use allow-stderr for kpartx-file-loopback, the new
gdisks version displays warnings on stderr now.
[ Fixed in 0.8.8-1 ]
* Added changes:
- d/t/kpartx-file-loopback: silence kpartx messages to stderr
- d/rules: remove -Bsymbolic-functions from LDFLAGS
-- Athos Ribeiro Mon, 21 Feb 2022
18:18:27 -0300
** Changed in: multipath-tools (Ubuntu)
Status: Triaged => 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/1961136
Title:
Syslog shows "multipathd[3142]: failed to increase buffer size" in
Ubuntu 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1961136/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961319] Re: ogre-next SMID fix for ppc64el, riscv64, s390x
This bug was fixed in the package ogre-next - 2.2.5+dfsg3-0ubuntu2 --- ogre-next (2.2.5+dfsg3-0ubuntu2) jammy; urgency=medium * Enable SIMD only in amd64 to fix ppc64el, riscv64, s390x (LP: #1961319) -- Jose Luis Rivero Thu, 17 Feb 2022 16:12:56 + ** Changed in: ogre-next (Ubuntu) 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/1961319 Title: ogre-next SMID fix for ppc64el, riscv64, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ogre-next/+bug/1961319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955325] Re: Firefox cannot open files in /usr/local/doc
There is a typo in the title: the directory in question is /usr/local/share/doc, not /usr/local/doc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955325 Title: Firefox cannot open files in /usr/local/doc To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1955325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961121] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1961121 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961121 Title: Not able to enter s2idle state on AMD platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961121] Re: Not able to enter s2idle state on AMD platforms
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) 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/1961121 Title: Not able to enter s2idle state on AMD platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960464] Re: mysql breaks apt, system, can't even be uninstalled
logrotate wiped out the record of when mysql was autoinstalled; over a year ago. Here are the updates from the last year: /var/log/apt/history.log.11.gz:Upgrade: mysql-server-5.7:amd64 (5.7.32-0ubuntu0.18.04.1, 5.7.33-0ubuntu0.18.04.1), mysql-server-core-5.7:amd64 (5.7.32-0ubuntu0.18.04.1, 5.7.33-0ubuntu0.18.04.1) /var/log/apt/history.log.1.gz:Upgrade: mysql-server-5.7:amd64 (5.7.36-0ubuntu0.18.04.1, 5.7.37-0ubuntu0.18.04.1), mysql-server-core-5.7:amd64 (5.7.36-0ubuntu0.18.04.1, 5.7.37-0ubuntu0.18.04.1) /var/log/apt/history.log.3.gz:Upgrade: mysql-server-5.7:amd64 (5.7.35-0ubuntu0.18.04.1, 5.7.36-0ubuntu0.18.04.1), mysql-server-core-5.7:amd64 (5.7.35-0ubuntu0.18.04.1, 5.7.36-0ubuntu0.18.04.1) /var/log/apt/history.log.6.gz:Upgrade: mysql-server-5.7:amd64 (5.7.34-0ubuntu0.18.04.1, 5.7.35-0ubuntu0.18.04.1), mysql-server-core-5.7:amd64 (5.7.34-0ubuntu0.18.04.1, 5.7.35-0ubuntu0.18.04.1) /var/log/apt/history.log.8.gz:Upgrade: mysql-server-5.7:amd64 (5.7.33-0ubuntu0.18.04.1, 5.7.34-0ubuntu0.18.04.1), mysql-server-core-5.7:amd64 (5.7.33-0ubuntu0.18.04.1, 5.7.34-0ubuntu0.18.04.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960464 Title: mysql breaks apt, system, can't even be uninstalled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1960464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961645] Re: QEMU packages have circular dependencies
** Patch added: "0001-remove-circular-dependencies.patch" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1961645/+attachment/5562608/+files/0001-remove-circular-dependencies.patch ** Description changed: This issue is related to https://git.launchpad.net/ubuntu/+source/qemu/commit/?id=9e281a416d6068af45a48ec0ec47a96e1e1ed220. - qemu-system-gui may depend on qemu-system-x86. However, qemu-block- - extra, qemu-system-common and qemu-system-data should not depend on - qemu-system-x86, they are already depended on by qemu-system-x86. + qemu-block-extra should not depend on qemu-system-x86, they are already + depended on by qemu-system-common. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961645 Title: QEMU packages have circular dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1961645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961646] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1961646 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Impish) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961646 Title: On AMD platforms s2idle may not work w/o proper FW To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961608] Re: [amdgpu] Screen freeze after wake from sleep
This might be related to bug 1958778... Please: 1. Reproduce the freeze again. 2. Wait 10 seconds. 3. Reboot. 4. Run: journalctl -b-1 > prevboot.txt lspci -k > lspci.txt 5. Attach the resulting text files here. ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961608 Title: [amdgpu] Screen freeze after wake from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961608] Re: Xorg freeze after wake from sleep
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Package changed: linux-hwe-5.11 (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Summary changed: - Xorg freeze after wake from sleep + [amdgpu] Screen freeze after wake from sleep -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961608 Title: [amdgpu] Screen freeze after wake from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958523] Re: [amdgpu] Static-noise-like effect
Please also attach a photo of the problem. I am wondering if bug 1961605 is similar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: [amdgpu] Static-noise-like effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961460] Re: [nouveau] My laptop shuts off randomly after displaying a black screen (nouveau crashes in nvkm_pmu_reset)
** Summary changed: - My laptop shuts off randomly after displaying a black screen (nouveau crashes in nvkm_pmu_reset) + [nouveau] My laptop shuts off randomly after displaying a black screen (nouveau crashes in nvkm_pmu_reset) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961460 Title: [nouveau] My laptop shuts off randomly after displaying a black screen (nouveau crashes in nvkm_pmu_reset) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961605] Re: Small window boxes are unstable and keep changing color
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Attachment added: "problemic_window.png" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961605/+attachment/5562606/+files/problemic_window.png ** Summary changed: - Small window boxes are unstable and keep changing color + amdgpu graphics corruption in kernel 5.13.0-30.33~20.04.1-generic ** Tags added: regression-update ** Summary changed: - amdgpu graphics corruption in kernel 5.13.0-30.33~20.04.1-generic + [amdgpu] graphics corruption in kernel 5.13.0-30.33~20.04.1-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961605 Title: [amdgpu] graphics corruption in kernel 5.13.0-30.33~20.04.1-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961596] Re: Ubuntu 20.04 with kernel version 5.11.0-34 stopped detecting external monitor
External monitors can't be detected because you have disabled the graphics driver. You need to remove the 'nomodeset' kernel parameter. ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Changed in: linux-hwe-5.11 (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/1961596 Title: Ubuntu 20.04 with kernel version 5.11.0-34 stopped detecting external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1961596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961646] [NEW] On AMD platforms s2idle may not work w/o proper FW
Public bug reported: It was raised because of a community member using a Lenovo platform having very odd s2idle failures. It was later debugged that it was caused by them choosing "Linux" mode in Lenovo BIOS setup rather than "Windows" mode and then choosing "s2idle" in /sys/power/mem_sleep. - In "Linux" mode there is both "deep" and "s2idle" offered in /sys/power/mem_sleep. - In "Windows" mode there is only "s2idle" offered in /sys/power/mem_sleep. That is by default no matter if the OEM offers S3 or S2idle /sys/power/mem_sleep will contain "s2idle", but on AMD platforms "s2idle" only works if the hardware has been configured properly by the firmware. The outward indications of this being configured properly are the FADT low power idle bit being set and the uPEP ACPI device being populated, which is what this patch now checks for. So now if a user has the firmware of the machine configured for S3 then they will only see "deep" on AMD systems. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: amd oem-priority originate-from-1956572 ** Tags added: amd oem-priority originate-from-1956572 ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) 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/1961646 Title: On AMD platforms s2idle may not work w/o proper FW To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961561] Re: [radeon] Blinking screen
Also the crash in comment #5 is different to the original problem here. Please follow all the steps in comment #3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961561 Title: [radeon] Blinking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961524] Re: Sudden crash with screen frozen after re-login
*** This bug is a duplicate of bug 1751508 ***
https://bugs.launchpad.net/bugs/1751508
Thanks, that is a duplicate of bug 1751508.
** This bug has been marked a duplicate of bug 1751508
Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("Couldn't add screen\n") from InitOutput()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961524
Title:
Sudden crash with screen frozen after re-login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1961524/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961561] Re: [radeon] Blinking screen
Please report crash files using the 'ubuntu-bug' or 'apport-cli' commands. We can't handle them here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961561 Title: [radeon] Blinking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958523] Re: [amdgpu] Static-noise-like effect
While the problem is happening please run: journalctl -b0 > journal.txt and attach the resulting text file here. ** This bug is no longer a duplicate of bug 1958591 [amdgpu] Random noise 'static' display after internal display turned off/on ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: [amdgpu] Static-noise-like effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
Mariusz, I have reopened bug 1958523 for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961546] Re: init freezes when >1 display connected on rocket lake PC
Changing status to 'Confirmed' as requested in comment #1. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961546 Title: init freezes when >1 display connected on rocket lake PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961645] [NEW] QEMU packages have circular dependencies
Public bug reported: This issue is related to https://git.launchpad.net/ubuntu/+source/qemu/commit/?id=9e281a416d6068af45a48ec0ec47a96e1e1ed220. qemu-system-gui may depend on qemu-system-x86. However, qemu-block- extra, qemu-system-common and qemu-system-data should not depend on qemu-system-x86, they are already depended on by qemu-system-x86. ** Affects: qemu (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/1961645 Title: QEMU packages have circular dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1961645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953052] Re: In Jammy sound level reset after reboot
Thanks Cam Cope, that's an interesting fix. It's probably better if we can avoid starting pipewire-media-session in GNOME sessions without other config changes. I don't want to cripple pipewire-media-session to the point of it not being able to replace PulseAudio in other session types. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1953052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961540] Re: tracker-miner-fs-3 massive CPU usage and system slowdown
** Bug watch added: gitlab.gnome.org/GNOME/tracker/-/issues #348 https://gitlab.gnome.org/GNOME/tracker/-/issues/348 ** Also affects: tracker via https://gitlab.gnome.org/GNOME/tracker/-/issues/348 Importance: Unknown Status: Unknown ** Changed in: tracker-miners (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961540 Title: tracker-miner-fs-3 massive CPU usage and system slowdown To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/1961540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1938845] Re: Legion 7 16ITHg6 - Touchpad undetected
*** This bug is a duplicate of bug 1937056 *** https://bugs.launchpad.net/bugs/1937056 What distribution and version are you running? Are you running a Legion 7i 16ITHg6 ? Later Ubuntu kernels have had a fix for this for some time. Same for the vanilla Linux source. Alas, there's still no fix for the sound on the 16ITHg6. You can only get the left channel out of both the left and right speakers, and you'll lose sound going to sleep. Hibernate is a work around, but Nvidia's drivers don't seem to support hibernate reliably so I leave the Nvidia GPU disabled for now (games aren't very good with only one audio channel after all). On 2/21/2022 4:37 PM, Darshan Shah wrote: > *** This bug is a duplicate of bug 1937056 *** > https://bugs.launchpad.net/bugs/1937056 > > Can you tell me how you fixed this issue... I am amateur person > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938845 Title: Legion 7 16ITHg6 - Touchpad undetected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958229] Re: UBSAN: array-index-out-of-bounds in dcn31_resources on AMD yellow carp platform
Has been committed to 5.15.0-19.19 or later. Currently respan in 5.15.0-22.22 in focal-proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958229 Title: UBSAN: array-index-out-of-bounds in dcn31_resources on AMD yellow carp platform To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959126] Re: Consider update to 3.68.2
** Merge proposal linked: https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/nss/+git/nss/+merge/415883 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959126 Title: Consider update to 3.68.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1959126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958229] Re: UBSAN: array-index-out-of-bounds in dcn31_resources on AMD yellow carp platform
** Changed in: linux (Ubuntu Jammy) Status: In Progress => 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/1958229 Title: UBSAN: array-index-out-of-bounds in dcn31_resources on AMD yellow carp platform To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251178] Re: qdbus and qdbusviewer crash with "No such file or directory"
And here we go again... - also with qdbusviewer, and also on 18.04 Previous workaround stopped working. After some digging it looks that qtchooser is looking into wrong Qt dir (qt4 instead of qt5) Some other people reported that apt install qt5-default may help - but I did not check this What worked was editing /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf and adding first line so it looks like this: /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf /usr/lib/qt5/bin /usr/lib/x86_64-linux-gnu/qt4/bin /usr/lib/x86_64-linux-gnu EOF -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251178 Title: qdbus and qdbusviewer crash with "No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1251178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821652] Re: unable to change display orientation xubuntu daily (live - 20190325)
** Summary changed: - unable to change display orientation on 19.04/19.10 xubuntu daily (live - 20190325) + unable to change display orientation xubuntu daily (live - 20190325) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821652 Title: unable to change display orientation xubuntu daily (live - 20190325) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1821652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938845] Re: Legion 7 16ITHg6 - Touchpad undetected
*** This bug is a duplicate of bug 1937056 *** https://bugs.launchpad.net/bugs/1937056 Can you tell me how you fixed this issue... I am amateur person -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938845 Title: Legion 7 16ITHg6 - Touchpad undetected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961196] Re: apparmor autotest failure on jammy with linux 5.15
Hmm so had to redo my merge after the 3.0.3-0ubuntu9 upload... see new bileto ticket/PPA for the current version of it https://bileto.ubuntu.com/#/ticket/4797 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961196 Title: apparmor autotest failure on jammy with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961641] Re: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
The version of shim-signed that you were upgrading to is the release version of shim-signed in 18.04. This version of shim-signed cannot be supported; it is 4 years old, and missing all security updates to shim that have been released in the past 4 years. It will quite simply become unbootable at a future date. The issue you're reporting is one that was fixed at some point in the history of bionic. You should have bionic-updates enabled when upgrading between releases. The simplest way to achieve this is to use do-release-upgrader or update-manager to manage the upgrade, which appears not to have been done here. ** Changed in: shim-signed (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/1961641 Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1961641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961641] Re: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
The error in the dpkg log is: Setting up shim-signed (1.34.9+13-0ubuntu2) ... Installing for x86_64-efi platform. EFI variables are not supported on this system. EFI variables are not supported on this system. grub-install: error: efibootmgr failed to register the boot entry: No such file or directory. [1mdpkg:[0m error processing package shim-signed (--configure): installed shim-signed package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961641 Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1961641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1118815] Re: Remove python-oauth from the archive
Removing packages: python-oauth 1.0.1-6ubuntu1 in jammy python-oauth 1.0.1-6ubuntu1 in jammy amd64 python-oauth 1.0.1-6ubuntu1 in jammy arm64 python-oauth 1.0.1-6ubuntu1 in jammy armhf python-oauth 1.0.1-6ubuntu1 in jammy i386 python-oauth 1.0.1-6ubuntu1 in jammy ppc64el python-oauth 1.0.1-6ubuntu1 in jammy riscv64 python-oauth 1.0.1-6ubuntu1 in jammy s390x python3-oauth 1.0.1-6ubuntu1 in jammy amd64 python3-oauth 1.0.1-6ubuntu1 in jammy arm64 python3-oauth 1.0.1-6ubuntu1 in jammy armhf python3-oauth 1.0.1-6ubuntu1 in jammy i386 python3-oauth 1.0.1-6ubuntu1 in jammy ppc64el python3-oauth 1.0.1-6ubuntu1 in jammy riscv64 python3-oauth 1.0.1-6ubuntu1 in jammy s390x Comment: (From Debian) RoQA; obsolete, replaced by python-oauthlib; Debian bug #1006229 Remove [y|N]? y ** Changed in: python-oauth (Ubuntu) Status: Confirmed => 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/1118815 Title: Remove python-oauth from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1118815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953052] Re: In Jammy sound level reset after reboot
So I can confirm that copying /usr/share/pipewire/media-session.conf to /etc/pipewire/media-session.d/media-session.conf and deleting these lines fixes the issue: $ diff /etc/pipewire/media-session.d/media-session.conf /usr/share/pipewire/media-session.d/media-session.conf 94a95,116 > with-audio = [ > metadata > default-nodes > default-profile > default-routes > alsa-seq > alsa-monitor > ] > with-alsa = [ > with-audio > ] > with-jack = [ > with-audio > ] > with-pulseaudio = [ > with-audio > bluez5 > bluez5-autoswitch > logind > restore-stream > streams-follow-default > ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1953052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955500] Re: firefox crashes often
I do still get pretty regular crashes. I will have to check with extensions disabled. Disabling adblocking is pretty painful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955500 Title: firefox crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1955500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953052] Re: In Jammy sound level reset after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pipewire (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1953052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1951698] Re: [upstream] under wayland items in menu bar sub-menus cannot be moved
The output of firefox --version is Mozilla Firefox 97.0 and the package is 97.0+build2-0ubuntu0.21.10.1 amd64 One more thing: I have a bunch of folders in my bookmark taskbar, which means when I pull something out, I need to go back and forth a bit to find a free place where I can drop the icon taken from another folder. When trying a few more times, I succeeded in one of 20 or so cases when I was very quick. So it seems to be either a timing issue or an issue that on a very low level when I'm hovering over another folder on my "way out" to the place where I want to drop the icon the strange effect of "losing the grip" (I hope it's understandable how I describe this) happens... This problem does not exist in X11. There, I can just drag my icon, take all the time I need, let it "travel" over the whole taskbar or even firefox window back and forth until I decide to let the mouse button go so it drops where I just put it to. I also have the general impression that my mouse is a bit faster than on X. But this is really hard to measure exactly and probably not relevant for the issue at hand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951698 Title: [upstream] under wayland items in menu bar sub-menus cannot be moved To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1951698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup
> packagekit will attempt to upgrade itself while running. This causes a packagekit crash That should not happen - do you have a backtrace for that? Reporting it at the PackageKit bugtracker would also be nice so I have it on my radar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914278 Title: Kernel updates marked as "manually installed", prevents old kernels cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1914278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960964] Re: Gather additional info when creating a bug about a snap
** Changed in: apport (Ubuntu) Status: Confirmed => In Progress ** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960964 Title: Gather additional info when creating a bug about a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1960964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960964] Re: Gather additional info when creating a bug about a snap
** Branch linked: lp:~ubuntu-core-dev/ubuntu/jammy/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960964 Title: Gather additional info when creating a bug about a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1960964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1951698] Re: [upstream] under wayland items in menu bar sub-menus cannot be moved
The Bug in the exact way as described originally is gone. I *can* move items *inside* the bookmark toolbar folder up and down. That being said, the handling of bookmark icons and folder still is not "normal" as in X11 sessions! In an X session, I can move Icons also in and out of folders, into subfolders in a taskbar folder, and back again. I can move an Icon from a taskbar bookmark folder directly to the taskbar. Under Wayland I can Move things *inside* a folder, but not back! This is valid from task bar into a main taskbar folder, but not back, and inside a taskbar folder into a subfolder - but not back. On the way back, there is a shortin blinking blue line showing where the icon is about to drop, but before i can let the mouse go to let it drop in that place, the icon goes back into it's original place in the folder. Not sure if I should open a new Bug for that, its probably technically the same area where the bug must hide, and very close to the originally described behaviour, only that up and down works now. On Mon, Feb 14, 2022 at 8:45 PM Olivier Tilloy <1951...@bugs.launchpad.net> wrote: > > You were using firefox 94.0+build3-0ubuntu0.21.10.1 at the time this bug > was reported, if you keep your system up-to-date with security updates, > you should now be at version 97.0+build2-0ubuntu0.21.10.1. > > Check the output of `firefox --version`. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1951698 > > Title: > [upstream] under wayland items in menu bar sub-menus cannot be moved > > To manage notifications about this bug go to: > https://bugs.launchpad.net/firefox/+bug/1951698/+subscriptions > -- Henning Sprang http://www.sprang.de -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951698 Title: [upstream] under wayland items in menu bar sub-menus cannot be moved To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1951698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961642] [NEW] No password samba share authentication error
Public bug reported: When trying to connect to a shared file from a windows pc via samba in nautilus, authentication is prompted. Windows pc has no password set. Nautilus does not understand this problem and keeps requesting authentication. Windows pc is windows 10. Only one account - Administrator with no password. Access to this windows pc is easy via another windows pc, credentials are prompted for and the login is "Administrator" with a blank password. With nautilus, when the password, nautilus will continually ask for login credentials, like they are invalid. Description:Ubuntu 21.10 Release:21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 17:14:50 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'initial-size' b'(2478, 1166)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2022-02-06 (14 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961642 Title: No password samba share authentication error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1961642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup
Hi Julian, Sounds good, but there's one caveat: If the Kubuntu users receive a packagekit upgrade via Discover, packagekit will attempt to upgrade itself while running. This causes a packagekit crash, from which the recovery is via the command line: sudo dpkg --configure -a sudo apt --fix-broken install sudo apt full-upgrade At this point, everything returns to normal, but for many users this can be problematic, especially in a stable release. While not a regression per se, the process would be problematic for Kubuntu users as they're the ones in Focal using this upgrade method. More advanced users can navigate this, but non-technical users would have a rough time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914278 Title: Kernel updates marked as "manually installed", prevents old kernels cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1914278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961641] [NEW] package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Public bug reported: Processing triggers for dbus (1.12.2-1ubuntu1.2) ... Processing triggers for sgml-base (1.29) ... Errors were encountered while processing: shim-signed Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (393.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): S *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...od: /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c: No such file or directory od: /sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: No such file or directory . *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 99% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/shim- signed/+filebug/688c605e-936b-11ec-a167-40a8f03099c8?field.title=package+shim- signed+1.34.9%2B13-0ubuntu2+failed+to+install%2Fupgrade%3A+installed+shim- signed+package+post- installation+script+subprocess+returned+error+exit+status+1 You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shim-signed 1.34.9+13-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi Date: Mon Feb 21 23:06:09 2022 EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: EFI variables are not supported on this system. EFITables: ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.12ubuntu0.2 SourcePackage: shim-signed Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2022-02-21 (0 days ago) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961641 Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1961641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960089] Re: Request 2.0 GiB Boot Partition for 22.04LTS FDE
** Description changed: Summary: We propose to increase the LVM /boot partition to 2.0 GiB. This provides the space needed so advanced users can use best practice to manage up to 3 kernel flavors. The current /boot partition on 20.04 and 22.04 is limited to just 705MiB, which allows only 3 concurrent kernels before filling and sometimes locking the system (each image set takes 180MiB total; 4 x 180 = 720MiB > 705MiB). Reasoning: Best practice recommends users keep at least two version of each kernel flavor in the /boot directory. If a user has 3 kernel flavors installed (e.g. oem, generic-hwe, and lowlatency-hwe), then one needs to reserve room for 2 x 3 = 6 kernels. The system needs the headroom of at least two additional kernels during any automated clean-up process due to package removal scheduling. I propose to also reserve room for 2 additional kernels as a safety measure. Thus the total recommend available space should accommodate 10 kernels. Each kernel file set takes up 180MiB in the /boot partition when used with Nvidia driver modules. These files include initrd.img, system.map, and vmlinuz. With future kernel and module growth, this may surpass 200MiB soon. Therefore, we suggest planning for 200M for each kernel. We therefore request a total LVM /boot partition size of 10 image x - 200MiB = 2.0 GiB. + 200MiB = 2.0GiB. Other Considerations: When unattended-upgrades works correctly (which does not yet employ best practice), we have seen users with just a single kernel flavor over-fill their /boot partitions. This is because unattended-upgrades can retain up to 4 kernels, while the /boot partition is only large enough for 3. I am currently working with others to improve the unattended-upgrades algorithm to use best practice. The installer could allow users to resize the /boot partition during - installation. In this case, we highly recommend a 2.0 GB default for the + installation. In this case, we highly recommend a 2.0GiB default for the reasons outlined above. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17 Uname: Linux 5.14.0-1011-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Feb 4 14:53:36 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed only-ubiquity quiet splash oem-config/enable=true --- InstallationDate: Installed on 2020-06-10 (604 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960089 Title: Request 2.0 GiB Boot Partition for 22.04LTS FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1960089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961476] Re: The laptop turns off only through the button and won't wake up from sleep (black screen)
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961476 Title: The laptop turns off only through the button and won't wake up from sleep (black screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1961476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961632] Re: linux-azure: Case VM fails to initialize CX4 VF due to mem fragmentation
** Also affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => 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/1961632 Title: linux-azure: Case VM fails to initialize CX4 VF due to mem fragmentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961630] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1961630 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961630 Title: Thunderbolt display not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup
Makes sense to me :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914278 Title: Kernel updates marked as "manually installed", prevents old kernels cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1914278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961630] Re: Thunderbolt display not working
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961630 Title: Thunderbolt display not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961626] Re: grub rescue after installing alongside
Bit hard to tell. But it has recently been fixed, so I could try and break my machine again with a new spin of the ISO tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961626 Title: grub rescue after installing alongside To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1961626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960089] Re: Request 2.0 GiB Boot Partition for 22.04LTS FDE
** Summary changed: - Request 2.0 GB Boot Partition for 22.04LTS FDE + Request 2.0 GiB Boot Partition for 22.04LTS FDE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960089 Title: Request 2.0 GiB Boot Partition for 22.04LTS FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1960089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960089] Re: Request 2.0 GB Boot Partition for 22.04LTS FDE
** Description changed: Summary: - We propose to increase the LVM /boot partition to 2.0 GB. This provides + We propose to increase the LVM /boot partition to 2.0 GiB. This provides the space needed so advanced users can use best practice to manage up to 3 kernel flavors. The current /boot partition on 20.04 and 22.04 is - limited to just 705M, which allows only 3 concurrent kernels before - filling and sometimes locking the system (each image set takes 180M - total; 4 x 180 = 720M > 705M). + limited to just 705MiB, which allows only 3 concurrent kernels before + filling and sometimes locking the system (each image set takes 180MiB + total; 4 x 180 = 720MiB > 705MiB). Reasoning: Best practice recommends users keep at least two version of each kernel flavor in the /boot directory. If a user has 3 kernel flavors installed (e.g. oem, generic-hwe, and lowlatency-hwe), then one needs to reserve room for 2 x 3 = 6 kernels. The system needs the headroom of at least two additional kernels during any automated clean-up process due to package removal scheduling. I propose to also reserve room for 2 additional kernels as a safety measure. Thus the total recommend available space should accommodate 10 kernels. - Each kernel file set takes up 180M in the /boot partition when used with - Nvidia driver modules. These files include initrd.img, system.map, and - vmlinuz. With future kernel and module growth, this may surpass 200M - soon. Therefore, we suggest planning for 200M for each kernel. + Each kernel file set takes up 180MiB in the /boot partition when used + with Nvidia driver modules. These files include initrd.img, system.map, + and vmlinuz. With future kernel and module growth, this may surpass + 200MiB soon. Therefore, we suggest planning for 200M for each kernel. - We therefore request a total LVM /boot partition size of 10 image x 200M - = 2.0 GB. + We therefore request a total LVM /boot partition size of 10 image x + 200MiB = 2.0 GiB. Other Considerations: When unattended-upgrades works correctly (which does not yet employ best practice), we have seen users with just a single kernel flavor over-fill their /boot partitions. This is because unattended-upgrades can retain up to 4 kernels, while the /boot partition is only large enough for 3. I am currently working with others to improve the unattended-upgrades algorithm to use best practice. The installer could allow users to resize the /boot partition during installation. In this case, we highly recommend a 2.0 GB default for the reasons outlined above. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17 Uname: Linux 5.14.0-1011-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Feb 4 14:53:36 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed only-ubiquity quiet splash oem-config/enable=true --- InstallationDate: Installed on 2020-06-10 (604 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960089 Title: Request 2.0 GiB Boot Partition for 22.04LTS FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1960089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961626] Re: grub rescue after installing alongside
I wonder if this might be related to LP: #1955109? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961626 Title: grub rescue after installing alongside To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1961626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961196] Re: apparmor autotest failure on jammy with linux 5.15
sorry, I was confused a bit about the issue. I have no objection to uploading the diff from #7. Still while the patch makes the immediate mctp issue go away from the current tests it isn't a full fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961196 Title: apparmor autotest failure on jammy with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876620] Re: Enable riscv64 build
This bug was fixed in the package grub2 - 2.06-2ubuntu5 --- grub2 (2.06-2ubuntu5) jammy; urgency=medium [ Julian Andres Klode ] * Free correct size when freeing params, rather than 16 Ki (LP: #1958623) * Build with FUSE3 (LP: #1935659) * Only run os-prober on first run and if it previously found other OS (LP: #1955109) [ Heinrich Schuchardt ] * Rename grub-core/loader/efi/linux.c * Add patches for GRUB on RISC-V * fat: fix listing the root directory * Enable building for RISC-V (LP: #1876620) [ Julian Andres Klode ] * Re-enable peimage code on other archs outside secure boot; this fixes LP: #1947046 when not booting in secure boot mode (secure boot pending security review of the code) -- Julian Andres Klode Fri, 18 Feb 2022 17:21:16 +0100 ** Changed in: grub2 (Ubuntu) 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/1876620 Title: Enable riscv64 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935659] Re: grub2 FTBFS when built with libfuse3-dev
This bug was fixed in the package grub2 - 2.06-2ubuntu5 --- grub2 (2.06-2ubuntu5) jammy; urgency=medium [ Julian Andres Klode ] * Free correct size when freeing params, rather than 16 Ki (LP: #1958623) * Build with FUSE3 (LP: #1935659) * Only run os-prober on first run and if it previously found other OS (LP: #1955109) [ Heinrich Schuchardt ] * Rename grub-core/loader/efi/linux.c * Add patches for GRUB on RISC-V * fat: fix listing the root directory * Enable building for RISC-V (LP: #1876620) [ Julian Andres Klode ] * Re-enable peimage code on other archs outside secure boot; this fixes LP: #1947046 when not booting in secure boot mode (secure boot pending security review of the code) -- Julian Andres Klode Fri, 18 Feb 2022 17:21:16 +0100 ** Changed in: grub2 (Ubuntu Jammy) Status: In Progress => 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/1935659 Title: grub2 FTBFS when built with libfuse3-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1935659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947046] Re: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
This bug was fixed in the package grub2 - 2.06-2ubuntu5 --- grub2 (2.06-2ubuntu5) jammy; urgency=medium [ Julian Andres Klode ] * Free correct size when freeing params, rather than 16 Ki (LP: #1958623) * Build with FUSE3 (LP: #1935659) * Only run os-prober on first run and if it previously found other OS (LP: #1955109) [ Heinrich Schuchardt ] * Rename grub-core/loader/efi/linux.c * Add patches for GRUB on RISC-V * fat: fix listing the root directory * Enable building for RISC-V (LP: #1876620) [ Julian Andres Klode ] * Re-enable peimage code on other archs outside secure boot; this fixes LP: #1947046 when not booting in secure boot mode (secure boot pending security review of the code) -- Julian Andres Klode Fri, 18 Feb 2022 17:21:16 +0100 ** Changed in: grub2 (Ubuntu Jammy) 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/1947046 Title: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955109] Re: boot menu not appearing after manual install of jellyfish daily build alongside other OS
This bug was fixed in the package grub2 - 2.06-2ubuntu5 --- grub2 (2.06-2ubuntu5) jammy; urgency=medium [ Julian Andres Klode ] * Free correct size when freeing params, rather than 16 Ki (LP: #1958623) * Build with FUSE3 (LP: #1935659) * Only run os-prober on first run and if it previously found other OS (LP: #1955109) [ Heinrich Schuchardt ] * Rename grub-core/loader/efi/linux.c * Add patches for GRUB on RISC-V * fat: fix listing the root directory * Enable building for RISC-V (LP: #1876620) [ Julian Andres Klode ] * Re-enable peimage code on other archs outside secure boot; this fixes LP: #1947046 when not booting in secure boot mode (secure boot pending security review of the code) -- Julian Andres Klode Fri, 18 Feb 2022 17:21:16 +0100 ** Changed in: grub2 (Ubuntu Jammy) Status: Confirmed => 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/1955109 Title: boot menu not appearing after manual install of jellyfish daily build alongside other OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961542] Re: libsmartcols: Revert back to previous behaviour of non-shell parsable column output (lsblk -P)
This bug was fixed in the package util-linux - 2.37.2-4ubuntu3 --- util-linux (2.37.2-4ubuntu3) jammy; urgency=medium * Revert the change to libsmartcols that outputs shell parsable column names when -P / --pairs is used in lsblk. The change breaks older MAAS and curtin versions, such that they cannot deploy Jammy. (LP: #1961542) - d/p/ubuntu/lp-1961542-Revert-libsmartcols-sanitize-variable-names-on-ex.patch -- Matthew Ruffell Mon, 21 Feb 2022 14:49:57 +1300 ** Changed in: util-linux (Ubuntu Jammy) Status: In Progress => 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/1961542 Title: libsmartcols: Revert back to previous behaviour of non-shell parsable column output (lsblk -P) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1961542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958623] Re: encounter RSOD while pxe booting from MaaS server
This bug was fixed in the package grub2 - 2.06-2ubuntu5 --- grub2 (2.06-2ubuntu5) jammy; urgency=medium [ Julian Andres Klode ] * Free correct size when freeing params, rather than 16 Ki (LP: #1958623) * Build with FUSE3 (LP: #1935659) * Only run os-prober on first run and if it previously found other OS (LP: #1955109) [ Heinrich Schuchardt ] * Rename grub-core/loader/efi/linux.c * Add patches for GRUB on RISC-V * fat: fix listing the root directory * Enable building for RISC-V (LP: #1876620) [ Julian Andres Klode ] * Re-enable peimage code on other archs outside secure boot; this fixes LP: #1947046 when not booting in secure boot mode (secure boot pending security review of the code) -- Julian Andres Klode Fri, 18 Feb 2022 17:21:16 +0100 ** Changed in: grub2 (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/1958623 Title: encounter RSOD while pxe booting from MaaS server To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1958623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961635] [NEW] [FFe] sync dfu-util 0.11-1 from Debian (now in DELAYED)
Public bug reported: Due to maintainer MIA the current package 0.9 in Debian testing (and Ubuntu) is nearly 7 years old. I have salvaged the package in Debian, but this has been a long process, and the new 0.11-1 package is now sitting in the delayed queue until February 26. Since this will barely miss the Feature Freeze I ask up front about an exception for this. https://ftp-master.debian.org/deferred.html (overview deferred) https://ftp-master.debian.org/deferred/ (package sources) ** Affects: dfu-util (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961635 Title: [FFe] sync dfu-util 0.11-1 from Debian (now in DELAYED) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dfu-util/+bug/1961635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
