[Bug 1876157] Re: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020
Addendum to comment #21: The memtest86+ version 5.31b ISO image from http://www.memtest.org/ seems to work fine on this hardware. Source is there as well. Will they let Ubuntu use it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876157 Title: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Changed in: oem-priority Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933716] Re: Black screen on boot after stable update
I have hit this bug as well. Please let me know if there is any information I can provide. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
Information required for implementation: - Where does the link go to, http://ubuntu.com/desktop/pro? - Does the banner only show if you haven't already attached this machine to Ubuntu Advantage? - When closing the banner, does it return next time? - Does it make sense for this to be in the "Livepatch" tab - should that tab be renamed to "Ubuntu Pro" at the same time? - When will this feature no-longer be a preview? Will that require a second SRU or can we determine that at runtime? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
Implementation at https://code.launchpad.net/~robert-ancell/software- properties/+git/software-properties/+ref/ubuntu-pro-beta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
** Attachment added: "Screenshot of implementation" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+attachment/5508533/+files/Screenshot%20from%202021-07-02%2016-58-30.png ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Xenial) 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/1934439 Title: Add Ubuntu Pro banner to Livepatch page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
** Attachment added: "Mockup of banner" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+attachment/5508532/+files/ubuntu-pro-mockup.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934439] [NEW] Add Ubuntu Pro banner to Livepatch page
Public bug reported: Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Impish) 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/1934439 Title: Add Ubuntu Pro banner to Livepatch page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201 on ADL
With CONFIG_IWLWIFI_DEBUG enabled. ** Attachment added: "dmesg.SDP-ADL-S-BETA-99ACNN-202105-29062.5.13.0-rc6-debug-ff8744b5eb11.iwlwifi-fw-64.97bbee0a.0" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933938/+attachment/5508531/+files/dmesg.SDP-ADL-S-BETA-99ACNN-202105-29062.5.13.0-rc6-debug-ff8744b5eb11.iwlwifi-fw-64.97bbee0a.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933938 Title: Missing CNVi firmware for Intel AX211/AX201 on ADL To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925973] Re: Nvidia driver 450.119 crashes lxpanel on Ubuntu 18.04
[Expired for lxpanel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lxpanel (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/1925973 Title: Nvidia driver 450.119 crashes lxpanel on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1925973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926574] Re: Not possible to share windows in a video conference
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: 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/1926574 Title: Not possible to share windows in a video conference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1926574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928890] Re: vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
5.10.0-1035.36 OEM node vought ** Tags added: sru-20210621 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928890 Title: vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928733] Re: Starting systemd Network Service fails with "Invalid argument"
Hi Dan, Thank you for that. The server is bare metal, not in a container. If I understand correctly the fix will go in the latest Bionic packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928733 Title: Starting systemd Network Service fails with "Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1928733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934428] [NEW] Request to pull-in new PERC11 PCI-id from upstream
Private bug reported: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:00e6:1028:2171 PERC H750 Mini 1000:00e6:1028:2172 PERC H355 Adapter 1000:00e6:1028:2173 PERC H355 Front 1000:00e6:1028:2174 PERC H350 Mini 1000:00e6:1028:2176 PERC H750 Adapter 1000:00e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids ** Affects: dellserver Importance: Undecided Status: New ** Affects: hwdata (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Also affects: dellserver 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/1934428 Title: Request to pull-in new PERC11 PCI-id from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932539] Re: Support thunderbolt on Intel Alder Lake P
** Summary changed: - Support thunderbolt on Intel Alder Lake + Support thunderbolt on Intel Alder Lake P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932539 Title: Support thunderbolt on Intel Alder Lake P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1932539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932124] Re: Add WWAN framework and drivers support
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932124 Title: Add WWAN framework and drivers support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1932124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932539] Re: Support thunderbolt on Intel Alder Lake
This bug was originally for thunderbolt on ADL-P, but comment #19 is for Maple Ridge on ADL-S. I'll file a new one for the latter and focus on the original purpose here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932539 Title: Support thunderbolt on Intel Alder Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1932539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934424] [NEW] kernel NULL pointer dereference during xen hibernation
Public bug reported: Encountered the following panic while doing hibernation/resume testing with linux-aws 5.8 on Focal on an m3.xlarge (xen) instance type: [ 594.291317] ACPI: Hardware changed while hibernated, success doubtful! [ 594.411609] BUG: kernel NULL pointer dereference, address: 01f4 [ 594.424658] #PF: supervisor write access in kernel mode [ 594.424660] #PF: error_code(0x0002) - not-present page [ 594.424661] PGD 0 P4D 0 [ 594.424665] Oops: 0002 [#1] SMP PTI [ 594.424668] CPU: 3 PID: 362 Comm: systemd-timesyn Not tainted 5.8.0-1036-aws #38~20.04.1-Ubuntu [ 594.424669] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 594.424675] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40 [ 594.424678] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90 [ 594.424679] RSP: 0018:c94e3848 EFLAGS: 00010046 [ 594.424680] RAX: RBX: 8883bcc0d000 RCX: 0e02 [ 594.424681] RDX: 0001 RSI: RDI: 01f4 [ 594.424682] RBP: c94e3850 R08: 8883b90b5ec0 R09: 005a [ 594.424683] R10: c94e3910 R11: R12: 0206 [ 594.424684] R13: ea000ee42d40 R14: R15: 0001 [ 594.424686] FS: 7f65ba055980() GS:8883c0ac() knlGS: [ 594.424687] CS: 0010 DS: ES: CR0: 80050033 [ 594.424688] CR2: 01f4 CR3: 0003b99f0001 CR4: 001606e0 [ 594.424692] Call Trace: [ 594.424699] xennet_start_xmit+0x158/0x570 [ 594.424704] dev_hard_start_xmit+0x91/0x1f0 [ 594.424706] ? validate_xmit_skb+0x300/0x340 [ 594.424710] sch_direct_xmit+0x113/0x340 [ 594.424712] __dev_queue_xmit+0x57c/0x8e0 [ 594.424714] ? neigh_add_timer+0x37/0x60 [ 594.424716] dev_queue_xmit+0x10/0x20 [ 594.424717] neigh_resolve_output+0x112/0x1c0 [ 594.424721] ip_finish_output2+0x19b/0x590 [ 594.424723] __ip_finish_output+0xc8/0x1e0 [ 594.424725] ip_finish_output+0x2d/0xb0 [ 594.424728] ip_output+0x7a/0xf0 [ 594.424730] ? __ip_finish_output+0x1e0/0x1e0 [ 594.424732] ip_local_out+0x3d/0x50 [ 594.424734] ip_send_skb+0x19/0x40 [ 594.424737] udp_send_skb.isra.0+0x165/0x390 [ 594.424739] udp_sendmsg+0xb0e/0xd50 [ 594.424742] ? ip_reply_glue_bits+0x50/0x50 [ 594.424747] ? delete_from_swap_cache+0x6a/0x90 [ 594.424750] ? _cond_resched+0x19/0x30 [ 594.424754] ? aa_sk_perm+0x43/0x1b0 [ 594.424757] inet_sendmsg+0x65/0x70 [ 594.424759] ? security_socket_sendmsg+0x35/0x50 [ 594.424760] ? inet_sendmsg+0x65/0x70 [ 594.424764] sock_sendmsg+0x5e/0x70 [ 594.424766] __sys_sendto+0x113/0x190 [ 594.424770] ? __secure_computing+0x42/0xe0 [ 594.424774] ? syscall_trace_enter+0x10d/0x280 [ 594.424777] __x64_sys_sendto+0x29/0x30 [ 594.424781] do_syscall_64+0x49/0xc0 [ 594.424783] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 594.424785] RIP: 0033:0x7f65baee4844 [ 594.424788] Code: 42 3f f7 ff 44 8b 4c 24 2c 4c 8b 44 24 20 89 c5 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 30 89 ef 48 89 44 24 08 e8 68 3f f7 ff 48 8b [ 594.424789] RSP: 002b:7ffe9b5fd3a0 EFLAGS: 0293 ORIG_RAX: 002c [ 594.424790] RAX: ffda RBX: 7ffe9b5fd4e0 RCX: 7f65baee4844 [ 594.424791] RDX: 0030 RSI: 7ffe9b5fd3f0 RDI: 0010 [ 594.424792] RBP: R08: 560426541678 R09: 0010 [ 594.424793] R10: 0040 R11: 0293 R12: [ 594.424794] R13: 7ffe9b5fd3e4 R14: 0068 R15: [ 594.424796] Modules linked in: btrfs blake2b_generic xor raid6_pq ufs msdos xfs libcrc32c dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd input_leds glue_helper serio_raw floppy sch_fq_codel drm ip_tables x_tables autofs4 [ 594.424813] CR2: 01f4 [ 594.424821] ---[ end trace bb5f35055c1a8060 ]--- [ 594.424822] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40 [ 594.424824] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90 [ 594.424824] RSP: 0018:c94e3848 EFLAGS: 00010046 [ 594.424825] RAX: RBX: 8883bcc0d000 RCX: 0e02 [ 594.424826] RDX: 0001 RSI: RDI: 01f4 [ 594.424826] RBP: c94e3850 R08: 8883b90b5ec0 R09: 005a [ 594.424827] R10: c94e3910 R11: R12: 0206 [ 594.424827] R13: ea000ee42d40 R14: R15: 0001 [ 594.424828] FS: 7f65ba055980()
[Bug 1930140] Re: GUI "Extract Here" bug - loop until disk is full
Hello, This is a fresh OS installation. I simply rightclick on the file and select extract option. Didint use any specific software. even though the unrar was not installed I was able to extract by right clicking on the file. ** Changed in: ubuntu Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1930140 Title: GUI "Extract Here" bug - loop until disk is full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1930140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage
bluez (5.53-0ubuntu3.2) focal-security; urgency=medium * SECURITY UPDATE: secure pairing passkey brute force - debian/patches/CVE-2020-26558.patch: fix not properly checking for secure flags in src/shared/att-types.h, src/shared/gatt-server.c. - CVE-2020-26558 * SECURITY UPDATE: DoS or code execution via double-free - debian/patches/CVE-2020-27153.patch: fix possible crash on disconnect in src/shared/att.c. - CVE-2020-27153 * SECURITY UPDATE: info disclosure via out of bounds read - debian/patches/CVE-2021-3588.patch: when client features is read check if the offset is within the cli_feat bounds in src/gatt-database.c. - CVE-2021-3588 -- Marc Deslauriers Wed, 09 Jun 2021 11:06:38 -0400 ** Changed in: bluez (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926548 Title: The gatt protocol has out-of-bounds read that leads to information leakage To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage
bluez (5.55-0ubuntu1.2) groovy-security; urgency=medium * SECURITY UPDATE: secure pairing passkey brute force - debian/patches/CVE-2020-26558.patch: fix not properly checking for secure flags in src/shared/att-types.h, src/shared/gatt-server.c. - CVE-2020-26558 * SECURITY UPDATE: info disclosure via out of bounds read - debian/patches/CVE-2021-3588.patch: when client features is read check if the offset is within the cli_feat bounds in src/gatt-database.c. - CVE-2021-3588 -- Marc Deslauriers Wed, 09 Jun 2021 11:01:25 -0400 ** Also affects: bluez (Ubuntu Groovy) Importance: Undecided Status: New ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-26558 ** Changed in: bluez (Ubuntu Groovy) Status: New => Fix Released ** Also affects: bluez (Ubuntu Focal) Importance: Undecided Status: New ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-27153 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926548 Title: The gatt protocol has out-of-bounds read that leads to information leakage To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934409] Re: Only one monitor showing in Color Corrections - System Settings Module
Okay, if I do a reinstallion of colord, I can see both monitors and actually set the profile on the second screen. I lose the printer profile upon doing this. This works until next reboot and then everything reverts (only see one monitor and the printer color profiles). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934409 Title: Only one monitor showing in Color Corrections - System Settings Module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1934409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153
Also seeing this failure through regression testing on 4.15.0-149.153 i386 lowlatency and generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864612] Re: requests ipmi-tool to include lasted patch for supporting quanta server
This bug was fixed in the package ipmitool - 1.8.18-10.1ubuntu1 --- ipmitool (1.8.18-10.1ubuntu1) impish; urgency=medium * d/p/add_basic_support_for_quanta.patch: Add basic support for Quanta - Enables support for IPMI events on Quanta Server hardware (LP: #1864612) -- Bryce Harrington Wed, 30 Jun 2021 17:19:24 -0700 ** Changed in: ipmitool (Ubuntu Impish) 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/1864612 Title: requests ipmi-tool to include lasted patch for supporting quanta server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1864612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621102] Re: /home symlink, snaps don't work
** Changed in: snapd (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621102 Title: /home symlink, snaps don't work To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1621102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934414] Re: linux ADT test failure with linux/4.15.0-149.153
** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/l/linux/20210625_024137_c7e43@/log.gz - i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux/20210625_011348_1dfec@/log.gz + i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz ** Summary changed: - linux ADT test failure with linux/4.15.0-149.153 + test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 ** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz + + + 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh + 03:37:02 DEBUG| [stdout] + 03:37:03 ERROR| [stderr] Segmentation fault + 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] + 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] + 03:37:03 DEBUG| [stdout] selftests: netdevice.sh + 03:37:03 DEBUG| [stdout] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
OK, that's progress. Please open two new bugs to cover those issues: * Nvidia driver 460 fails in install on 21.04 * Brightness control is missing on HP Pavilion Gaming Laptop 15-dk0xxx Assuming the Intel GPU is wired to the laptop screen those are different bugs. ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
^^^ Note bug 1933221 is really a duplicate of this one. That's why it's 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
This bug was fixed in the package bluez - 5.56-0ubuntu4.2 --- bluez (5.56-0ubuntu4.2) hirsute; urgency=medium * debian/patches/0001-fix-reading-from-rfkill-socket.patch: - fix reading from rfkill socket (lp: #1933221) -- Andy Chi Tue, 22 Jun 2021 08:07:12 + ** Changed in: bluez (Ubuntu Hirsute) 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
This bug was fixed in the package bluez - 5.53-0ubuntu3.3 --- bluez (5.53-0ubuntu3.3) focal; urgency=medium * debian/patches/0001-fix-reading-from-rfkill-socket.patch: - fix reading from rfkill socket (lp: #1933221) -- Andy Chi Tue, 22 Jun 2021 14:27:12 +0800 ** Changed in: bluez (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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931547] Re: DisplayLink displays are black after Mesa update
** Also affects: xorg-server (Ubuntu Impish) Importance: High Assignee: Timo Aaltonen (tjaalton) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931547 Title: DisplayLink displays are black after Mesa update To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934414] [NEW] linux ADT test failure with linux/4.15.0-149.153
Public bug reported: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/l/linux/20210625_024137_c7e43@/log.gz i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux/20210625_011348_1dfec@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934414 Title: linux ADT test failure with linux/4.15.0-149.153 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable
If you still experience a problem in kernel 5.8.0-52 or later then please open a new bug by running: ubuntu-bug linux -- 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 kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics 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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Note we're still missing a fix for impish. It's marked as Fix Committed because it's committed upstream and coming in release 1.20.12 but that tag doesn't exist yet. ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-1.20.12 fixed-upstream ** Also affects: xorg-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Impish) Importance: Undecided Status: Fix Committed ** Changed in: xorg-server (Ubuntu Focal) Assignee: (unassigned) => Dave Walker (davewalker) ** Changed in: xorg-server (Ubuntu Hirsute) Assignee: (unassigned) => Dave Walker (davewalker) ** Changed in: xorg-server (Ubuntu Focal) Status: New => In Progress ** Changed in: xorg-server (Ubuntu Hirsute) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875354] Re: No more smb access after migration to UBUNTU 20.04 from UBUNTU 19.10
File sharing stopped working after upgrading to Ubuntu 20.04. Turns out there was a change in behavior in Sambva v4.11 that disabled SMB1 protocol by default. Here’s the fix, from Reddit https://www.reddit.com/r/linuxquestions/comments/djvpdn/smb_connection_nautilus_error_debian_bullseye/ You can reenable it by adding client min protocol = CORE to the [global] section of you /etc/samba/smb.conf file on your client machine. ou might want to add that it is then necessary to restart the smb daemon: sudo systemctl restart smbd.service Hope it is helpfull. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875354 Title: No more smb access after migration to UBUNTU 20.04 from UBUNTU 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1875354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621102] Re: /home symlink, snaps don't work
This has been covered extensively elsewhere, for example on the forum, etc. but we don't have immediate plans to support symlinked homes, and bind mounts are an appropriate work-around: https://snapcraft.io/docs /home-outside-home. I for some reason have lost my permission to change the snapd debian package priority, but it should also be "Low", like the snapd project here I just added. ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Triaged ** Changed in: snapd Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621102 Title: /home symlink, snaps don't work To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1621102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1011.11)
All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1011.11) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: sl-modem/2.9.11~20110321-16ubuntu1 (amd64) oss4/4.2-build2010-5ubuntu8 (amd64) lttng-modules/2.12.2-1ubuntu3 (amd64) rtl8821ce/5.5.2.1-0ubuntu6 (amd64) systemd/247.3-3ubuntu3.1 (amd64) backport-iwlwifi-dkms/8613-0ubuntu2 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64) v4l2loopback/0.12.5-1ubuntu1 (amd64) virtualbox/6.1.18-dfsg-5 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions 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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934409] Re: Only one monitor showing in Color Corrections - System Settings Module
>From system settings, I can see both monitors in Display configuration. >From command prompt, I can see both displays when I use xrandr. >From command prompt, I can only see one display when I use colormgr get- devices-by-kind display Did not have this issue with Kubuntu 20.10. My notebook, which hasn't been upgraded from 20.10 yet (I'll hold off) does not have this issue and it does show all display devices in Display Configuration, useing xrandr from command prompt, and colormgr from command prompt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934409 Title: Only one monitor showing in Color Corrections - System Settings Module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1934409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934410] [NEW] Second Monitor shuts off.
Public bug reported: I'm running two identical monitors daisy-chained via my DV port on my NUC10i7. The second monitor shuts down with a no signal error message, though the system still seems to see it. If I change it's refresh rate it will come back but, depending on the software I'm using, goes into low power mode and blanks off again. Sometimes randomly. Always when starting video conferencing software (e.g. zoom or webex). Today when using abd and fastboot from the command line in a terminal window. ** Affects: linux (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/1934410 Title: Second Monitor shuts off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934409] [NEW] Only one monitor showing in Color Corrections - System Settings Module
Public bug reported: I just made the switch to 21.04, and I've immediatly run into problem with color corrections. In the Color Correction - System settings Module, I can only see and apply a color profile to my first display on the first display port (DP0). My second display on the 2nd display Port (DP1) is not shown, so I'm unable to apply a color profile to make the two monitors look identical. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: colord 1.4.5-3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 1 17:43:58 2021 InstallationDate: Installed on 2019-04-19 (804 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: colord UpgradeStatus: Upgraded to hirsute on 2021-07-01 (0 days ago) ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934409 Title: Only one monitor showing in Color Corrections - System Settings Module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1934409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1231091] Re: Screenreader starts, but does not work with installer (ubiquity) in live session
Regarding @hellsworth's observation (post # 11):
Though this observation may well lead us down the correct path, I
strongly believe both run as the superuser. Here's why:
For the record, the MATE desktop's window manager is Marco; the "window
manager" on stock Ubuntu is Mutter since stock Ubuntu uses the GNOME
desktop. Another thing to note is that stock Ubuntu tends to use
Wayland by default, whereas Ubuntu MATE exclusively uses X11 (mainly
because the MATE applications don't work very well on Wayland yet).
Marco adds the " (as superuser)" suffix to the end of windows which are
owned by the superuser. The Marco code which adds the suffix is located
on lines 486-491 in the source file `src/core/window-props.c` (see
https://github.com/mate-desktop/marco/blob/master/src/core/window-
props.c#L486-L491):
if (window_owner==0)
{
/* Simple case-- don't bother to look it up. It's root. */
*target = g_strdup_printf (_("%s (as superuser)"),
title);
}
I was going to look up whether Mutter has a similar block of code for
the function, but I discovered I didn't need to: On stock Ubuntu, the
maybe-ubiquity screen uses just a plain old, client-side-decorated
header bar, which bypasses the window manager's own decorations. I can
prove it since this screenshot (https://phoenixnap.com/kb/wp-
content/uploads/2021/04/choose-keyboard-layout-for-ubuntu-20.04.png)
shows Ubiquity's title bar without the menu button on the left side of
the window title bar; the menu icon (which is a group of three white
horizontal lines) always appears with the default Mutter settings if
Mutter draws the window title. Note that Mutter never draws the window
title on Wayland.
So in other words, just because one says it's run as the superuser and
the other doesn't say it does not mean that the other is not run as the
superuser. To find the real answer, we'd have to boot up a stock Ubuntu
to the maybe-ubiquity screen, press Ctrl-Alt-F1 to go to a console, log
in, and then use `ps` to find out who owns the `ubiquity` process.
However, furthermore it would be a good experiment to find out if the
Wayland / X11 difference is the culprit. I wonder if any accessibility
information is communicated over the X protocol, or if it's all done via
D-Bus?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231091
Title:
Screenreader starts, but does not work with installer (ubiquity) in
live session
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1231091/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904362] Re: [Wishlist] Disable hostname lookup by default for logwatch service sshd
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/405065 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/405066 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/405067 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904362 Title: [Wishlist] Disable hostname lookup by default for logwatch service sshd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1904362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930541] Re: Maven 3.6.3-1 fails to run with OpenJDK 16
Is there any assistance I can provide to move this forward? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930541 Title: Maven 3.6.3-1 fails to run with OpenJDK 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maven/+bug/1930541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934402] Re: get_species_taxids does not print all information when invoked with -n
Attached proposed patch. Should probably send to upstream. ** Patch added: "Debdiff patch" https://bugs.launchpad.net/ubuntu/+source/ncbi-blast+/+bug/1934402/+attachment/5508518/+files/ncbi-blast+_2.9.0-2ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934402 Title: get_species_taxids does not print all information when invoked with -n To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncbi-blast+/+bug/1934402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934400] Re: Audio signal interference when using in conjunction with firefox
Roberto, based on your description, the problem does not seem specific to gstreamer (VLC does not use gstreamer). So I am changing the package to pulseaudio for now to help gather information. Please run the following command from the affected machine to automatically gather audio information: apport-collect 1934400 ** Package changed: gstreamer1.0 (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (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/1934400 Title: Audio signal interference when using in conjunction with firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925010] Re: shim-signed 15.4 does not boot on EFI 1.10 systems
Hi - I believe I'm experiencing this issue on my Thinkpad X1 Extreme (Gen1). I set up a dual-boot, Ubuntu (Groovy) and Win11 beta. I'd be able to select my OS in a Grub2 menu, after the Lenovo splash screen on start up. When I was navigating Ubuntu today, I was notified of the available upgrade to 21.04 and went through the steps to upgrade. At the end of the steps, I needed to reboot my machine: 1) Lenovo splash screen 2) Grub2 menu 3) Select Ubuntu 4) Screen goes black and is unresponsive 5) Hold power to shutdown/restart After noticing the issue with booting into Ubuntu, I tried to boot into Windows and experienced the same issue - black, unresponsive screen. I tried several times to boot Ubuntu in recovery mode via advanced options and no dice. This is a really crummy issue that's rendered my laptop unusable. -D. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925010 Title: shim-signed 15.4 does not boot on EFI 1.10 systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
This bug was fixed in the package apt - 1.6.14 --- apt (1.6.14) bionic; urgency=medium * RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026) * Fix downloads of unsized files that are largest in pipeline (LP: #1921626), and warn about packages without size (option Acquire::AllowUnsizedPackages) * JSON hooks 0.2 and assorted JSON bugfixes (LP: #1926150) - encoder fixes: + json: Escape strings using \u escape sequences, add test + json: Actually pop states + json: Encode NULL strings as null - json: Flush standard file descriptors before calling hooks (this avoids output from hooks in middle of apt output) - Minor fixes to include and C++ namespaces - non-code changes: + test/json: Make the test hook more reliable + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) - semantic changes (new fields, hooks, and protocol 0.2): + json: Add origins fields to version + upgrade: Add JSON hook support (AptCli::Hooks::Upgrade) + json: Add `package-list` and `statistics` install hooks + json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes) + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) * Avoid infinite loop on EOF on media change prompt (LP: #1928687) -- Julian Andres Klode Tue, 15 Jun 2021 16:12:38 +0200 ** Changed in: apt (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/1898026 Title: interruption of dist-upgrade can leave you next release in sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921626] Re: size mismatch error if request of unknown size is larger than others
This bug was fixed in the package apt - 1.6.14 --- apt (1.6.14) bionic; urgency=medium * RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026) * Fix downloads of unsized files that are largest in pipeline (LP: #1921626), and warn about packages without size (option Acquire::AllowUnsizedPackages) * JSON hooks 0.2 and assorted JSON bugfixes (LP: #1926150) - encoder fixes: + json: Escape strings using \u escape sequences, add test + json: Actually pop states + json: Encode NULL strings as null - json: Flush standard file descriptors before calling hooks (this avoids output from hooks in middle of apt output) - Minor fixes to include and C++ namespaces - non-code changes: + test/json: Make the test hook more reliable + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) - semantic changes (new fields, hooks, and protocol 0.2): + json: Add origins fields to version + upgrade: Add JSON hook support (AptCli::Hooks::Upgrade) + json: Add `package-list` and `statistics` install hooks + json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes) + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) * Avoid infinite loop on EOF on media change prompt (LP: #1928687) -- Julian Andres Klode Tue, 15 Jun 2021 16:12:38 +0200 ** Changed in: apt (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/1921626 Title: size mismatch error if request of unknown size is larger than others To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1921626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926150] Re: [SRU] Backport JSON hooks 0.2
This bug was fixed in the package apt - 1.6.14 --- apt (1.6.14) bionic; urgency=medium * RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026) * Fix downloads of unsized files that are largest in pipeline (LP: #1921626), and warn about packages without size (option Acquire::AllowUnsizedPackages) * JSON hooks 0.2 and assorted JSON bugfixes (LP: #1926150) - encoder fixes: + json: Escape strings using \u escape sequences, add test + json: Actually pop states + json: Encode NULL strings as null - json: Flush standard file descriptors before calling hooks (this avoids output from hooks in middle of apt output) - Minor fixes to include and C++ namespaces - non-code changes: + test/json: Make the test hook more reliable + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) - semantic changes (new fields, hooks, and protocol 0.2): + json: Add origins fields to version + upgrade: Add JSON hook support (AptCli::Hooks::Upgrade) + json: Add `package-list` and `statistics` install hooks + json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes) + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) * Avoid infinite loop on EOF on media change prompt (LP: #1928687) -- Julian Andres Klode Tue, 15 Jun 2021 16:12:38 +0200 ** Changed in: apt (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/1926150 Title: [SRU] Backport JSON hooks 0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928687] Re: Avoid infinite loop on EOF on media change prompt
This bug was fixed in the package apt - 1.6.14 --- apt (1.6.14) bionic; urgency=medium * RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026) * Fix downloads of unsized files that are largest in pipeline (LP: #1921626), and warn about packages without size (option Acquire::AllowUnsizedPackages) * JSON hooks 0.2 and assorted JSON bugfixes (LP: #1926150) - encoder fixes: + json: Escape strings using \u escape sequences, add test + json: Actually pop states + json: Encode NULL strings as null - json: Flush standard file descriptors before calling hooks (this avoids output from hooks in middle of apt output) - Minor fixes to include and C++ namespaces - non-code changes: + test/json: Make the test hook more reliable + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) - semantic changes (new fields, hooks, and protocol 0.2): + json: Add origins fields to version + upgrade: Add JSON hook support (AptCli::Hooks::Upgrade) + json: Add `package-list` and `statistics` install hooks + json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes) + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) * Avoid infinite loop on EOF on media change prompt (LP: #1928687) -- Julian Andres Klode Tue, 15 Jun 2021 16:12:38 +0200 ** Changed in: apt (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/1928687 Title: Avoid infinite loop on EOF on media change prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1928687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934192] Re: regression between 2.04-1ubuntu44 and 2.04-1ubuntu44.2 breaks netboot on arm64
Rebuilding in focal, but with hirsute's binutils makes the issue go away. Now to dig into binutils changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934192 Title: regression between 2.04-1ubuntu44 and 2.04-1ubuntu44.2 breaks netboot on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1934192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
This bug was fixed in the package apt - 2.0.6 --- apt (2.0.6) focal; urgency=medium * RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026) * test suite fix: Check for and discard expected warning from MaybeAddAuth * Fix downloads of unsized files that are largest in pipeline (LP: #1921626), and warn about packages without size (option Acquire::AllowUnsizedPackages) * JSON hooks 0.2 and assorted JSON bugfixes (LP: #1926150) - encoder fixes: + json: Escape strings using \u escape sequences, add test + json: Actually pop states + json: Encode NULL strings as null - json: Flush standard file descriptors before calling hooks (this avoids output from hooks in middle of apt output) - non-code changes: + test/json: Make the test hook more reliable + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) - semantic changes (new fields, hooks, and protocol 0.2): + json: Add origins fields to version + upgrade: Add JSON hook support (AptCli::Hooks::Upgrade) + json: Add `package-list` and `statistics` install hooks + json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes) + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) * Avoid infinite loop on EOF on media change prompt (LP: #1928687) -- Julian Andres Klode Tue, 15 Jun 2021 13:05:46 +0200 ** Changed in: apt (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/1898026 Title: interruption of dist-upgrade can leave you next release in sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921626] Re: size mismatch error if request of unknown size is larger than others
This bug was fixed in the package apt - 2.0.6 --- apt (2.0.6) focal; urgency=medium * RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026) * test suite fix: Check for and discard expected warning from MaybeAddAuth * Fix downloads of unsized files that are largest in pipeline (LP: #1921626), and warn about packages without size (option Acquire::AllowUnsizedPackages) * JSON hooks 0.2 and assorted JSON bugfixes (LP: #1926150) - encoder fixes: + json: Escape strings using \u escape sequences, add test + json: Actually pop states + json: Encode NULL strings as null - json: Flush standard file descriptors before calling hooks (this avoids output from hooks in middle of apt output) - non-code changes: + test/json: Make the test hook more reliable + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) - semantic changes (new fields, hooks, and protocol 0.2): + json: Add origins fields to version + upgrade: Add JSON hook support (AptCli::Hooks::Upgrade) + json: Add `package-list` and `statistics` install hooks + json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes) + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) * Avoid infinite loop on EOF on media change prompt (LP: #1928687) -- Julian Andres Klode Tue, 15 Jun 2021 13:05:46 +0200 ** Changed in: apt (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/1921626 Title: size mismatch error if request of unknown size is larger than others To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1921626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921626] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921626 Title: size mismatch error if request of unknown size is larger than others To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1921626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926150] Re: [SRU] Backport JSON hooks 0.2
This bug was fixed in the package apt - 2.0.6 --- apt (2.0.6) focal; urgency=medium * RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026) * test suite fix: Check for and discard expected warning from MaybeAddAuth * Fix downloads of unsized files that are largest in pipeline (LP: #1921626), and warn about packages without size (option Acquire::AllowUnsizedPackages) * JSON hooks 0.2 and assorted JSON bugfixes (LP: #1926150) - encoder fixes: + json: Escape strings using \u escape sequences, add test + json: Actually pop states + json: Encode NULL strings as null - json: Flush standard file descriptors before calling hooks (this avoids output from hooks in middle of apt output) - non-code changes: + test/json: Make the test hook more reliable + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) - semantic changes (new fields, hooks, and protocol 0.2): + json: Add origins fields to version + upgrade: Add JSON hook support (AptCli::Hooks::Upgrade) + json: Add `package-list` and `statistics` install hooks + json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes) + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) * Avoid infinite loop on EOF on media change prompt (LP: #1928687) -- Julian Andres Klode Tue, 15 Jun 2021 13:05:46 +0200 ** Changed in: apt (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/1926150 Title: [SRU] Backport JSON hooks 0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928687] Re: Avoid infinite loop on EOF on media change prompt
This bug was fixed in the package apt - 2.0.6 --- apt (2.0.6) focal; urgency=medium * RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026) * test suite fix: Check for and discard expected warning from MaybeAddAuth * Fix downloads of unsized files that are largest in pipeline (LP: #1921626), and warn about packages without size (option Acquire::AllowUnsizedPackages) * JSON hooks 0.2 and assorted JSON bugfixes (LP: #1926150) - encoder fixes: + json: Escape strings using \u escape sequences, add test + json: Actually pop states + json: Encode NULL strings as null - json: Flush standard file descriptors before calling hooks (this avoids output from hooks in middle of apt output) - non-code changes: + test/json: Make the test hook more reliable + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) - semantic changes (new fields, hooks, and protocol 0.2): + json: Add origins fields to version + upgrade: Add JSON hook support (AptCli::Hooks::Upgrade) + json: Add `package-list` and `statistics` install hooks + json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes) + Fix a typo in json-hooks-protocol.md (thanks to Brian Murray) * Avoid infinite loop on EOF on media change prompt (LP: #1928687) -- Julian Andres Klode Tue, 15 Jun 2021 13:05:46 +0200 ** Changed in: apt (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/1928687 Title: Avoid infinite loop on EOF on media change prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1928687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928687] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928687 Title: Avoid infinite loop on EOF on media change prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1928687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930279] Re: [Ivy Bridge] flashing triangles on screen
** Summary changed: - [Ivy Bridge] flashing triangles on screen + [Ivy Bridge] flashing sliced triangles on screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930279 Title: [Ivy Bridge] flashing sliced triangles on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904362] Re: [Wishlist] Disable hostname lookup by default for logwatch service sshd
** Also affects: logwatch (Ubuntu Impish) Importance: Wishlist Status: 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/1904362 Title: [Wishlist] Disable hostname lookup by default for logwatch service sshd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1904362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.11/5.11.0.1011.11~20.04.10)
All autopkgtests for the newly accepted linux-meta-azure-5.11 (5.11.0.1011.11~20.04.10) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.31-0ubuntu9.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure-5.11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions 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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876379] Re: Screen is broken into triangles
*** This bug is a duplicate of bug 1875712 *** https://bugs.launchpad.net/bugs/1875712 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (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/1876379 Title: Screen is broken into triangles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932303] Re: Dell XPS 17 9700 sound not working on linux-oem-5.10
** Summary changed: - Dell XPS 17 9700 wifi + Dell XPS 17 9700 sound not working on linux-oem-5.10 ** Summary changed: - Dell XPS 17 9700 sound not working on linux-oem-5.10 + Dell XPS 17 9700 microphone not working on linux-oem-5.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932303 Title: Dell XPS 17 9700 microphone not working on linux-oem-5.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1932303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.8/5.8.0.61.68~20.04.44)
All autopkgtests for the newly accepted linux-meta-hwe-5.8 (5.8.0.61.68~20.04.44) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.7 (armhf) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, armhf, arm64, ppc64el) linux-hwe-5.8/5.8.0-61.68~20.04.1 (s390x, amd64, arm64, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.8 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions 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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Sorry Alex... could you please explain what you mean by #9? Sorry for the newbie question, but I want to help, and I am not sure what you would like me to do. On Wed, Jun 30, 2021 at 11:10 PM Alex Tu <1932...@bugs.launchpad.net> wrote: > Hi Steve, > > is the firmware from #9 fixed the issue? > So far, we don't sure if the firmware crashing the root cause of your > issue, so KC separated it to LP: #1933755. And firmware from #9 helps LP: > #1933755 (see LP: #1933755 comment #2) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1932548 > > Title: > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on > wireless [8086:a0f0] > > Status in OEM Priority Project: > Confirmed > Status in linux-oem-5.10 package in Ubuntu: > New > > Bug description: > Whenever I am using a wireless connection, the image freezes roughly > every two minutes. Sometimes, email cannot be retrieved / computer > complains the connection was momentarily lost. > > - If I am on a wire, this problem does NOT occur. > - This problems occurs on wireless independent of the platform used > (behavior seen in both Google Hangout and Zoom) > - This problem does NOT occur on Windows. I did a meeting where both my > Linux and Windows machines were connected to the same meeting and using the > same wifi router, and while the performance on Windows was flawless, > unfortunately it was not so on the Ubuntu box. So I don't think my wifi > router or network is to blame. > - As far as I can recall, the problem used not to be there 2 weeks ago. > So it may have been introduced by a recent update. > - As communicated before, I am on a certified machine from Dell, > recently purchased with Ubuntu already on board from factory (I assume the > logs there were sent to you would contain the information). > - I tried to generate a log on the wireless, but the process did not let > me do this very easily. I am more than happy to send you additional > information - but please let me know which package you want me to spy upon > exactly, as I am not sure what would be helpful in this matter. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 > Uname: Linux 5.10.0-1029-oem x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 18 09:47:58 2021 > DistUpgraded: Fresh install > 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 > DistroCodename: focal > DistroVariant: ubuntu > EcryptfsInUse: Yes > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA > controller]) > Subsystem: Dell Device [1028:0991] > InstallationDate: Installed on 2021-04-24 (54 days ago) > InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary > 20200502-05:58 > MachineType: Dell Inc. XPS 13 9310 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem > root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/25/2021 > dmi.bios.release: 2.1 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 2.1.1 > dmi.board.name: 08607K > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: XPS > dmi.product.name: XPS 13 9310 > dmi.product.sku: 0991 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1932548/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.
Re: [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Kai-Chuan: Let me do this after I just reproduced the bug. The last two days I kept my computer connected through Ethernet because the freeze really impedes my ability to understand my counterparts. Best Regards, Steve On Wed, Jun 30, 2021 at 7:55 PM Kai-Chuan Hsieh <1932...@bugs.launchpad.net> wrote: > Hello Steve, > > Can you attach your kernel log? upload output of "$ journalctl -k". > > Thanks, > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1932548 > > Title: > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on > wireless [8086:a0f0] > > Status in OEM Priority Project: > Confirmed > Status in linux-oem-5.10 package in Ubuntu: > New > > Bug description: > Whenever I am using a wireless connection, the image freezes roughly > every two minutes. Sometimes, email cannot be retrieved / computer > complains the connection was momentarily lost. > > - If I am on a wire, this problem does NOT occur. > - This problems occurs on wireless independent of the platform used > (behavior seen in both Google Hangout and Zoom) > - This problem does NOT occur on Windows. I did a meeting where both my > Linux and Windows machines were connected to the same meeting and using the > same wifi router, and while the performance on Windows was flawless, > unfortunately it was not so on the Ubuntu box. So I don't think my wifi > router or network is to blame. > - As far as I can recall, the problem used not to be there 2 weeks ago. > So it may have been introduced by a recent update. > - As communicated before, I am on a certified machine from Dell, > recently purchased with Ubuntu already on board from factory (I assume the > logs there were sent to you would contain the information). > - I tried to generate a log on the wireless, but the process did not let > me do this very easily. I am more than happy to send you additional > information - but please let me know which package you want me to spy upon > exactly, as I am not sure what would be helpful in this matter. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 > Uname: Linux 5.10.0-1029-oem x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 18 09:47:58 2021 > DistUpgraded: Fresh install > 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 > DistroCodename: focal > DistroVariant: ubuntu > EcryptfsInUse: Yes > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA > controller]) > Subsystem: Dell Device [1028:0991] > InstallationDate: Installed on 2021-04-24 (54 days ago) > InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary > 20200502-05:58 > MachineType: Dell Inc. XPS 13 9310 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem > root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/25/2021 > dmi.bios.release: 2.1 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 2.1.1 > dmi.board.name: 08607K > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: XPS > dmi.product.name: XPS 13 9310 > dmi.product.sku: 0991 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1932548/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly
[Bug 1933646] Re: Port removed gsettings-desktop-schemas into gesttings-ubuntu-schemas [Impish]
** Branch linked: lp:~khurshid-alam/gsettings-ubuntu-touch-schemas/gds- to-gus-impish ** Branch unlinked: lp:~khurshid-alam/unity-settings-daemon/gds-to-usd- impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933646 Title: Port removed gsettings-desktop-schemas into gesttings-ubuntu-schemas [Impish] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1933646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876157] Re: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020
Addendum to comment #21: sudo apt list --installed | grep memtest WARNING: apt does not have a stable CLI interface. Use with caution in scripts. memtest86+/hirsute,now 5.01-3.1ubuntu4 amd64 [installed] memtester/hirsute,now 4.5.0-1 amd64 [installed] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876157 Title: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** 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/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934402] Re: get_species_taxids does not print all information when invoked with -n
The attachment "script from 2.12.0" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934402 Title: get_species_taxids does not print all information when invoked with -n To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncbi-blast+/+bug/1934402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out
Yes, it is still an issue in focal. Was there an update since last year that should have addressed this? ** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871726 Title: "systemd --user" and child processes fail to exit when user logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924604] Re: do-release-upgrade crashed with KeyError in __getitem__(): "The cache has no package named 'python-is-python2'"
The same changes to the python is python2 quirk exist in the Impish
version of ubuntu-release-upgrader although the quirk has been disabled
as it is unnecessary.
https://launchpadlibrarian.net/546274717/ubuntu-release-
upgrader_1%3A21.10.3_1%3A21.10.4.diff.gz
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Fix Released
** Description changed:
[Impact]
Users with universe not enabled and python2 packages installed are unable to
upgrade from Ubuntu 18.04 to Ubuntu 20.04.
- [Test Case]
+ [Test Plan]
---
On an Ubuntu 18.04 system with universe and multiverse disabled
1) apt-get install duplicity (it depends on python2.7)
2) run do-release-upgrade
Observe the upgrader hang at Calculating the changes (in text mode) kill
it and observe a Traceback in /var/log/dist-upgrade/main.log.
...
- File "/usr/lib/python3/dist-packages/apt/cache.py", line 303, in __getitem__
- raise KeyError('The cache has no package named %r' % key)
+ File "/usr/lib/python3/dist-packages/apt/cache.py", line 303, in __getitem__
+ raise KeyError('The cache has no package named %r' % key)
KeyError: "The cache has no package named 'python-is-python2'"
With the version of the release-upgrader from -proposed (do-release-
upgrade -p) you'll instead receive a message regarding universe not
being enabled and the need to either remove python2 packages or enable
universe.
[Original Description]
This is because python-minimal was installed and universe was not enabled on
the system being upgraded.
Error Tracker buckets:
https://errors.ubuntu.com/problem/f92900f3c057db7600d88857e7c05434b69d2496
https://errors.ubuntu.com/problem/23e6edb38993cb74331d30beeadccdfffe1d557a
ProblemType: CrashDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.31
ProcVersionSignature: Ubuntu 5.4.0-71.79~18.04.1-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
Date: Thu Apr 15 10:59:53 2021
ExecutablePath: /usr/bin/do-release-upgrade
ExecutableTimestamp: 1606763386
InstallationDate: Installed on 2021-04-13 (1 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
(20200806.1)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 -s ./focal --frontend DistUpgradeViewText
ProcCwd: /tmp/ubuntu-release-upgrader-e397n4sn
ProcEnviron:
TERM=screen
SHELL=/bin/bash
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
PATH=(custom, no user)
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal,
3.6.7-1~18.04
PythonArgs: ['/usr/bin/do-release-upgrade', '--frontend',
'DistUpgradeViewText']
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal,
2.7.15~rc1-1SourcePackage: ubuntu-release-upgrader
Title: do-release-upgrade crashed with KeyError in __getitem__(): "The cache
has no package named 'python-is-python2'"
UpgradeStatus: Upgraded to bionic on 2021-04-15 (0 days ago)
** Description changed:
[Impact]
Users with universe not enabled and python2 packages installed are unable to
upgrade from Ubuntu 18.04 to Ubuntu 20.04.
[Test Plan]
---
On an Ubuntu 18.04 system with universe and multiverse disabled
1) apt-get install duplicity (it depends on python2.7)
2) run do-release-upgrade
Observe the upgrader hang at Calculating the changes (in text mode) kill
it and observe a Traceback in /var/log/dist-upgrade/main.log.
...
File "/usr/lib/python3/dist-packages/apt/cache.py", line 303, in __getitem__
raise KeyError('The cache has no package named %r' % key)
KeyError: "The cache has no package named 'python-is-python2'"
With the version of the release-upgrader from -proposed (do-release-
upgrade -p) you'll instead receive a message regarding universe not
being enabled and the need to either remove python2 packages or enable
universe.
+
+ [Where problems could occur]
+ The switch to using the finally clause in DistUpgradeCache.py is a
significant (albeit safe) change but it is necessary for the error message to
actually be displayed. So it'd make sense to run through a whole release
upgrade to ensure that the gui behaves normally.
[Original Description]
This is because python-minimal was installed and universe was not enabled on
the system being upgraded.
Error Tracker buckets:
https://errors.ubuntu.com/problem/f92900f3c057db7600d88857e7c05434b69d2496
https://errors.ubuntu.com/problem/23e6edb38993cb74331d30beeadccdfffe1d557a
ProblemType: CrashDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.31
ProcVersionSignature: Ubuntu 5.4.0-71.79~18.04.1-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
Date: Thu Apr 15 10:59:53 2021
ExecutablePath: /usr/bin/do-release-upgrade
[Bug 1934402] [NEW] get_species_taxids does not print all information when invoked with -n
Public bug reported: On ubuntu 20.04.2, ncbi-blast+ 2.9.0-2 It appears that the parsing logic in the script was broken by the ncbi entrez api at some point. When running this script with -n [species], it returns the number of results and no more. Running the script included with the latest version, 2.12.0, functions correctly with its modified parsing. Best way to resolve this is likely to just put the 2.12.0 script in the package. Attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ncbi-blast+ 2.9.0-2 ProcVersionSignature: Ubuntu 5.8.0-1036.38~20.04.1-azure 5.8.18 Uname: Linux 5.8.0-1036-azure x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 1 20:15:40 2021 InstallationDate: Installed on 2021-06-29 (1 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: ncbi-blast+ UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ncbi-blast+ (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal patch uec-images ** Patch added: "script from 2.12.0" https://bugs.launchpad.net/bugs/1934402/+attachment/5508502/+files/get_species_taxids.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934402 Title: get_species_taxids does not print all information when invoked with -n To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncbi-blast+/+bug/1934402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable
I was using linux-image-5.8.0-55-generic:amd64 - this kernel still has the issues. Reverting to 5.8.0-48 removes the issues. Changing to the 5.4 kernel (latest) also removes the issues -- 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 kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics 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 1876157] Re: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020
Memtest86 5.01 hangs at 60% of first test on Ubuntu 21.04. The machine is Athlon II 640 on AMIBIOS 6.11 motherboard. I have seen another case just like this (hangs at 60%) on AskUbuntu. It worked fine when two 2 Gig DDR3 1333 MHZ SRAM sticks in place and failed when two more identical sticks (same vendor, same part number) were installed. I used 'memtester 6650M' (just leaves enough for OS) for 5 cycles with no errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876157 Title: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934401] [NEW] Control netfilter flow table timeouts via sysctl
Public bug reported: * Explain the bug(s) TCP and UDP connections may be offloaded from nf conntrack to nf flow table. Offloaded connections are aged after 30 seconds of inactivity. Once aged, ownership is returned to conntrack with a hard coded tcp/udp pickup time of 120/30 seconds, after which the connection may be deleted. The current hard-coded pickup intervals may introduce a very aggressive aging policy. For example, offloaded tcp connections in established state will timeout from nf conntrack after just 150 seconds of inactivity, instead of 5 days. In addition, the hard-coded 30 second offload timeout period can significantly increase the hardware insertion rate requirements in some use cases. * Brief explanation of fixes This patchset provides the user with the ability to configure protocol specific offload timeout and pickup intervals via sysctl. The first and second patches revert the existing non-upstream solution. The next two patches introduce the sysctl configuration for tcp and udp protocols. The last patch modifies nf flow table aging mechanisms to use the configured time intervals. * How to test Control tcp/udp connection timeout using the following sysctl parameters: net.netfilter.nf_flowtable_tcp_pickup = 120 net.netfilter.nf_flowtable_tcp_timeout = 30 net.netfilter.nf_flowtable_udp_pickup = 30 net.netfilter.nf_flowtable_udp_timeout = 30 * What it could break. Existing configuration scripts – not kernel related ** Affects: linux-bluefield (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/1934401 Title: Control netfilter flow table timeouts via sysctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924605] Re: Grub2 menu not loading - could not create MokListXRT: Out of Resources
It worked for me to. I am on Ubuntu 21.04 and got the same messages: "Failed to set MokListXRT: Out of resources Could not create MokListXRT: Out of resources" Updated shim-signed from hirsute-proposed and the system boots with no messages. Thanks for the fix! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924605 Title: Grub2 menu not loading - could not create MokListXRT: Out of Resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1924605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] Re: Kernel panic booting on Unmatched with kernel 5.8
** Changed in: linux-riscv-5.8 (Ubuntu) Milestone: ubuntu-20.04.3 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934400] [NEW] Audio signal interference when using in conjunction with firefox
Public bug reported: When using the program to listen to music and open firefox, in some cases this action generates a strong and persistent hiss. The problem also occurs with vlc player too, just close the browser to stop the noise. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgstreamer1.0-0 1.16.2-2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 17:04:56 2021 InstallationDate: Installed on 2021-01-12 (169 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1934400 Title: Audio signal interference when using in conjunction with firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1934400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.11.0.1013.11)
All autopkgtests for the newly accepted linux-meta-raspi (5.11.0.1013.11) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: wireguard-linux-compat/unknown (arm64) systemd/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions 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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1010.10)
All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1010.10) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.5-1ubuntu1 (amd64) rtl8821ce/5.5.2.1-0ubuntu6 (amd64) oss4/4.2-build2010-5ubuntu8 (amd64) virtualbox/6.1.22-dfsg-2~ubuntu1.21.04.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) systemd/247.3-3ubuntu3.1 (amd64) backport-iwlwifi-dkms/8613-0ubuntu2 (amd64) lttng-modules/2.12.2-1ubuntu3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions 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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
> Other than the obvious approach of enabling systemd-userdb for Ubuntu, I don't see how that would help, given that sytemd-userdb.service has RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 You basically have the same issue as with systemd-logind.service. Or am I missing something here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
** Attachment added: "Screenshot from 2021-07-01 22-55-12.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+attachment/5508496/+files/Screenshot%20from%202021-07-01%2022-55-12.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
$ uname -a Linux ter 5.11.0-22-generic #23-Ubuntu SMP Thu Jun 17 00:34:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I have updated ubuntu. This did not help the problem remained. Also there is no brightness editing. ** Attachment added: "Screenshot from 2021-07-01 22-46-30.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+attachment/5508495/+files/Screenshot%20from%202021-07-01%2022-46-30.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
1) Include drop-in conf files for systemd-logind and systemd-udevd to remove the networking sandbox Those drop-in configs should be shipped in the nis package. I don't see a reason to ship a drop-in for systemd-udevd, fwiw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934155] Re: fetchmail can no longer connect to underwood & gives false error msg (TLS issues)
I appreciate the quick response, but I have to say both of you overlooked some of the data I presented, so I will elaborate. I was able to workaround the bug, but there are still bugs here. Having read the man page more times, I continue to find more anomalies than answers, which I will elaborate here. To be clear, fetchmail changed, not my config. This config works on fetchmail 6.3.26 but fails on 6.4.16: ``` skip underwood-onion via 127.0.0.1 protocol imap port 12345 username "billyikes" fetchall ``` Nothing in your response suggests that I should expect this config to be treated differently from the two different versions of fetchmail. But it is. Verbose output shows that version 6.4.16 sends a "STARTTLS" even though the config does not call for SSL/TLS in any way. That's a bug. The man page says "sslproto auto" is a default which superficially seems reasonable until you notice that "auto" actually imposes TLS. This is a distortion of what users expect by the meaning of "automatic". My first attempt at a fix for underwood was to add these lines (which fixed some of my stanzas for other servers): ~~~ sslproto 'SSL3+' no sslcertck ~~~ Intution suggests this means: "If the server demands SSL, then be permissive and allow SSL3 or newer, but don't bother checking whether the cert is good or not, just use it if the server insists". But what we find is that the behavior is not intuitive w.r.t the options. And because it fails the rule of least astonishment, I'm calling it a bug. Moreover, the new manpage states: "This option has a dual use, out of historic fetchmail behaviour. It controls both the SSL/TLS protocol version and, if --ssl is not specified, the STARTTLS behaviour (upgrading the protocol to an SSL or TLS connection in-band). Some other options may however make TLS mandatory." To say sslproto "controls STARTTLS behaviour" without fully specifying how that behavior is controlled is a recipe for confusion. An empty argument is said to disable STARTTLS, but that was always the case. So there are two problems here. The first problem is that STARTTLS is technical under-the-hood jargon that end users probably should not be responsible for understanding. Users are basically told whether SSL/TLS is used, not what low-level commands are being passed to make that happen. The second problem is that auto states "require TLS", but does not mention the low-level "STARTTLS" that the section mentioned earlier. To developers, perhaps it is clear that "TLS" and "STARTTLS" are one in the same, but it's not clear to users who don't know the underlying details expressed in RFC specs. IOW, STARTTLS is mentioned just enough to confuse, and not enough to be understandable. Apart from the misleading & non-intuitive wording, some things are plainly false. E.g. this statement from the man page is simply not true: "Only if this option [sslproto] and --ssl are both missing for a poll, there will be opportunistic TLS for POP3 and IMAP, where fetchmail will attempt to upgrade to TLSv1 or newer." If that were a true statement, then the first stanza at the top of this post would work. This is a contradiction in the man page. That is, "sslproto auto" ironically states that TLS is mandated while simultaneously saying "auto" is also a default, and yet this behavior is not opportunistic. Opportunistic means: accommodate (or even proactively request) higher levels of security, but ultimately settle for no security at all if availability demands it. The "sslproto ''" empty string option is bizarre because it strictly disables STARTTLS without stating whether SSL is also disabled, apart from saying that it's incompatible with --ssl. To expressly /force/ no encryption can be useful but only in limited & obscure test situations. It's still good that it exists, but what about the much more common case of users who need opportunistic connections? The empty string denies the opportunity for crypto while all the other sslproto options deny the possibility of no encryption. Even more strange is "SSL23". How often does someone want to insist on SSL2 or SSL3, but not the higher options? There should be a "sslproto SSL2+". And most importantly there should be a "sslproto none+" to truly deliver opportunistic sessions. Regarding this suggestion: ``` poll underwood2hj3pwd.onion via 127.0.0.1 plugin "socat STDIO SOCKS4A:127.0.0.1:%h:%p,socksport=9050" ``` which I expanded to: ``` skip underwood2hj3pwd.onion via 127.0.0.1 plugin "socat STDIO SOCKS4A:127.0.0.1:%h:%p,socksport=9050" protocol imap port 143 username "billyikes" fetchall ``` result was: ``` fetchmail: running socat STDIO SOCKS4A:127.0.0.1:%h:%p,socksport=9050 (host 127.0.0.1 service 143) 2021/07/01 16:25:44 socat[2202] E socks: connect request rejected or failed fetchmail: socket error while fetching from
[Bug 1932331] Re: ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish
** Changed in: apparmor 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/1932331 Title: ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1932331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934398] Re: Prevent spurious wakeups on amd s2idle
The patch is queued upstream for 5.14-rc1: https://lore.kernel.org /linux- acpi/CAJZ5v0jhYL6Qrj5vvU=5FguF=mvryfrbbtgvc8chzckkxm_...@mail.gmail.com/T/#mb0e0b54da3256cfb04cee38e45322a086d523652 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934398 Title: Prevent spurious wakeups on amd s2idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1934398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934398] [NEW] Prevent spurious wakeups on amd s2idle
Public bug reported: [Impact] Several AMD based OEM designs have spurious wakeups occurring from EC events during s2idle. This leads to non-functional wakeup sources or higher power consumption. [Fix] Prevent setting the GPE for the EC for wakeup source on AMD systems. [Test] Verify s2idle on OEM system. [Where problems could occur] Code is guarded to only run on AMD systems, which are just now getting s2idle support in oem kernel. ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: Kai-Heng Feng (kaihengfeng) Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Assignee: Kai-Heng Feng (kaihengfeng) Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934398 Title: Prevent spurious wakeups on amd s2idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1934398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924604] Re: do-release-upgrade crashed with KeyError in __getitem__(): "The cache has no package named 'python-is-python2'"
** Description changed:
- This is because python-minimal was installed and universe was not
- enabled on the system being upgraded.
+ [Impact]
+ Users with universe not enabled and python2 packages installed are unable to
upgrade from Ubuntu 18.04 to Ubuntu 20.04.
+
+ [Test Case]
+ ---
+ On an Ubuntu 18.04 system with universe and multiverse disabled
+ 1) apt-get install duplicity (it depends on python2.7)
+ 2) run do-release-upgrade
+
+ Observe the upgrader hang at Calculating the changes (in text mode) kill
+ it and observe a Traceback in /var/log/dist-upgrade/main.log.
+
+ ...
+ File "/usr/lib/python3/dist-packages/apt/cache.py", line 303, in __getitem__
+ raise KeyError('The cache has no package named %r' % key)
+ KeyError: "The cache has no package named 'python-is-python2'"
+
+ With the version of the release-upgrader from -proposed (do-release-
+ upgrade -p) you'll instead receive a message regarding universe not
+ being enabled and the need to either remove python2 packages or enable
+ universe.
+
+ [Original Description]
+ This is because python-minimal was installed and universe was not enabled on
the system being upgraded.
Error Tracker buckets:
https://errors.ubuntu.com/problem/f92900f3c057db7600d88857e7c05434b69d2496
https://errors.ubuntu.com/problem/23e6edb38993cb74331d30beeadccdfffe1d557a
ProblemType: CrashDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.31
ProcVersionSignature: Ubuntu 5.4.0-71.79~18.04.1-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
Date: Thu Apr 15 10:59:53 2021
ExecutablePath: /usr/bin/do-release-upgrade
ExecutableTimestamp: 1606763386
InstallationDate: Installed on 2021-04-13 (1 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
(20200806.1)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 -s ./focal --frontend DistUpgradeViewText
ProcCwd: /tmp/ubuntu-release-upgrader-e397n4sn
ProcEnviron:
TERM=screen
SHELL=/bin/bash
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
PATH=(custom, no user)
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal,
3.6.7-1~18.04
PythonArgs: ['/usr/bin/do-release-upgrade', '--frontend',
'DistUpgradeViewText']
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal,
2.7.15~rc1-1SourcePackage: ubuntu-release-upgrader
Title: do-release-upgrade crashed with KeyError in __getitem__(): "The cache
has no package named 'python-is-python2'"
UpgradeStatus: Upgraded to bionic on 2021-04-15 (0 days ago)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924604
Title:
do-release-upgrade crashed with KeyError in __getitem__(): "The cache
has no package named 'python-is-python2'"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924604/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508493/+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/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508494/+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/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508492/+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/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508491/+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/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] Re: Kernel panic booting on Unmatched with kernel 5.8
apport information ** Tags added: apport-collected ** Description changed: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909] macb 1009.ethernet: GEM doesn't support hardware ptp. [ 18.757942] status: 00020100 badaddr: 005f8141b42c cause: 000c [ 18.757998] ---[ end trace ecc2ef275d977b47 ]--- [ 18.765916] libphy: MACB_mii_bus: probed [ 18.772384] Kernel panic - not syncing: Fatal exception in interrupt [ 18.821245] SMP: stopping secondary CPUs
[Bug 1934387] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508490/+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/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.8.0.1032.34)
All autopkgtests for the newly accepted linux-meta-kvm (5.8.0.1032.34) for groovy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.10.2 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.10.2 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.20.10.2 (amd64) nvidia-graphics-drivers-418-server/418.197.02-0ubuntu0.20.10.1 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.10.1 (amd64) nvidia-graphics-drivers-390/390.143-0ubuntu0.20.10.1 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.10.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions 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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925827] Re: [v247] backport routing policy rule fix
I have this queued up for hirsute, with a test build here: https://launchpad.net/~ddstreet/+archive/ubuntu/systemd it seems to fix the issue for me, please let me know if it doesn't work for you, I plan to upload systemd either this week or early next week -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925827 Title: [v247] backport routing policy rule fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
Other than the obvious approach of enabling systemd-userdb for Ubuntu, which is a much larger discussion/decision, I think there are really only 2 ways to address this: 1) Include drop-in conf files for systemd-logind and systemd-udevd to remove the networking sandbox 2) add configuration documentation to nis and openldap instructing the system admin to create drop-in conf files for systemd-logind and systemd-udevd as part of system configuration Option #1 has the advantage of 'just working' without any local admin changing anything, but has the disadvantage of completely removing network sandboxing for logind/udevd. Option #2 has the advantage of keeping the sandboxing and allowing the admin to customize it more specifically, such as allowing networking only to specific nis/ldap servers instead of allowing all networking, but has the disadvantage of requiring the system admin to read the docs and actually perform the additional configuration. I'm skeptical of option #1 as the network sandboxing is a security feature, but also I'm pretty sure if we go with option #2 there will be plenty more bugs opened due to admins missing that part of the local system configuration. Any opinions or other ideas on approaches? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Here is a debdiff against the version in hirsute. It builds fine against 5.11.0-22-generic, and loads. Cascardo. ** Patch added: "debdiff against version in hirsute" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+attachment/5508488/+files/evdi_1.9.1-1ubuntu3~21.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928733] Re: Starting systemd Network Service fails with "Invalid argument"
ok it looks like this *might* be upstream bug 16156, which unfortunately was just very recently fixed, so backporting that to bionic may be difficult. I'll mark the bug and take a look but even if it is possible to backport the fix, it will likely take a while. ** Changed in: systemd (Ubuntu) Status: Incomplete => Triaged ** Bug watch added: github.com/systemd/systemd/issues #16156 https://github.com/systemd/systemd/issues/16156 ** Also affects: systemd via https://github.com/systemd/systemd/issues/16156 Importance: Unknown Status: Unknown ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: Triaged ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Groovy) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928733 Title: Starting systemd Network Service fails with "Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1928733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
