[Bug 1925126] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install
ubiquity (21.04.18) hirsute; urgency=medium * Only auto-configure ESP larger than 50 MiB - this works around LP 1924823, where the 5 MB ESP on the install medium was configured as /boot/efi. ** Changed in: ubiquity (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/1924823 Title: ESP on install medium automatically configured as ESP for install, failing install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490020/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490019/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490018/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490017/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490016/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490015/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490014/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490013/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490012/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490011/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490010/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490009/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490008/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490006/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490007/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490005/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925126] [NEW] Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50
Public bug reported: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome- terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected focal ** Tags added: apport-collected focal ** Description changed: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome- terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915
[Bug 1925124] Re: panic in ipt_do_table+0x621/0x640
** Description changed: 1.This bug has happened on the following kernel version: - 4.4.0-104-generic - 4.15.0-88-generic - 4.15.0-13-generic - 5.4.0-42-generic - 5.4.0-47-generic + 4.4.0-104-generic + 4.15.0-88-generic + 4.15.0-13-generic + 5.4.0-42-generic + 5.4.0-47-generic 2.we cannot reliably reproduce this issue. 3.this patch seems to fix this issue. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/netfilter/x_tables.c?id=175e476b8cdf2a4de7432583b49c871345e4f8a1 4.the following crash dmesg from 5.4.0-47-generic: [2021-03-19 12:17:53][3581678.514072] audit: audit_lost=1 audit_rate_limit=1 audit_backlog_limit=1024 [2021-03-23 21:57:06][3962019.737898] general protection fault: [#1] SMP PTI [2021-03-23 21:57:06][3962019.739019] CPU: 4 PID: 0 Comm: swapper/4 Kdump: loaded Not tainted 5.4.0-47-generic #51~18.04.1-Ubuntu [2021-03-23 21:57:06][3962019.740433] Hardware name: Tencent Cloud CVM, BIOS seabios-1.9.1-qemu-project.org 04/01/2014 [2021-03-23 21:57:06][3962019.741829] RIP: 0010:ipt_do_table+0x621/0x640 [ip_tables] [2021-03-23 21:57:06][3962019.742587] Code: ff ff ff 45 31 d2 48 89 85 50 ff ff ff e9 7e fe ff ff 83 ad 70 ff ff ff 01 48 8b bd 78 ff ff ff 8b 85 70 ff ff ff 4c 8b 34 c7 <41> 0f b7 46 5a 49 01 c6 e9 [2021-03-23 21:57:06]18 fb ff ff c7 45 a4 00 00 00 00 e9 e9 [2021-03-23 21:57:06][3962019.745295] RSP: 0018:bcd080184c18 EFLAGS: 00010246 [2021-03-23 21:57:06][3962019.745988] RAX: RBX: 96b7e9b717b0 RCX: dcd07f70a150 [2021-03-23 21:57:06][3962019.747025] RDX: 0001ab6a RSI: 96b7e1d98d80 RDI: 96b7e1d98d80 [2021-03-23 21:57:06][3962019.748015] RBP: bcd080184d08 R08: 0008 R09: 96b82aca2980 [2021-03-23 21:57:06][3962019.748988] R10: 0d38 R11: 96b7cacaa380 R12: 96b833fea000 [2021-03-23 21:57:06][3962019.749927] R13: 96b7ebb4a04e R14: 3f13d7139e6d8ccb R15: 96b7d2c28f00 [2021-03-23 21:57:06][3962019.750873] FS: () GS:96b83fb0() knlGS: [2021-03-23 21:57:06][3962019.751919] CS: 0010 DS: ES: CR0: 80050033 [2021-03-23 21:57:06][3962019.752720] CR2: 7fee206258f0 CR3: 000f9c428001 CR4: 003606e0 [2021-03-23 21:57:06][3962019.753603] DR0: DR1: DR2: [2021-03-23 21:57:06][3962019.754619] DR3: DR6: fffe0ff0 DR7: 0400 [2021-03-23 21:57:06][3962019.755606] Call Trace: [2021-03-23 21:57:06][3962019.755984] [2021-03-23 21:57:06][3962019.756282] iptable_filter_hook+0x1f/0x30 [iptable_filter] [2021-03-23 21:57:06][3962019.757199] nf_hook_slow+0x48/0xc0 [2021-03-23 21:57:06][3962019.757753] ip_forward+0x410/0x480 [2021-03-23 21:57:06][3962019.758350] ? ip4_key_hashfn+0xc0/0xc0 [2021-03-23 21:57:06][3962019.758907] ip_rcv_finish+0x84/0xa0 [2021-03-23 21:57:06][3962019.759469] ip_rcv+0xbc/0xd0 [2021-03-23 21:57:06][3962019.760543] ? ip_rcv_finish_core.isra.18+0x3b0/0x3b0 [2021-03-23 21:57:06][3962019.761916] __netif_receive_skb_one_core+0x86/0xa0 [2021-03-23 21:57:06][3962019.763210] __netif_receive_skb+0x18/0x60 [2021-03-23 21:57:06][3962019.764341] process_backlog+0xa0/0x170 [2021-03-23 21:57:06][3962019.765600] net_rx_action+0x140/0x3c0 [2021-03-23 21:57:06][3962019.766550] __do_softirq+0xe4/0x2da [2021-03-23 21:57:06][3962019.767792] irq_exit+0xae/0xb0 [2021-03-23 21:57:06][3962019.768857] smp_call_function_single_interrupt+0x48/0xd0 [2021-03-23 21:57:06][3962019.770140] call_function_single_interrupt+0xf/0x20 [2021-03-23 21:57:06][3962019.771315] [2021-03-23 21:57:06][3962019.772038] RIP: 0010:native_safe_halt+0x12/0x20 - [2021-03-23 21:57:06][3962019.773239] Code: 00 0f 00 2d 32 98 53 00 f4 5d c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d 12 98 53 00 fb f4 <5d> c3 90 90 90 90 90 90 90 [2021-03-23 21:57:06]90 90 90 90 90 0f 1f 44 00 00 55 48 89 - [2021-03-23 21:57:06][3962019.776646] RSP: 0018:bcd080093e70 EFLAGS: 0246 ORIG_RAX: ff04 - [2021-03-23 21:57:06][3962019.778015] RAX: 93ad22f0 RBX: 0004 RCX: 0001 - [2021-03-23 21:57:06][3962019.779356] RDX: 96b83fb2ba80 RSI: bcd080093e40 RDI: - [2021-03-23 21:57:06][3962019.780633] RBP: bcd080093e70 R08: 0010e421e97a71a1 R09: 0001 - [2021-03-23 21:57:06][3962019.782033] R10: 007e8c00 R11: 0fca3b36 R12: 0004 - [2021-03-23 21:57:06][3962019.783373] R13: R14: R15: - [2021-03-23 21:57:06][3962019.784725] ? ldsem_down_write+0x230/0x230 - [2021-03-23 21:57:06][3962019.785741] default_idle+0x22/0x150 - [2021-03-23 21:57:06][3962019.786673] arch_cpu_idle+0x15/0x20 - [2021-03-23 21:57:06][3962019.787667]
[Bug 1838038] Re: [snap] Snapped apps do not work with .local mdns/avahi name resolution
Just repeating what I said on the forum, I believe this could be implemented through updates to the base snaps with no changes to snapd or any application snaps. The mdns4_minimal NSS plugin is an 18K binary (which compresses to about 6KB) that delegates its lookups to avahi-daemon using a single purpose lookups-only unix socket protocol (i.e. no D-Bus access). The AppArmor policy fragment grants access to this socket, so any snap plugging "network" already has permission to communicate. If the plugin cannot connect to Avahi, it should error out very quickly. Updating the base snaps to include the NSS plugin and reference it in their nsswitch.conf file would likely be all that is needed. It should work equally well for applications on classic distros and those on Ubuntu Core with the avahi snap installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838038 Title: [snap] Snapped apps do not work with .local mdns/avahi name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/snap-core18/+bug/1838038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925125] Re: cosmetic issue on calamares summary screen /home%4
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925125 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925125 Title: cosmetic issue on calamares summary screen /home%4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1925125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925124] 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 1925124 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 ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925124 Title: panic in ipt_do_table+0x621/0x640 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925125] [NEW] cosmetic issue on calamares summary screen /home%4
Public bug reported: Lubuntu hirsute QA-test install on - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) manual partitioning with various options; re-use of /home I think is key to issue Note photo see https://photos.app.goo.gl/9yn2z42TJAjNFxWx5 ** expected result "Set up ext4 partition /dev/sda8 with mount point /home" ** actual result "Set up ext4 partition /dev/sda8 with mount point /home%4" ** issue the %4 shouldn't be there. It's minor, and easily ignored by users, but users may still back out & check they didn't do something wrong (/home was selected from a drop down and wasn't entered) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: calamares 3.2.37-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 .etc.calamares.modules.finished.conf: --- restartNowMode: user-checked restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.shellprocess_logs.conf: --- dontChroot: true timeout: 30 script: - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: --- unpack: - source: "/cdrom/casper/filesystem.squashfs" sourcefs: "squashfs" destination: "" ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: LXQt Date: Tue Apr 20 14:37:16 2021 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) RelatedPackageVersions: calamares-settings-ubuntu-common 1:21.04.2 calamares-settings-lubuntu 1:21.04.2 xfsprogs 5.10.0-2ubuntu3 btrfs-progs 5.10.1-1build1 SourcePackage: calamares UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: calamares (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Description changed: - to be filled in shortly (when photo uploaded hopefully) + Lubuntu hirsute QA-test install on + - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) + + manual partitioning with various options; re-use of /home I think is key + to issue + + Note photo + + see https://photos.app.goo.gl/9yn2z42TJAjNFxWx5 + + ** expected result + + "Set up ext4 partition /dev/sda8 with mount point /home" + + ** actual result + + "Set up ext4 partition /dev/sda8 with mount point /home%4" + + ** issue + + the %4 shouldn't be there. It's minor, and easily ignored by users, but + users may still back out & check they didn't do something wrong (/home + was selected from a drop down and wasn't entered) + ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: calamares 3.2.37-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 .etc.calamares.modules.finished.conf: - --- - restartNowMode: user-checked - restartNowCommand: "systemctl -i reboot" + --- + restartNowMode: user-checked + restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.shellprocess_logs.conf: - --- - dontChroot: true - timeout: 30 - script: - - calamares-logs-helper @@ROOT@@ + --- + dontChroot: true + timeout: 30 + script: + - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: - --- - unpack: - - source: "/cdrom/casper/filesystem.squashfs" - sourcefs: "squashfs" - destination: "" + --- + unpack: + - source: "/cdrom/casper/filesystem.squashfs" + sourcefs: "squashfs" + destination: "" ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: LXQt Date: Tue Apr 20 14:37:16 2021 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) RelatedPackageVersions: - calamares-settings-ubuntu-common 1:21.04.2 - calamares-settings-lubuntu 1:21.04.2 - xfsprogs 5.10.0-2ubuntu3 - btrfs-progs 5.10.1-1build1 + calamares-settings-ubuntu-common 1:21.04.2 + calamares-settings-lubuntu 1:21.04.2 + xfsprogs 5.10.0-2ubuntu3 + btrfs-progs 5.10.1-1build1 SourcePackage: calamares 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/1925125 Title: cosmetic issue on calamares summary screen /home%4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1925125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925124] [NEW] panic in ipt_do_table+0x621/0x640
Public bug reported: 1.This bug has happened on the following kernel version: 4.4.0-104-generic 4.15.0-88-generic 4.15.0-13-generic 5.4.0-42-generic 5.4.0-47-generic 2.we cannot reliably reproduce this issue. 3.this patch seems to fix this issue. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/netfilter/x_tables.c?id=175e476b8cdf2a4de7432583b49c871345e4f8a1 4.the following crash dmesg from 5.4.0-47-generic: [2021-03-19 12:17:53][3581678.514072] audit: audit_lost=1 audit_rate_limit=1 audit_backlog_limit=1024 [2021-03-23 21:57:06][3962019.737898] general protection fault: [#1] SMP PTI [2021-03-23 21:57:06][3962019.739019] CPU: 4 PID: 0 Comm: swapper/4 Kdump: loaded Not tainted 5.4.0-47-generic #51~18.04.1-Ubuntu [2021-03-23 21:57:06][3962019.740433] Hardware name: Tencent Cloud CVM, BIOS seabios-1.9.1-qemu-project.org 04/01/2014 [2021-03-23 21:57:06][3962019.741829] RIP: 0010:ipt_do_table+0x621/0x640 [ip_tables] [2021-03-23 21:57:06][3962019.742587] Code: ff ff ff 45 31 d2 48 89 85 50 ff ff ff e9 7e fe ff ff 83 ad 70 ff ff ff 01 48 8b bd 78 ff ff ff 8b 85 70 ff ff ff 4c 8b 34 c7 <41> 0f b7 46 5a 49 01 c6 e9 [2021-03-23 21:57:06]18 fb ff ff c7 45 a4 00 00 00 00 e9 e9 [2021-03-23 21:57:06][3962019.745295] RSP: 0018:bcd080184c18 EFLAGS: 00010246 [2021-03-23 21:57:06][3962019.745988] RAX: RBX: 96b7e9b717b0 RCX: dcd07f70a150 [2021-03-23 21:57:06][3962019.747025] RDX: 0001ab6a RSI: 96b7e1d98d80 RDI: 96b7e1d98d80 [2021-03-23 21:57:06][3962019.748015] RBP: bcd080184d08 R08: 0008 R09: 96b82aca2980 [2021-03-23 21:57:06][3962019.748988] R10: 0d38 R11: 96b7cacaa380 R12: 96b833fea000 [2021-03-23 21:57:06][3962019.749927] R13: 96b7ebb4a04e R14: 3f13d7139e6d8ccb R15: 96b7d2c28f00 [2021-03-23 21:57:06][3962019.750873] FS: () GS:96b83fb0() knlGS: [2021-03-23 21:57:06][3962019.751919] CS: 0010 DS: ES: CR0: 80050033 [2021-03-23 21:57:06][3962019.752720] CR2: 7fee206258f0 CR3: 000f9c428001 CR4: 003606e0 [2021-03-23 21:57:06][3962019.753603] DR0: DR1: DR2: [2021-03-23 21:57:06][3962019.754619] DR3: DR6: fffe0ff0 DR7: 0400 [2021-03-23 21:57:06][3962019.755606] Call Trace: [2021-03-23 21:57:06][3962019.755984] [2021-03-23 21:57:06][3962019.756282] iptable_filter_hook+0x1f/0x30 [iptable_filter] [2021-03-23 21:57:06][3962019.757199] nf_hook_slow+0x48/0xc0 [2021-03-23 21:57:06][3962019.757753] ip_forward+0x410/0x480 [2021-03-23 21:57:06][3962019.758350] ? ip4_key_hashfn+0xc0/0xc0 [2021-03-23 21:57:06][3962019.758907] ip_rcv_finish+0x84/0xa0 [2021-03-23 21:57:06][3962019.759469] ip_rcv+0xbc/0xd0 [2021-03-23 21:57:06][3962019.760543] ? ip_rcv_finish_core.isra.18+0x3b0/0x3b0 [2021-03-23 21:57:06][3962019.761916] __netif_receive_skb_one_core+0x86/0xa0 [2021-03-23 21:57:06][3962019.763210] __netif_receive_skb+0x18/0x60 [2021-03-23 21:57:06][3962019.764341] process_backlog+0xa0/0x170 [2021-03-23 21:57:06][3962019.765600] net_rx_action+0x140/0x3c0 [2021-03-23 21:57:06][3962019.766550] __do_softirq+0xe4/0x2da [2021-03-23 21:57:06][3962019.767792] irq_exit+0xae/0xb0 [2021-03-23 21:57:06][3962019.768857] smp_call_function_single_interrupt+0x48/0xd0 [2021-03-23 21:57:06][3962019.770140] call_function_single_interrupt+0xf/0x20 [2021-03-23 21:57:06][3962019.771315] [2021-03-23 21:57:06][3962019.772038] RIP: 0010:native_safe_halt+0x12/0x20 [2021-03-23 21:57:06][3962019.773239] Code: 00 0f 00 2d 32 98 53 00 f4 5d c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d 12 98 53 00 fb f4 <5d> c3 90 90 90 90 90 90 90 [2021-03-23 21:57:06]90 90 90 90 90 0f 1f 44 00 00 55 48 89 [2021-03-23 21:57:06][3962019.776646] RSP: 0018:bcd080093e70 EFLAGS: 0246 ORIG_RAX: ff04 [2021-03-23 21:57:06][3962019.778015] RAX: 93ad22f0 RBX: 0004 RCX: 0001 [2021-03-23 21:57:06][3962019.779356] RDX: 96b83fb2ba80 RSI: bcd080093e40 RDI: [2021-03-23 21:57:06][3962019.780633] RBP: bcd080093e70 R08: 0010e421e97a71a1 R09: 0001 [2021-03-23 21:57:06][3962019.782033] R10: 007e8c00 R11: 0fca3b36 R12: 0004 [2021-03-23 21:57:06][3962019.783373] R13: R14: R15: [2021-03-23 21:57:06][3962019.784725] ? ldsem_down_write+0x230/0x230 [2021-03-23 21:57:06][3962019.785741] default_idle+0x22/0x150 [2021-03-23 21:57:06][3962019.786673] arch_cpu_idle+0x15/0x20 [2021-03-23 21:57:06][3962019.787667] default_idle_call+0x23/0x30 [2021-03-23 21:57:06][3962019.788803] do_idle+0x1bd/0x270 [2021-03-23 21:57:06][3962019.789875] cpu_startup_entry+0x1d/0x20 [2021-03-23 21:57:06][3962019.790990] start_secondary+0x166/0x1c0 [2021-03-23
[Bug 1915670] Re: iotop 0.6-24-g733f3f8-1 fails with 'UnboundLocalError' on newly installed 20.04 release
[Expired for iotop (Ubuntu) because there has been no activity for 60 days.] ** Changed in: iotop (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/1915670 Title: iotop 0.6-24-g733f3f8-1 fails with 'UnboundLocalError' on newly installed 20.04 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/1915670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
[Expired for lm-sensors (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lm-sensors (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/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
[Expired for linux-signed-hwe-5.8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed-hwe-5.8 (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/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915903] Re: Up-to-date net-tools package tells me to recompile it
[Expired for net-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: net-tools (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/1915903 Title: Up-to-date net-tools package tells me to recompile it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1915903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489982/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489981/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489980/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489979/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489978/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489977/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489976/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489975/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489973/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489974/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489971/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489972/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489970/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489969/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489968/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924997] Re: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80%
apport information ** Tags added: apport-collected focal ** Description changed: A cracking noises is noticed when doing audio playback from the built-in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: u 1444 F pulseaudio + CasperMD5CheckResult: skip + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X90 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-04-13 (6 days ago) + InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD + Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint + Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. Vostro 3500 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.10.0-1020-oem N/A + linux-backports-modules-5.10.0-1020-oem N/A + linux-firmware 1.187.10 + Tags: focal + Uname: Linux 5.10.0-1020-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 02/02/2021 + dmi.bios.release: 1.2 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.2.2 + dmi.board.name: 09YKK0 + dmi.board.vendor: Dell Inc. + dmi.board.version: X00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: + dmi.product.family: Vostro + dmi.product.name: Vostro 3500 + dmi.product.sku: 0A24 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489967/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919468] Re: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD-method requests
Hello Utkarsh, Yes, that sounds like a good plan, thanks. I forgot to mention, but aside from the changelog, they also maintain this wonderful list of fixed bugs: https://www.haproxy.org/bugs/bugs-2.0.13.html Let me know if I can help with this SRU ;) Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919468 Title: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD- method requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1919468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925118] [NEW] package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida d
Public bug reported: update-alternatives: utilizando /var/lib/mecab/dic/ipadic-utf8 para proveer /var/lib/mecab/dic/debian (mecab-dictionary) en modo automático dpkg: problemas de dependencias impiden la configuración de mysql-server: mysql-server depende de mysql-server-8.0; sin embargo: El paquete `mysql-server-8.0' no está configurado todavía. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 19 23:00:58 2021 ErrorMessage: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida de error 127 InstallationDate: Installed on 2020-03-31 (385 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Logs.var.log.daemon.log: MySQLVarLibDirListing: [] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=04f891e0-c575-48d0-894c-bef31061e9b4 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida de error 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925118 Title: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida de error 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1925118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923453] Re: [focal-wallaby] Services not running that should be: neutron-openvswitch-agent
Reviewed: https://review.opendev.org/c/openstack/neutron/+/786272 Committed: https://opendev.org/openstack/neutron/commit/1dfbf5b3455391c849dc5ab7b61df86f6e0c8c16 Submitter: "Zuul (22348)" Branch:master commit 1dfbf5b3455391c849dc5ab7b61df86f6e0c8c16 Author: Corey Bryant Date: Wed Apr 14 11:45:47 2021 -0400 Initialize privsep library for neutron-ovs-cleanup Closes-Bug: #1923453 Change-Id: Ie91ab1c359955a2911e558ab5a4bc8b0ff28bada ** Changed in: neutron 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/1923453 Title: [focal-wallaby] Services not running that should be: neutron- openvswitch-agent To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-gateway/+bug/1923453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install
@juliank I saw your update last night, and hoped I'd see a new RC/daily to test your applied workaround, so if there something I can help test.. let me know.. (I've had this issue on 2x dell optiplex 755, a 780 & hp dc7700 but I suspect it occurs regardless of bios box.. the dc7700 & one d755 I use only in QA-testing; the others I actually use so are only rarely used for install testing (& always replace a partition type installs)... I've returned to lubuntu QA-testing) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924823 Title: ESP on install medium automatically configured as ESP for install, failing install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919468] Re: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD-method requests
Hi Simon, Thanks for working on this! And wow, the debdiff looks huge but well, I don't expect it to be any smaller either, considering that it's a 2.0.13 -> 2.0.22. But well, I'd still copy the SRU team to take their opinion on this and to actually confirm whether they'd be OK with this being SRU'd to Focal or not. Anyway, the upstream changelog looks good and honestly, I like the fact how they neatly put each commit categorized into subsets, making it very clear what that commit is about. I could swing this by one of the members of the SRU team tonight and maybe once they are onboard with this, we could then workout the other things (backporting, testing, checking, uploading, et al.), hope that sounds OK to you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919468 Title: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD- method requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1919468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924611] Re: setting extended attribute may cause memory leak
This bug was fixed in the package linux - 4.4.0-210.242 --- linux (4.4.0-210.242) xenial; urgency=medium * xenial/linux: 4.4.0-210.242 -proposed tracker (LP: #1924644) * setting extended attribute may cause memory leak (LP: #1924611) - SAUCE: vfs_setxattr: free converted value if xattr_permission returns error -- Stefan Bader Fri, 16 Apr 2021 11:33:09 +0200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924611 Title: setting extended attribute may cause memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924611] Re: setting extended attribute may cause memory leak
This bug was fixed in the package linux-raspi2-5.3 - 5.3.0-1040.42 --- linux-raspi2-5.3 (5.3.0-1040.42) bionic; urgency=medium * bionic/linux-raspi2-5.3: 5.3.0-1040.42 -proposed tracker (LP: #1924651) [ Ubuntu: 5.3.0-74.70 ] * bionic/linux-hwe: 5.3.0-74.70 -proposed tracker (LP: #1924647) * setting extended attribute may cause memory leak (LP: #1924611) - SAUCE: vfs_setxattr: free converted value if xattr_permission returns error -- Stefan Bader Fri, 16 Apr 2021 11:13:35 +0200 ** Changed in: linux (Ubuntu Xenial) 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/1924611 Title: setting extended attribute may cause memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924611] Re: setting extended attribute may cause memory leak
This bug was fixed in the package linux-hwe - 5.3.0-74.70 --- linux-hwe (5.3.0-74.70) bionic; urgency=medium * bionic/linux-hwe: 5.3.0-74.70 -proposed tracker (LP: #1924647) * setting extended attribute may cause memory leak (LP: #1924611) - SAUCE: vfs_setxattr: free converted value if xattr_permission returns error -- Stefan Bader Fri, 16 Apr 2021 10:22:31 +0200 ** Changed in: linux-raspi2-5.3 (Ubuntu Bionic) 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/1924611 Title: setting extended attribute may cause memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924611] Re: setting extended attribute may cause memory leak
This bug was fixed in the package linux-gke-5.3 - 5.3.0-1043.46 --- linux-gke-5.3 (5.3.0-1043.46) bionic; urgency=medium * bionic/linux-gke-5.3: 5.3.0-1043.46 -proposed tracker (LP: #1924650) [ Ubuntu: 5.3.0-74.70 ] * bionic/linux-hwe: 5.3.0-74.70 -proposed tracker (LP: #1924647) * setting extended attribute may cause memory leak (LP: #1924611) - SAUCE: vfs_setxattr: free converted value if xattr_permission returns error -- Stefan Bader Fri, 16 Apr 2021 10:57:46 +0200 ** Changed in: linux-gke-5.3 (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: linux-hwe (Ubuntu Bionic) 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/1924611 Title: setting extended attribute may cause memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923000] Re: Can't adjust brightness on HP ZBook Fury 17 G7
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1023.24 --- linux-oem-5.10 (5.10.0-1023.24) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1023.24 -proposed tracker (LP: #1924513) * Can't adjust brightness on HP ZBook Fury 17 G7 (LP: #1923000) - SAUCE: drm/i915/dp add a quirk for backlight issue * CIFS DFS entries not accessible with 5.4.0-71.74-generic (LP: #1923670) - Revert "cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag on setting cifs_sb->prepath." -- Stefan Bader Thu, 15 Apr 2021 15:12:17 +0200 ** Changed in: linux-oem-5.10 (Ubuntu Focal) 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/1923000 Title: Can't adjust brightness on HP ZBook Fury 17 G7 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1923000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923670] Re: CIFS DFS entries not accessible with 5.4.0-71.74-generic
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1023.24 --- linux-oem-5.10 (5.10.0-1023.24) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1023.24 -proposed tracker (LP: #1924513) * Can't adjust brightness on HP ZBook Fury 17 G7 (LP: #1923000) - SAUCE: drm/i915/dp add a quirk for backlight issue * CIFS DFS entries not accessible with 5.4.0-71.74-generic (LP: #1923670) - Revert "cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag on setting cifs_sb->prepath." -- Stefan Bader Thu, 15 Apr 2021 15:12:17 +0200 ** Changed in: linux-oem-5.10 (Ubuntu Focal) 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/1923670 Title: CIFS DFS entries not accessible with 5.4.0-71.74-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925114] [NEW] not installing ,showing error
Public bug reported: I dont know how to describe it. it just showed some error and i cant boot ubuntu after restarting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 20 09:09:13 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925114 Title: not installing ,showing error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1925114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881941] Re: Ubuntu dock behaves crazy when hidden at the bottom of the screen
For myself, I'm only seeing this issue when IntelliJ is open and over the dock location, versions 2020.3 and 2021.1 thus far. I can't reproduce with any other application. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881941 Title: Ubuntu dock behaves crazy when hidden at the bottom of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1881941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923000] Re: Can't adjust brightness on HP ZBook Fury 17 G7
I just compared the test results in -1021(NG) and -1023(OK) kernels and could confirm the fix in one of the affected HP machines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923000 Title: Can't adjust brightness on HP ZBook Fury 17 G7 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1923000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: nextcloud crashed with SIGSEGV.
I have the same issue in Wayland. Program received signal SIGSEGV, Segmentation fault. doActivate (sender=0x0, signal_index=9, argv=0x7fffb1f0) at kernel/qobject.cpp:3768 3768kernel/qobject.cpp: No such file or directory. (gdb) bt #0 doActivate(QObject*, int, void**) (sender=0x0, signal_index=9, argv=0x7fffb1f0) at kernel/qobject.cpp:3768 #1 0x7fffeb9745a6 in QGuiApplication::screenAdded(QScreen*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #2 0x7fffde7464f8 in QtWaylandClient::QWaylandDisplay::handleScreenInitialized(QtWaylandClient::QWaylandScreen*) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #3 0x7fffde74fa07 in QtWaylandClient::QWaylandScreen::maybeInitialize() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #4 0x7fffea120249 in () at /lib/x86_64-linux-gnu/libffi.so.8 #5 0x7fffea11f639 in () at /lib/x86_64-linux-gnu/libffi.so.8 #6 0x7fffde6c4502 in () at /lib/x86_64-linux-gnu/libwayland-client.so.0 #7 0x7fffde6c0aea in () at /lib/x86_64-linux-gnu/libwayland-client.so.0 #8 0x7fffde6c21dc in wl_display_dispatch_queue_pending () at /lib/x86_64-linux-gnu/libwayland-client.so.0 #9 0x7fffde746145 in QtWaylandClient::QWaylandDisplay::forceRoundTrip() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #10 0x7fffde746c94 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x7fffde767cce in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x7fffea120249 in () at /lib/x86_64-linux-gnu/libffi.so.8 #13 0x7fffea11f639 in () at /lib/x86_64-linux-gnu/libffi.so.8 #14 0x7fffde6c4502 in () at /lib/x86_64-linux-gnu/libwayland-client.so.0 #15 0x7fffde6c0aea in () at /lib/x86_64-linux-gnu/libwayland-client.so.0 #16 0x7fffde6c21dc in wl_display_dispatch_queue_pending () at /lib/x86_64-linux-gnu/libwayland-client.so.0 #17 0x7fffde746145 in QtWaylandClient::QWaylandDisplay::forceRoundTrip() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #18 0x7fffde7463fa in QtWaylandClient::QWaylandDisplay::QWaylandDisplay(QtWaylandClient::QWaylandIntegration*) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #19 0x7fffde73984f in QtWaylandClient::QWaylandIntegration::QWaylandIntegration() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #20 0x77fbd53b in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqwayland-generic.so #21 0x7fffeb9789fc in QGuiApplicationPrivate::createPlatformIntegration() () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7fffeb979e88 in QGuiApplicationPrivate::createEventDispatcher() () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #23 0x7fffeafaee46 in QCoreApplicationPrivate::init() (this=) at kernel/qcoreapplication.cpp:834 #24 0x7fffeb97ce02 in QGuiApplicationPrivate::init() () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x7fffef318fed in QApplicationPrivate::init() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x5571c68b in SharedTools::QtSingleApplication::QtSingleApplication(QString const&, int&, char**) (this=0x7fffd5b0, appId=..., argc=, argv=, this=, appId=, argc=, argv=) at ./src/3rdparty/qtsingleapplication/qtsingleapplication.cpp:56 #27 0x5563d30c in OCC::Application::Application(int&, char**) (this=0x7fffd5b0, argc=@0x7fffd55c: 1, argv=0x7fffd7b8, this=, argc=, argv=) at ./src/gui/application.cpp:116 #28 0x556093c7 in main(int, char**) (argc=, argv=0x7fffd7b8) at ./src/gui/main.cpp:80 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923053 Title: nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925095] Re: GNOME Desktop selection is misallinged with the mouse on 21.04-dev
The bug is easily noticeable on the video attached here. ** Attachment added: "Bug happening while being recorded." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925095/+attachment/5489924/+files/2021-04-19%2021-58-16.mkv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925095 Title: GNOME Desktop selection is misallinged with the mouse on 21.04-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925095] [NEW] GNOME Desktop selection is misallinged with the mouse on 21.04-dev
Public bug reported: When dragging the mouse while selected on the Desktop, the selection box is misaligned with the mouse pointer. The issue only started happening on 21.04 after upgrading from 20.04 to the dev version of the OS. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 22:00:22 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-12-28 (112 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-13 (6 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925095 Title: GNOME Desktop selection is misallinged with the mouse on 21.04-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
when problems happens, please run: $sudo sh -c 'echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef' Then run alsa-info to collect an alsa-info.txt (bad) Then poweroff the machine and poweron it, make sure the audio works normally, run: $sudo sh -c 'echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef' Then run alsa-info to collect an alsa-info.txt (good) and upload the alsa-info.txt-bad and alsa-info.txt-good, let us compare them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
Should be this one: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
5.8.0-51 is not in groovy-proposed - developer options (or focal-proposed I'd assume) It's available here: https://launchpad.net/~canonical-kernel-team -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915722] Re: rustc 1.50 and cargo 0.51 will be required by a future version of firefox
Oh oops forgot about that. Uploaded now. How serious do you regard the s390x/groovy situation? I'm sure it's fixable but it would be tedious in the extreme I think... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915722 Title: rustc 1.50 and cargo 0.51 will be required by a future version of firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1915722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919468] Re: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD-method requests
The attachment "lp1919468.debdiff" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue 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/1919468 Title: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD- method requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1919468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925088] Re: Headphones don't work when speakers work
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1925088/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925088 Title: Headphones don't work when speakers work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1925088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921105] Re: SRU: backport cvise to 18.04 LTS, 20.04 LTS and 20.10
> Regression potential: None, as these are new packages. This is incorrect, because it is no longer a new package; it exists in -updates. So we need a test case and an analysis of the risk of regression vs the previous SRU. ** Changed in: cvise (Ubuntu Bionic) Status: New => Incomplete ** Changed in: cvise (Ubuntu Focal) Status: New => Incomplete ** Changed in: cvise (Ubuntu Groovy) 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/1921105 Title: SRU: backport cvise to 18.04 LTS, 20.04 LTS and 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cvise/+bug/1921105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847275] Re: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability
Would anyone like to test the 5.56 version with upstream patches? I have it backported to bionic and focal here: https://launchpad.net/~nerdboy/+archive/ubuntu/embedded/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865515] Re: Chainbooting from grub over the network to local shim breaks chain of trust
I'm using the default LXD settings, attached is qemu.conf. ** Attachment added: "qemu.conf" https://bugs.launchpad.net/maas/+bug/1865515/+attachment/5489916/+files/qemu.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865515 Title: Chainbooting from grub over the network to local shim breaks chain of trust To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865515] Re: Chainbooting from grub over the network to local shim breaks chain of trust
I was told that the latest SHIM/GRUB from Hirsute may have fixed this issue. It looks like chain loading from network GRUB to local GRUB works but the VM turns off when it tries to start the kernel. Attached is GRUB output with debug="all" My test setup is as follows: grub over the network and local: 2.04-1ubuntu45 shim over the network and local: 1.46+15.4-0ubuntu1 OS: Ubuntu 21.04 Machine: LXD VM 4.0.5 qemu command: /snap/lxd/19647/bin/qemu-system-x86_64 -S -name lxd-vm -uuid f5fec2be-21c7-4ffb-847f-f88589c06686 -daemonize -cpu host -nographic -serial chardev:console -nodefaults -no-reboot -no-user-config -sandbox on,obsolete=deny,elevateprivileges=allow,spawn=deny,resourcecontrol=deny -readconfig /var/snap/lxd/common/lxd/logs/maas_lxd-vm/qemu.conf -pidfile /var/snap/lxd/common/lxd/logs/maas_lxd-vm/qemu.pid -D /var/snap/lxd/common/lxd/logs/maas_lxd-vm/qemu.log -chroot /var/snap/lxd/common/lxd/virtual-machines/maas_lxd-vm -smbios type=2,manufacturer=Canonical Ltd.,product=LXD -runas lxd ** Attachment added: "secure-boot.log" https://bugs.launchpad.net/maas/+bug/1865515/+attachment/5489915/+files/secure-boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865515 Title: Chainbooting from grub over the network to local shim breaks chain of trust To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925093] [NEW] Mnemosyne won't launch
Public bug reported:
Error from command line launch:
Log body:
An unexpected error has occurred.
Please forward the following info to the developers:
Traceback (innermost last):
File "/usr/local/bin/mnemosyne", line 4, in
__import__('pkg_resources').run_script('Mnemosyne==2.7.3', 'mnemosyne')
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 665, in
run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1463,
in run_script
exec(code, namespace, namespace)
File
"/usr/local/lib/python3.8/dist-packages/Mnemosyne-2.7.3-py3.8.egg/EGG-INFO/scripts/mnemosyne",
line 150, in
from PyQt5 import QtWebEngineWidgets # Needs to happen first for some
reason.
ImportError: /lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.15' not
found (required by
/home/brendan/.local/lib/python3.8/site-packages/PyQt5/QtCore.abi3.so)
Lenovo Yoga 720
Ubuntu 20.10 Groovy
Mnemosyne v 2.7.2+
I expected the program to launch.
The program didn't launch.
** Affects: mnemosyne (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/1925093
Title:
Mnemosyne won't launch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mnemosyne/+bug/1925093/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924835] Re: package python-backports.functools-lru-cache 1.5-3build1 failed to install/upgrade: installed python-backports.functools-lru-cache package post-installation script subprocess returne
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. Specifically it looks like the Python installation on your system is broken somehow, possibly due to some local intervention. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: backports.functools-lru-cache (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/1924835 Title: package python-backports.functools-lru-cache 1.5-3build1 failed to install/upgrade: installed python-backports.functools-lru-cache package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backports.functools-lru-cache/+bug/1924835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924713] Re: package apache2 2.4.46-1ubuntu1 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: apache2 (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/1924713 Title: package apache2 2.4.46-1ubuntu1 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1924713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
** Changed in: oem-priority Assignee: Yuan-Chen Cheng (ycheng-twn) => Alex Tu (alextu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924609] Re: onion sites inaccessible due to internal DNS lookup
Thank you for your report. This does not seem likely to be a bug in Ubuntu's packaging of fetchmail to me, so since there is unlikely to be any action to take in Ubuntu itself on this, I'm marking the bug task representing the fetchmail package in Ubuntu as Won't Fix to make this clear. Rather, it seems to me that you're hitting a limitation of fetchmail in that the usual techniques to redirect a non-Tor-aware app into Tor do not work with it. It seems like a reasonable request to me for fetchmail to support this. But as it seems likely to me that this isn't related to how fetchmail is packaged in Ubuntu, and upstream fetchmail built from source would have the same issue, you're probably best checking that and, if confirmed, contacting fetchmail upstream about this. If this is resolved upstream, then Ubuntu will adopt the change in time and we can update the status accordingly. Alternatively if you think my interpretation is wrong, please feel free to explain and reopen. ** Changed in: fetchmail (Ubuntu) Importance: Undecided => Wishlist ** Changed in: fetchmail (Ubuntu) Status: New => Won't Fix ** Tags added: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924609 Title: onion sites inaccessible due to internal DNS lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1924609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749393] Re: sbrk() not working under qemu-user with a PIE-compiled binary?
There's a request for a backport of this fix to be made to Ubuntu 20.04 in duplicate bug 1924231, so I'm adding a task for that. ** Also affects: qemu (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Focal) Status: New => Confirmed ** Changed in: qemu (Ubuntu Focal) Status: Confirmed => Triaged ** Changed in: qemu (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749393 Title: sbrk() not working under qemu-user with a PIE-compiled binary? To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1749393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906187] Re: Version tag is not respected when put last
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: netplan.io (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/1906187 Title: Version tag is not respected when put last To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1906187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924231] Re: Getting "qemu: uncaught target signal 11 (Segmentation fault)" when the installing "libc-bin" which "wget" depends on.
*** This bug is a duplicate of bug 1749393 *** https://bugs.launchpad.net/bugs/1749393 Thank you for taking the time to report this bug and helping to make Ubuntu better. In Launchpad we use one bug per issue. Since this issue is already reported in bug 1749393, I'm marking this bug as a duplicate of that one. You're requesting to backport the fix to 20.04. We can track this in the other bug with a bug task, which I'll open now. ** This bug has been marked a duplicate of bug 1749393 sbrk() not working under qemu-user with a PIE-compiled binary? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924231 Title: Getting "qemu: uncaught target signal 11 (Segmentation fault)" when the installing "libc-bin" which "wget" depends on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1924231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903716] Re: [20.04.1] VROC - mdadm missing in live-installer ISO
Set back to Incomplete. I presume Pawel should comment on this so we can sort out what the actuall issue is. ** Changed in: subiquity Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903716 Title: [20.04.1] VROC - mdadm missing in live-installer ISO To manage notifications about this bug go to: https://bugs.launchpad.net/mdadm/+bug/1903716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242417] Re: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio)
This bug was fixed years before focal was released. Please file a new bug report for your issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242417 Title: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923040] Re: en-gb thesaurus is missing
** Changed in: libreoffice-dictionaries (Debian) Status: Unknown => 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/1923040 Title: en-gb thesaurus is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1923040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838038] Re: [snap] Snapped apps do not work with .local mdns/avahi name resolution
Applied a Snap-side workaround to my Snaps which implements the fix presented in the snapcraft.io thread mentioned in my previous post: CUPS Snap: https://github.com/OpenPrinting/cups-snap/commit/f241f3f02 PostScript Printer Application: https://github.com/OpenPrinting/ps-printer-app/commit/1f6ca389 Note that doing this on any Snap which needs it in the future is awkward, so we really need to fix core18 and core20. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838038 Title: [snap] Snapped apps do not work with .local mdns/avahi name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/snap-core18/+bug/1838038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925088] [NEW] Headphones don't work when speakers work
Public bug reported: Hi! I have problem with front panel audio output connector. Speakers still work after my headphones is connected. Everything correctly works on windows 10. I selected headphones in Settings -> Sound -> Output, but speakers were continuing working. PulseAudio Volume Control didn't help too. I've tried to change configuration and select headphones as output devices. When i disconnected speakers, headphones weren't still working. I've done all list from https://help.ubuntu.com/community/SoundTroubleshooting and haven't found any problems. pacmd - https://pastebin.com/Jkfqt4ft aplay - https://pastebin.com/NGq37fVb snd - https://pastebin.com/7bS0GKzc lspci - https://pastebin.com/Z6CYmRU2 alsa - http://alsa-project.org/db/?f=b5701e36e1510cb211fd3047c36598da27fef2d9 My hardware: CPU - Intel i9 10900k Mobo - Asus z590-e with the latest bios. GPU - Nvidia RTX 3070 If you need some additional information, I will provide it. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925088 Title: Headphones don't work when speakers work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1925088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919468] Re: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD-method requests
I'm attaching a debdiff to have Focal upgraded from 2.0.13 to 2.0.22 (latest upstream 2.0 stable). ** Patch added: "lp1919468.debdiff" https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1919468/+attachment/5489911/+files/lp1919468.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919468 Title: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD- method requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1919468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242417] Re: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio)
This problem also affects grub-efi-amd64-signed on Focal Fossa if GRUB_DISTRIBUTOR is not set to "ubuntu" in /etc/default/grub. I stumbled across this in Ubuntu 20.04-based KDE neon, but in general it's sufficient to set GRUB_DISTRIBUTOR to a "wrong" value - the grub binary tries to load itself from a hardcoded path which ends in "ubuntu" and loading will fail and end in the grub shell. How to add Focal as an affected version? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242417 Title: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242417] Re: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kubuntu-settings (Ubuntu Precise) 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/1242417 Title: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242417] Re: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2-signed (Ubuntu Precise) Status: New => Confirmed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1242417 Title: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1242417] Re: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2 (Ubuntu Precise) 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/1242417 Title: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
I should probably clarify - I know that these three packages were part of the core extensions. However, I noticed that the timestamps for all of the core extensions were the same _except_ for those three. I reinstalled the gnome-shell-extensions package make sure they were correct, but those three extensions were not updated, or at least their timestamps did not change. I then purged the package and observed that those three extensions were still present, so I deleted them and reinstalled the gnome-shell-extensions package. I expected to see those three extensions restored, but they were not reinstalled. As for the non-core extensions, I was planning to test them one at a time, but after taking the steps above I could not replicate the issue. Since that time I have not had any problems with gnome-shell crashing. If I could not repeat the issue with them installed, it seemed moot to removing the extensions one by one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899299] Re: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot
** Description changed: + === Begin SRU Template === + [Impact] + The 'Paths' class has a 'run_dir' attribute that was introduced since the release of Trusty. Because of this, performing a `do-release-upgrade` on Trusty followed by a reboot will have cloud-init fail with a traceback. + + The change here should fix that failure. + + [Test Plan] + - Launch a Trusty instance + - Perform a `do-release-upgrade` + - Reboot + + On un-patched versions, `cloud-init status` will show error, and there + will be a traceback in /var/log/cloud-init.log. Patched versions should + show no error or traceback. + + [Where problems could occur] + Any problem here would mean we're continuing to unpickle data incorrectly, thus we'd see similar behavior to the bug we're fixing. + + [Other Info] + Pull request: https://github.com/canonical/cloud-init/pull/863 + Commit: https://github.com/canonical/cloud-init/commit/83f6bbfbe5b924be61a3c098f4202377d69c8947 + + == End SRU Template == + + == Original Description == + After performing a do-release-upgrade from stock trusty to xenial and rebooting cloud-init traces in it's attempt to preserve instance data: Probably obj.pkl issues across upgrade and a need to refresh Paths object after the dist upgrade. 2020-10-10 18:01:02,377 - util.py[DEBUG]: Read 298 bytes from /etc/os-release 2020-10-10 18:01:02,378 - util.py[WARNING]: failed stage init-local 2020-10-10 18:01:02,379 - util.py[DEBUG]: failed stage init-local Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 653, in status_wrapper - ret = functor(name, args) - File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 351, in main_init - _maybe_persist_instance_data(init) - File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 695, in _maybe_persist_instance_data - init.datasource.persist_instance_data() - File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 332, in persist_instance_data - json_sensitive_file = os.path.join(self.paths.run_dir, + File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 653, in status_wrapper + ret = functor(name, args) + File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 351, in main_init + _maybe_persist_instance_data(init) + File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 695, in _maybe_persist_instance_data + init.datasource.persist_instance_data() + File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 332, in persist_instance_data + json_sensitive_file = os.path.join(self.paths.run_dir, AttributeError: 'Paths' object has no attribute 'run_dir' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cloud-init 20.3-2-g371b392c-0ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 CloudName: LXD Date: Sat Oct 10 21:22:46 2020 PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 SourcePackage: cloud-init UpgradeStatus: Upgraded to xenial on 2020-10-10 (0 days ago) cloud-init-log-warnings: - 2020-10-10 18:01:02,378 - util.py[WARNING]: failed stage init-local - AttributeError: 'Paths' object has no attribute 'run_dir' - 2020-10-10 18:01:02,979 - util.py[WARNING]: failed stage init - AttributeError: 'Paths' object has no attribute 'run_dir' + 2020-10-10 18:01:02,378 - util.py[WARNING]: failed stage init-local + AttributeError: 'Paths' object has no attribute 'run_dir' + 2020-10-10 18:01:02,979 - util.py[WARNING]: failed stage init + AttributeError: 'Paths' object has no attribute 'run_dir' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899299 Title: do-release-upgrade from Trusty to Xenial breaks cloud-init init-local on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1899299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923305] Re: LibreOffice 6.4 OpenType Features unusable
Thank you for your suggestion to cherrypick this onto the 6.4 branch. We try to keep the branches as in line with upstream as possible so if you would like to use the newer 7.X then I suggest you try the snap out: https://snapcraft.io/libreoffice Remove the libreoffice deb and install the snap with: $ sudo apt purge libreoffice* $ sudo snap install libreoffice -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923305 Title: LibreOffice 6.4 OpenType Features unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1923305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922739] Re: AttributeError: 'DataSourceNoCloud' object has no attribute 'vendordata2_raw'
** Description changed: === Begin SRU Template === [Impact] In PR #777, we added 'vendordata2' and 'vendordata2_raw' attributes to the DataSource class, but didn't use the upgrade framework to deal with an unpickle after upgrade. Because of this, anybody upgrading their cloud-init from an older version to 21.1 who hasn't also run `cloud-init clean` will have cloud-init fail with a traceback. The change here should fix that failure. [Test Plan] Launch an instance or install a cloud-init package using version earlier than 21.1-19-gbad84ad4-0ubuntu1 (if downgrading also run `cloud-init clean`). Upgrade to 21.1-19-gbad84ad4-0ubuntu1 or later, then reboot (without running `cloud-init clean`). On un-patched versions, `cloud-init status` will show error, and there will be a traceback in /var/log/cloud-init.log. Patched versions should show no error or traceback. [Where problems could occur] - Any problem here would mean we're continuing to unpickle data incorrectly, thus we'd see similar behavior to the bug we're fixing. + Any problem here would mean we're continuing to unpickle data incorrectly, thus we'd see similar behavior to the bug we're fixing. [Other Info] Pull request: https://github.com/canonical/cloud-init/pull/869 - A test has also been added upstream and to our CI to prevent these types of errors from happening in the future: https://github.com/canonical/cloud-init/blob/master/tests/integration_tests/test_upgrade.py#L107 + Commit: https://github.com/canonical/cloud-init/commit/d132356cc361abef2d90d4073438f3ab759d5964 + + A test has also been added upstream and to our CI to prevent these types + of errors from happening in the future: https://github.com/canonical + /cloud-init/blob/master/tests/integration_tests/test_upgrade.py#L107 == End SRU Template == == Original Description == On a test LXD VM instance, I see: 2021-04-06 14:05:11,296 - util.py[WARNING]: failed stage init 2021-04-06 14:05:11,302 - util.py[DEBUG]: failed stage init Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 652, in status_wrapper ret = functor(name, args) File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 376, in main_init init.update() File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 371, in update self._store_raw_vendordata(self.datasource.get_vendordata2_raw(), File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 506, in get_vendordata2_raw return self.vendordata2_raw AttributeError: 'DataSourceNoCloud' object has no attribute 'vendordata2_raw' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922739 Title: AttributeError: 'DataSourceNoCloud' object has no attribute 'vendordata2_raw' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1922739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925084] [NEW] package snapd 2.49+21.04build1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
Public bug reported: Post install ProblemType: Package DistroRelease: Ubuntu 21.04 Package: snapd 2.49+21.04build1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 AptOrdering: gnome-software-plugin-snap:amd64: Purge snapd:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 31 12:42:32 2021 Df: Filesystem 1K-blocks Used Available Use% Mounted on tmpfs1616652 12556 1604096 1% /run ErrorMessage: installed snapd package post-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-19 (0 days ago) InstallationMedia: Ubuntu Unity 21.04 Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.2-2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.7.1ubuntu4 apt 2.2.2 SourcePackage: snapd Title: package snapd 2.49+21.04build1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925084 Title: package snapd 2.49+21.04build1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1925084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880211] Re: Logwatch package points to wrong location for zfs utils
This bug was fixed in the package logwatch - 7.5.5-1ubuntu2 --- logwatch (7.5.5-1ubuntu2) hirsute; urgency=medium * d/p/0010-zz-zfs-detect-zfs-location.patch: Use explicit paths for finding zfs and zpool executables. (LP: #1880211) -- Bryce Harrington Wed, 14 Apr 2021 20:11:05 + ** Changed in: logwatch (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/1880211 Title: Logwatch package points to wrong location for zfs utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1880211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
Before I change the status of this bug, I would like to report my findings here. I am testing things on a Bionic s390x machine with everything up-to- date: # apt policy systemd systemd: Installed: 237-3ubuntu10.46 ... # apt policy containerd containerd: Installed: 1.4.4-0ubuntu1~18.04.2 ... # apt policy docker.io docker.io: Installed: 20.10.2-0ubuntu1~18.04.2 ... # apt policy runc runc: Installed: 1.0.0~rc93-0ubuntu1~18.04.1 ... Following the reproduction steps listed in the Description section still fail for me: # systemd-nspawn Spawning container h on /root/h. Press ^] three times within 1s to kill container. # bash -c 'test -x /usr/bin/gpg || echo Fail' Fail When I'm in a hirsute Docker container, it also fails: $ docker run -it --rm ubuntu:hirsute root@78506947b11f:/# bash -c 'test -x /usr/bin/gpg || echo Fail' Fail This is impacting the build of the 21.04 OCI images on s390x (amd64, arm64 and ppc64el succeed). I'm still not sure what's causing this, nor why this is happening only on s390x. I will post more details when I have them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925002] Re: Installer crashes during manual installation with disk encryption
This bug was fixed in the package ubiquity - 21.04.19 --- ubiquity (21.04.19) hirsute; urgency=medium [ Didier Roche ] [ Jean-Baptiste Lallement ] * Only set the recovery key when partman-auto is used (LP: #1925002) -- Jean-Baptiste Lallement Mon, 19 Apr 2021 15:17:58 +0200 ** Changed in: ubiquity (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/1925002 Title: Installer crashes during manual installation with disk encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1925002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924855] Re: Dock is sporadically blank when booting up or when waking from hibernation
Since I applied the latest updates I've not had the issue. I will give it a few days and if the problem arises I will apply your patch and see if that resolves it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924855 Title: Dock is sporadically blank when booting up or when waking from hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1924855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922739] Re: AttributeError: 'DataSourceNoCloud' object has no attribute 'vendordata2_raw'
** Description changed: + === Begin SRU Template === + [Impact] + In PR #777, we added 'vendordata2' and 'vendordata2_raw' attributes to the DataSource class, but didn't use the upgrade framework to deal with an unpickle after upgrade. Because of this, anybody upgrading their cloud-init from an older version to 21.1 who hasn't also run `cloud-init clean` will have cloud-init fail with a traceback. + + The change here should fix that failure. + + [Test Plan] + Launch an instance or install a cloud-init package using version earlier than 21.1-19-gbad84ad4-0ubuntu1 (if downgrading also run `cloud-init clean`). + + Upgrade to 21.1-19-gbad84ad4-0ubuntu1 or later, then reboot (without + running `cloud-init clean`). + + On un-patched versions, `cloud-init status` will show error, and there + will be a traceback in /var/log/cloud-init.log. Patched versions should + show no error or traceback. + + [Where problems could occur] + Any problem here would mean we're continuing to unpickle data incorrectly, thus we'd see similar behavior to the bug we're fixing. + + [Other Info] + Pull request: https://github.com/canonical/cloud-init/pull/869 + A test has also been added upstream and to our CI to prevent these types of errors from happening in the future: https://github.com/canonical/cloud-init/blob/master/tests/integration_tests/test_upgrade.py#L107 + + == End SRU Template == + + == Original Description == + On a test LXD VM instance, I see: 2021-04-06 14:05:11,296 - util.py[WARNING]: failed stage init 2021-04-06 14:05:11,302 - util.py[DEBUG]: failed stage init Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 652, in status_wrapper - ret = functor(name, args) - File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 376, in main_init - init.update() - File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 371, in update - self._store_raw_vendordata(self.datasource.get_vendordata2_raw(), - File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 506, in get_vendordata2_raw - return self.vendordata2_raw + File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 652, in status_wrapper + ret = functor(name, args) + File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 376, in main_init + init.update() + File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 371, in update + self._store_raw_vendordata(self.datasource.get_vendordata2_raw(), + File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 506, in get_vendordata2_raw + return self.vendordata2_raw AttributeError: 'DataSourceNoCloud' object has no attribute 'vendordata2_raw' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922739 Title: AttributeError: 'DataSourceNoCloud' object has no attribute 'vendordata2_raw' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1922739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
