[Bug 2056111] Re: Bluetooth disabled with MODULES=dep on 24.04
Just to confirm this is still an issue on the final Noble release. Not a huge problem, MODULES=most is the default and works fine. It was nice to be able to have smaller files and thus more space in /boot when it worked with MODULES=dep previously though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056111 Title: Bluetooth disabled with MODULES=dep on 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056111] Re: Bluetooth disabled with MODULES=dep on 24.04
** Summary changed: - Bluetooth driver disappears from initramfs with MODULES=dep on 24.04 + Bluetooth disabled with MODULES=dep on 24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056111 Title: Bluetooth disabled with MODULES=dep on 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056111] Re: Bluetooth driver disappears from initramfs with MODULES=dep on 24.04
Interestingly, if I rebuild the initramfs with "MODULES=dep", I get the following firmware files in the initramfs under usr/lib/firmware/intel: usr/lib/firmware/intel/ibt-11-5.ddc.zst usr/lib/firmware/intel/ibt-11-5.sfi.zst usr/lib/firmware/intel/ibt-12-16.ddc.zst usr/lib/firmware/intel/ibt-12-16.sfi.zst And the following (currently loaded) btintel kernel module: usr/lib/modules/6.8.0-11-generic/kernel/drivers/bluetooth/btintel.ko.zst Note that my failure is for intel/ibt-19-0-4.sfi specifically though, not listed above. Building with "most", I get none of the above, these are the only files in the "intel" directory: usr/lib/firmware/intel/ice usr/lib/firmware/intel/ice/ddp usr/lib/firmware/intel/ice/ddp/ice-1.3.35.0.pkg.zst usr/lib/firmware/intel/ice/ddp/ice.pkg.zst There's also no match (via lsinitramfs) for "btintel" when I build using "most". However, bluetooth works fine using "most', and not with "dep", so I'm likely barking up the wrong tree here. Full diff between the two initramfs files here: https://paste.ubuntu.com/p/vMR5BGf9Hy/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056111 Title: Bluetooth driver disappears from initramfs with MODULES=dep on 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056111] [NEW] Bluetooth driver disappears from initramfs with MODULES=dep on 24.04
Public bug reported: Hi, I'm running the noble prerelease on x86, and have had MODULES=dep set in /etc/initramfs-tools/initramfs.conf for some time with no issues. Over the weekend, I noticed updates to linux-image-6.8.0-11-generic, linux-modules-6.8.0-11-generic etc, with an associated initramfs rebuild. After the next reboot, bluetooth was unavailable - via dmesg: 2024-03-04T13:32:47.584364+07:00 x1c9 kernel: Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-4.sfi (-2) 2024-03-04T13:32:47.584367+07:00 x1c9 kernel: Bluetooth: hci0: Reading supported features failed (-56) 2024-03-04T13:32:47.584367+07:00 x1c9 kernel: Bluetooth: hci0: Error reading debug features 2024-03-04T13:32:47.584368+07:00 x1c9 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. 2024-03-04T13:32:47.584368+07:00 x1c9 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-56) I'd set MODULES=dep via /etc/initramfs-tools/initramfs.conf many releases ago (this system was installed with 21.04 and has been upgraded to each of the six subsequent series in turn since), which had always worked until now. Reverting that to MODULES=most (which I believe is the default), rebuilding the initramfs and rebooting has restored Bluetooth functionality. I'm not entirely sure which package this should be filed against - I know the referenced intel/ibt-19-0-4.sfi file is actually part of linux- firmware, and initramfs-tools is presumably also involved, but I see no recent updates to either of those packages (last updated on my system in early February, and I've definitely rebooted since then with no issues), so I'm assuming this must be kernel-related, but I may be misunderstanding how this all fits together. ** 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/2056111 Title: Bluetooth driver disappears from initramfs with MODULES=dep on 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
Broadcom Emulex has verified the 14.0.0.4 lpfc Ubuntu 22.04 driver patchset in the package linux - 5.15.0-23.23 kernel. Thank you for your support Laurie Barry Software Program Manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session
Driver team has highlighted this patch is required to address this
issue:
author James Smart 2022-04-12 15:19:44 -0700
committer Martin K. Petersen 2022-04-18
22:48:43 -0400
commit e294647b1aed4247fe52851f3a3b2b19ae906228 (patch)
treefd7e11a3c6f680d5aabd468d523d08ffcd66b59f /drivers/scsi/lpfc
parent b83a8c21f3fe874e12eb2b6e6c5cfb220d35c446 (diff)
downloadscsi-e294647b1aed4247fe52851f3a3b2b19ae906228.tar.gz
scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg()
In an attempt to log message 0126 with LOG_TRACE_EVENT, the following hard
lockup call trace hangs the system.
Call Trace:
_raw_spin_lock_irqsave+0x32/0x40
lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc]
lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc]
lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc]
lpfc_els_flush_cmd+0x43c/0x670 [lpfc]
lpfc_els_flush_all_cmd+0x37/0x60 [lpfc]
lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc]
lpfc_do_work+0x1485/0x1d70 [lpfc]
kthread+0x112/0x130
ret_from_fork+0x1f/0x40
Kernel panic - not syncing: Hard LOCKUP
The same CPU tries to claim the phba->port_list_lock twice.
Move the cfg_log_verbose checks as part of the lpfc_printf_vlog() and
lpfc_printf_log() macros before calling lpfc_dmp_dbg(). There is no need
to take the phba->port_list_lock within lpfc_dmp_dbg().
Link: https://lore.kernel.org/r/2022041008.126521-3-jsmart2...@gmail.com
Co-developed-by: Justin Tee
Signed-off-by: Justin Tee
Signed-off-by: James Smart
Signed-off-by: Martin K. Petersen
Diffstat (limited to 'drivers/scsi/lpfc')
-rw-r--r-- drivers/scsi/lpfc/lpfc_init.c 29
-rw-r--r-- drivers/scsi/lpfc/lpfc_logmsg.h 6
2 files changed, 4 insertions, 31 deletions
diff --git a/drivers/scsi/lpfc/lpfc_init.c b/drivers/scsi/lpfc/lpfc_init.c
index 461d333b1b3a8..f9cd4b72d949a 100644
--- a/drivers/scsi/lpfc/lpfc_init.c
+++ b/drivers/scsi/lpfc/lpfc_init.c
@@ -15700,34 +15700,7 @@ void lpfc_dmp_dbg(struct lpfc_hba *phba)
unsigned int temp_idx;
int i;
int j = 0;
- unsigned long rem_nsec, iflags;
- bool log_verbose = false;
- struct lpfc_vport *port_iterator;
-
- /* Don't dump messages if we explicitly set log_verbose for the
-* physical port or any vport.
-*/
- if (phba->cfg_log_verbose)
- return;
-
- spin_lock_irqsave(>port_list_lock, iflags);
- list_for_each_entry(port_iterator, >port_list, listentry) {
- if (port_iterator->load_flag & FC_UNLOADING)
- continue;
- if (scsi_host_get(lpfc_shost_from_vport(port_iterator))) {
- if (port_iterator->cfg_log_verbose)
- log_verbose = true;
-
- scsi_host_put(lpfc_shost_from_vport(port_iterator));
-
- if (log_verbose) {
- spin_unlock_irqrestore(>port_list_lock,
- iflags);
- return;
- }
- }
- }
- spin_unlock_irqrestore(>port_list_lock, iflags);
+ unsigned long rem_nsec;
if (atomic_cmpxchg(>dbg_log_dmping, 0, 1) != 0)
return;
diff --git a/drivers/scsi/lpfc/lpfc_logmsg.h b/drivers/scsi/lpfc/lpfc_logmsg.h
index 7d480c7987942..a5aafe230c74f 100644
--- a/drivers/scsi/lpfc/lpfc_logmsg.h
+++ b/drivers/scsi/lpfc/lpfc_logmsg.h
@@ -73,7 +73,7 @@ do { \
#define lpfc_printf_vlog(vport, level, mask, fmt, arg...) \
do { \
{ if (((mask) & (vport)->cfg_log_verbose) || (level[1] <= '3')) { \
- if ((mask) & LOG_TRACE_EVENT) \
+ if ((mask) & LOG_TRACE_EVENT && !(vport)->cfg_log_verbose) \
lpfc_dmp_dbg((vport)->phba); \
dev_printk(level, &((vport)->phba->pcidev)->dev, "%d:(%d):" \
fmt, (vport)->phba->brd_no, vport->vpi, ##arg); \
@@ -89,11 +89,11 @@ do { \
(phba)->pport->cfg_log_verbose : \
(phba)->cfg_log_verbose; \
if (((mask) & log_verbose) || (level[1] <= '3')) { \
- if ((mask) & LOG_TRACE_EVENT) \
+ if ((mask) & LOG_TRACE_EVENT && !log_verbose) \
lpfc_dmp_dbg(phba); \
dev_printk(level, &((phba)->pcidev)->dev, "%d:" \
fmt, phba->brd_no, ##arg); \
- } else if (!(phba)->cfg_log_verbose)\
+ } else if (!log_verbose)\
lpfc_dbg_print(phba, "%d:" fmt, phba->brd_no, ##arg); \
} \
} while (0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971193
Title:
Server Crash while running IO and switch port bounce test with 2K
login session
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971193/+subscriptions
--
[Bug 1971193] [NEW] Server Crash while running IO and switch port bounce test with 2K login session
Public bug reported: Server crash and Call trace reported on one of the servers running IO and switch port bounce test from the 2K login session configuration. Call Trace: [56048.470488] Call Trace: [56048.470489] _raw_spin_lock_irqsave+0x32/0x40 [56048.470489] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470490] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470490] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470490] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470491] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470491] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470492] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470492] ? __schedule+0x280/0x700 [56048.470492] ? finish_wait+0x80/0x80 [56048.470493] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470493] kthread+0x112/0x130 [56048.470493] ? kthread_flush_work_fn+0x10/0x10 [56048.470494] ret_from_fork+0x1f/0x40 [56048.470494] Kernel panic - not syncing: Hard LOCKUP [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G IOE- - - 4.18.0-240.el8.x86_64 #1 [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS 2.11.2 004/21/2021 [56048.470496] Call Trace: [56048.470496] [56048.470496] dump_stack+0x5c/0x80 [56048.470497] panic+0xe7/0x2a9 [56048.470497] ? __switch_to_asm+0x51/0x70 [56048.470497] nmi_panic.cold.9+0xc/0xc [56048.470498] watchdog_overflow_callback.cold.7+0x5c/0x70 [56048.470498] __perf_event_overflow+0x52/0xf0 [56048.470499] handle_pmi_common+0x1db/0x270 [56048.470499] ? __set_pte_vaddr+0x32/0x50 [56048.470499] ? __native_set_fixmap+0x24/0x30 [56048.470500] ? ghes_copy_tofrom_phys+0xd3/0x1c0 [56048.470500] ? __ghes_peek_estatus.isra.12+0x49/0xa0 [56048.470500] intel_pmu_handle_irq+0xbf/0x160 [56048.470501] perf_event_nmi_handler+0x2d/0x50 [56048.470501] nmi_handle+0x63/0x110 [56048.470501] default_do_nmi+0x4e/0x100 [56048.470502] do_nmi+0x128/0x190 [56048.470502] end_repeat_nmi+0x16/0x6a [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 75 f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75 [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002 [56048.470505] RAX: 0101 RBX: 0246 RCX: 001f [56048.470505] RDX: RSI: RDI: 94dcf5341dc0 [56048.470506] RBP: 94dcf534 R08: 0002 R09: 00029600 [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12: 94dcf5341db0 [56048.470507] R13: 94dcf5341dc0 R14: 94dcc4ae8a00 R15: 0003 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470508] [56048.470508] _raw_spin_lock_irqsave+0x32/0x40 [56048.470509] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470509] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470509] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470510] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470510] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470510] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470511] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470511] ? __schedule+0x280/0x700 [56048.470511] ? finish_wait+0x80/0x80 [56048.470512] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470512] kthread+0x112/0x130 [56048.470513] ? kthread_flush_work_fn+0x10/0x10 [56048.470513] ret_from_fork+0x1f/0x40 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.3 (Ootpa) [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/module/lpfc/version 0:14.0.390.2 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/scsi_host/host*/modeldesc Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/scsi_host/host*/fwrev 14.0.390.1, sli-4:2:c 14.0.390.1, sli-4:2:c [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/fc_host/host*/port_name 0x1090faf09459 0x1090faf0945a [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# HBA Attributes for 10:00:00:90:fa:f0:94:59 Host Name : ms-svr3-10-231-131-160 Manufacturer : Emulex Corporation Serial Number : FC70793283 Model : LPe32002-M2 Model Desc: Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter Node WWN : 20 00 00 90 fa f0 94 59 Node Symname : HW Version: 000c 0001 FW Version: 14.0.390.1 Vendor Spec ID
[Bug 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Same here on Razer Blade 15 Advanced (2022). I tried acpi_osi= in the grub line and that results in the trackpad not working at all upon reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798363 Title: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
I am experiencing the exact same symptoms on a Razer Blade 15 (early 2022) model running 5.17.1 from Ubuntu mainline: $ uname -r 5.17.1-051701-generic The issue only happens after S3 suspend. s2idle does not cause the problem, but I experience huge battery drain in s2idle (10%/hour). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
Jeff - thank you for the update but what is the ETA for a kernel with these patches integrated? Laurie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1951111] Re: [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for Ubuntu 22.04
Thank you On Monday, January 10, 2022, Jeff Lane <1951...@bugs.launchpad.net> wrote: > ** Changed in: linux (Ubuntu) >Status: Incomplete => Confirmed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/195 > > Title: > [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for > Ubuntu 22.04 > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > The purpose of this bug is to track the incremental patches needed in > Ubuntu 22.04 for the Broadcom Emulex FC HBA lpfc driver that are > committed to the 5.16 upstream kernel and not part of the 5.15 kernel > that 22.04 is rebased to. > > Please integrate the following patches from the 5.16 kernel per James > Smart the lpfc maintainter. > > James Smart > Fri, Nov 12, 2:31 PM (4 days ago) > to me, Dick, Justin, Teresa > > I would argue to take all of the patches in the following list > (14.0.0.2 & 14.0.0.3 & a mbx cmd failure issue) > > -- james > > > Applied to 5.16/scsi-queue, thanks! > > [1/8] lpfc: Revert LOG_TRACE_EVENT back to LOG_INIT prior to > driver_resource_setup > https://git.kernel.org/mkp/scsi/c/a516074c2026 > [2/8] lpfc: Wait for successful restart of SLI3 adapter during host > sg_reset > https://git.kernel.org/mkp/scsi/c/d305c253af69 > [3/8] lpfc: Correct sysfs reporting of loop support after SFP status > change > https://git.kernel.org/mkp/scsi/c/7a1dda943630 > [4/8] lpfc: Fix use-after-free in lpfc_unreg_rpi() routine > https://git.kernel.org/mkp/scsi/c/79b20beccea3 > [5/8] lpfc: Allow PLOGI retry if previous PLOGI was aborted > https://git.kernel.org/mkp/scsi/c/15af02d8a585 > [6/8] lpfc: Fix link down processing to address NULL pointer dereference > https://git.kernel.org/mkp/scsi/c/1854f53ccd88 > [7/8] lpfc: Allow fabric node recovery if recovery is in progress before > devloss > https://git.kernel.org/mkp/scsi/c/af984c87293b > [8/8] lpfc: Update lpfc version to 14.0.0.3 > https://git.kernel.org/mkp/scsi/c/83c3a7beaef7 > > Applied to 5.16/scsi-queue, thanks! > > [1/1] lpfc: Fix mailbox command failure during driver initialization > https://git.kernel.org/mkp/scsi/c/efe1dc571a5b > > > Applied to 5.16/scsi-queue, thanks! > > [01/14] lpfc: Fix list_add corruption in lpfc_drain_txq > https://git.kernel.org/mkp/scsi/c/99154581b05c > [02/14] lpfc: Don't release final kref on Fport node while ABTS > outstanding > https://git.kernel.org/mkp/scsi/c/982fc3965d13 > [03/14] lpfc: Fix premature rpi release for unsolicited TPLS and LS_RJT > https://git.kernel.org/mkp/scsi/c/20d2279f90ce > [04/14] lpfc: Fix hang on unload due to stuck fport node > https://git.kernel.org/mkp/scsi/c/88f7702984e6 > [05/14] lpfc: Fix rediscovery of tape device after issue lip > https://git.kernel.org/mkp/scsi/c/3a874488d2e9 > [06/14] lpfc: Don't remove ndlp on PRLI errors in P2P mode > https://git.kernel.org/mkp/scsi/c/a864ee709bc0 > [07/14] lpfc: Fix NVME I/O failover to non-optimized path > https://git.kernel.org/mkp/scsi/c/b507357f7917 > [08/14] lpfc: Fix FCP I/O flush functionality for TMF routines > https://git.kernel.org/mkp/scsi/c/cd8a36a90bab > [09/14] lpfc: Fix EEH support for NVME I/O > https://git.kernel.org/mkp/scsi/c/25ac2c970be3 > [10/14] lpfc: Adjust bytes received vales during cmf timer interval > https://git.kernel.org/mkp/scsi/c/d5ac69b332d8 > [11/14] lpfc: Fix I/O block after enabling managed congestion mode > https://git.kernel.org/mkp/scsi/c/3ea998cbf9e7 > [12/14] lpfc: Zero CGN stats only during initial driver load and stat > reset > https://git.kernel.org/mkp/scsi/c/afd63fa51149 > [13/14] lpfc: Improve PBDE checks during SGL processing > https://git.kernel.org/mkp/scsi/c/315b3fd13521 > [14/14] lpfc: Update lpfc version to 14.0.0.2 > https://git.kernel.org/mkp/scsi/c/0d6b26795bd2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 195/+subscriptions > > -- *Laurie Barry* Software Program Manager | Emulex Connectivity Division office/soft phone: 978-719-1503 | mobile: 603-930-1771 200 Brickstone Square | Andover, MA 01810 laurie.ba...@broadcom.com | broadcom.com -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are
[Bug 1956982] [NEW] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
Public bug reported: Please integrate this customer critical/reported fix that was submitted as a stand along patch: Accepted 11/29/21: Applied to 5.16/scsi-fixes, thanks! [1/1] lpfc: Fix nonrecovery of remote ports following an unsolicited LOGO https://git.kernel.org/mkp/scsi/c/0956ba63bd94 As well as this latest set of bug fix patches accepted upstream 12/6/2021: scsi: lpfc: Fix leaked lpfc_dmabuf mbox allocations with NPIV commitf0d3919697492950f57a26a1093aee53880d669d scsi: lpfc: Change return code on I/Os received during link bounce commit2e81b1a374da5d6024208c16c4a5224a70cafa64 scsi: lpfc: Fix lpfc_force_rscn ndlp kref imbalance commit7576d48c64f36f6fea9df2882f710a474fa35f40 scsi: lpfc: Fix NPIV port deletion crash commit8ed190a91950564775cbaae9e8e8083a69a8da23 scsi: lpfc: Trigger SLI4 firmware dump before doing driver cleanup commit7dd2e2a923173d637c272e483966be8e96a72b64 scsi: lpfc: Adjust CMF total bytes and rxmonitor commita6269f837045acb02904f31f05acde847ec8f8a7 scsi: lpfc: Cap CMF read bytes to MBPI commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 scsi: lpfc: Add additional debugfs support for CMF commit6014a2468f0e49194f612b1f09f99eacee0a409a scsi: lpfc: Update lpfc version to 14.0.0.4 commit4437503bfbec2f02b41b2492520fe627715889a7 Extended log info: -cover-letter.patch 0001-lpfc-Fix-leaked-lpfc_dmabuf-mbox-allocations-with-np.patch commitf0d3919697492950f57a26a1093aee53880d669d lpfc: Fix memory leaked lpfc_dmabuf mbox allocations Fix leaked lpfc_dmabuf allocations in an mbox. svn: r82112 bz: 249968 250131 0002-lpfc-Change-return-code-on-ios-received-during-link-.patch commit2e81b1a374da5d6024208c16c4a5224a70cafa64 lpfc: Group RPI_SUSPENDED error action with DID_REQUEUE Fix Medusa IO errors on Scope and Scale LIP test svn: r82348 bz: 247164 250466 Fix Medusa IO errors on Scope and Scale LIP test - build svn: r82377 bz: 247164 250466 0003-lpfc-Fix-lpfc_force_rscn-ndlp-kref-imbalance.patch commit7576d48c64f36f6fea9df2882f710a474fa35f40 lpfc: Fix lpfc_force_rscn ndlp kref imbalance Fix ndlp kref crash during lpfc_force_rscn svn: r82526 bz: 250692 250695 0004-lpfc-Fix-NPIV-port-deletion-crash.patch commit8ed190a91950564775cbaae9e8e8083a69a8da23 lpfc: Fix NPIV port deletion crash Fix crash when deleting a large number of vports. svn: r82120 bz: 240671 250158 Fix a log message formatting error introduced in svn r82120. svn: r82743 bz: 249968 250131 0005-lpfc-Trigger-SLI4-firmware-dump-before-doing-driver-.patch commit7dd2e2a923173d637c272e483966be8e96a72b64 lpfc: Trigger SLI4 firmware dump immediately without delays Trigger SLI4 firmware dump immediately without delays svn: r82770 bz: 250111 251061 0006-lpfc-Adjust-CMF-total-bytes-and-rxmonitor.patch commita6269f837045acb02904f31f05acde847ec8f8a7 lpfc: Adjust CMF total bytes and rxmonitor Adjust CMF total bytes and add to rxmonitor svn: r82429 bz: 250581 250587 0007-lpfc-Cap-CMF-read-bytes-to-MBPI.patch commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 lpfc: Cap CMF read bytes to MBPI Cap CMF read bytes to MBPI only for shortened timer intervals svn: r82483 bz: 250605 251274 0008-lpfc-Add-additional-debugfs-support-for-CMF.patch commit6014a2468f0e49194f612b1f09f99eacee0a409a lpfc: Add additional debugfs support for CMF Add debugfs support for CMF parameters svn: r82144 bz: 250206 250237 Coverity: CID 19805 Fix memory illegal access svn: r82349 bz: 250454 250465 0009-lpfc-Update-lpfc-version-to-14.0.0.4.patch commit4437503bfbec2f02b41b2492520fe627715889a7 ** 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/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776030] Re: Backup fails with "an unknown error"
Tested a theory this morning: try a restore from the old/failed backup. Was thinking maybe it had lost the login credentials to the NAS; nope: gave the same error message: "Restore Failed" and lines 1555, 1541, 1393, etc. (same as when attempted to create a backup). Again I have no idea what this means other that "it broke" but maybe is useful to the programmers . As I said, creating a new backup location fixes (more patches) the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776030 Title: Backup fails with "an unknown error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776030] Re: Backup fails with "an unknown error"
Update on what I found The easiest and fastest way to ‘correct’ is to create a new directory to back up to and change the storage location to the new back up point. I looked at permissions as suggested in one of the posts above: barry@NZXT:~$ getfacl/media/NSA320_Backups/DejaDup_NZXT_02 getfacl: Removing leading '/' from absolute path names # file: media/NSA320_Backups/DejaDup_NZXT_02 # owner: barry # group: barry user::rwx group::rwx other::rwx barry@NZXT:~$ ls -lS /media/NSA320_Backups total 0 drwxrwxrwx 2 barry barry 0 Apr 29 2020 Backend_3 drwxrwxrwx 2 barry barry 0 Oct 25 19:24 DejaDup_NZXT_01 drwxrwxrwx 2 barry barry 0 Dec 17 02:36 DejaDup_NZXT_02 barry@NZXT:~$ ls -lS /media/NSA320_Backups/DejaDup_NZXT_02 -rwxrwxrwx 1 barry barry187 Jul 30 03:33 duplicity-inc.20210729T082208Z.to.20210730T082213Z.manifest -rwxrwxrwx 1 barry barry187 Aug 10 03:33 duplicity-inc.20210809T082232Z.to.20210810T082229Z.manifest To me looks like everyone and their uncle can do what they want (so chmod 777?). No idea. LIS, I created and pointed to a new directory and it’s making a full backup now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776030 Title: Backup fails with "an unknown error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776030] Re: Backup fails with "an unknown error"
As much as I hate to be a "me too" message the same 'failed with unknown error' occurred with last night's automated backup, as well as the manual retests. Running Ubuntu 18.04. Nothing was changed here, although I did create a script on two Raspberry Pi's to monitor the status of accessing the remote NAS -- RPi with Motion, storage to the NAS; this Ubuntu system with storage to the same NAS, different directory. (No issues with the RPi writing.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776030 Title: Backup fails with "an unknown error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950448] Re: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40
The bug referred to above (https://bugzilla.kernel.org/show_bug.cgi?id=214455) is marked as RESOLVED CODE_FIX. When should we expect to be getting this in Ubuntu? ** Bug watch added: Linux Kernel Bug Tracker #214455 https://bugzilla.kernel.org/show_bug.cgi?id=214455 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951111] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for Ubuntu 22.04
Please note that this patch includes fixes needed by IBMp for it's upcoming Broadcom Emulex HBA program. Thank you Laurie Barry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/195 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951111] [NEW] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for Ubuntu 22.04
Public bug reported: The purpose of this bug is to track the incremental patches needed in Ubuntu 22.04 for the Broadcom Emulex FC HBA lpfc driver that are committed to the 5.16 upstream kernel and not part of the 5.15 kernel that 22.04 is rebased to. Please integrate the following patches from the 5.16 kernel per James Smart the lpfc maintainter. James Smart Fri, Nov 12, 2:31 PM (4 days ago) to me, Dick, Justin, Teresa I would argue to take all of the patches in the following list (14.0.0.2 & 14.0.0.3 & a mbx cmd failure issue) -- james Applied to 5.16/scsi-queue, thanks! [1/8] lpfc: Revert LOG_TRACE_EVENT back to LOG_INIT prior to driver_resource_setup https://git.kernel.org/mkp/scsi/c/a516074c2026 [2/8] lpfc: Wait for successful restart of SLI3 adapter during host sg_reset https://git.kernel.org/mkp/scsi/c/d305c253af69 [3/8] lpfc: Correct sysfs reporting of loop support after SFP status change https://git.kernel.org/mkp/scsi/c/7a1dda943630 [4/8] lpfc: Fix use-after-free in lpfc_unreg_rpi() routine https://git.kernel.org/mkp/scsi/c/79b20beccea3 [5/8] lpfc: Allow PLOGI retry if previous PLOGI was aborted https://git.kernel.org/mkp/scsi/c/15af02d8a585 [6/8] lpfc: Fix link down processing to address NULL pointer dereference https://git.kernel.org/mkp/scsi/c/1854f53ccd88 [7/8] lpfc: Allow fabric node recovery if recovery is in progress before devloss https://git.kernel.org/mkp/scsi/c/af984c87293b [8/8] lpfc: Update lpfc version to 14.0.0.3 https://git.kernel.org/mkp/scsi/c/83c3a7beaef7 Applied to 5.16/scsi-queue, thanks! [1/1] lpfc: Fix mailbox command failure during driver initialization https://git.kernel.org/mkp/scsi/c/efe1dc571a5b Applied to 5.16/scsi-queue, thanks! [01/14] lpfc: Fix list_add corruption in lpfc_drain_txq https://git.kernel.org/mkp/scsi/c/99154581b05c [02/14] lpfc: Don't release final kref on Fport node while ABTS outstanding https://git.kernel.org/mkp/scsi/c/982fc3965d13 [03/14] lpfc: Fix premature rpi release for unsolicited TPLS and LS_RJT https://git.kernel.org/mkp/scsi/c/20d2279f90ce [04/14] lpfc: Fix hang on unload due to stuck fport node https://git.kernel.org/mkp/scsi/c/88f7702984e6 [05/14] lpfc: Fix rediscovery of tape device after issue lip https://git.kernel.org/mkp/scsi/c/3a874488d2e9 [06/14] lpfc: Don't remove ndlp on PRLI errors in P2P mode https://git.kernel.org/mkp/scsi/c/a864ee709bc0 [07/14] lpfc: Fix NVME I/O failover to non-optimized path https://git.kernel.org/mkp/scsi/c/b507357f7917 [08/14] lpfc: Fix FCP I/O flush functionality for TMF routines https://git.kernel.org/mkp/scsi/c/cd8a36a90bab [09/14] lpfc: Fix EEH support for NVME I/O https://git.kernel.org/mkp/scsi/c/25ac2c970be3 [10/14] lpfc: Adjust bytes received vales during cmf timer interval https://git.kernel.org/mkp/scsi/c/d5ac69b332d8 [11/14] lpfc: Fix I/O block after enabling managed congestion mode https://git.kernel.org/mkp/scsi/c/3ea998cbf9e7 [12/14] lpfc: Zero CGN stats only during initial driver load and stat reset https://git.kernel.org/mkp/scsi/c/afd63fa51149 [13/14] lpfc: Improve PBDE checks during SGL processing https://git.kernel.org/mkp/scsi/c/315b3fd13521 [14/14] lpfc: Update lpfc version to 14.0.0.2 https://git.kernel.org/mkp/scsi/c/0d6b26795bd2 ** 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/195 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+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 and 17
The upstream fix from Debian requires guice >=4.2.3 and, implicitly, a newer version of guava (Debian repo has 29.0). The current available versions in Ubuntu 20.04 are guice 4.2.1 and guava 19.0, so both of these package updates will have to be backported. Attempting to build maven 3.6.3 with the changes described by the commit in the upstream bug report (https://salsa.debian.org/java- team/maven/-/commit/48fb5b2ae0dcd860d61e4b258d60fcee03d2713c) resulted in maven packages that were missing some required "Depends" declarations, for example libcommons-cli-java and libgeronimo- annotation-1.3-spec-java. These are listed as "Build-Depends" and installing them does allow maven to run on Java 16+. Hopefully there is some useful info here for the maintainers. -- 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 and 17 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 1930541] Re: Maven 3.6.3-1 fails to run with OpenJDK 16 and 17
** Summary changed: - Maven 3.6.3-1 fails to run with OpenJDK 16 + Maven 3.6.3-1 fails to run with OpenJDK 16 and 17 -- 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 and 17 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 1936253] [NEW] Juju 2.9.8 tries to use an empty UID when deleting Kubernetes objects, and cannot remove applications
Public bug reported: I did a little digging on this, and it's definitely the UID on the RBAC role. I'd blame this commit: https://github.com/juju/juju/commit/35e712ef6bf485aaeb8b718e6e6aa10683e381bc#diff-1bb294296419d47846f2432fb32f22cd9f42745a4c0aa8568f140bf499799b9fR85 Juju calls a factory with a name only: https://github.com/juju/juju/blob/develop/caas/kubernetes/provider/application/application.go#L934 Then gets a bare struct where UID is definitely empty, and immediately try to delete it with an empty precondition: https://github.com/juju/juju/blob/dcc82d771253673354f5cd96cc87b528bd81e7b2/caas/kubernetes/provider/resources/clusterrolebinding.go#L31 ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Package changed: v4l2loopback (Ubuntu) => juju (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936253 Title: Juju 2.9.8 tries to use an empty UID when deleting Kubernetes objects, and cannot remove applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1936253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933139] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
I seem to have fixed this by adding ConditionPathExists=/etc/fstab ConditionVirtualization=!container to the end of the [Unit] section of /lib/systemd/system/systemd-remount- fs.service. I'm not a maintainer, so this should be reviewed by someone who knows what they are doing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933139 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1933139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933139] [NEW] package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Public bug reported: I was do-release-upgrade of a Bionic container to Focal. When I reboot I have a systemd unit systemd-remount-fs.service. Error:can't find LABEL=cloudimg-rootfs ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lxd 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 21 14:24:25 2021 ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: lxd Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-06-21 (0 days ago) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933139 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1933139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910301] [NEW] installing Ubuntu in Virtual Box
Public bug reported: Unknown, was installing and this was here when I got back to the install Advanced partitioning, ZFS with encryption ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 18:04:04 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910301 Title: installing Ubuntu in Virtual Box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1910301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579268] Re: Mouse cursor is different inside graphical windows of snaps (snaps not using system theme)
Happens to me with Chromium and Discord snaps BUT ONLY if I start them quickly after system startup. If I wait at least ~15 seconds, or quit & restart the app, they display with normal correct system pointer/cursor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579268 Title: Mouse cursor is different inside graphical windows of snaps (snaps not using system theme) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1579268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876282] Re: libc++1 is kept back after upgrade to focal
Same as comment #4, I encountered this issue after upgrading from 20.04 -> 20.10. So it's not specific to an upgrade to focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876282 Title: libc++1 is kept back after upgrade to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1876282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902760] [NEW] Please merge linker bugfix into Ubuntu 20.04 LTS
Public bug reported: Binutils bug https://sourceware.org/bugzilla/show_bug.cgi?id=26262 fixes a problem that Intel Fortran is running into when using the -ipo option to request link time optimization. Please merge the fix into Ubuntu 20.04 LTS ** Affects: binutils (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/1902760 Title: Please merge linker bugfix into Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1902760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: How do I request an upgrade to binutils in Ubuntu 20.04 LTS?
Hello? Is this the right list for this question? From: Tannenbaum, Barry M Sent: Friday, October 30, 2020 3:09 PM To: Ubuntu Quality Team Subject: How do I request an upgrade to binutils in Ubuntu 20.04 LTS? Binutils bug https://sourceware.org/bugzilla/show_bug.cgi?id=26262 fixes a problem that Intel Fortran is running into. It will affect any compiler using interprocess optimization (-ipo) or Link Time Optimization (LTO). How do I request that it be merged into Ubuntu 20.04 LTS? Thanks. - Barry Tannenbaum Intel Corporation -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
How do I request an upgrade to binutils in Ubuntu 20.04 LTS?
Binutils bug https://sourceware.org/bugzilla/show_bug.cgi?id=26262 fixes a problem that Intel Fortran is running into. It will affect any compiler using interprocess optimization (-ipo) or Link Time Optimization (LTO). How do I request that it be merged into Ubuntu 20.04 LTS? Thanks. - Barry Tannenbaum Intel Corporation -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
[Bug 1899270] Re: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously
Filed ... https://bugs.chromium.org/p/chromium/issues/detail?id=1142850 :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899270 Title: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899270] Re: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously
And still present after updating to Chrome/86.0.4240.111. B -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899270 Title: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899270] Re: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously
Yes, there are still problems regardless of the command line switches, as long as "Settings/Use hardware acceleration ..." is turned on. (Go full screen and we have an unstable display with elements that flash or alternate between one position and another. Opening 'Help/Report an issue' also gives unreliable results, sometimes with the Cancel and Save buttons flashing, too.) B -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899270 Title: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899270] Re: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously
Here are the first sections of chrome://gpu output without and with --ignore-gpu-blacklist. The only difference is in Hardware Protected Video Decode which is 'Unavailable' in the first case and 'Hardware Accelerated' in the second. Note, also, that both of these lists are different to the output that I posted a couple of days ago where, despite my having written that Hardware Acceleration was turned on in chrome://settings, I believe it was still actually turned off when I captured the output. (I've a feeling that although I changed the setting I didn't click the Relaunch button.) Please accept my apologies for this, I hope it hasn't caused much confusion. For confirmation, I've reattached the full set of chrome://gpu output captured without --ignore-gpu-blacklist. B > /opt/google/chrome/chrome Graphics Feature Status Canvas: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled OpenGL: Enabled Hardware Protected Video Decode: Unavailable Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Enabled Video Decode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated > /opt/google/chrome/chrome --ignore-gpu-blacklist Graphics Feature Status Canvas: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled OpenGL: Enabled Hardware Protected Video Decode: Hardware accelerated Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Enabled Video Decode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated ** Attachment added: "gpu, no switches.html" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+attachment/5425644/+files/gpu%2C%20no%20switches.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899270 Title: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899270] Re: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously
glxinfo output is attached. I'm not routinely running anything that needs acceleration. I'm a musician/programmer so primarily audio and code, not even games come to think of it. I did do some work in Blender over a year ago, but I only used this machine for extra rendering work (using the CPU, not the GPU). I just fired it up again and it's behaving properly, though I've no idea whether it's using acceleration. By the way, the Software Update package is reporting that a new version of Google Chrome is available. Would it be helpful if I held off updating it until you've got to the bottom of this. Or shall I go ahead and check behaviour in the latest version? B ** Attachment added: "glxinfo.txt" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+attachment/5425588/+files/glxinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899270 Title: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899270] Re: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously
Here's my chrome://gpu output (with acceleration enabled, if that makes a difference): Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled OpenGL: Disabled Hardware Protected Video Decode: Disabled Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Enabled Video Decode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Software only, hardware acceleration unavailable WebGL2: Software only, hardware acceleration unavailable Problems Detected Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable. Disabled Features: gpu_compositing Accelerated video decode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_decode Version Information Data exported 2020-10-20T16:06:56.191Z Chrome version Chrome/86.0.4240.75 Operating systemLinux 5.4.0-51-lowlatency Software rendering list URL https://chromium.googlesource.com/chromium/src/+/c69c33933bfc72a159aceb4aeca939eb0087416c/gpu/config/software_rendering_list.json Driver bug list URL https://chromium.googlesource.com/chromium/src/+/c69c33933bfc72a159aceb4aeca939eb0087416c/gpu/config/gpu_driver_bug_list.json ANGLE commit id 8fe030942169 2D graphics backend Skia/86 fe61f1806d406858a2ed399b6dfeef1c40d06284 Command Line/usr/bin/google-chrome-stable --flag-switches-begin --flag-switches-end Driver Information Initialization time 50 In-process GPU false Passthrough Command Decoder false Sandboxed true GPU0VENDOR= 0x8086 [Google Inc.], DEVICE=0x0166 [Google SwiftShader] *ACTIVE* Optimus false AMD switchable false Driver vendor Driver version 4.1.0.7 GPU CUDA compute capability major version 0 Pixel shader version3.00 Vertex shader version 3.00 Max. MSAA samples 4 Machine model name Machine model version GL_VENDOR Google Inc. GL_RENDERER Google SwiftShader GL_VERSION OpenGL ES 3.0 SwiftShader 4.1.0.7 GL_EXTENSIONS GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24 GL_OES_depth32 GL_OES_depth_texture GL_OES_depth_texture_cube_map GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_EGL_sync GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_framebuffer_object GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_texture_3D GL_OES_vertex_array_object GL_OES_vertex_half_float GL_EXT_blend_minmax GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_draw_buffers GL_EXT_float_blend GL_EXT_instanced_arrays GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_texture_compression_dxt1 GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA GL_EXT_texture_rg GL_ARB_texture_rectangle GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_texture_filtering_hint GL_NV_depth_buffer_float2 GL_NV_fence GL_NV_read_depth GL_NV_read_stencil Disabled Extensions Disabled WebGL Extensions Window system binding vendorGoogle Inc. Window system binding version 1.4 SwiftShader 4.1.0.7 Window system binding extensionsEGL_KHR_create_context EGL_KHR_get_all_proc_addresses EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_KHR_image_base EGL_KHR_surfaceless_context EGL_ANGLE_iosurface_client_buffer EGL_ANDROID_framebuffer_target EGL_ANDROID_recordable Window manager Xfwm4 XDG_CURRENT_DESKTOP XFCE GDMSESSION xfce Compositing manager Yes System visual ID0 RGBA visual ID 0 Direct rendering versionunknown Reset notification strategy 0x GPU process crash count 0 gfx::BufferFormats supported for allocation and texturing R_8: not supported, R_16: not supported, RG_88: not supported, BGR_565: not supported, RGBA_: not supported, RGBX_: not supported, RGBA_: not supported, BGRX_: not supported, BGRA_1010102: not supported, RGBA_1010102: not supported, BGRA_: not supported, RGBA_F16: not supported, YVU_420: not supported, YUV_420_BIPLANAR: not supported, P010: not supported Compositor Information Tile Update ModeOne-copy Partial Raster Enabled GpuMemoryBuffers Status R_8 Software only R_16Software only RG_88 Software only BGR_565 Software only RGBA_ Software only RGBX_ Software only RGBA_ Software only BGRX_ Software
[Bug 1899270] [NEW] Chrome on Ubuntu, press F11 for full screen and the message flashes continuously
Public bug reported: After pressing F11 there's a text box at the top of the screen with the message Press F11 to Exit, etc. Usually this goes away by itself after a few seconds. Now it flashes continuously and won't clear. Pressing F11 again quits full screen mode, but the tab is still flashing in some way and the whole browser is now unstable and not usable. Chrome: Version 86.0.4240.75 (Official Build) (64-bit) System: Ubuntu Studio, Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899270 Title: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817389] Re: GIMP icon sizes small on large and huge setting
I was able to work around the issue by changing the theme in Gnome Tweaks from Yaru to Adwaita or sticking with Yaru and removing the gtk- icon-sizes defintion (note it spans multiple lines) in the gtk2 rc at /usr/share/themes/Yaru/gtk-2.0/gtkrc This may break the look of other gtk2 applications --- /usr/share/themes/Yaru/gtk-2.0/gtkrc.orig 2020-09-09 16:46:30.332864005 -0500 +++ /usr/share/themes/Yaru/gtk-2.0/gtkrc2020-09-09 16:47:25.297208691 -0500 @@ -34,12 +34,7 @@ # Set GTK settings gtk-auto-mnemonics = 1 gtk-primary-button-warps-slider = 1 -gtk-icon-sizes="gtk-menu=16,16: -gtk-button=16,16: -gtk-small-toolbar=16,16: -gtk-dnd=16,16: -gtk-dialog=16,16" gtk-toolbar-style = GTK_TOOLBAR_ICONS gtk-menu-images = 0 gtk-menu-popup-delay = 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817389 Title: GIMP icon sizes small on large and huge setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1817389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1883312] Re: [SRU] NVMe FC Auto-connect is not working for Ubuntu 20.04
Thank you Jeff. Yeah, at this point I think it sits until you naturally update your userspace to the latest packages. We don't have the BW to prioritize doing anything special for this one. *Laurie Barry* Software Program Manager | Emulex Connectivity Division office/soft phone: 978-719-1503 | mobile: 603-930-1771 200 Brickstone Square | Andover, MA 01810 laurie.ba...@broadcom.com | broadcom.com On Thu, Aug 27, 2020 at 11:15 AM Jeff Lane <1883...@bugs.launchpad.net> wrote: > Hi Laurie, > This has sat a while, I wanted to check up on it. In general, we will not > upgrade userspace packages in a released version of Ubuntu, however, we can > certainly backport patches to fix bugs. > > Alternately, if your customer has an Ubuntu Advantage agreement with us, > they can file a support case that way and our Sustaining Engineering > team would take a look and do what is necessary. > > I'm happy to continue working on this to push bug fixes, but to do so, > I'd need to have access to the upstream git tree and a list of patches > needed to resolve the issue. From there, I can work on an SRU to the > version of nvme-cli in Focal. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1883312 > > Title: > [SRU] NVMe FC Auto-connect is not working for Ubuntu 20.04 > > Status in nvme-cli package in Ubuntu: > New > Status in nvme-cli source package in Focal: > New > > Bug description: > [SUMMARY] > > Auto-connect is not working for Ubuntu 20.04. However manual nvme > discover and connect commands works. > > root@ubuntu2004:~# uname -a > Linux ubuntu2004 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:06:57 UTC > 2020 > x86_64 x86_64 x86_64 GNU/Linux > > root@ubuntu2004:~# nvme version > nvme version 1.9 > > root@ubuntu2004:~# cat /sys/module/lpfc/version > 0:12.6.0.4 > > The fix is to update nvme-cli to version 1.10.1 or later. Groovy > currently contains version 1.12-1 so it would seem the easiest would > be to update nvme-cli in Focal to the version in Groovy. > > > [IMPACT] > > Connectivity to NVMe Namespaces are lost after an link bounce or after > a server reboot. > > [FIXES] > > Update nvme-cli to 1.10.1 > > [TESTING] > > [REGRESSION RISK] > > No > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1883312/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883312 Title: [SRU] NVMe FC Auto-connect is not working for Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1883312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885591] [NEW] error pop up whlie grub is installing
Public bug reported: I am actually trying to install ubuntu on external drive and when it reaches the point of installing the grub the installation crashes and an error message pop up " grub installation fails" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 15:47:50 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885591 Title: error pop up whlie grub is installing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1885591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883312] Re: NVMe FC Auto-connect is not working for Ubuntu 20.04
We have a large enterprise customer planning to start their validation of NVMe FC on Ubuntu 20.04 starting in September. Laurie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883312 Title: NVMe FC Auto-connect is not working for Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1883312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883312] [NEW] NVMe FC Auto-connect is not working for Ubuntu 20.04
Public bug reported: Jeff, Please update Ubuntu 20.04 to from nvme-cli 1.9 to nvme-cli 1.10.1. 1.9 autoconnect is not working. thank you Laurie -- Auto-connect is not working for Ubuntu 20.04. However manual nvme discover and connect commands works. root@ubuntu2004:~# uname -a Linux ubuntu2004 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:06:57 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu2004:~# nvme version nvme version 1.9 root@ubuntu2004:~# cat /sys/module/lpfc/version 0:12.6.0.4 root@ubuntu2004:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal root@ubuntu2004:~# ** 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/1883312 Title: NVMe FC Auto-connect is not working for Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821251] Re: please add cnf support to debmirror
** Changed in: debmirror (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821251 Title: please add cnf support to debmirror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1821251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845795] Re: authentication window got stuck over other windows at top left
*** This bug is a duplicate of bug 1824874 *** https://bugs.launchpad.net/bugs/1824874 ** This bug has been marked a duplicate of bug 1824874 undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845795 Title: authentication window got stuck over other windows at top left To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873138] Re: monitoring-plugins-standard installs rpcbind via recommends
It should probably be noted that this was rejected in Debian a while back: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751120 I've filed a separate bug against rpcbind (LP:1873166) to see whether check_rpc could be split into its own package. If that were to happen, then monitoring-plugins could Recommend the new package to satisfy its own requirements without the overhead of also installing and running the rpcbind daemon. ** Bug watch added: Debian Bug tracker #751120 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751120 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873138 Title: monitoring-plugins-standard installs rpcbind via recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1873138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873166] [NEW] Consider splitting check_rpc into a separate package
Public bug reported: There are situations in which the check_rpc utility is required, but in which the user does not wish to also gain an rpc daemon running as root, particularly given LP:1687930 (and perhaps LP:1430181). Separating out the check_rpc utility into its own package seems the simplest way to address this. ** Affects: rpcbind (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/1873166 Title: Consider splitting check_rpc into a separate package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1873166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873138] [NEW] monitoring-plugins-standard installs rpcbind via recommends
Public bug reported: The monitoring-plugins-standard package has a long list of recommends: Recommends: bind9-host | host, dnsutils, libnet-snmp-perl, rpcbind, smbclient, snmp, libdbi1 (>= 0.8.4), libldap-2.4-2 (>= 2.4.7), libmysqlclient20 (>= 5.7.11), libpq5 Given that apt-get will install Recommends by default, this means that any machine with Nagios plugins installed will also end up with a rpc daemon running as root. Could rpcbind perhaps be moved to Suggests? ** Affects: monitoring-plugins (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873138 Title: monitoring-plugins-standard installs rpcbind via recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1873138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [ubuntu-uk] New to Ubuntu
On 13/04/2020 14:32, Peter Callum wrote: > Hello. > I am new to this and am having a few problems with what the best way of > getting assistance is. I keep getting messages from livepatch saying > that there is a problem. Also need to know if I can register for some > paid assistance in the UK. > Any help would be appreciated. > > Kind Regards > Peter Callum > Peter Callum > 27 Rectory Lane > Poringland > Norwich > Norfolk > NR14 7ST > Tel 07722142107 > petercallu...@gmail.com <mailto:petercallu...@gmail.com> > Hi Peter, Welcome to the wonderful world of Linux. :) The best place for new users to get help is face-to-face with other Linux users. You are lucky in that you have an active user group in Norwich; please see here:- https://www.alug.org.uk/ Another good place is to post your question on the website AskUbuntu. You have a good chance of getting help from experienced users. https://askubuntu.com/ The answers may be quite technical so be sure to tell them that you are a new user. The golden rule is to be polite and patient as they are volunteers, giving their time for free. Cheers, Barry T -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
[Bug 1871302] [NEW] Console bell sound is broken
Public bug reported: This is in 20.04 focal on amd64, package version 0.15.0-1build1 Kitty is unable to make a bell sound, erroring with: > Failed to load libcanberra.so, cannot play beep sound, with error: (null) This was fixed upstream here: https://github.com/kovidgoyal/kitty/pull/2178 Fix was released in 0.15.1, but focal is on 0.15.0. ** Affects: kitty (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/1871302 Title: Console bell sound is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kitty/+bug/1871302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
Jeff - is there a date by when we'll see a kernel we can run through our test group? thank you and be well Laurie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855303 Title: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865382] [NEW] after pressing 'reboot' no reboot
Public bug reported: After pressing 'reboot' the installer didn't prompt me to remove install medium (USB stick) and didn't reboot. I had to hold down the power button to power off laptop and then restart the laptop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 14:22:13 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865382 Title: after pressing 'reboot' no reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1865382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858840] Re: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs
Ignore comment #5, that was intended for a different bug and added in error. Laurie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858840 Title: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
Jeff, I just realized I updated the wrong bug...here's the list of additional patches we'll need to include to update 20.04 to the latest upstream for lpfc. There's one additional kernel patch we need you to include below please. thx Laurie Here is the list of additional patch commit ids that would be used to update from 12.6.0.2 (end of list in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855303) to 12.6.0.3 and 12.6.0.4 and to add FPIN/mpio support: scsi: lpfc: Fix incomplete NVME discovery when target commit 3ec5ec408ca633e17d3483e8b806c9fa447e19cc scsi: lpfc: Fix: Rework setting of fdmi symbolic node name registration commit d4e9ddd5ae8f26c521692283c7cbedc7e9881529 scsi: lpfc: Fix missing check for CSF in Write Object Mbox Rsp commit a0c94c5ef874b214305cca965acc7edc27bb69a6 scsi: lpfc: Fix Fabric hostname registration if system hostname changes commit 3712967ea7f2d3793ae2a39e9eae2df111d770b5 scsi: lpfc: Fix ras_log via debugfs commit 25d4132f95c25e6f78a94666a1e067291272888a scsi: lpfc: Fix disablement of FC-AL on lpe35000 models commit 265fb8efca11eee1ffe8edd2bc0a9fbf31b6b84e scsi: lpfc: Fix unmap of dpp bars affecting next driver load commit b88d705fa037b222ecdd5de867132ae25403fe48 scsi: lpfc: Fix MDS Latency Diagnostics Err-drop rates commit 78a7872570fbeed44e7362354619b403c6e6de1e scsi: lpfc: Fix improper flag check for IO type commit f44ccecf36581a2030313e979127013f9d455d3a scsi: lpfc: Update lpfc version to 12.6.0.3 commit e627554eedcfac83bb2ba073adf711a13049273a scsi: lpfc: Fix RQ buffer leakage when no IOCBs available commit9c75a0dee87b2bad80d381ad9fa8ef90847d3a1d scsi: lpfc: Fix lpfc_io_buf resource leak in lpfc_get_scsi_buf_s4 error path commit89cc9dba63c91a6c796dc46342c1d57c82c9b0cd scsi: lpfc: Fix broken Credit Recovery after driver load commit692fc8380ca0f9185e75e01a74357d2cf3083743 scsi: lpfc: Fix registration of ELS type support in fdmi commit0f74f70cb674e3b8712e896863ad85db4d193d46 scsi: lpfc: Fix release of hwq to clear the eq relationship commit01034e708a353fed29963d084c35d58785a317a6 scsi: lpfc: Fix compiler warning on frame size commit3cd50eac891db354e945bf9898726e163a19560e scsi: lpfc: Fix coverity errors in fmdi attribute handling commit3ad04f4f0ad75ad4e7d886133f673d9fe20aa9c4 scsi: lpfc: Remove handler for obsolete ELS - Read Port Status (RPS) commit8d9fae72109e9921f52be342007b4c78490ea4fe scsi: lpfc: Clean up hba max_lun_queue_depth checks commit20d674a4bf64acf54eadc7215ea32b88a3a7687e scsi: lpfc: Update lpfc version to 12.6.0.4 commit35817310d9e05e666dbd242750008dad33ed8992 scsi: lpfc: Copyright updates for 12.6.0.4 patches commitfd6cc30f341fea14bac45bf1c5c9d10702c18a9d --- This one--> scsi: fc: Update Descriptor definition and add RDF and Link Integrity FPINs commit73ec6d2748dc35db2b32cf3c182a27c4a0837b9b scsi: lpfc: add RDF registration and Link Integrity FPIN logging commitdf3fe76658ed47617741819a501e2bd2ae446962 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855303 Title: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858840] Re: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs
Jeff, We have a few more patches required to bring out driver up to date with upstream. Looks like there's 1 additional kernel patch we'll need you to integrate before getting us a pointer to a kernel we can then apply our lpfc driver patches to. See the additional patches we need to bring us up to date since we first filed this bug. thx Laurie Here is the list of additional patch commit ids that would be used to update from 12.6.0.2 (end of list in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855303) to 12.6.0.3 and 12.6.0.4 and to add FPIN/mpio support: scsi: lpfc: Fix incomplete NVME discovery when target commit 3ec5ec408ca633e17d3483e8b806c9fa447e19cc scsi: lpfc: Fix: Rework setting of fdmi symbolic node name registration commit d4e9ddd5ae8f26c521692283c7cbedc7e9881529 scsi: lpfc: Fix missing check for CSF in Write Object Mbox Rsp commit a0c94c5ef874b214305cca965acc7edc27bb69a6 scsi: lpfc: Fix Fabric hostname registration if system hostname changes commit 3712967ea7f2d3793ae2a39e9eae2df111d770b5 scsi: lpfc: Fix ras_log via debugfs commit 25d4132f95c25e6f78a94666a1e067291272888a scsi: lpfc: Fix disablement of FC-AL on lpe35000 models commit 265fb8efca11eee1ffe8edd2bc0a9fbf31b6b84e scsi: lpfc: Fix unmap of dpp bars affecting next driver load commit b88d705fa037b222ecdd5de867132ae25403fe48 scsi: lpfc: Fix MDS Latency Diagnostics Err-drop rates commit 78a7872570fbeed44e7362354619b403c6e6de1e scsi: lpfc: Fix improper flag check for IO type commit f44ccecf36581a2030313e979127013f9d455d3a scsi: lpfc: Update lpfc version to 12.6.0.3 commit e627554eedcfac83bb2ba073adf711a13049273a scsi: lpfc: Fix RQ buffer leakage when no IOCBs available commit9c75a0dee87b2bad80d381ad9fa8ef90847d3a1d scsi: lpfc: Fix lpfc_io_buf resource leak in lpfc_get_scsi_buf_s4 error path commit89cc9dba63c91a6c796dc46342c1d57c82c9b0cd scsi: lpfc: Fix broken Credit Recovery after driver load commit692fc8380ca0f9185e75e01a74357d2cf3083743 scsi: lpfc: Fix registration of ELS type support in fdmi commit0f74f70cb674e3b8712e896863ad85db4d193d46 scsi: lpfc: Fix release of hwq to clear the eq relationship commit01034e708a353fed29963d084c35d58785a317a6 scsi: lpfc: Fix compiler warning on frame size commit3cd50eac891db354e945bf9898726e163a19560e scsi: lpfc: Fix coverity errors in fmdi attribute handling commit3ad04f4f0ad75ad4e7d886133f673d9fe20aa9c4 scsi: lpfc: Remove handler for obsolete ELS - Read Port Status (RPS) commit8d9fae72109e9921f52be342007b4c78490ea4fe scsi: lpfc: Clean up hba max_lun_queue_depth checks commit20d674a4bf64acf54eadc7215ea32b88a3a7687e scsi: lpfc: Update lpfc version to 12.6.0.4 commit35817310d9e05e666dbd242750008dad33ed8992 scsi: lpfc: Copyright updates for 12.6.0.4 patches commitfd6cc30f341fea14bac45bf1c5c9d10702c18a9d --- This is the one we need you to add --> scsi: fc: Update Descriptor definition and add RDF and Link Integrity FPINs commit73ec6d2748dc35db2b32cf3c182a27c4a0837b9b scsi: lpfc: add RDF registration and Link Integrity FPIN logging commitdf3fe76658ed47617741819a501e2bd2ae446962 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858840 Title: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 (5.0) on Broadcom FC HBAs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859098] [NEW] Exiting Writer's Print Preview mode is slow in long documents
Public bug reported: (Cross-posting from https://bugs.documentfoundation.org/show_bug.cgi?id=129900 as problem not reproducible on Windows.) Compared to LibreOffice 5, exiting Print Preview in long documents on LO6 is extremely slow. With a 1,500 page document, for example, exiting Print Preview is instant in LO5, but takes 5-6 seconds (!) in LO6. To reproduce: 1. In LibreOffice 6 Writer, fill a document with text so that it comprises at least a few hundred pages. 2. Enter Print Preview (e.g. File -> Print Preview). 3. Observe it takes a second or two (based on document length) to display the Print Preview screen. This is similar to LibreOffice 5. 4. Press Escape to exit Print Preview mode. 5. Observe a significant delay (approx. 5-6 seconds for a 1,500 page document) with CPU usage spiking before returning to normal view. There is no such delay in LibreOffice 5.3.0.3 Writer. I tend to flip back and forth between Normal View and Print Preview when editing a document, and this new delay makes this very awkward. Ubuntu 19.10 Version: 6.3.4.2 Build ID: 1:6.3.4-0ubuntu0.19.10.1 CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice-writer 1:6.3.4-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 10:53:20 2020 InstallationDate: Installed on 2013-04-11 (2464 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to eoan on 2019-11-07 (63 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-03-26T08:56:12.843910 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan 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/1859098 Title: Exiting Writer's Print Preview mode is slow in long documents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1859098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858840] [NEW] Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 on Broadcom FC HBAs
Public bug reported: Jeff, We have analyzed this issue and see that there are 3 missing patches required to fix this problem. Otherwise vport creation >3 (depending on the customers configuration) will result in a hang for FC or NVMe/FC adapters. Please pull these changes into the next hardware release. These are the missing commits: 959239d [scsi] scsi: core: avoid pre-allocating big SGL for data 5418f2f [scsi] scsi: core: avoid pre-allocating big SGL for protection information 250f285 [nvme] scsi: lib/sg_pool.c: improve APIs for allocating sg pool Laurie - CONFIGURATION DETAILS Host OS with Support Pack - Ubuntu 18.04.3 - HWE () Guest/VM OS Details- System(s) Under Test - IBM x3650 M4 Adapter(s) Under Test - Prism 1-port IPL Name - Active Profile ID - Network Configuration - SAN Configuration - OneCapture file attached - BUG REPRODUCTION DETAILS Test Case ID or ATID - Reproducibility of Bug - Always Last Known Working Build - Time to Reproduce Bug - 5 mins Steps To Reproduce Bug - Create 126 vports on Prism adapter, observe that server goes out of memory and hung. root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G1.7G 13G1.3M299M 13G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G2.1G 12G1.3M299M 12G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G6.1G8.7G1.5M301M8.7G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 13G1.4G1.6M303M1.4G Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G523M1.7M303M528M Swap: 2.0G 0B2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G147M 96K 48M5.0M Swap: 2.0G 38M2.0G root@ubuntu18043:~# free -h totalusedfree shared buff/cache available Mem:15G 14G145M 96K 49M3.6M Swap: 2.0G 38M2.0G Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.166689] scsi host112: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.233464] lpfc :11:00.0: 0:(111):1825 Vport Created. Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.234071] scsi host1: vport-1:0-110 created via shost1 channel 0 Nov 28 05:37:29 ubuntu18043 kernel: [ 1523.698396] scsi host113: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable Nov 28 05:37:30 ubuntu18043 kernel: [ 1523.862582] lpfc :11:00.0: 0:(112):1825 Vport Created. Nov 28 05:37:30 ubuntu18043 kernel: [ 1523.863142] scsi host1: vport-1:0-111 created via shost1 channel 0 Nov 28 05:37:31 ubuntu18043 kernel: [ 1525.097335] scsi host114: Emulex LPe36000 32Gb PCIe Fibre Channel Adapter on PCI bus 11 device 00 irq 26 port 0 Logical Link Speed: 8000 Mbps PCI resettable After creating 111 vports, server ran out of memory. As server is in hung state, no Crash dump got collected. ** 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/1858840 Title: Vport creation leads to out of memory and server hung on Ubuntu 18.04.3 on Broadcom FC HBAs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856340] [NEW] Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies
Public bug reported: Jeff, Here are the kernel and cli updates we discussed in email related to LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc 12.6.0.x solution. Please pull these into Ubuntu 20.04. Thank you Laurie Expected that ubuntu is pulling in kernel v5.4 as a base. These would go on top of that. Additional patches recommended: ( ) f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2 53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes 44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu 7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared regardless of a Disconnect LS 48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli 64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page 863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow module references c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues -- - nvme cli rev 1.9 or later must be installed in their system as well, so that auto-connect scripts for systemd are installed. see https://github.com/linux-nvme/nvme-cli - nvmetcli rev v0.7 or later should be installed in their system as well see http://git.infradead.org/users/hch/nvmetcli.git ** 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/1856340 Title: Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom Emulex lpfc driver 12.6.0.x dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855303] Re: Update Broadcom Emulex lpfc driver in Ubuntu 20.0.4 to 12.6.0.x
There are many many bugs fixed in the proposed update to 19.04. We are not intending to supply all the logs for every fix we've already resolved. This request was submitted after discussions wiht Jeff Lane. Marking Confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855303 Title: Update Broadcom Emulex lpfc driver in Ubuntu 20.0.4 to 12.6.0.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855303] [NEW] Update Broadcom Emulex lpfc driver in Ubuntu 20.0.4 to 12.6.0.x
Public bug reported: Jeff, Here's the list of committed patches on top of your current git tree that we require for lpfc. Please let me know what other information you require. I'm working with James Smart to obtain the list of additional patch kernel dependencies needed and will file a separate launchpad bug for that. --- Dick Kennedy Wed, Dec 4, 9:23 AM (1 day ago) to me They can skip all the ones that say Merge, they should know that anyway. I went all the way back to 12.2.0.3 so that they can see where their tree stopped. eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list() 6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences 6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity: lpfc_get_scsi_buf_s3(): Null pointer dereferences 61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix lpfc_cpumask_of_node_init() eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel warning triggered by lpfc_sli4_enable_intr() 765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel warning triggered by lpfc_get_sgl_per_hdwq() aff6ab9e7221c1b5d15418419b9797e5badd4aec scsi: lpfc: Update lpfc version to 12.6.0.1 171f6c41949f6e9d5e09dcac842a10bf8dda8dcc scsi: lpfc: Add enablement of multiple adapter dumps dcaa213679387e95a315dca05c57dbb15273703c scsi: lpfc: Change default IRQ model on AMD architectures 93a4d6f40198dffcca35d9a928c409f9290f1fe0 scsi: lpfc: Add registration for CPU Offline/Online events b9da814cd5f5bb93041a6e4dbc9c5149713186ff scsi: lpfc: Clarify FAWNN error message 69641627c653464db46f3e3d8c438349be055670 scsi: lpfc: Sync with FC-NVMe-2 SLER change to require Conf with SLER dda5bdf074da3782ff9e785ee50cd2a3f214d498 scsi: lpfc: Fix dynamic fw log enablement check 2332e6e475b016e2026763f51333f84e2e6c57a3 scsi: lpfc: Fix unexpected error messages during RSCN handling 6c1e803eac846f886cd35131e6516fc51a8414b9 scsi: lpfc: Fix kernel crash at lpfc_nvme_info_show during remote port bounce 6bfb1620829825c01e1dcdd63b6a7700352babd9 scsi: lpfc: Fix configuration of BB credit recovery in service parameters 7cfd5639d99bec0d27af089d0c8c114330e43a72 scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow 7b10db555257d1248398643a23e10cf36b50d516 scsi: lpfc: Make lpfc_debugfs_ras_log_data static c3e5aac3e2f501ad4fcb03fed0e32a6f009faea2 scsi: lpfc: Fix NULL check before mempool_destroy is not needed 5792a0e81678da41f05bb724ebd20f134604fa15 scsi: lpfc: fix spelling error in MAGIC_NUMER_xxx 9e2edb41c3d4cab6da0eedcc07ae04758af62ab8 scsi: lpfc: fix build error of lpfc_debugfs.c for vfree/vmalloc 5314995e370e46ac12d12378544ad4575b6f6672 scsi: lpfc: lpfc_nvmet: Fix Use plain integer as NULL pointer 2c7fb469024f0da98f4d078fcf570786ec87c384 scsi: lpfc: lpfc_attr: Fix Use plain integer as NULL pointer 74acec655f560ef721c1e191732af2bcb094b537 scsi: lpfc: Update lpfc version to 12.6.0.0 b4b3417cf6c8051f9f210cd694e6342fb008795c scsi: lpfc: Add additional discovery log messages 83c6cb1ae8be6948b5fa43b2450a176dba80688b scsi: lpfc: Add FC-AL support to lpe32000 models e7d8595272553c27846946601b72e4c581f9712a scsi: lpfc: Add FA-WWN Async Event reporting b1dfa5411ea440f7a5bd65176259ffb3bfbdecf0 scsi: lpfc: Add log macros to allow print by serverity or verbosity setting 95bfc6d8ad86a76c89f62bb466f740b0fc05a667 scsi: lpfc: Make FW logging dynamically configurable 8156d378c4cbf8ca19df5d8f0c610ce6923b61e2 scsi: lpfc: Revise interrupt coalescing for missing scenarios ea85a20cd54f3b09880f6c08994b059f0d114a11 scsi: lpfc: Remove lock contention target write path 22770cbabf6bb77a397d9f11d41f97667dd0caa2 scsi: lpfc: Slight fast-path performance optimizations f84f8f93f01feb64fdda8dd6c72d1b7dc24ad11d scsi: lpfc: fix coverity error of dereference after null check 91a52b617cdb8bf6d298892101c061d438b84a19 scsi: lpfc: Fix hardlockup in lpfc_abort_handler 324e1c402069e8d277d2a2b18ce40bde1265b96a scsi: lpfc: Fix bad ndlp ptr in xri aborted handling feff8b3d84d3d9570f893b4d83e5eab6693d6a52 scsi: lpfc: Fix SLI3 hba in loop mode not discovering devices 27f3efd637ce4859a44a7ca730c72392b4111c26 scsi: lpfc: Fix lockdep errors in sli_ringtx_put 0a5ce731977da1cc6d8d6d7df01c2e53ebb81796 scsi: lpfc: Fix reporting of read-only fw error errors 97a9ed3b3ae8eae27a231129c0939151879d5f2b scsi: lpfc: fix lpfc_nvmet_mrq to be bound by hdw queue count f7cb0d0945ebc9879aff72cf7b3342fd1040ffaa scsi: lpfc: Make function lpfc_defer_pt2pt_acc static
[Bug 1848797] Re: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found."
Got stuck on this today after upgrading from 19.04 -> 19.10. I do dual- boot Windows. Also Ubuntu is on a 2-disk mdadm RAID array. - I couldn't get boot-repair-disk to work: It wouldn't recognize the internet connection. The LXTerminal it comes with was broken too and didn't respond to keyboard input, so I couldn't fix it. - I couldn't install boot-repair from within a live Ubuntu 19.10 USB: It refused because of an unmet dependency for package boot-sav, even though I'd added the recommended PPA. - I did fix it by installing mdadm (sudo apt install mdadm) from within the live Ubuntu USB, reassembling the RAID array (mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1), mounting it, mounting all the other crap you need to make chroot work, entering chroot, then running update-grub and grub-install a few times on both disks (grub-install /dev/sda1, grub-install /dev/sdb1). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848797 Title: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
Hi Paride, sorry for the late reply - summer holidays. 1). Unfortunately it's a rare one, and I'm not sure exactly what state the service needs to be in, in order to trigger the bug. 2). I believe the pastebin in comment #7 is representative, and that the PIDs don't change, but rather new haproxy processes appear alongside the older ones. I'll certainly confirm and update this bug next time this pops up. It just might be a while before that happens again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629839] Re: pstree reports "/proc/xxxx: No such file or directory"
At the time of filing this bug report, I used to use pstree to determine if a script was called from cron or an interactive terminal, but I found a simpler solution by inspecting the $TERM environment variable. I guess the number of "users affected" dropped by 1 ;) Thanks for your updates guys. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629839 Title: pstree reports "/proc/: No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1629839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629839] Re: pstree reports "/proc/xxxx: No such file or directory"
** Description changed: At random occasions, pstree returns "/proc/: No such file or directory" on stderr. No output on stdout is produced. I can reproduce the problem using this script: #!/bin/bash for i in $(seq 1 1000); do - unset p - p=$(pstree -s -A $$ 2>/dev/null) - if [ "$?" -ne "0" ]; then - p=$(pstree -s -A $$ 2>/dev/null) - echo "Retry: $p" - fi - sleep 0.02 + unset p + p=$(pstree -s -A $$ 2>/dev/null) + if [ "$?" -ne "0" ]; then + p=$(pstree -s -A $$ 2>/dev/null) + echo "Retry: $p" + fi + sleep 0.02 done I have seen this behavior in version 22.15 (shipped with Ubuntu 12.04 LTS, package version 22.15-2ubuntu1.2). The problem does not seem to occur on version 22.21 (shipped with Ubuntu 16.04 LTS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629839 Title: pstree reports "/proc/: No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1629839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
It was marked Incomplete in #4, so there's new detail in #5, #7 and #8 - I just missed re-opening it until now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
** Changed in: haproxy (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 672029] Re: Lubuntu installer crashed when it couldn't write files to disk
Trying to install lubuntu 18.04 LTS on Acer Aspire N15WS from USB. Device /dev/mmcblk0p1, 31 GB apport.log: ERROR: apport (pid 973) Thu Jul 4 23:21:23 2019: called for pid 969, signal 7, core limit 0, dump mode 1 ERROR: apport (pid 973) Thu Jul 4 23:21:23 2019: executable: /usr/sbin/rsyslogd (command line "/usr/sbin/rsyslogd -n") ERROR: apport (pid 973) Thu Jul 4 23:21:23 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 973) Thu Jul 4 23:21:23 2019: wrote report /var/crash/_usr_sbin_rsyslogd.0.crash ERROR: apport (pid 1115) Thu Jul 4 23:21:24 2019: called for pid 1114, signal 7, core limit 0, dump mode 1 ERROR: apport (pid 1115) Thu Jul 4 23:21:24 2019: executable: /usr/sbin/rsyslogd (command line "/usr/sbin/rsyslogd -n") ERROR: apport (pid 1115) Thu Jul 4 23:21:24 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 1115) Thu Jul 4 23:21:24 2019: apport: report /var/crash/_usr_sbin_rsyslogd.0.crash already exists and unseen, doing nothing to avoid disk usage DoS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/672029 Title: Lubuntu installer crashed when it couldn't write files to disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/672029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833803] [NEW] executing grub-install /dev/sda failed
Public bug reported: New install Toshiba Satellite c50 Ubuntu 18.04 The installer fails when executing grub-installer ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CasperVersion: 1.394 Date: Sat Jun 22 15:15:31 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833803 Title: executing grub-install /dev/sda failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1833803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
Never mind, here it is on Xenial: https://pastebin.ubuntu.com/p/3zbQdnTBtF/ There's nothing relevant to haproxy in syslog, but here's the relevant lines from /var/log/haproxy.log: https://pastebin.ubuntu.com/p/HJT3WRc8Dw/ While the proxy processes apparently did stop, the pid 2215 process did not. Running 'systemctl restart haproxy.service' afterwards killed both processes, and started a single fresh one with a new pid, which I think is correct behaviour. So this does indeed seem likely to be down to using 'service' here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
Something similar came up today on a Trusty instance, the WARNING lines are possibly relevant here. To be clear, no certificates were involved in this case, but I did catch the old processes still running after a reload: ubuntu@foo:~$ ps auxf | grep haproxy ubuntu 10790 0.0 0.0 10480 932 pts/2S+ 07:20 0:00 \_ grep --color=auto haproxy haproxy 15581 0.0 0.0 21424 2048 ?Ss May23 1:36 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -D -sf 15502 ubuntu@foo:~$ sudo service haproxy reload * Reloading haproxy haproxy [WARNING] 143/072015 (10813) : config : 'option httplog' not usable with frontend 'foo-lb-2-80' (needs 'mode http'). Falling back to 'option tcplog'. [WARNING] 143/072015 (10815) : config : 'option httplog' not usable with frontend 'foo-lb-2-80' (needs 'mode http'). Falling back to 'option tcplog'. [ OK ] ubuntu@foo:~$ ps auxf | grep haproxy ubuntu 10845 0.0 0.0 10480 932 pts/2S+ 07:20 0:00 \_ grep --color=auto haproxy haproxy 15581 0.0 0.0 21424 2048 ?Ss May23 1:36 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -D -sf 15502 haproxy 10816 0.0 0.0 21016 1536 ?Ss 07:20 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -D -sf 15581 ubuntu@juju-prodstack-ols-assertions-sign-machine-14:~$ In this case though, neither a 'service haproxy restart' nor a stop+start would kill the old process, I had to send it a TERM signal in the end. I understand that Trusty is no longer supported outside of ESM - if this isn't helpful, I'll delete and update if/when I can reproduce on Xenial or later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
This is haproxy 1.6.3-1ubuntu0.2 on Xenial/16.04 running on amd64 hardware. Reproduction steps: 1. Install haproxy and configure it to use a TLS certificate 2. Renew and replace that certificate 3. Run 'service haproxy reload' 4. Sometimes this starts serving the new certificate, sometimes it doesn't ** Changed in: haproxy (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827330] Re: [block layer] please pull below upstream patch to Ubuntu 19.04 kernel
If you provide us a kernel we can test it here or we can ship HBA's for your test environment or both. Laurie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827330 Title: [block layer] please pull below upstream patch to Ubuntu 19.04 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] [NEW] service haproxy reload sometimes fails to pick up new TLS certificates
Public bug reported: I suspect this is the same thing reported on StackOverflow: "I had this same issue where even after reloading the config, haproxy would randomly serve old certs. After looking around for many days the issue was that "reload" operation created a new process without killing the old one. Confirm this by "ps aux | grep haproxy"." https://stackoverflow.com/questions/46040504/haproxy-wont-recognize-new- certificate In our setup, we automate Let's Encrypt certificate renewals, and a fresh certificate will trigger a reload of the service. But occasionally this reload doesn't seem to do anything. Will update with details next time it happens, and hopefully confirm the multiple process theory. ** Affects: haproxy (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/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808437] Re: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability
Closing as fixed in 19.04 and 18.04.3 HWE. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808437 Title: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459692] Re: [MIR] anope
** No longer affects: inspircd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459692 Title: [MIR] anope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anope/+bug/1459692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459692] Re: [MIR] anope
** Also affects: inspircd (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/1459692 Title: [MIR] anope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anope/+bug/1459692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752182] Re: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes
Verified by Broadcom Emulex. Thank you Laurie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752182 Title: [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815151] [NEW] Install failed partway through
Public bug reported: Installing failed about two-thirds way through 'copying files' with "Errno 5 Input/output error". I have done multiple attempts to install and first time I've seen this message. I have a question posted on Ask Ubuntu at https://askubuntu.com/questions/1116536/nzxt-asus-m5a97-r2-0-and-18-04-1 -installation-problems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Thu Feb 7 18:35:59 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity fb=false service rsyslog stop --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815151 Title: Install failed partway through To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1815151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702793] Re: Full backport SRU for unattended-upgrades
lukasz, After a kernel update yesterday I can confirmed that the old kernel was removed and the was no reboot today. apt-cache policy unattended-upgrades unattended-upgrades: Installed: 1.1ubuntu1.18.04.7~16.04.1 Candidate: 1.1ubuntu1.18.04.7~16.04.1 Also installed from xenial-proposed: apt-cache policy update-notifier-common update-notifier-common: Installed: 3.168.10 Candidate: 3.168.10 My system: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.5 LTS Release:16.04 Codename: xenial tag:verification-done ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702793 Title: Full backport SRU for unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1702793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [ubuntu-uk] Encrypted Message
On 01/02/2019 6:09 pm, Paul Sutton wrote: > Hi All > > Sorry if this is off topic, I was not sure where I could ask about this. > > I am not sure if anyone can help with this directly but perhaps as a > community it is an opportunity to engage and perhaps recruit people who > can help with the testing / development process and spread the word on > Ubuntu, Free Software and GNU / Linux in general. > > For the past few years I have been involved in running the Torbay Tech > jam in Paignton, Devon. This simply was a tech event designed to > inspire people to learn about coding, and a place for like minded people > to meet up, chat, share and work on projects etc. This event closed in > 2018, but fast forward to 2019 and it has been re-launched as the South > Devon Tech Jam, with a more formal structure and hopefully we can move > forward in a more positive way. We will be running this once a month. > > I am not sure how the community in the Uk get involved directly with > events. I know there is a need for people to download and test releases > of Ubuntu, report bugs and problems and help fix them. This is a lot of > work,and sometimes complex work but is a very important job. > > One thing I do know is platforms such as Launchpad are both very > comprehensive but quite complex for beginners so having a good grounding > in this would probably save developers and others a lot of time trying > to get the right information out of anyone sending in test results or > bug reports. > > I just wondered if: - > > Anyone would or does do outreach to small events either from the Ubuntu > Community or from Canonical ? Engage with people so that people can > become effective at this job and, perhaps as this will build up > different skill sets, what sort of career path people are able to get in > to, after all having something like Ubuntu Tester / Developer on a CV > should count for something, to a potential employer and this will > actually encourage people to get involved, (even if their initial > motivation is to help) > > As Ubuntu is now more than a desktop / Server OS, but has moved in to > hosting Snaps, Containers etc, would someone be able to give talks on > that too. > > Granted people can look this information up, but there is actually > something effective about face to face engagement, that allows > conversation and networking between people. Also if you talk to 10 > people about Launchpad, there is a chance 1 person won't remember > everything but between those 10 people they should remember different > aspects to then help each other later on. > > There are plenty of opportunities to help but also many barriers to > doing so. If we can find a way to break down those barriers then we > should be able to get more people confident enough to get involved. > > I would perhaps hope to also reach out to local organizations who work > with Young people for example Princes Trust or Young Devon as being > involved with Free software opens up many opportunities. > > As we are only just starting up as an event. I am not looking at > anything such as the above in the immediate future, but thought I would > set the ball rolling here, and just ask, and see what is possible for > later on. > > On a similar note if anyone living in the area would be interested in > such talks this could be a good opportunity to not have to travel too far. > > Thank you > > Regards > > Paul Sutton > Hi Paul, You cover quite a few points in your post but I feel qualified to respond to only a couple of them:- I have run stalls to promoting linux at several events in the north east, with mixed results:- - It was difficult finding enough volunteers to adequately man the stall, one person cannot do the job on his/her own especially if the event lasts two days. - The general public was found to be mostly completely ignorant of linux, but the interest shown was surprisingly good. - Creating the stall required a significant amount of time and money, which am not able to commit to. - I was not able to follow up on the events due to a mixture of personal and family issues. My local LUG has run occasional events, such as promoting security/privacy on line, but these are sporadic rather than structured. Paul, how do you fund and find man power for the Devon event? Secondly, I also find Launchpad quite intimidating to use. I have had a couple of bad (hostile) experiences when trying report bugs. Regards, Barry T -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
[Bug 1808437] Re: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability
Joe Salisbury, Can you please help us get this critical fix into the next 19.04 update? Thank you Laurie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808437 Title: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1808437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808437] Re: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability
Also, if possible and more importantly get this into the existing 18.04 since that's an LTS kernel. thx Laurie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808437 Title: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1808437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] Re: removing kernels should not require a restart afterward
I also can verify 1.1ubuntu1.18.04.7~16.04.1. Yesterday new kernels were installed and a reboot performed. Today old kernel was removed and no reboot performed. This test also used the new update-notifier-common version 3.168.10. Yesterday I received an email telling me that new kernels had been installed and a reboot was performed, as it should, but today I received no email stating the old kernel had been removed. I expected one. Is this a new bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808437] [NEW] Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability
Public bug reported: We are unable to obtain a LPe35000 adapter firmware dump in Ubuntu 18.04. This prevents our debugging customer firmware related issues. This patch was missed during upstream and inbox integration. Our testing for months appeared to have succeeded due to invalid test case. Test case have been corrected to validate fw dump was correctly provided. This fix is very straightforward. Reference upstream submit: James Smart 2018-12-10 19:43:42 PST The patch has been pushed upstream: https://marc.info/?l=linux-scsi=154449943301058=2 Commit is pending from the upstream maintainer. --- Management support for IF_TYPE=6 Symptoms: Firmware dump, loopback, etc are not working on Prism Cause: The driver has a strict check for SLI_INTF_IF_TYPE_2 Fix: Extend the management support for SLI_INTF_IF_TYPE_6 Unit Testing: Ran Onekat and captured firmware dump on Prism ** Affects: linux-aws (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/1808437 Title: Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1808437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] Re: removing kernels should not require a restart afterward
@tjaalton My 16.04 server doesn't have update-notifier installed but does have update-notifier-common installed. If I install update-notifier from propose it will install a slew of other packages. If I install update- notifier-common from propose it just installs the new update-notifier- common version 3.168.10. So should i test update-notifier-common instead of update-notifier? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] Re: removing kernels should not require a restart afterward
Brian, On Dec 3rd I installed from xenial-proposed version 1.1ubuntu1.18.04.7~16.04.0. On Dec 4th unattended-upgrades installed new kernel and rebooted, as it should. Today, Dec 5 unattended-upgrades removed old kernels, which it should do, and then rebooted which it shouldn't do. I have attached unattended-upgrades.log for the relevant days. On a side note unattended-upgrades emailed me after it installed the new kernel on Dec 4th, as it should, but did not email me after removing old kernels on Dec 5th. It should have. Let me know if I can provide any other information or do any further testing. My system is Ubuntu 16.04.5 LTS server. Barry ** Attachment added: "unattended-upgrades.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/5219447/+files/unattended-upgrades.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 743176] Re: Pink layer on taken screenshots (gnome-screenshot)
Hi Folks! Updates on the above. I have not found where BDSword's suggestion for (in comment #31) changing that 200 value in the g_timeout line goes -- it doesn't appear to be a clear text file. Did find using the Metacity option does not have the pink overlay option like the Compiz option does, or at least here. I just started testing with Metacity but so far Compiz and Metacity look the same, so for others if one gives a pink overlay try the other as a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/743176 Title: Pink layer on taken screenshots (gnome-screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/743176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 743176] Re: Pink layer on taken screenshots (gnome-screenshot)
Hi! No idea if this is a significant discovery or a statement of the obvious but will post anyway. Running Ubuntu 16.04 here; for whatever reason for the past roughly six months I have been been having random lock-ups: display freezes except for the mouse point (usually) and the processes (DejaDup, the Virtual Machine running Windows XP, etc.) also usually continue to work. Recently found a work-around: boot, log-out (via the gear icon at the upper right), log back in but first click on the foot icon and select a different option. Here I have Gnome, Gnome Flashback (Compiz), Gnome Flashback (Metacopy), and Ubuntu (default). I selected the ‘Compiz’ one and my lockups magically went away! According to the post I was following this reduced/eliminated video hardware acceleration. ...The side effect, at least for me, is area screen shots (Shift_PrintScreen) now have the pink overlay. What I’m wondering is in Post #31 BDSword suggest an increase of the 200 value in “g_timeout_add (200, emit_select_callback_in_idle, cb_data)”, something about a delay timeout. I’m wondering if there is a connection between this value and it has effectively been slowed down by my changing from the Ubuntu option to the Compiz option, the latter supposedly turning off video acceleration. Just a WAG, but may help the developers and troubleshooters to find the solution. (Now to try increasing that 200 value – to what??! And from my notes what file?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/743176 Title: Pink layer on taken screenshots (gnome-screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/743176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793056] Re: On Ubuntu 18.04 virt-copy-out fails with "tar: This does not look like a tar archive"
Sorry, had a typo in my post above...I appended (>>), I didn't overwrite (>). However, point taken about creating a new file. I've done that and is working. Thanks. For anyone coming from google, the temp solution on Ubuntu 18.04 is: # echo dash > /usr/lib/x86_64-linux-gnu/guestfs/supermin.d/zz-lp-1793056 (Just remember to clean up zz-lp-1793056 once the problem is fixed in future package release). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793056 Title: On Ubuntu 18.04 virt-copy-out fails with "tar: This does not look like a tar archive" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1793056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793056] Re: On Ubuntu 18.04 virt-copy-out fails with "tar: This does not look like a tar archive"
Richard: Thanks for the help in figuring out this easy workaround. Just a note, for me the solution was: # echo dash > /usr/lib/x86_64-linux-gnu/guestfs/supermin.d/packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793056 Title: On Ubuntu 18.04 virt-copy-out fails with "tar: This does not look like a tar archive" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1793056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793056] [NEW] On Ubuntu 18.04 virt-copy-out fails with "tar: This does not look like a tar archive"
Public bug reported: Version-Release number of selected component (if applicable): Tested with: - libguestfs 1.36.13 (Ubuntu 18.04) - tar v1.29 (Ubuntu 18.04) How reproducible: 100% Steps to Reproduce: 1. # virt-builder debian-8 -o deb8.img --no-network 2. # mkdir ~/deb8fs 3. # virt-copy-out -a deb8.img / ~/deb8fs Actual results: libguestfs: error: file receive cancelled by daemon libguestfs: error: tar subprocess failed: tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors See attached debug.txt log that was produced by using "export LIBGUESTFS_DEBUG=1 and LIBGUESTFS_TRACE=1" before running **Note** I have downloaded 1.39.9 from github/libguestfs and this version works without an error in my build directory. It appears that the actual problem is not with "virt-copy-out" specifically, but with the 'guestfish' which it relies on. Running this on 1.36.13 (Ubuntu) fails: # guestfish > add-drive deb8.img > run > tar-out / - | tar tf - libguestfs: error: file receive cancelled by daemon tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors Whereas running the above on guestfish 1.39.9 from git does not produce that error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libguestfs-tools 1:1.36.13-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 17 23:06:00 2018 InstallationDate: Installed on 2018-09-10 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: libguestfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libguestfs (Ubuntu) Importance: Undecided Status: New ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Debug from LIBGUESTFS_DEBUG=1 and LIBGUESTFS_TRACE=1" https://bugs.launchpad.net/bugs/1793056/+attachment/5190033/+files/debug.txt ** Also affects: virt-manager (Ubuntu) Importance: Undecided Status: New ** Summary changed: - On Ubuntu 18.04 virt-copy0out fails with "tar: This does not look like a tar archive" + On Ubuntu 18.04 virt-copy-out fails with "tar: This does not look like a tar archive" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793056 Title: On Ubuntu 18.04 virt-copy-out fails with "tar: This does not look like a tar archive" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1793056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
This is a problem with an Epson GT-1500 in ubuntu 18.04 and the work around does not help. This problem seems to have been here for a long long time. Isn't there anyone to try to fix it?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776012] Re: Sync rkhunter 1.4.6-2 (universe) from Debian unstable (main)
Lukasz, I just installed the proposed version and it ran fine. I didn't see that error message. I will be using this version daily and will let you know if something else pops up, but it seems to be fine. Thanks to all for the work on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776012 Title: Sync rkhunter 1.4.6-2 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rkhunter/+bug/1776012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789133] [NEW] LCDd does not support ConnectionType ftdi with driver hd44780
Public bug reported: With upgrade to lcdproc v0.5.9 hd44780 does not support "ConnectionType=ftdi" Action: update from Ubuntu LTS 16.04.5 to 18.04.1 Observed behaviour: /var/log/syslog kernel: usb 1-1.1: Manufacturer: FTDI kernel: usbcore: registered new interface driver ftdi_sio kernel: usbserial: USB Serial support registered for FTDI USB Serial Device kernel: ftdi_sio 1-1.1:1.0: FTDI USB Serial Device converter detected kernel: usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUSB0 kernel: usb 1-1.1: Manufacturer: FTDI kernel: usbcore: registered new interface driver ftdi_sio kernel: usbserial: USB Serial support registered for FTDI USB Serial Device kernel: ftdi_sio 1-1.1:1.0: FTDI USB Serial Device converter detected kernel: usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUSB0 LCDd: driver_load(name="hd44780", filename="/usr/lib/x86_64-linux-gnu/lcdproc/hd44780.so") LCDd: hd44780: unknown ConnectionType: ftdi LCDd: Driver [hd44780] init failed, return code -1 LCDd: Module /usr/lib/x86_64-linux-gnu/lcdproc/hd4478 could not be loaded LCDd: Could not load driver hd44780 LCDd: There is no output driver LCDd: Critical error while initializing, abort. Expected behaviour: hd44780 driver is loaded with ftdi support, HD44780 connected to FTDI controller is working properly Configuration: LCDd.conf as per 0.5.5 description (partial) ... ## Hitachi HD44780 driver ## [hd44780] # Select what type of connection. See documentation for available types. ConnectionType=ftdi ftdi_mode=4 ftdi_line_EN=0x10 ftdi_line_RS=0x20 ftdi_line_RW=0x40 ... SW / Libraries: lcdproc 0.5.9-2 lcdproc-extra-drivers 0.5.9-2 libftdi1:amd64 0.20-4build3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lcdproc 0.5.9-2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 26 22:32:33 2018 InstallationDate: Installed on 2017-02-24 (548 days ago) InstallationMedia: Mythbuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lcdproc UpgradeStatus: Upgraded to bionic on 2018-08-26 (0 days ago) ** Affects: lcdproc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789133 Title: LCDd does not support ConnectionType ftdi with driver hd44780 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lcdproc/+bug/1789133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [ubuntu-uk] Adobe Flash problem
On 21/08/18 08:27, Paul Sutton wrote: > > > On 21/08/18 06:39, Michael wrot >> Problems watching ITV on 32bit 18.04. Have tried several Adobe flash >> versions, nothing happens after unpack, Which Adobe flash version for >> 18.04 please, how do I do it.Tks, Michael D >> >> > > Which browser are you using, I think firefox relies on an external > plugin for flash to work, however chromium( and i guess chrome) have > better internal support. > > Maybe we need to petition some of these sites and ask them to start > using html5 and dump flash. > > I am not sure on the status, in terms of support of 32 bit flash here > and if the websites are properly supporting the 32 bit versions. > > Paul > I don't think it is the flash player per se, it is the Adobe flash DRM that these sites still use that is unsupported (Channel 4 is the same). As long as Microsoft browsers continue to support this out dated technology by default these companies will see no reason to change. Barry T -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
[Bug 1784191] Re: smartd sends mail before network is up on boot
Andreas, Thanks for your response. I agree with your assessment, this is a corner case. I use ssmtp instead of a MTA because I just want to send an email from a script. As in the case of smartd,I have smartd call my script which sends the test message and also the output of smartctl -H which reports the health of the hard drive. So upon start up I get an email reporting the health of my drives. So this is defiantly a local preference. For completeness I have modified my work around to be more inline with systemd's philosophy. Instead of coping /lib/systemd/system/smartd.service to /etc/systemd/system, I created the directory /etc/systemd/system/smartd.service.d. In that directory I created the file extend.conf with the folowing contents: [Unit] # Added to make sure networking is up before sending mail. # This covers a local corner case during boot. After=network-online.target I wanted to add my change in case someone else had this problem. Thanks again for your help with this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784191 Title: smartd sends mail before network is up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1784191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784193] Re: clamav-daemon fails to start
After a few purges and re-installs I have some insight into this. My goal was to use clamav with Thunderbird's plugin clamrib. In order to do that I need to add to lines two to clamav-daemon.conf. So I thought I needed use dpkg-reconfigure clamav-daemon and pick no for manually configure. That is what added .dpkg.old to extend.conf. So I did a purge and re-install and just added my two lines to clamav-daemon.conf and all is working as expected. According to the first dialog box in dpkg- reconfigure, see the third picture in my attachment notes.txt,I shouldn't have to worry about future upgrades removing my additions to clamav-daemon.conf. As a side note, I tried using dpkg-reconfigure and pick yes to handle the configuration automatically. I picked all the default values until it started looping between the two dialog boxes shown at the top of my attachment. I don't think I need to use dpkg-reconfigure. At this point I'm not sure if I have discovered a bug or just didn't understand what I was doing. In any case thank you for your help and time. ** Attachment added: "Notes.txt" https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1784193/+attachment/5170165/+files/Notes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784193 Title: clamav-daemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1784193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784193] Re: clamav-daemon fails to start
Andreas, In /etc/systemd/system/clamav-daemon.service.d I have extend.conf.dpkg.old instead of extend.conf. That is where I got the two lines ExecStartPre=-/bin/mkdir /run/clamav ExecStartPre=/bin/chown clamav /run/clamav from. Tjat would explain why i don't have the Drop-in line. The packages I have are ii clamav 0.100.1+dfsg-1ubuntu0.18.04.2 amd64anti-virus utility for Unix - command-line interface ii clamav-base0.100.1+dfsg-1ubuntu0.18.04.2 all anti-virus utility for Unix - base package ii clamav-daemon 0.100.1+dfsg-1ubuntu0.18.04.2 amd64anti-virus utility for Unix - scanner daemon ii clamav-freshclam 0.100.1+dfsg-1ubuntu0.18.04.2 amd64anti-virus utility for Unix - virus database update utility ii libclamav7:amd64 0.100.1+dfsg-1ubuntu0.18.04.2 amd64anti-virus utility for Unix - library Which appear to be the same as yours. Looking in /var/log/apt/term file I see the line id:'clamav': no such user, but no other errors. I would be glad to uninstall and re-install to see if /etc/systemd/system/clamav-daemon.service/extend.conf.dpkd.old has the right file name if you like. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784193 Title: clamav-daemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1784193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784193] Re: clamav-daemon fails to start
I was able to fix this by copying /lib/systemd/system/clamav-daemon.service to /etc/systemd/system/clamav.service and adding the two lines: ExecStartPre=-/bin/mkdir /run/clamav ExecStartPre=/bin/chown clamav /run/clamav to the top of the [Service] section. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784193 Title: clamav-daemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1784193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784193] [NEW] clamav-daemon fails to start
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy clamav clamav: Installed: 0.100.1+dfsg-1ubuntu0.18.04.2 Expected clamav-daemon to be running. What happens: clamav-daemon fails to start sudo systemctl status clamav-daemon ● clamav-daemon.service - Clam AntiVirus userspace daemon Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-07-28 19:53:14 CDT; 6s ago Docs: man:clamd(8) man:clamd.conf(5) https://www.clamav.net/documents/ Process: 3589 ExecStart=/usr/sbin/clamd --foreground=true (code=exited, status=1/FAILURE) Main PID: 3589 (code=exited, status=1/FAILURE) Jul 28 19:53:04 Bionic-Desktop systemd[1]: Started Clam AntiVirus userspace daemon. Jul 28 19:53:14 Bionic-Desktop clamd[3589]: Sat Jul 28 19:53:14 2018 -> !LOCAL: Could not create socket directory: /var/run/clamav: Permission denied Jul 28 19:53:14 Bionic-Desktop clamd[3589]: Sat Jul 28 19:53:14 2018 -> !LOCAL: Socket file /var/run/clamav/clamd.ctl could not be bound: No such file or directory Jul 28 19:53:14 Bionic-Desktop clamd[3589]: Sat Jul 28 19:53:14 2018 -> !Can't unlink the socket file /var/run/clamav/clamd.ctl Jul 28 19:53:14 Bionic-Desktop systemd[1]: clamav-daemon.service: Main process exited, code=exited, status=1/FAILURE Jul 28 19:53:14 Bionic-Desktop systemd[1]: clamav-daemon.service: Failed with result 'exit-code'. What other information can I provide? ** Affects: clamav (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/1784193 Title: clamav-daemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1784193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784191] [NEW] smartd sends mail before network is up on boot
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy smartmontools smartmontools: Installed: 6.5+svn4324-1 Candidate: 6.5+svn4324-1 Version table: *** 6.5+svn4324-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Expected behavior: smartd sends a test email on boot. What happens: No mail is recieved. sSMTP logs "Unable to locate Mail server" and "cannot open mailserver:25". I'm using the same smartd.conf and my script smartd calls that I used on 14.04, which worked flawlessly. Work around: I had my script sleep 5 seconds before sending the mail. This worked fine leading me to believe smartd is calling my script before networking is up. But this is not an elegant solution. So I copied /lib/systemd/system/smartd.service to /etc/systemd/system/smartd.service and add the line "After=network-online.target"This worked fine. So the full smartd.sevice unit is: [Unit] Description=Self Monitoring and Reporting Technology (SMART) Daemon Documentation=man:smartd(8) man:smartd.conf(5) After=network-online.target [Service] EnvironmentFile=-/etc/default/smartmontools ExecStart=/usr/sbin/smartd -n $smartd_opts ExecReload=/bin/kill -HUP $MAINPID StandardOutput=syslog [Install] WantedBy=multi-user.target I haven't got any other machines to test this on. So I hope the report will help some one else ** Affects: smartmontools (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/1784191 Title: smartd sends mail before network is up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1784191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783632] Re: clamav-daemon won't start after upgrade to 0.100.1+dfsg, complaining of "Unknown option StatsEnabled"
Marc, I manually changed clamd.conf. There was no indication from the installer that there was any changes to clamd.conf. The only indication I had was when the Thunderbird extension, clamrib, complained it couldn't connect to clamd. I checked clamd and indeed it was not running. I tried to restart it using the System V init script. It complained about an unknown option StatsEnabled. So I commented out StatsEnabled. and tried to start clamd. It compained about the option StatsTimeout. So I commented it out and repeated this process until clamd started. Releasing an update warning about changes for user modified clamd.conf should be a good solution. Thanks for the prompt work on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783632 Title: clamav-daemon won't start after upgrade to 0.100.1+dfsg, complaining of "Unknown option StatsEnabled" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1783632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
