[Bug 1840821] Re: bionic/linux-azure-edge: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840802 packages: meta: linux-meta-azure-edge - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:21 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 21. August 2019 05:36 UTC reason: - prepare-package: Holding -- waiting for master bug - prepare-package-meta: Holding -- waiting for master bug + prepare-package-meta: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840821 Title: bionic/linux-azure-edge: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836308] Re: Unhide Nvidia HDA audio controller
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836308 Title: Unhide Nvidia HDA audio controller To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Wednesday, 21. August 2019 04:26 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + prepare-package-meta: Stalled -- package tag not yet published + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840802 Title: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581711] Re: 024C:B723 Need support for Realtek Wifi card rtl8723bs
Mainline kernel has rtl8723bs support for a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581711 Title: 024C:B723 Need support for Realtek Wifi card rtl8723bs To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1581711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838208] Re: Wifi stops responding sporadically on lenovo-yoga-720-15ikb
Can you please still attach dmesg with latest kernel/firmware when the issue happens? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838208] Re: Wifi stops responding sporadically on lenovo-yoga-720-15ikb
If restarting network-manager can fix the issue then it's less likely to be a kernel bug. ** Also affects: network-manager (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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS
I can't installed ubuntu 18.04.x LTS release with error. of HASH SUM MISMATCH DURING INSTALLATION. I have tried to install it 5 times. But same error in my machine. ** Attachment added: "Installation_Error.rar" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/+attachment/5283617/+files/Installation_Error.rar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785778 Title: Hash Sum mismatch Ubuntu Server 18.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS
** Changed in: apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785778 Title: Hash Sum mismatch Ubuntu Server 18.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
** Description changed: From bug: https://bugs.launchpad.net/bugs/1840511 - clockhouse builds test started failing because of the presence of stderr + clickhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840511] Re: Eoan FTBFS with gcc-9 and MySQL 8
** Changed in: clickhouse (Ubuntu Eoan) Status: Fix Released => In Progress ** Changed in: mysql-8.0 (Ubuntu Eoan) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840511 Title: Eoan FTBFS with gcc-9 and MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clickhouse/+bug/1840511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840816] Re: disco/linux: 5.0.0-27.28 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:31 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed + promote-to-proposed: Pending -- builds not complete in ppa meta:failed trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840816 Title: disco/linux: 5.0.0-27.28 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840823] Re: bionic/linux-gke-5.0: 5.0.0-1014.14~18.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840822 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1840808 packages: main: linux-gke-5.0 meta: linux-meta-gke-5.0 signed: linux-signed-gke-5.0 - phase: Ready for Packaging - phase-changed: Wednesday, 21. August 2019 03:43 UTC + phase: Packaging + phase-changed: Wednesday, 21. August 2019 04:40 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-gke-5.0/gke-kernel: bug 1840822 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840823 Title: bionic/linux-gke-5.0: 5.0.0-1014.14~18.04.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840803] Re: disco/linux-azure: 5.0.0-1018.19 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:41 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait trackers: bionic/linux-azure: bug 1840802 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840803 Title: disco/linux-azure: 5.0.0-1018.19 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840823] Re: bionic/linux-gke-5.0: 5.0.0-1014.14~18.04.2 -proposed tracker
** Summary changed: - bionic/linux-gke-5.0: -proposed tracker + bionic/linux-gke-5.0: 5.0.0-1014.14~18.04.2 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840823 Title: bionic/linux-gke-5.0: 5.0.0-1014.14~18.04.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840875] [NEW] genaral Swap for errors
Public bug reported: I have problem with my snap packages I have problem with DPKG being not able to do upgrades I have problem with my Livepatch since I can't sign in to it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-59.66-generic 4.15.18 Uname: Linux 4.15.0-59-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 21 07:24:59 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-59-generic root=UUID=fbe95d05-80c6-41a8-9680-336df596acb7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 033MX4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/26/2012:svnDellInc.:pnInspiron3521:pvrA02:rvnDellInc.:rn033MX4:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840875 Title: genaral Swap for errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1840875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Holding -- master bug not ready for proposed variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840796] Re: sound not working in 4.15.0-58, but does in 4.15.0-55
Speakers in the laptop don't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840796 Title: sound not working in 4.15.0-58, but does in 4.15.0-55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Packaging - phase-changed: Wednesday, 21. August 2019 03:43 UTC + phase: Packaging + phase-changed: Wednesday, 21. August 2019 04:26 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840802 Title: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839983] Re: xenial/linux-aws-hwe: 4.15.0-1046.48~16.04.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839985 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 04:10 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839983 Title: xenial/linux-aws-hwe: 4.15.0-1046.48~16.04.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-azure: -proposed tracker + bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840802 Title: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840511] Re: Eoan FTBFS with gcc-9 and MySQL 8
Well it looks like clickhouse is an amd64 only package, I have added more architectures in the PPA, please ignore those building errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840511 Title: Eoan FTBFS with gcc-9 and MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clickhouse/+bug/1840511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
The attachment "cpuinfo_0.0~git20190201.d5e37ad-1ubuntu1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840858] Re: installer crashed
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD). You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM. You might also retry your installation with new media. In the event that is is not in fact an error with your installation media please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete ** Tags added: ident-mismatch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840858 Title: installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1840858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1527680] Re: [needs-packaging] spotify
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1527680 Title: [needs-packaging] spotify To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1527680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833512] Re: Wifi password dialog popup don't take more the 20 ASCII-encoded characters
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833512 Title: Wifi password dialog popup don't take more the 20 ASCII-encoded characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1833512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833197] Re: crashes when creating annotations (Segmentation fault (core dumped))
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833197 Title: crashes when creating annotations (Segmentation fault (core dumped)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840874] [NEW] Mono Runtime error because of bug in LargeArrayBuilder in Mono 5.18
Public bug reported: This bug happens in Mono 5.18, in Ubuntu Disco (19.04). I am using the package 5.18.0.240+dfsg-2ubuntu2. You can reproduce the bug with the attached test program. It has been fixed upstream in Mono 5.20, with quite a simple patch. I got the patch merged into the Debian Mono package: https://salsa.debian.org/dotnet-team/mono/merge_requests/3 Is there any chance, this patch could be applied to the next Ubuntu release (19.10), or even Ubuntu Disco (19.04)? See for more details: https://bugzilla.redhat.com/show_bug.cgi?id=1704847 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919194 ** Affects: mono (Ubuntu) Importance: Undecided Status: New ** Attachment added: "reproduce the bug with this code" https://bugs.launchpad.net/bugs/1840874/+attachment/5283599/+files/file_1704847.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840874 Title: Mono Runtime error because of bug in LargeArrayBuilder in Mono 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1840874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839983] Re: xenial/linux-aws-hwe: 4.15.0-1046.48~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839985 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe - phase: Packaging - phase-changed: Friday, 16. August 2019 18:50 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 21. August 2019 04:10 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839983 Title: xenial/linux-aws-hwe: 4.15.0-1046.48~16.04.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840808] Re: disco/linux-gcp: 5.0.0-1015.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840808 Title: disco/linux-gcp: 5.0.0-1015.15 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued + promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840872] [NEW] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g5: libvirt fails to check for duplicate address in hotplug xml and causes the guest to go to shutoff state
Public bug reported: == Comment: #0 - INDIRA P. JOGA - 2018-05-24 09:32:53 == Problem Description: === libvirt fails to check for duplicate address in hotplug xml & error out before even trying to hotplug anything. Steps to re-create: 1. boslcp4 is up with BMC:1.20 & PNOR: 20180420 levels 2. Guest is up with kernel root@boslcp3g5:~# uname -a Linux boslcp3g5 4.4.0-122-generic #146-Ubuntu SMP Mon Apr 23 15:33:25 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g5:~# uname -r 4.4.0-122-generic 3. boslcp3g5 guest is running with LTP run (45 hours) & stress-ng aio class ( 15 minutes). 4. Hotplug xml root@boslcp3:/home# cat hp-disk.xml 5.Tried hotplug with duplicate address root@boslcp3:/home# virsh attach-device boslcp3g5 hp-disk.xml --live error: Failed to attach device from hp-disk.xml error: internal error: unable to execute QEMU command 'device_add': Duplicate ID 'scsi0-0-0-2' for device root@boslcp3:/home# root@boslcp3:/home# virsh list --all IdName State 3 boslcp3g2 running 4 boslcp3g3 running 7 boslcp3g4 running - boslcp3g1 shut off - boslcp3g5 shut off 6. Libvirt fails to check the duplicate address in hotplug xml & error before even trying to hotplug anything == Comment: #5 - Daniel Henrique Barboza - 2019-03-26 15:43:55 == The fix for this bug was pushed upstream: commit f1d658531c7b23b8796a0faa4411c3531996 Author: Daniel Henrique Barboza Date: Fri Mar 15 18:06:45 2019 -0300 domain_conf: check device address before attach After this patch, Libvirt is checking for duplicated address before trying to do hotplug operations. ** Affects: libvirt (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-168186 severity-high targetmilestone-inin--- ** Tags added: architecture-ppc64le bugnameltc-168186 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => libvirt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840872 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g5: libvirt fails to check for duplicate address in hotplug xml and causes the guest to go to shutoff state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1840872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
PPA containing clickhouse build (LP: #1840511) and cpuinfo with this fix: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1840511 Debdiff with proposed changes are attached to this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840511] Re: Eoan FTBFS with gcc-9 and MySQL 8
** Patch added: "clickhouse_18.16.1+ds-4ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1840511/+attachment/5283598/+files/clickhouse_18.16.1+ds-4ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840511 Title: Eoan FTBFS with gcc-9 and MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clickhouse/+bug/1840511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840511] Re: Eoan FTBFS with gcc-9 and MySQL 8
I guess if tests make the build hard to happen we can just enable: #export DEB_BUILD_OPTIONS+=nocheck in debian/rules but, for now, I tried to avoid that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840511 Title: Eoan FTBFS with gcc-9 and MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clickhouse/+bug/1840511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840511] Re: Eoan FTBFS with gcc-9 and MySQL 8
PPA containing clickhouse build and cpuinfo, with needed fix from (LP: #1840847): https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1840511 Debdiff with proposed changes are attached to this bug. ** Patch removed: "0001-G-9-crashes-returning-exception-using-true-false-syn.patch" https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1840511/+attachment/5283438/+files/0001-G-9-crashes-returning-exception-using-true-false-syn.patch ** Patch removed: "0002-MySQL-8-integration-requires-previous-declaration-ch.patch" https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1840511/+attachment/5283439/+files/0002-MySQL-8-integration-requires-previous-declaration-ch.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840511 Title: Eoan FTBFS with gcc-9 and MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clickhouse/+bug/1840511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840511] Re: Eoan FTBFS with gcc-9 and MySQL 8
Fixing libcpuid I was able to run all tests and, apart from those already marked as buggy and/or flaky, in debian/rules, I'm adding those extra for now: # # LP: #1840511 cleanup # # libm precision on exp() related functions SKIP_TESTS+=00536 00534 # long_http_bufferization ? SKIP_TESTS+=00429 # system processes port ? (bind: error already in use) SKIP_TESTS+=00379 # clickhouse-clang not found SKIP_TESTS+=00281 # end of LP: #1840511 cleanup They don't seem to be indicating real issues with this build of clickhouse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840511 Title: Eoan FTBFS with gcc-9 and MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clickhouse/+bug/1840511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840803] Re: disco/linux-azure: 5.0.0-1018.19 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:41 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: bionic/linux-azure: bug 1840802 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840803 Title: disco/linux-azure: 5.0.0-1018.19 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840802] Re: bionic/linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:18 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 21. August 2019 03:43 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840802 Title: bionic/linux-azure: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840823] Re: bionic/linux-gke-5.0: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840822 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1840808 packages: main: linux-gke-5.0 meta: linux-meta-gke-5.0 signed: linux-signed-gke-5.0 - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:21 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 21. August 2019 03:43 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-gke-5.0/gke-kernel: bug 1840822 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840823 Title: bionic/linux-gke-5.0: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840808] Re: disco/linux-gcp: 5.0.0-1015.15 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Packaging - phase-changed: Tuesday, 20. August 2019 20:50 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840808 Title: disco/linux-gcp: 5.0.0-1015.15 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-kvm meta: linux-meta-kvm - phase: Packaging - phase-changed: Tuesday, 20. August 2019 21:15 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840816] Re: disco/linux: 5.0.0-27.28 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:31 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840816 Title: disco/linux: 5.0.0-27.28 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840806] Re: bionic/linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:19 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 21. August 2019 03:43 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840806 Title: bionic/linux-gcp: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840803] Re: disco/linux-azure: 5.0.0-1018.19 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Tuesday, 20. August 2019 21:05 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 21. August 2019 03:41 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: bionic/linux-azure: bug 1840802 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840803 Title: disco/linux-azure: 5.0.0-1018.19 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840185] Re: simple-scan app closes with a big delay
This is the SANE drivers taking a long time to shutdown. Simple Scan waits for them to complete, in case there is important things that need to be done. I don't know which driver takes a long time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840185 Title: simple-scan app closes with a big delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1840185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840816] Re: disco/linux: 5.0.0-27.28 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Packaging - phase-changed: Tuesday, 20. August 2019 19:06 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 21. August 2019 03:31 UTC reason: - prepare-package-lrm: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840816 Title: disco/linux: 5.0.0-27.28 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840619] Re: skb_warn_bad_offload kernel splat due to CHECKSUM target not compatible with GSO skbs
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1840619 [Impact] In environments which have CHECKSUM iptables rules set, the following kernel call trace will be created when a GSO skb is processed by the CHECKSUM target: WARNING: CPU: 34 PID: 806048 at /build/linux-zdslHp/linux-4.4.0/net/core/dev.c:2456 skb_warn_bad_offload+0xcf/0x110() qr-f78bfdf7-fe: caps=(0x0fdb58e9, 0x0fdb58e9) len=1955 data_len=479 gso_size=1448 gso_type=1 ip_summed=3 CPU: 34 PID: 806048 Comm: haproxy Tainted: GW OE 4.4.0-138-generic #164-Ubuntu Call Trace: dump_stack+0x63/0x90 warn_slowpath_common+0x82/0xc0 warn_slowpath_fmt+0x5c/0x80 ? ___ratelimit+0xa2/0xe0 skb_warn_bad_offload+0xcf/0x110 skb_checksum_help+0x185/0x1a0 checksum_tg+0x22/0x29 [xt_CHECKSUM] ipt_do_table+0x301/0x730 [ip_tables] ? ipt_do_table+0x349/0x730 [ip_tables] iptable_mangle_hook+0x39/0x107 [iptable_mangle] nf_iterate+0x68/0x80 nf_hook_slow+0x73/0xd0 ip_output+0xcf/0xe0 ? __ip_flush_pending_frames.isra.43+0x90/0x90 ip_local_out+0x3b/0x50 ip_queue_xmit+0x154/0x390 __tcp_transmit_skb+0x52b/0x9b0 tcp_write_xmit+0x1dd/0xf50 __tcp_push_pending_frames+0x31/0xd0 tcp_push+0xec/0x110 tcp_sendmsg+0x749/0xba0 inet_sendmsg+0x6b/0xa0 sock_sendmsg+0x3e/0x50 SYSC_sendto+0x101/0x190 ? __sys_sendmsg+0x51/0x90 SyS_sendto+0xe/0x10 entry_SYSCALL_64_fastpath+0x22/0xc1 The CHECKSUM target does not support GSO skbs, and when a GSO skb is passed to skb_checksum_help(), it errors out and skb_warn_bad_offload() is called. The above call trace was found in a customer environment which has an Openstack deployment, with the following sorts of iptables rules set: -A neutron-l3-agent-POSTROUTING -o qr-+ -p tcp -m tcp --sport 9697 -j CHECKSUM --checksum-fill -A neutron-dhcp-age-POSTROUTING -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill This was causing haproxy running on the node to crash and restart every time a GSO skb was processed by the CHECKSUM target. I recommend reading the netdev mailing list thread for more details: https://www.spinics.net/lists/netdev/msg517366.html [Fix] This was fixed in 4.19 upstream with the below commit: commit 10568f6c5761db24249c610c94d6e44d5505a0ba Author: Florian Westphal Date: Wed Aug 22 11:33:27 2018 +0200 Subject: netfilter: xt_checksum: ignore gso skbs This commit adds a check to see if the current skb is a gso skb, and if it is, skips skb_checksum_help(). It then continues on to check if the packet uses udp, and if it does, exits early. Otherwise it prints a single warning that CHECKSUM should be avoided, and if really needed, only for use with outbound udp. Note, 10568f6c5761db24249c610c94d6e44d5505a0ba was included in upstream stable version 4.18.13, and was backported to bionic in 4.15.0-58.64 by LP #1836426. This patch required minor backporting for 4.4, by slightly adjusting the context in the final patch hunk. [Testcase] You can reproduce this by adding the following iptables rule to the mangle table: -A POSTROUTING -p tcp -m tcp --sport 80 -j CHECKSUM --checksum-fill and running traffic over port 80 with incorrect checksums in the ip header. I built a test kernel, which is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf216537-test For unpatched kernels, this causes the process which was handeling the socket to crash, as seen by haproxy crashing on a node in production which hits this issue. - On patched kernels you see the warning printed to dmesg and no crashes - occur. + On patched kernels you see the below warning printed to dmesg and no + crashes occur. + + xt_CHECKSUM: CHECKSUM should be avoided. If really needed, restrict + with "-p udp" and only use in OUTPUT [Regression Potential] The changes are limited only to users which have CHECKSUM rules enabled in their iptables configs. Openstack commonly configures such rules on deployment, even though they are not necessary, as almost all packets have their checksum calculated by NICs these days, and CHECKSUM is only around to service old dhcp clients which would discard UDP packets with empty checksums. This commit was selected for upstream -stable 4.18.13, and has made its way into bionic 4.15.0-58.64 by LP #1836426. There have been no reported problems and those kernels would have had sufficient testing with Openstack and its configured iptables rules. If any users are affected by regression, then they can simply delete any CHECKSUM entries in their iptables configs. ** Description changed: BugLink: https://bugs.launchpad.net/bugs/1840619 [Impact] In environments which have CHECKSUM iptables rules set, the following kernel call trace will be created when a GSO skb is processed by the CHECKSUM target: WARNING: CPU: 34
[Bug 1840867] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1840867 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840867 Title: pthread test from ubuntu_stress_smoke_test hang with X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792294] Re: Generates unbootable initrd: Out of Memory Error
I mean the kernel is bootable is you install 0.131ubuntu15 and regenerate the initramfs. They have a later version now, hopefully it fixes the issues as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792294 Title: Generates unbootable initrd: Out of Memory Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840867] [NEW] pthread test from ubuntu_stress_smoke_test hang with X
Public bug reported: Issue found on the following nodes: Power8 "modoc" 2 failures out of 2 attempts i386 "pepe" 2 failures out of 2 attempts ARM64 "wright" 1 failure out of 1 attempt Syslog from node pepe: Aug 19 05:51:55 pepe stress-ng: invoked with './stress-n' by user 0 Aug 19 05:51:55 pepe stress-ng: system: 'pepe' Linux 4.4.0-160-generic #188-Ubuntu SMP Wed Aug 14 04:17:20 UTC 2019 i686 Aug 19 05:51:55 pepe stress-ng: memory (MB): total 3991.91, free 3669.34, shared 2.11, buffer 132.39, swap 1023.99, free swap 970.16 Aug 19 05:51:55 pepe stress-ng: info: [25162] dispatching hogs: 4 pthread Aug 19 05:52:00 pepe stress-ng: info: [25164] stress-ng-pthread: 99.75% of iterations could not reach requested 1024 threads (instance 1) Aug 19 05:54:49 pepe systemd[1]: Starting Cleanup of Temporary Directories... Aug 19 05:54:49 pepe systemd-tmpfiles[28049]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Aug 19 05:54:49 pepe systemd[1]: Started Cleanup of Temporary Directories. Aug 19 06:03:16 pepe systemd[1]: Time has been changed Aug 19 06:03:16 pepe systemd[2037]: Time has been changed Aug 19 06:16:05 pepe systemd[2037]: Time has been changed Syslog from node wright: Aug 19 21:36:28 wright-kernel stress-ng: invoked with './stress-n' by user 0 Aug 19 21:36:28 wright-kernel stress-ng: system: 'wright-kernel' Linux 4.15.0-59-generic #66~16.04.1-Ubuntu SMP Wed Aug 14 15:43:01 UTC 2019 aarch64 Aug 19 21:36:28 wright-kernel stress-ng: memory (MB): total 128876.61, free 126748.83, shared 9.28, buffer 63.37, swap 9215.99, free swap 9215.99 Aug 19 21:36:28 wright-kernel stress-ng: info: [16352] dispatching hogs: 4 pthread Aug 19 21:36:28 wright-kernel stress-ng: info: [16352] cache allocate: using defaults, can't determine cache details from sysfs Aug 19 21:39:19 wright-kernel systemd[3731]: Time has been changed Aug 19 21:39:19 wright-kernel rsyslogd-2007: action 'action 11' suspended, next retry is Mon Aug 19 21:40:19 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Aug 19 21:39:19 wright-kernel systemd[1]: Time has been changed Aug 19 22:00:55 wright-kernel systemd[3731]: Time has been changed Aug 19 22:00:55 wright-kernel rsyslogd-2007: action 'action 11' suspended, next retry is Mon Aug 19 22:01:55 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Aug 19 22:00:55 wright-kernel systemd[1]: Time has been changed Aug 19 22:13:47 wright-kernel systemd[1]: Time has been changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-160-generic 4.4.0-160.188 ProcVersionSignature: Ubuntu 4.4.0-160.188-generic 4.4.186 Uname: Linux 4.4.0-160-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 19 05:45 seq crw-rw 1 root audio 116, 33 Aug 19 05:45 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-160-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.19 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Aug 21 02:27:28 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0 ProcLoadAvg: 0.00 0.00 0.00 1/1313 25458 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 /home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/swap.img file 1048512 0 -2 ProcVersion: Linux version 4.4.0-160-generic (buildd@bos02-ppc64el-002) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10) ) #188-Ubuntu SMP Wed Aug 14 04:17:46 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.4.0-160-generic N/A linux-backports-modules-4.4.0-160-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.694 GHz (cpu 2) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Colin Ian King (colin-king) Status: New ** Tags:
[Bug 1840511] Re: Eoan FTBFS with gcc-9 and MySQL 8
Instead of reverting the libcpuid change (done in Debian and not upstream) I will make libcpuid not to stderr for warnings for now: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840847 And this might fix comment #14 issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840511 Title: Eoan FTBFS with gcc-9 and MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clickhouse/+bug/1840511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
** Patch added: "cpuinfo_0.0~git20190201.d5e37ad-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840847/+attachment/5283577/+files/cpuinfo_0.0~git20190201.d5e37ad-1ubuntu1.debdiff ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Description changed: From bug: https://bugs.launchpad.net/bugs/1840511 clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). + FOR THE KERNEL TEAM: + Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
I'm changing CPUINFO_LOG_LEVEL from warning to error only to mitigate this issue. Unfortunately this is the best way to address: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1840511 Right now, allowing clickhouse build to succeed and unblocking MySQL 8 upgrade. ** Changed in: cpuinfo (Ubuntu) Status: New => In Progress ** Changed in: cpuinfo (Ubuntu) Importance: Undecided => Medium ** Changed in: cpuinfo (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840857] Re: Couldn't run grub-install on created EFI partition. Doesn't like boot on an NTFS
Thank you for taking the time to report this bug and helping to make Ubuntu better. This is not a bug I suspect. The EFI spec states the format should be FAT12, FAT16, or FAT32 as I read https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf#G17.1019485 The bug is more whomever installed your system in a non-EFI specification compatible mode, not with Ubuntu which is following the EFI specifications. The following is quoted from EFI specification link provided :- 13.3 File System Format The file system supported by the Extensible Firmware Interface is based on the FAT file system. EFI defines a specific version of FAT that is explicitly documented and testable. Conformance to the EFI specification and its associate reference documents is the only definition of FAT that needs to be implemented to support EFI. To differentiate the EFI file system from pure FAT, a new partition file system type has been defined. EFI encompasses the use of FAT32 for a system partition, and FAT12 or FAT16 for removable media. The FAT32 system partition is identified by an OSType value other than that used to identify previous versions of FAT. This unique partition type distinguishes an EFI defined file system from a normal FAT file system. The file system supported by EFI includes support for long file names. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840857 Title: Couldn't run grub-install on created EFI partition. Doesn't like boot on an NTFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1840857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840796] Re: sound not working in 4.15.0-58, but does in 4.15.0-55
Which audio device deosn't work under -58 kernel? Intel hdmi audio, NV hdmi audio, speaker or headphone? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840796 Title: sound not working in 4.15.0-58, but does in 4.15.0-55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Running the program in Windows gave me a Blue Screen Error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840697] Re: Ubuntu installer mishandling of previously existing EFI partitions
** Description changed:
Issue seen on Ubuntu 19.04 (workstation); might present in previous
versions ?
Previous situation ("pre-bug") :
/dev/sda = WDC disk 2TB
/dev/sdb = SSD disk, 256GB
boot loader in /dev/sda
Ubuntu 19.04 was installed before Windows as I wanted it on the SSD
drive for most of it; slow I-Os went on the WDC disk.
disk layout:
/dev/sda1 = Windows Recovery partition, 500MB
/dev/sda2 = Windows EFI partition, 100MB
/dev/sda3 = Windows NTFS OS + Data partition, 400G
/dev/sda4 = Linux LVM2. remainder of disk
/dev/sdb1 = ubuntu /boot partition, xfs, 512MB
/dev/sdb2 = ubuntu /boot/efi, 350MB
/dev/sdb3 = Linux LVM2, remainder of disk
1. Ubuntu and Windows both boot just fine, Windows using /dev/sda2 as
its EFI partition, Ubuntu using /dev/sdb2 for its EFI partition.
2. For some reason I needed to re-install Ubuntu exactly where it was. I
slapped my DVD in the reader, booted the installer, and started. At the
partman section, I've left off everything Windows-related on /dev/sda,
making sure that /dev/sda2 was left at "Do not use partition". As
/dev/sd[ab]2 was already tagged as "EFI partition", and that I've left
/dev/sda2 at "Do not use", I was assuming the installer would use
/dev/sdb2 as /boot/efi.
Expected result is as above. Actual result follows.
3. End result: the installer leaves off /dev/sdb2 and overwrites
/dev/sda2 even with a "Do not use partition flag". Subsequent boots
would not see the Windows OS installed as its EFI partition had been
- overwritten by the installer.
+ overwritten by the installer. Looks like that the installer (or whatever
+ its subcomponent) grabs the first EFI partition it sees and uses it.
- 4. To fix:
+ 4. To fix (workaround):
a=> mount -t vfat /dev/sdb2 /mnt && cd /boot/efi && tar cf - . | (cd /mnt ;
tar xf -)
- b=> cd / && umount /mnt
- c=> find a win10 boot cd, go in repair mode, reinstall EFI code+files in
/dev/sda2
- d=> reboot in Ubuntu, os-prober && update-grub
+ b=> find a win10 boot cd, go in repair mode, reinstall EFI code+files in
/dev/sda2
+ c=> reboot in Ubuntu, os-prober && update-grub
Further observations:
- Other installers (Fedora's anaconda to name one) would let you specify the
mountpoint of an EFI partition (yes, it should always be /boot/efi). This is
not foolproof, I agree, but at least it'd leave no place to doubt on setups
similar as mine as which EFI partition Ubuntu is directed to use.
+ Other installers (Fedora's anaconda, to name one) would let you specify the
mountpoint of an EFI partition (yes, it should always be /boot/efi). This is
not foolproof, I agree, but at least it'd leave no place to doubt on setups
similar as mine on which EFI partition Ubuntu is directed to use.
--Jeff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840697
Title:
Ubuntu installer mishandling of previously existing EFI partitions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1840697/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840697] Re: Ubuntu installer mishandling of previously existing EFI partitions
Bug replicated on Ubuntu 18.10 this evening. Same result, same outcome, same workaround -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840697 Title: Ubuntu installer mishandling of previously existing EFI partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1840697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
You said the internal mic works well under windows10, so please run this dump program under windows10, then upload the dump file to launchpad, maybe we can find some difference from the linux. ** Attachment added: "RtHDDump_V226.zip" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+attachment/5283575/+files/RtHDDump_V226.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836916] Re: alsa/hdmi: add icelake hdmi audio support for a Dell machine
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836916 Title: alsa/hdmi: add icelake hdmi audio support for a Dell machine To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840619] Re: skb_warn_bad_offload kernel splat due to CHECKSUM target not compatible with GSO skbs
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1840619 [Impact] In environments which have CHECKSUM iptables rules set, the following kernel call trace will be created when a GSO skb is processed by the CHECKSUM target: WARNING: CPU: 34 PID: 806048 at /build/linux-zdslHp/linux-4.4.0/net/core/dev.c:2456 skb_warn_bad_offload+0xcf/0x110() qr-f78bfdf7-fe: caps=(0x0fdb58e9, 0x0fdb58e9) len=1955 data_len=479 gso_size=1448 gso_type=1 ip_summed=3 CPU: 34 PID: 806048 Comm: haproxy Tainted: GW OE 4.4.0-138-generic #164-Ubuntu Call Trace: dump_stack+0x63/0x90 warn_slowpath_common+0x82/0xc0 warn_slowpath_fmt+0x5c/0x80 ? ___ratelimit+0xa2/0xe0 skb_warn_bad_offload+0xcf/0x110 skb_checksum_help+0x185/0x1a0 checksum_tg+0x22/0x29 [xt_CHECKSUM] ipt_do_table+0x301/0x730 [ip_tables] ? ipt_do_table+0x349/0x730 [ip_tables] iptable_mangle_hook+0x39/0x107 [iptable_mangle] nf_iterate+0x68/0x80 nf_hook_slow+0x73/0xd0 ip_output+0xcf/0xe0 ? __ip_flush_pending_frames.isra.43+0x90/0x90 ip_local_out+0x3b/0x50 ip_queue_xmit+0x154/0x390 __tcp_transmit_skb+0x52b/0x9b0 tcp_write_xmit+0x1dd/0xf50 __tcp_push_pending_frames+0x31/0xd0 tcp_push+0xec/0x110 tcp_sendmsg+0x749/0xba0 inet_sendmsg+0x6b/0xa0 sock_sendmsg+0x3e/0x50 SYSC_sendto+0x101/0x190 ? __sys_sendmsg+0x51/0x90 SyS_sendto+0xe/0x10 entry_SYSCALL_64_fastpath+0x22/0xc1 The CHECKSUM target does not support GSO skbs, and when a GSO skb is passed to skb_checksum_help(), it errors out and skb_warn_bad_offload() is called. The above call trace was found in a customer environment which has an Openstack deployment, with the following sorts of iptables rules set: -A neutron-l3-agent-POSTROUTING -o qr-+ -p tcp -m tcp --sport 9697 -j CHECKSUM --checksum-fill -A neutron-dhcp-age-POSTROUTING -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill This was causing haproxy running on the node to crash and restart every time a GSO skb was processed by the CHECKSUM target. I recommend reading the netdev mailing list thread for more details: https://www.spinics.net/lists/netdev/msg517366.html [Fix] This was fixed in 4.19 upstream with the below commit: commit 10568f6c5761db24249c610c94d6e44d5505a0ba Author: Florian Westphal Date: Wed Aug 22 11:33:27 2018 +0200 Subject: netfilter: xt_checksum: ignore gso skbs This commit adds a check to see if the current skb is a gso skb, and if it is, skips skb_checksum_help(). It then continues on to check if the packet uses udp, and if it does, exits early. Otherwise it prints a single warning that CHECKSUM should be avoided, and if really needed, only for use with outbound udp. Note, 10568f6c5761db24249c610c94d6e44d5505a0ba was included in upstream stable version 4.18.13, and was backported to bionic in 4.15.0-58.64 by LP #1836426. This patch required minor backporting for 4.4, by slightly adjusting the context in the final patch hunk. [Testcase] - You can reproduce this by adding the following iptables rule: + You can reproduce this by adding the following iptables rule to the + mangle table: -A POSTROUTING -p tcp -m tcp --sport 80 -j CHECKSUM --checksum-fill - and running traffic over port 80. + and running traffic over port 80 with incorrect checksums in the ip + header. I built a test kernel, which is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf216537-test For unpatched kernels, this causes the process which was handeling the socket to crash, as seen by haproxy crashing on a node in production which hits this issue. On patched kernels you see the warning printed to dmesg and no crashes occur. [Regression Potential] The changes are limited only to users which have CHECKSUM rules enabled in their iptables configs. Openstack commonly configures such rules on deployment, even though they are not necessary, as almost all packets have their checksum calculated by NICs these days, and CHECKSUM is only around to service old dhcp clients which would discard UDP packets with empty checksums. This commit was selected for upstream -stable 4.18.13, and has made its way into bionic 4.15.0-58.64 by LP #1836426. There have been no reported problems and those kernels would have had sufficient testing with Openstack and its configured iptables rules. If any users are affected by regression, then they can simply delete any CHECKSUM entries in their iptables configs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840619 Title: skb_warn_bad_offload kernel splat due to CHECKSUM target not compatible with GSO skbs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840619/+subscriptions --
[Bug 1840347] Re: Ceph 12.2.12 restarts services during upgrade
** Merge proposal linked: https://code.launchpad.net/~slashd/ubuntu/+source/ceph/+git/ceph/+merge/371551 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840347 Title: Ceph 12.2.12 restarts services during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1840347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577038] Re: [Upstream] Hard lock in opening files from a remote NFS volume
** Description changed: Binary package hint: openoffice.org I recently updated to Lucid, and noticed that Openoffice would lock with opening certain files. First I thought the problem was a corrupt file, now I can reproducibly hard lock OO.org when trying to open ANY file (.xls, .doc, .odt) that is present in a remote NFS volume (locally mounted). Any file on the local hard disk can be opened without problems. Any file on the mounted NFS directory causes a hard lock, requiring a force-quit. Other applications don't show this behaviour (e.g. gedit, command line programs). FilesystemSize Used Avail Use% Mounted on /dev/md0 70G 17G 50G 26% / 192.168.10.72:/home/fernan243G 182G 42G 82% /home/fernan/gama-remote - http://yourrxstore.com/product-category/buy-soma-online/ - http://yourrxstore.com/blog/order-tramadol-online-severe-and-acute-pain/ ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openoffice.org 1:3.2.0-7ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri May 7 11:48:21 2010 EcryptfsInUse: Yes ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: openoffice.org -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/577038 Title: [Upstream] Hard lock in opening files from a remote NFS volume To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/577038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837029] Re: Order Tramadol Online at YourRxStore.Com
** Package changed: ubuntu => null-and-void ** Information type changed from Public to Private ** Changed in: null-and-void Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837029 Title: Order Tramadol Online at YourRxStore.Com To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1837029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840347] Re: Ceph 12.2.12 restarts services during upgrade
** Merge proposal linked: https://code.launchpad.net/~slashd/ubuntu/+source/ceph/+git/ceph/+merge/371550 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840347 Title: Ceph 12.2.12 restarts services during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1840347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838109] Re: civetweb does not allow tuning of maximum socket connections
** Merge proposal linked: https://code.launchpad.net/~slashd/ubuntu/+source/ceph/+git/ceph/+merge/371549 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838109 Title: civetweb does not allow tuning of maximum socket connections To manage notifications about this bug go to: https://bugs.launchpad.net/ceph/+bug/1838109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828617] Re: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
** Merge proposal linked: https://code.launchpad.net/~slashd/ubuntu/+source/ceph/+git/ceph/+merge/371549 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828617 Title: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1828617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840347] Re: Ceph 12.2.12 restarts services during upgrade
** Merge proposal linked: https://code.launchpad.net/~slashd/ubuntu/+source/ceph/+git/ceph/+merge/371549 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840347 Title: Ceph 12.2.12 restarts services during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1840347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840858] [NEW] installer crashed
Public bug reported: repeat problem, installer failed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 Date: Tue Aug 20 19:45:00 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840858 Title: installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1840858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840857] [NEW] Couldn't run grub-install on created EFI partition. Doesn't like boot on an NTFS
Public bug reported: Couldn't run grub-install on created EFI partition. Doesn't like boot being on a small NTFS. Wants it to be vfat. I can't change that without wiping out existing Win 10 Pro install. Not going to mess with that. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 Date: Tue Aug 20 19:50:36 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840857 Title: Couldn't run grub-install on created EFI partition. Doesn't like boot on an NTFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1840857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840854] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1840854 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840854 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840854] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
The customer installed 4.15.0-59 from -proposed to a machine with Mellanox Ethernet CX4LX cards, using the mlx5_core kernel module. Checksums are now calculated correctly and the kernel spat does not occur when the devices are brought up. Marking this as verified. ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840854 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840854] [NEW] mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/1840854 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, after installing 4.15.0-56 or later there is the following kernel splat: bond0: hw csum failure CPU: 63 PID: 2473 Comm: in:imklog Tainted: P OE 4.15.0-58-generic #64~16.04.1-Ubuntu Call Trace: dump_stack+0x63/0x8b netdev_rx_csum_fault+0x38/0x40 __skb_checksum_complete+0xc0/0xd0 nf_ip_checksum+0xca/0xf0 tcp_error+0xe0/0x1a0 [nf_conntrack] ? tcp_v4_rcv+0x7c6/0xa70 nf_conntrack_in+0xde/0x520 [nf_conntrack] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] nf_hook_slow+0x48/0xd0 ? skb_send_sock+0x50/0x50 ip_rcv+0x30f/0x370 ? inet_del_offload+0x40/0x40 __netif_receive_skb_core+0x879/0xba0 ? tcp4_gro_receive+0x117/0x1b0 __netif_receive_skb+0x18/0x60 ? __netif_receive_skb+0x18/0x60 netif_receive_skb_internal+0x45/0xf0 napi_gro_receive+0xd0/0xf0 mlx5e_handle_rx_cqe_mpwrq+0x4a1/0x8a0 [mlx5_core] mlx5e_poll_rx_cq+0xc3/0x880 [mlx5_core] mlx5e_napi_poll+0x9b/0x280 [mlx5_core] net_rx_action+0x265/0x3b0 __do_softirq+0xf5/0x2a8 irq_exit+0xca/0xd0 do_IRQ+0x57/0xe0 common_interrupt+0x8c/0x8c In 4.15.0-56, a commit was added from upstream -stable that introduced an optimisation for checksumming packets which have had zero bytes padded to the end of the packet. commit 88078d98d1bb085d72af8437707279e203524fa5 Author: Eric Dumazet Date: Wed Apr 18 11:43:15 2018 -0700 subject: net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends You can read it here: https://github.com/torvalds/linux/commit/88078d98d1bb085d72af8437707279e203524fa5 It was discussed in this bugzilla link: https://bugzilla.kernel.org/show_bug.cgi?id=201849 This commit causes problems with a number of NIC devices, including Mellanox. This is best described by the maintainer, Dimitris Michailidis: > > > MLNX devices have an issue with packets that are padded past the end of > > > the L3 payload with bytes that aren't all 0s. They use a mode of checksum > > > reporting which should be including the padding bytes but MLNX devices > > > leave those out. When the padding bytes aren't all 0 this omission causes > > > a checksum error. This device behavior has existed for a long time but it > > > has begun causing errors only this year. Before a padded packet had its > HW > > > checksum ignored so it wasn't material what HW had reported. More > recently > > > padded packet checksums started using the HW value and now it is > > > noticeable when that value isn't right. Now, some routers stick additional information in the zero padding section on occasion, which will change the hardware checksum. Since the hardware checksum was ignored until 4.15.0-56 with 88078d98d1bb085d72af8437707279e203524fa5, this wasn't an issue. But with the optimisation, we start running into trouble since the hardware checksums no longer match what the kernel is expecting. [Fix] This was fixed for Mellanox 4 and 5 series drivers recently. Mellanox 4: 74abc07dee613086f9c0ded9e263ddc959a6de04 https://github.com/torvalds/linux/commit/74abc07dee613086f9c0ded9e263ddc959a6de04 Mellanox 5: e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a https://github.com/torvalds/linux/commit/e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a This customer hit the issue with mlx5_core driver, so the fix is: commit e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a Author: Cong Wang Date: Mon Dec 3 22:14:04 2018 -0800 subject: net/mlx5e: Force CHECKSUM_UNNECESSARY for short ethernet frames This is actually present in 4.15.0-59, which is currently sitting in -proposed. The commits are a part of 4.9.156, 4.14.99, 4.19.21 upstream -stable releases, and have been pulled into bionic as a part of LP #1837664 [Testcase] Simply try and bring an interface up on a machine with Mellanox series 5 NICs. When a packet comes through which is smaller than required and padding is added, the problem will be triggered. The 4.15.0-59 from -proposed has been tested by the customer, and resolves the issue. [Regression Potential] This patch has a low chance of regression since it fixes a regression introduced by 88078d98d1bb085d72af8437707279e203524fa5 in 4.15.0-56. The changes are limited to mlx5_core driver, and have been well tested and accepted by the community due to their selection for upstream -stable. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: Fix Committed ** Tags: sts verification-done-bionic ** Description changed: - BugLink: https://bugs.launchpad.net/bugs/ + BugLink: https://bugs.launchpad.net/bugs/1840854 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, after installing 4.15.0-56 or later there is the following kernel splat: bond0: hw csum failure CPU: 63 PID: 2473 Comm: in:imklog
[Bug 1811504] Re: scan with Laserjet MFP-M28 fails
I would not have revisited this bug report if it had not been for https://bugs.launchpad.net/hplip/+bug/1840842 Now I find it is fixed. However, I feel like complaining about the way the issue has been treated. 1. Bug reported on 2019-01-12; fix announced on 2019-07-17. A 6 month wait. 2. In 3.19.6, models.dat still has "plugin=0". Why then is a plugin required? Nobody has ever explained. 3. "scan-type=9" is still undocumented. 4. The Release Notes for 3.19.6 have absolutely no mention of this bug (or any other bug) being fixed. Talk about keeping everyone in the dark. I regard this lack of changelog detail as a serious defect. 5. Correct information about the cause or origin of the issue is completely lacking. If upstream do not know, at least say so; we are not mushrooms. :) 6. HPLIP is important, quality software. It deserves better. -- Brian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811504 Title: scan with Laserjet MFP-M28 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1811504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839500] Re: Add a future-proof provides btrfs-progs name for ease of usability
This bug was fixed in the package btrfs-tools - 4.4-1ubuntu1.1 --- btrfs-tools (4.4-1ubuntu1.1) xenial; urgency=medium * Add `Provides: btrfs-progs` to btrfs-tools as a more common upstream name for the package, which started to be used by default in bionic and later. This helps users to install the btrfs utility irrespective if they use legacy or the futureproof name. LP: #1839500 -- Dimitri John Ledkov Thu, 08 Aug 2019 16:30:00 +0100 ** Changed in: btrfs-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839500 Title: Add a future-proof provides btrfs-progs name for ease of usability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1839500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839500] Update Released
The verification of the Stable Release Update for btrfs-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839500 Title: Add a future-proof provides btrfs-progs name for ease of usability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1839500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840347] Re: Ceph 12.2.12 restarts services during upgrade
# Before the upgrade : 12.2.12-0ubuntu0.18.04.1 ceph 15176 1 0 17:57 ? 00:00:59 /usr/bin/ceph-osd -f # After the upgrade: 12.2.12-0ubuntu0.18.04.2 # ==> It's a test pkg (not in the archive yet) ceph 15176 1 0 17:57 ? 00:01:00 /usr/bin/ceph-osd -f . I'll submit the MP to Cloud team for approval by end of week. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840347 Title: Ceph 12.2.12 restarts services during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1840347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840347] Re: Ceph 12.2.12 restarts services during upgrade
Ok the change works as expected: # Before the upgrade : 12.2.12-0ubuntu0.18.04.1 root4019 1 0 17:45 ?00:00:00 bash /lib/systemd/system/jujud-unit-ceph-osd-1/exec-start.sh root40334019 0 17:45 ?00:00:04 /var/lib/juju/tools/unit-ceph-osd-1/jujud unit --data-dir /var/lib/juju --unit-name ceph-osd/1 --debug ceph 15176 1 0 17:57 ?00:00:59 /usr/bin/ceph-osd -f --cluster ceph --id 1 --setuser ceph --setgroup ceph root 258134033 50 22:58 ?00:00:02 python3 /var/lib/juju/agents/unit-ceph-osd-1/charm/hooks/update-status ubuntu 25910 25782 0 22:58 pts/000:00:00 grep --color=auto -i ceph-osd # After the upgrade: 12.2.12-0ubuntu0.18.04.2 # ==> It's a test pkg (not in the archive yet) root4019 1 0 17:45 ?00:00:00 bash /lib/systemd/system/jujud-unit-ceph-osd-1/exec-start.sh root40334019 0 17:45 ?00:00:04 /var/lib/juju/tools/unit-ceph-osd-1/jujud unit --data-dir /var/lib/juju --unit-name ceph-osd/1 --debug ceph 15176 1 0 17:57 ?00:01:00 /usr/bin/ceph-osd -f --cluster ceph --id 1 --setuser ceph --setgroup ceph root 28926 26301 0 23:01 pts/000:00:00 grep --color=auto -i ceph I'll submit the MP to Cloud team for approval by end of week. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840347 Title: Ceph 12.2.12 restarts services during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1840347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687436] Re: cupsd uses 100% CPU
I'm having this issue on Disco. Stopping cups-browsed solves the issue, restarting it makes the issue reappear after a few seconds. I'm seeing this in the error log: W [20/Aug/2019:18:46:37 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'KONICA_MINOLTA_C368Series_cali_sys-CMYK..\' already exists E [20/Aug/2019:18:46:53 -0400] [Client 608] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/KONICA_MINOLTA_C368Series_cali_sys) from localhost. W [20/Aug/2019:18:46:53 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'KONICA_MINOLTA_C368Series_cali_sys-Gray..\' already exists W [20/Aug/2019:18:46:53 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'KONICA_MINOLTA_C368Series_cali_sys-CMYK..\' already exists E [20/Aug/2019:18:47:09 -0400] [Client 611] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/KONICA_MINOLTA_C368Series_cali_sys) from localhost. W [20/Aug/2019:18:47:09 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'KONICA_MINOLTA_C368Series_cali_sys-Gray..\' already exists W [20/Aug/2019:18:47:09 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'KONICA_MINOLTA_C368Series_cali_sys-CMYK..\' already exists E [20/Aug/2019:18:47:24 -0400] [Client 612] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/KONICA_MINOLTA_C368Series_cali_sys) from localhost. W [20/Aug/2019:18:47:24 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'KONICA_MINOLTA_C368Series_cali_sys-Gray..\' already exists W [20/Aug/2019:18:47:24 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'KONICA_MINOLTA_C368Series_cali_sys-CMYK..\' already exists E [20/Aug/2019:18:47:40 -0400] [Client 613] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/KONICA_MINOLTA_C368Series_cali_sys) from localhost. W [20/Aug/2019:18:47:40 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'KONICA_MINOLTA_C368Series_cali_sys-Gray..\' already exists W [20/Aug/2019:18:47:40 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'KONICA_MINOLTA_C368Series_cali_sys-CMYK..\' already exists -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687436 Title: cupsd uses 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1687436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Tuesday, 20. August 2019 10:40 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840004 Title: xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840080] Re: cloud-init cc_ubuntu_drivers does not set up /etc/default/linux-modules-nvidia
** Merge proposal linked: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371545 ** Merge proposal linked: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371546 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840080 Title: cloud-init cc_ubuntu_drivers does not set up /etc/default/linux- modules-nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1840080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581711] Re: 024C:B723 Need support for Realtek Wifi card rtl8723bs
With 19 more months of support for 16.04 (and the 4.4 kernel), consider the 8723bs drivers in the trusty-chestersmill repository ( http://oem.archive.canonical.com/updates/ trusty-chestersmill public) These drivers worked fine through the Ubuntu 4.4.0-142 release (when the API change broke many drivers). The fix for that problem may be much simpler than changing the lwfinger or hadess drivers. Note, bug 1755309 for the header fix necessary for the audio packages from that repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581711 Title: 024C:B723 Need support for Realtek Wifi card rtl8723bs To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1581711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581711] Re: 024C:B723 Need support for Realtek Wifi card rtl8723bs
With 19 more months of support for 16.04 (and the 4.4 kernel), consider the 8723bs drivers in the trusty-chestersmill repository ( http://oem.archive.canonical.com/updates/ trusty-chestersmill public) These drivers worked fine through the Ubuntu 4.4.0-142 release (when the API change broke many drivers). The fix for that problem may be much simpler than changing the lwfinger or hadess drivers. Note, bug 175309 for the header fix necessary for the audio packages from that repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581711 Title: 024C:B723 Need support for Realtek Wifi card rtl8723bs To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1581711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810976] Re: wxbanker: depends on obsolete python-beautifulsoup
This would shortly after need a port to python3 (https://github.com/mrooney/wxbanker/issues/10). If development has stopped, I think it's time to remove from Ubuntu. ** Bug watch added: github.com/mrooney/wxbanker/issues #10 https://github.com/mrooney/wxbanker/issues/10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810976 Title: wxbanker: depends on obsolete python-beautifulsoup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wxbanker/+bug/1810976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840511] Re: Eoan FTBFS with gcc-9 and MySQL 8
Im currently building the to-be-suggested source package locally so I can push it to a PPA for the debdiff reviewers before final upload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840511 Title: Eoan FTBFS with gcc-9 and MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clickhouse/+bug/1840511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840762] Re: Remove baloo from Eoan
INFO:root:baloo (4:4.14.3-3/4:4.14.3-3), removed from Debian on 2019-08-20 baloo's binaries are not seeded. Removing packages: baloo 4:4.14.3-3 in eoan baloo-dev 4:4.14.3-3 in eoan amd64 baloo-dev 4:4.14.3-3 in eoan arm64 baloo-dev 4:4.14.3-3 in eoan armhf baloo-dev 4:4.14.3-3 in eoan i386 baloo-dev 4:4.14.3-3 in eoan ppc64el baloo-dev 4:4.14.3-3 in eoan s390x baloo-utils 4:4.14.3-3 in eoan amd64 baloo-utils 4:4.14.3-3 in eoan arm64 baloo-utils 4:4.14.3-3 in eoan armhf baloo-utils 4:4.14.3-3 in eoan i386 baloo-utils 4:4.14.3-3 in eoan ppc64el baloo-utils 4:4.14.3-3 in eoan s390x baloo-utils-dbgsym 4:4.14.3-3 in eoan amd64 baloo-utils-dbgsym 4:4.14.3-3 in eoan arm64 baloo-utils-dbgsym 4:4.14.3-3 in eoan armhf baloo-utils-dbgsym 4:4.14.3-3 in eoan i386 baloo-utils-dbgsym 4:4.14.3-3 in eoan ppc64el baloo-utils-dbgsym 4:4.14.3-3 in eoan s390x baloo4 4:4.14.3-3 in eoan amd64 baloo4 4:4.14.3-3 in eoan arm64 baloo4 4:4.14.3-3 in eoan armhf baloo4 4:4.14.3-3 in eoan i386 baloo4 4:4.14.3-3 in eoan ppc64el baloo4 4:4.14.3-3 in eoan s390x baloo4-dbgsym 4:4.14.3-3 in eoan amd64 baloo4-dbgsym 4:4.14.3-3 in eoan arm64 baloo4-dbgsym 4:4.14.3-3 in eoan armhf baloo4-dbgsym 4:4.14.3-3 in eoan i386 baloo4-dbgsym 4:4.14.3-3 in eoan ppc64el baloo4-dbgsym 4:4.14.3-3 in eoan s390x libbaloocore4 4:4.14.3-3 in eoan amd64 libbaloocore4 4:4.14.3-3 in eoan arm64 libbaloocore4 4:4.14.3-3 in eoan armhf libbaloocore4 4:4.14.3-3 in eoan i386 libbaloocore4 4:4.14.3-3 in eoan ppc64el libbaloocore4 4:4.14.3-3 in eoan s390x libbaloocore4-dbgsym 4:4.14.3-3 in eoan amd64 libbaloocore4-dbgsym 4:4.14.3-3 in eoan arm64 libbaloocore4-dbgsym 4:4.14.3-3 in eoan armhf libbaloocore4-dbgsym 4:4.14.3-3 in eoan i386 libbaloocore4-dbgsym 4:4.14.3-3 in eoan ppc64el libbaloocore4-dbgsym 4:4.14.3-3 in eoan s390x libbaloofiles4 4:4.14.3-3 in eoan amd64 libbaloofiles4 4:4.14.3-3 in eoan arm64 libbaloofiles4 4:4.14.3-3 in eoan armhf libbaloofiles4 4:4.14.3-3 in eoan i386 libbaloofiles4 4:4.14.3-3 in eoan ppc64el libbaloofiles4 4:4.14.3-3 in eoan s390x libbaloofiles4-dbgsym 4:4.14.3-3 in eoan amd64 libbaloofiles4-dbgsym 4:4.14.3-3 in eoan arm64 libbaloofiles4-dbgsym 4:4.14.3-3 in eoan armhf libbaloofiles4-dbgsym 4:4.14.3-3 in eoan i386 libbaloofiles4-dbgsym 4:4.14.3-3 in eoan ppc64el libbaloofiles4-dbgsym 4:4.14.3-3 in eoan s390x libbaloopim4 4:4.14.3-3 in eoan amd64 libbaloopim4 4:4.14.3-3 in eoan arm64 libbaloopim4 4:4.14.3-3 in eoan armhf libbaloopim4 4:4.14.3-3 in eoan i386 libbaloopim4 4:4.14.3-3 in eoan ppc64el libbaloopim4 4:4.14.3-3 in eoan s390x libbaloopim4-dbgsym 4:4.14.3-3 in eoan amd64 libbaloopim4-dbgsym 4:4.14.3-3 in eoan arm64 libbaloopim4-dbgsym 4:4.14.3-3 in eoan armhf libbaloopim4-dbgsym 4:4.14.3-3 in eoan i386 libbaloopim4-dbgsym 4:4.14.3-3 in eoan ppc64el libbaloopim4-dbgsym 4:4.14.3-3 in eoan s390x libbalooqueryparser4 4:4.14.3-3 in eoan amd64 libbalooqueryparser4 4:4.14.3-3 in eoan arm64 libbalooqueryparser4 4:4.14.3-3 in eoan armhf libbalooqueryparser4 4:4.14.3-3 in eoan i386 libbalooqueryparser4 4:4.14.3-3 in eoan ppc64el libbalooqueryparser4 4:4.14.3-3 in eoan s390x libbalooqueryparser4-dbgsym 4:4.14.3-3 in eoan amd64 libbalooqueryparser4-dbgsym 4:4.14.3-3 in eoan arm64 libbalooqueryparser4-dbgsym 4:4.14.3-3 in eoan armhf libbalooqueryparser4-dbgsym 4:4.14.3-3 in eoan i386 libbalooqueryparser4-dbgsym 4:4.14.3-3 in eoan ppc64el libbalooqueryparser4-dbgsym 4:4.14.3-3 in eoan s390x libbalooxapian4 4:4.14.3-3 in eoan amd64 libbalooxapian4 4:4.14.3-3 in eoan arm64 libbalooxapian4 4:4.14.3-3 in eoan armhf libbalooxapian4 4:4.14.3-3 in eoan i386 libbalooxapian4 4:4.14.3-3 in eoan ppc64el libbalooxapian4 4:4.14.3-3 in
[Bug 1840744] Re: Remove krecipes from Eoan
INFO:root:krecipes (2.1.0-3/2.1.0-3build1), removed from Debian on 2019-08-20 krecipes's binaries are not seeded. Removing packages: krecipes 2.1.0-3build1 in eoan krecipes 2.1.0-3build1 in eoan amd64 krecipes 2.1.0-3build1 in eoan arm64 krecipes 2.1.0-3build1 in eoan armhf krecipes 2.1.0-3build1 in eoan i386 krecipes 2.1.0-3build1 in eoan ppc64el krecipes 2.1.0-3build1 in eoan s390x krecipes-data 2.1.0-3build1 in eoan amd64 krecipes-data 2.1.0-3build1 in eoan arm64 krecipes-data 2.1.0-3build1 in eoan armhf krecipes-data 2.1.0-3build1 in eoan i386 krecipes-data 2.1.0-3build1 in eoan ppc64el krecipes-data 2.1.0-3build1 in eoan s390x krecipes-dbgsym 2.1.0-3build1 in eoan amd64 krecipes-dbgsym 2.1.0-3build1 in eoan arm64 krecipes-dbgsym 2.1.0-3build1 in eoan armhf krecipes-dbgsym 2.1.0-3build1 in eoan i386 krecipes-dbgsym 2.1.0-3build1 in eoan ppc64el krecipes-dbgsym 2.1.0-3build1 in eoan s390x krecipes-doc 2.1.0-3build1 in eoan amd64 krecipes-doc 2.1.0-3build1 in eoan arm64 krecipes-doc 2.1.0-3build1 in eoan armhf krecipes-doc 2.1.0-3build1 in eoan i386 krecipes-doc 2.1.0-3build1 in eoan ppc64el krecipes-doc 2.1.0-3build1 in eoan s390x Comment: (From Debian) ROM; Obsolet libs - Qt4; Dead upstream; Debian bug #935023 Remove [y|N]? y ** Changed in: krecipes (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840744 Title: Remove krecipes from Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krecipes/+bug/1840744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840743] Re: Remove smokegen from Eoan
INFO:root:smokegen (4:4.14.3-1/4:4.14.3-1build1), removed from Debian on 2019-08-20 smokegen's binaries are not seeded. Removing packages: smokegen 4:4.14.3-1build1 in eoan libsmokebase3v5 4:4.14.3-1build1 in eoan amd64 libsmokebase3v5 4:4.14.3-1build1 in eoan arm64 libsmokebase3v5 4:4.14.3-1build1 in eoan armhf libsmokebase3v5 4:4.14.3-1build1 in eoan i386 libsmokebase3v5 4:4.14.3-1build1 in eoan ppc64el libsmokebase3v5 4:4.14.3-1build1 in eoan s390x smoke-dev-tools 4:4.14.3-1build1 in eoan amd64 smoke-dev-tools 4:4.14.3-1build1 in eoan arm64 smoke-dev-tools 4:4.14.3-1build1 in eoan armhf smoke-dev-tools 4:4.14.3-1build1 in eoan i386 smoke-dev-tools 4:4.14.3-1build1 in eoan ppc64el smoke-dev-tools 4:4.14.3-1build1 in eoan s390x smokegen-dbg 4:4.14.3-1build1 in eoan amd64 smokegen-dbg 4:4.14.3-1build1 in eoan arm64 smokegen-dbg 4:4.14.3-1build1 in eoan armhf smokegen-dbg 4:4.14.3-1build1 in eoan i386 smokegen-dbg 4:4.14.3-1build1 in eoan ppc64el smokegen-dbg 4:4.14.3-1build1 in eoan s390x Comment: (From Debian) ROM; Obsolete libs - Qt4; Debian bug #935074 Remove [y|N]? y ** Changed in: smokegen (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840743 Title: Remove smokegen from Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smokegen/+bug/1840743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840357] Re: bionic/linux-azure-edge: 5.0.0-1016.17~18.04.1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840357 Title: bionic/linux-azure-edge: 5.0.0-1016.17~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828639] Re: Unlooping all the trigger loops!!!!!
This bug was fixed in the package dpkg - 1.19.0.5ubuntu2.2 --- dpkg (1.19.0.5ubuntu2.2) bionic; urgency=medium * Cherry-pick upstream fixes for trigger loops (LP: #1828639) - dpkg: Negate tortoise_not_in_hare() function name and return value - dpkg: Initialize trigcyclenode's next member once - dpkg: Factor trigproc_new_cyclenode() out from check_trigger_cycle() - dpkg: Mark the package we are giving up on a trigger cycle as istobe normal - dpkg: Switch dependtry from an int to an enum - dpkg: Reset progress_bytrigproc once we have injected into the current iteration - dpkg: Split trigger processing types into required, try-queued and try-deferred - dpkg: Convert one trigger processing required type into the new try-queued - dpkg: Move trigproc cycle reset inside try-deferred conditional - dpkg: Introduce a new dependency try level for trigger processing - dpkg: Introduce a new dependency try level for trigger cycle checks -- Julian Andres Klode Tue, 16 Jul 2019 14:57:11 +0200 ** Changed in: dpkg (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828639 Title: Unlooping all the trigger loops! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1828639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840812] Re: bionic/linux-hwe: 5.0.0-27.28~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Ready for Packaging - phase-changed: Tuesday, 20. August 2019 20:15 UTC + phase: Packaging + phase-changed: Tuesday, 20. August 2019 21:32 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840812 Title: bionic/linux-hwe: 5.0.0-27.28~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840511] Re: Eoan FTBFS with gcc-9 and MySQL 8
I have opened the following BUG: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840847 To address this issue, for now.. I might have to drop the specific patch: From: Alexander GQ Gerasiov Date: Fri, 4 Jan 2019 03:04:07 +0300 Subject: Replace cpuid with cpuinfo. cpuinfo is already shipped in Debian and provides more suitable API. This commit is not enough for inclusion into upstream codebase. One also needs to replace cpuid with cpuinfo in the "contrib" directory. Signed-off-by: Alexander GQ Gerasiov That introduced this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840511 Title: Eoan FTBFS with gcc-9 and MySQL 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clickhouse/+bug/1840511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840847] [NEW] cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
Public bug reported: >From bug: https://bugs.launchpad.net/bugs/1840511 clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) >From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? ** Affects: cpuinfo (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: From bug: https://bugs.launchpad.net/bugs/1840511 - clockhouse test started failing because of the presence of stderr + clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) - /* - * Android NDK headers before platform 21 do not define CPU_SETSIZE, - * so we hard-code its value, as defined in platform 21 headers - */ - #if defined(__LP64__) - static const uint32_t default_max_processors_count = 1024; - #else - static const uint32_t default_max_processors_count = 32; - #endif + /* + * Android NDK headers before platform 21 do not define CPU_SETSIZE, + * so we hard-code its value, as defined in platform 21 headers + */ + #if defined(__LP64__) + static const uint32_t default_max_processors_count = 1024; + #else + static const uint32_t default_max_processors_count = 32; + #endif #else - static const uint32_t default_max_processors_count = CPU_SETSIZE; + static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) - /* - * sched.h is only used for CPU_SETSIZE constant. - * Android NDK headers before platform 21 do have this constant in sched.h - */ - #include + /* + * sched.h is only used for CPU_SETSIZE constant. + * Android NDK headers before platform 21 do have this constant in sched.h + */ + #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840846] Re: Disco update: upstream stable patchset 2019-08-20
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2019-08-20 -upstream stable patchset 2019-08-20 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.19.60, v5.1.19, + v4.19.61, v5.1.20 + + from git://git.kernel.org/ ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-08-20 - Ported from the following upstream stable releases: - v4.19.60, v5.1.19, - v4.19.61, v5.1.20 + Ported from the following upstream stable releases: + v4.19.60, v5.1.19, + v4.19.61, v5.1.20 from git://git.kernel.org/ + + Revert "e1000e: fix cyclic resets at link up with active tx" + e1000e: start network tx queue only when link is up + Input: synaptics - enable SMBUS on T480 thinkpad trackpad + nilfs2: do not use unexported cpu_to_le32()/le32_to_cpu() in uapi header + drivers: base: cacheinfo: Ensure cpu hotplug work is done before Intel RDT + firmware: improve LSM/IMA security behaviour + irqchip/gic-v3-its: Fix command queue pointer comparison bug + clk: ti: clkctrl: Fix returning uninitialized data + efi/bgrt: Drop BGRT status field reserved bits check + perf/core: Fix perf_sample_regs_user() mm check + ARM: dts: gemini Fix up DNS-313 compatible string + ARM: omap2: remove incorrect __init annotation + afs: Fix uninitialised spinlock afs_volume::cb_break_lock + x86/apic: Fix integer overflow on 10 bit left shift of cpu_khz + be2net: fix link failure after ethtool offline test + ppp: mppe: Add softdep to arc4 + sis900: fix TX completion + ARM: dts: imx6ul: fix PWM[1-4] interrupts + pinctrl: mcp23s08: Fix add_data and irqchip_add_nested call order + dm table: don't copy from a NULL pointer in realloc_argv() + dm verity: use message limit for data block corruption message + x86/boot/64: Fix crash if kernel image crosses page table boundary + x86/boot/64: Add missing fixup_pointer() for next_early_pgt access + HID: chicony: add another quirk for PixArt mouse + pinctrl: mediatek: Ignore interrupts that are wake only during resume + cpu/hotplug: Fix out-of-bounds read when setting fail state + pinctrl: mediatek: Update cur_mask in mask/mask ops + linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL + genirq: Delay deactivation in free_irq() + genirq: Fix misleading synchronize_irq() documentation + genirq: Add optional hardware synchronization for shutdown + x86/ioapic: Implement irq_get_irqchip_state() callback + x86/irq: Handle spurious interrupt after shutdown gracefully + x86/irq: Seperate unused system vectors from spurious entry again + ARC: hide unused function unw_hdr_alloc + s390: fix stfle zero padding + s390/qdio: (re-)initialize tiqdio list entries + s390/qdio: don't touch the dsci in tiqdio_add_input_queues() + crypto: talitos - move struct talitos_edesc into talitos.h + crypto: talitos - fix hash on SEC1. + crypto/NX: Set receive window credits to max number of CRBs in RxFIFO + drm/udl: introduce a macro to convert dev to udl. + drm/udl: move to embedding drm device inside udl device. + x86/entry/32: Fix ENDPROC of common_spurious + irqchip/irq-csky-mpintc: Support auto irq deliver to all cpus + arm64: dts: ls1028a: Fix CPU idle fail. + selftests/powerpc: Add test of fork with mapping above 512TB + x86/efi: fix a -Wtype-limits compilation warning + pinctrl: ocelot: fix gpio direction for pins after 31 + pinctrl: ocelot: fix pinmuxing for pins after 31 + mm/oom_kill.c:
[Bug 1840812] Re: bionic/linux-hwe: 5.0.0-27.28~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-hwe: -proposed tracker + bionic/linux-hwe: 5.0.0-27.28~18.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840812 Title: bionic/linux-hwe: 5.0.0-27.28~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840847] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1840847 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840846] Re: Disco update: upstream stable patchset 2019-08-20
** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840846 Title: Disco update: upstream stable patchset 2019-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Packaging - phase-changed: Tuesday, 20. August 2019 20:12 UTC + phase: Packaging + phase-changed: Tuesday, 20. August 2019 21:15 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829749] Re: [MIR] Please add support for SIPL
** Changed in: linux-signed (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829749 Title: [MIR] Please add support for SIPL To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker
** Summary changed: - disco/linux-kvm: -proposed tracker + disco/linux-kvm: 5.0.0-1015.16 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
