[Bug 1815733] Re: unnecessary request_queue freeze

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1038.43

---
linux-oem (4.15.0-1038.43) bionic; urgency=medium

  [ Ubuntu: 4.15.0-50.54 ]

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS
  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux-oem (4.15.0-1037.42) bionic; urgency=medium

  * linux-oem: 4.15.0-1037.42 -proposed tracker (LP: #1826336)

  * unnecessary request_queue freeze (LP: #1815733)
- block: avoid setting nr_requests to current value
- block: avoid setting none scheduler if it's already none

  * Screen freeze after resume from S3 when HDMI monitor plugged on Dell
Precision 7740 (LP: #1825958)
- PCI: Restore resized BAR state on resume

  [ Ubuntu: 4.15.0-49.53 ]

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)
  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.
  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions
  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- 

[Bug 1815733] Re: unnecessary request_queue freeze

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1038.43

---
linux-oem (4.15.0-1038.43) bionic; urgency=medium

  [ Ubuntu: 4.15.0-50.54 ]

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS
  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux-oem (4.15.0-1037.42) bionic; urgency=medium

  * linux-oem: 4.15.0-1037.42 -proposed tracker (LP: #1826336)

  * unnecessary request_queue freeze (LP: #1815733)
- block: avoid setting nr_requests to current value
- block: avoid setting none scheduler if it's already none

  * Screen freeze after resume from S3 when HDMI monitor plugged on Dell
Precision 7740 (LP: #1825958)
- PCI: Restore resized BAR state on resume

  [ Ubuntu: 4.15.0-49.53 ]

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)
  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.
  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions
  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- 

[Bug 1803127] Re: remmina not able to redirect smart card reader

[Roelf Renkema]

*nudge* Need this security very badly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803127

Title:
  remmina not able to redirect smart card reader

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1803127/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825272] Re: headset-mic doesn't work on two Dell laptops.

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1038.43

---
linux-oem (4.15.0-1038.43) bionic; urgency=medium

  [ Ubuntu: 4.15.0-50.54 ]

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS
  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux-oem (4.15.0-1037.42) bionic; urgency=medium

  * linux-oem: 4.15.0-1037.42 -proposed tracker (LP: #1826336)

  * unnecessary request_queue freeze (LP: #1815733)
- block: avoid setting nr_requests to current value
- block: avoid setting none scheduler if it's already none

  * Screen freeze after resume from S3 when HDMI monitor plugged on Dell
Precision 7740 (LP: #1825958)
- PCI: Restore resized BAR state on resume

  [ Ubuntu: 4.15.0-49.53 ]

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)
  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.
  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions
  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- 

[Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1038.43

---
linux-oem (4.15.0-1038.43) bionic; urgency=medium

  [ Ubuntu: 4.15.0-50.54 ]

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS
  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux-oem (4.15.0-1037.42) bionic; urgency=medium

  * linux-oem: 4.15.0-1037.42 -proposed tracker (LP: #1826336)

  * unnecessary request_queue freeze (LP: #1815733)
- block: avoid setting nr_requests to current value
- block: avoid setting none scheduler if it's already none

  * Screen freeze after resume from S3 when HDMI monitor plugged on Dell
Precision 7740 (LP: #1825958)
- PCI: Restore resized BAR state on resume

  [ Ubuntu: 4.15.0-49.53 ]

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)
  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.
  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions
  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- 

[Bug 1825272] Re: headset-mic doesn't work on two Dell laptops.

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1038.43

---
linux-oem (4.15.0-1038.43) bionic; urgency=medium

  [ Ubuntu: 4.15.0-50.54 ]

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS
  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux-oem (4.15.0-1037.42) bionic; urgency=medium

  * linux-oem: 4.15.0-1037.42 -proposed tracker (LP: #1826336)

  * unnecessary request_queue freeze (LP: #1815733)
- block: avoid setting nr_requests to current value
- block: avoid setting none scheduler if it's already none

  * Screen freeze after resume from S3 when HDMI monitor plugged on Dell
Precision 7740 (LP: #1825958)
- PCI: Restore resized BAR state on resume

  [ Ubuntu: 4.15.0-49.53 ]

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)
  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.
  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions
  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- 

[Bug 1825487] Re: The Realtek card reader does not enter PCIe 1.1/1.2

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1038.43

---
linux-oem (4.15.0-1038.43) bionic; urgency=medium

  [ Ubuntu: 4.15.0-50.54 ]

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS
  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux-oem (4.15.0-1037.42) bionic; urgency=medium

  * linux-oem: 4.15.0-1037.42 -proposed tracker (LP: #1826336)

  * unnecessary request_queue freeze (LP: #1815733)
- block: avoid setting nr_requests to current value
- block: avoid setting none scheduler if it's already none

  * Screen freeze after resume from S3 when HDMI monitor plugged on Dell
Precision 7740 (LP: #1825958)
- PCI: Restore resized BAR state on resume

  [ Ubuntu: 4.15.0-49.53 ]

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)
  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.
  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions
  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- 

[Bug 1815733] Re: unnecessary request_queue freeze

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1038.43

---
linux-oem (4.15.0-1038.43) bionic; urgency=medium

  [ Ubuntu: 4.15.0-50.54 ]

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS
  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux-oem (4.15.0-1037.42) bionic; urgency=medium

  * linux-oem: 4.15.0-1037.42 -proposed tracker (LP: #1826336)

  * unnecessary request_queue freeze (LP: #1815733)
- block: avoid setting nr_requests to current value
- block: avoid setting none scheduler if it's already none

  * Screen freeze after resume from S3 when HDMI monitor plugged on Dell
Precision 7740 (LP: #1825958)
- PCI: Restore resized BAR state on resume

  [ Ubuntu: 4.15.0-49.53 ]

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)
  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.
  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions
  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- 

[Bug 1829439] Re: GIMP crash when closing the About dialog box

[Daniel Manrique]

** Project changed: canonical-identity-provider => gimp (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829439

Title:
  GIMP crash when closing the About dialog box

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1829439/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815733] Re: unnecessary request_queue freeze

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1038.43

---
linux-oem (4.15.0-1038.43) bionic; urgency=medium

  [ Ubuntu: 4.15.0-50.54 ]

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS
  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux-oem (4.15.0-1037.42) bionic; urgency=medium

  * linux-oem: 4.15.0-1037.42 -proposed tracker (LP: #1826336)

  * unnecessary request_queue freeze (LP: #1815733)
- block: avoid setting nr_requests to current value
- block: avoid setting none scheduler if it's already none

  * Screen freeze after resume from S3 when HDMI monitor plugged on Dell
Precision 7740 (LP: #1825958)
- PCI: Restore resized BAR state on resume

  [ Ubuntu: 4.15.0-49.53 ]

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)
  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.
  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions
  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- 

[Bug 1825487] Re: The Realtek card reader does not enter PCIe 1.1/1.2

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1038.43

---
linux-oem (4.15.0-1038.43) bionic; urgency=medium

  [ Ubuntu: 4.15.0-50.54 ]

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS
  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux-oem (4.15.0-1037.42) bionic; urgency=medium

  * linux-oem: 4.15.0-1037.42 -proposed tracker (LP: #1826336)

  * unnecessary request_queue freeze (LP: #1815733)
- block: avoid setting nr_requests to current value
- block: avoid setting none scheduler if it's already none

  * Screen freeze after resume from S3 when HDMI monitor plugged on Dell
Precision 7740 (LP: #1825958)
- PCI: Restore resized BAR state on resume

  [ Ubuntu: 4.15.0-49.53 ]

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)
  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.
  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions
  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- 

[Bug 1825195] Re: qemu dropped osxsave/ospke feature triggering upgrade issues

[Christian Ehrhardt ]

** Changed in: qemu (Ubuntu)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825195

Title:
  qemu dropped osxsave/ospke feature triggering upgrade issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1825195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826336] Re: linux-oem: 4.15.0-1037.42 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1038.43

---
linux-oem (4.15.0-1038.43) bionic; urgency=medium

  [ Ubuntu: 4.15.0-50.54 ]

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS
  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option
  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux-oem (4.15.0-1037.42) bionic; urgency=medium

  * linux-oem: 4.15.0-1037.42 -proposed tracker (LP: #1826336)

  * unnecessary request_queue freeze (LP: #1815733)
- block: avoid setting nr_requests to current value
- block: avoid setting none scheduler if it's already none

  * Screen freeze after resume from S3 when HDMI monitor plugged on Dell
Precision 7740 (LP: #1825958)
- PCI: Restore resized BAR state on resume

  [ Ubuntu: 4.15.0-49.53 ]

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)
  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.
  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions
  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- 

[Bug 1829439] [NEW] GIMP crash when closing the About dialog box

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

```
GNU Image Manipulation Program version 2.10.10
git-describe: 5e662c37d7cc472266989f259c4ae579d66a6617
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/7/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
7.3.0-27ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-7 
--program-prefix=i686-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto 
--enable-targets=all --enable-multiarch --disable-werror --with-arch-32=i686 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu 
--target=i686-linux-gnu
Thread model: posix
gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) 

using GEGL version 0.4.14 (compiled against version 0.4.14)
using GLib version 2.56.4 (compiled against version 2.56.3)
using GdkPixbuf version 2.36.11 (compiled against version 2.36.11)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.40.14 (compiled against version 1.40.14)
using Fontconfig version 2.12.6 (compiled against version 2.12.6)
using Cairo version 1.15.10 (compiled against version 1.15.10)

```
> fatal error: Abandon

Stack trace:
```

# Stack traces obtained from PID 2235 - Thread 2235 #

[New LWP 2236]
[New LWP 2237]
[New LWP 2238]
[New LWP 2239]
[New LWP 2259]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
0xb7fc3d09 in __kernel_vsyscall ()
  Id   Target Id Frame 
* 1Thread 0xb62c8d00 (LWP 2235) "gimp-2.10" 0xb7fc3d09 in __kernel_vsyscall 
()
  2Thread 0xb5d02b40 (LWP 2236) "worker" 0xb7fc3d09 in __kernel_vsyscall ()
  3Thread 0xb4a2cb40 (LWP 2237) "gmain" 0xb7fc3d09 in __kernel_vsyscall ()
  4Thread 0xb422bb40 (LWP 2238) "gdbus" 0xb7fc3d09 in __kernel_vsyscall ()
  5Thread 0xad39ab40 (LWP 2239) "async" 0xb7fc3d09 in __kernel_vsyscall ()
  6Thread 0xab145b40 (LWP 2259) "swap writer" 0xb7fc3d09 in 
__kernel_vsyscall ()

Thread 6 (Thread 0xab145b40 (LWP 2259)):
#0  0xb7fc3d09 in __kernel_vsyscall ()
#1  0xb6d3b3a7 in syscall () at ../sysdeps/unix/sysv/linux/i386/syscall.S:29
#2  0xb6fda11e in g_cond_wait () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb74b551d in  () at /usr/lib/i386-linux-gnu/libgegl-0.4.so.0
#4  0xb6fba66a in  () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb6e293bd in start_thread (arg=0xab145b40) at pthread_create.c:463
pd = 0xab145b40
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1226575872, -1424729280, 
-1226575872, -1424732632, -1584941891, 1278970502}, mask_was_saved = 0}}, priv 
= {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 
0}}}
not_first_call = 0
#6  0xb6d3fe16 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108

Thread 5 (Thread 0xad39ab40 (LWP 2239)):
#0  0xb7fc3d09 in __kernel_vsyscall ()
#1  0xb6d3b3a7 in syscall () at ../sysdeps/unix/sysv/linux/i386/syscall.S:29
#2  0xb6fda11e in g_cond_wait () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x0077b206 in  ()
#4  0xb6fba66a in  () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb6e293bd in start_thread (arg=0xad39ab40) at pthread_create.c:463
pd = 0xad39ab40
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1226575872, -1388729536, 
-1226575872, -1388732888, -98061135, 1278970502}, mask_was_saved = 0}}, priv = 
{pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 
0}}}
not_first_call = 0
#6  0xb6d3fe16 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108

Thread 4 (Thread 0xb422bb40 (LWP 2238)):
#0  0xb7fc3d09 in __kernel_vsyscall ()
#1  0xb6d3543b in __GI___poll (fds=0x1de7680, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 
resultvar = 
sc_cancel_oldtype = 0
sc_ret = 
sc_ret = 
nfds = 2
fds = 0x1de7680
timeout = -1
#2  0xb6fa17c0 in g_poll () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb6f9226a in  () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb6f926b9 in g_main_loop_run () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb733d075 in  () at /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0xb6fba66a in  () at 

[Bug 1641457] Re: Ubuntu Budgie: Some appindicator icons are huge

[Bug Watch Updater]

** Changed in: budgie-indicator-applet
   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/1641457

Title:
  Ubuntu Budgie: Some appindicator icons are huge

To manage notifications about this bug go to:
https://bugs.launchpad.net/budgie-indicator-applet/+bug/1641457/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1668296] Re: not failing back to IPv4 when AAAA returns SERVFAIL

[Bug Watch Updater]

** Changed in: systemd
   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/1668296

Title:
  not failing back to IPv4 when  returns SERVFAIL

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1668296/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682484] Re: systemd: Logging from gnome session is passed on to all syslog facilities

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682484

Title:
  systemd: Logging from gnome session is passed on to all syslog
  facilities

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1682484/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1688689] Re: Owner and group of few files and folders from Bind directory visible as nobody/nogroup within nspawn container

[Bug Watch Updater]

** Changed in: systemd
   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/1688689

Title:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup within nspawn container

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1688689/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824017] Related fix proposed to horizon (stable/stein)

[OpenStack Infra]

Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/659718

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824017

Title:
  stein requires python-cinderclient >= 4.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1824017/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1673215] Re: Second unity8 user session hangs with a black screen

[Bug Watch Updater]

** Changed in: systemd
   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/1673215

Title:
  Second unity8 user session hangs with a black screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1693327] Re: Unable to open file: /etc/ima/ima-policy (-2)

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693327

Title:
  Unable to open file: /etc/ima/ima-policy (-2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1693327/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line

[Bug Watch Updater]

** Changed in: systemd
   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/1682154

Title:
  loginctl ignoring user given sessions IDs at command-line

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1682154/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827102] Re: dpdk 18.11-6 ADT test failure with linux 5.1.0-1.1

[Christian Ehrhardt ]

One day there will be a 5.1 HWE kernel for Bionic.
Most likely this will be part of 17.11.6 and since the 5.1 HWE will take quite 
a while we can wait for that.

** Also affects: dpdk (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: dpdk (Ubuntu Bionic)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827102

Title:
  dpdk 18.11-6 ADT test failure with linux 5.1.0-1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1827102/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591411

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600000] Re: libnss-resolve treats two trailing dots on a domain name incorrectly

[Bug Watch Updater]

** Changed in: systemd
   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/160

Title:
  libnss-resolve treats two trailing dots on a domain name incorrectly

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/160/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1623003] Re: udev-generated /dev/disk/by-path names broken for virtio disks

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623003

Title:
  udev-generated /dev/disk/by-path names broken for virtio disks

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1623003/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1624071] Re: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624071

Title:
  libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624071/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Bug Watch Updater]

** Changed in: systemd
   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/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1628778] Re: systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628778

Title:
  systemd-resolved: after network reconnection, DNSSEC unsigned zones
  treated as bogus, stop resolving

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1628778/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1699850] Re: Reliable network connectivity for apt-daily

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699850

Title:
  Reliable network connectivity for apt-daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1699850/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1703393] Re: TCP offloads disabled by default

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1703393

Title:
  TCP offloads disabled by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1703393/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647485

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1647485/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1627950] Re: Stopped (with error) ... messages on encrypted LVM shutdown

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627950

Title:
  Stopped (with error) ... messages on encrypted LVM shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1627950/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644330] Re: resolved: correctly handle address families with /etc/hosts lookups

[Bug Watch Updater]

** Changed in: systemd
   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/1644330

Title:
  resolved: correctly handle address families with /etc/hosts lookups

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1644330/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1633274] Re: Systemd-networkd crashes with core dump

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633274

Title:
  Systemd-networkd crashes with core dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1633274/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820957] Re: package rdma-core needed for mlx functionality

[Christian Ehrhardt ]

Fixed in Eoan, forgot the bug ref :-/

** Also affects: dpdk (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: dpdk (Ubuntu)
   Status: New => Incomplete

** Changed in: dpdk (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: dpdk (Ubuntu Disco)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820957

Title:
  package rdma-core needed for mlx functionality

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1820957/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

[Timo Aaltonen]

hard to tell, but I know that changes in 5.0.6 (which the ubuntu kernel
in 19.04 basically has) likely did not regress this way

but you are free to test a mainline build of 5.0.2

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.2/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826125

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828992] Re: Merge Chrony 3.4-4

[Launchpad Bug Tracker]

This bug was fixed in the package chrony - 3.4-4ubuntu1

---
chrony (3.4-4ubuntu1) eoan; urgency=medium

  * Merge with Debian unstable (LP: #1828992). Remaining changes:
- d/chrony.conf: use ubuntu ntp pool and server (LP 1744664 1754358)
- Set -x as default if unable to set time (e.g. in containers) (LP 1589780)
  Chrony is a single service which acts as both NTP client (i.e. syncing the
  local clock) and NTP server (i.e. providing NTP services to the network),
  and that is both desired and expected in the vast majority of cases.
  But in containers syncing the local clock is usually impossible, but this
  shall not break the providing of NTP services to the network.
  To some extent this makes chrony's default config more similar to 'ntpd',
  which complained in syslog but still provided NTP server service in those
  cases.
  + debian/chrony.service: allow the service to run without CAP_SYS_TIME
  + debian/control: add new dependency libcap2-bin for capsh (usually
installed anyway, but make them explicit to be sure).
  + debian/chrony.default: new option SYNC_IN_CONTAINER to not fall back
(Default off) [fixed a minor typo in the comment in this update]
  + debian/chronyd-starter.sh: wrapper to handle special cases in containers
and if CAP_SYS_TIME is missing. Effectively allows to run NTP server in
containers on a default installation and avoid failing to sync time (or
if allowed to sync, avoid multiple containers to fight over it by
accident).
  + debian/install: make chrony-starter.sh available on install.
  + debian/docs, debian/README.container: provide documentation about the
handling of this case.
- d/postrm: re-establish systemd-timesyncd on removal (LP 1764357)
- d/postrm: respect policy-rc.d when restoring systemd-timesyncd
  (LP 1771994)
  * Added Changes:
- removed d/init to avoid weird interactions between sysV and systemd
  * Dropped Changes:
- Notify chrony to update sources in response to systemd-networkd
  events (LP: 1718227)
  + d/links: link dispatcher script to networkd-dispatcher events routable
and off
  + d/control: set Recommends to networkd-dispatcher
  [Those are in Debian, except that we agreed to have networkd-dispatcher
   to only be a Suggests]

chrony (3.4-4) unstable; urgency=medium

  * debian/patches/*:
- Add allow-further-syscalls-in-seccomp-filter.patch. Supplementing the
seccomp filter whitelist with those syscalls is a prerequisite, notably for
the arm64 architecture.

  [ Leigh Brown ]
  * debian/patches/*:
- Add allow-recv-send-in-seccomp-filter.patch. Necessary on armel and
ppc64el. Other architectures might also be affected. (Closes: #924494)

chrony (3.4-3) unstable; urgency=medium

  * debian/.gitlab-ci.yml:
- Check for missing hardening flags.

  * debian/patches/*:
- Add allow-_llseek-in-seccomp-filter.patch. Needed on various 32-bit
plateforms to log the {raw}measurements and statistics information when
the seccomp filter is enabled. Thanks a lot to Francesco Poli (wintermute)
 for the report. (Closes: #923137)
- Add allow-waitpid-in-seccomp-filter.patch. Needed to correctly stop
chronyd on some plateforms when the seccomp filter is enabled.

chrony (3.4-2) unstable; urgency=medium

  * debian/.gitlab-ci.yml:
- Replace home-made GitLab CI with the standard Salsa pipeline.
- Allow autopkgtest job to fail. The time-sources-from-dhcp-servers test
currently fails due to a testbed issue on salsa CI.

  * debian/chrony.default:
- Enable the system call filter by default.

  * debian/control:
- Bump standard-version to 4.3.0 (no changes required).
- Use the new debhelper-compat (= 12) notation and drop d/compat.
- Add Pre-Depends: ${misc:Pre-Depends}. Debhelper compatibility level 12
makes use of the “--skip-systemd-native” flag from “invoke-rc.d”. Adding
Pre-Depends: ${misc:Pre-Depends} to d/control ensure that we have a recent
enough version of “init-system-helpers”.
- Suggest networkd-dispatcher.

  * debian/copyright:
- Add myself as a copyright holder for 2019.

  * debian/links:
- Now that “networkd-dispatcher” is in the Debian archive, link
NetworkManager dispatcher script to networkd-dispatcher routable and off
states. Patch cherry-picked from Ubuntu; thanks to Christian Ehrhardt
 for working on this.

  * debian/NEWS:
- Report that a system call filter is now enabled by default and the way
to disable it if needed.

  * debian/rules:
- Don’t enable the system call filter on some architectures due to missing
support in the “libseccomp” and/or the Linux kernel.

  * debian/upstream/:
- Strip upstream key from extra signatures. Thanks lintian!
- Remove the Miroslav-Lichvar.txt file as it serves no purpose.

  * debian/usr.sbin.chronyd:
- 

[Bug 1737569] Re: sosreport does not collect /etc/postgresql contents

[Bug Watch Updater]

** Changed in: sosreport
   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/1737569

Title:
  sosreport does not collect /etc/postgresql contents

To manage notifications about this bug go to:
https://bugs.launchpad.net/sosreport/+bug/1737569/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1734983] Re: Request to backport sosreport v3.5

[Bug Watch Updater]

** Changed in: sosreport
   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/1734983

Title:
  Request to backport sosreport v3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/sosreport/+bug/1734983/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1586691] Re: Update Numix and Greybird for GTK+ 3.20

[Bug Watch Updater]

** Changed in: greybird-gtk-theme
   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/1586691

Title:
  Update Numix and Greybird for GTK+ 3.20

To manage notifications about this bug go to:
https://bugs.launchpad.net/greybird-gtk-theme/+bug/1586691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1703987] Re: New style permitnonkernelfacility imklog option inside module() doesn't work

[Bug Watch Updater]

** Changed in: rsyslog
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1703987

Title:
  New style permitnonkernelfacility imklog option inside module()
  doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/rsyslog/+bug/1703987/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1668722] Re: 60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check

[Bug Watch Updater]

** Changed in: sddm
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668722

Title:
  60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check

To manage notifications about this bug go to:
https://bugs.launchpad.net/sddm/+bug/1668722/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683857] Re: Terminal border doubles when more than 1 tab

[Bug Watch Updater]

** Changed in: greybird-gtk-theme
   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/1683857

Title:
  Terminal border doubles when more than 1 tab

To manage notifications about this bug go to:
https://bugs.launchpad.net/greybird-gtk-theme/+bug/1683857/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828994] Re: POSIX fix for ftrace in ubuntu_kernel_selftests

[Po-Hsu Lin]

*** This bug is a duplicate of bug 1828995 ***
https://bugs.launchpad.net/bugs/1828995

** This bug has been marked a duplicate of bug 1828995
   POSIX fix for ftrace test in ubuntu_kernel_selftests

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828994

Title:
  POSIX fix for ftrace in ubuntu_kernel_selftests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828994/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820490] Re: i find them while xdiagnose

[Launchpad Bug Tracker]

[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/1820490

Title:
  i find them while xdiagnose

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1820490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1793595] Re: [radeon] Shell freezes, mostly when running chrome or editing text files.

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (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/1793595

Title:
  [radeon] Shell freezes, mostly when running chrome or editing text
  files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1793595/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820530] Re: Add arm64 CONFIG_ARCH_MESON=y and related configs Edit

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (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/1820530

Title:
  Add arm64 CONFIG_ARCH_MESON=y and related configs Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820303] Re: Ubuntu 18.04 LTS

[Launchpad Bug Tracker]

[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gdm3 (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/1820303

Title:
  Ubuntu 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820303/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820368] Re: x

[Launchpad Bug Tracker]

[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/1820368

Title:
  x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1820368/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1793595] Re: [radeon] Shell freezes, mostly when running chrome or editing text files.

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (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/1793595

Title:
  [radeon] Shell freezes, mostly when running chrome or editing text
  files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1793595/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829458] [NEW] [ubuntu 19.04]All .desktop configuration files are opening in text editor

[Ron Stephen Mathew]

Public bug reported:

All .desktop configuration files are opening in text editor. Because of
that we can't creat custom shortcuts and having troubles while
application making. Please fix this bug on next update. I have an Ubuntu
19.04.

Tanks

** Affects: glib2.0 (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/1829458

Title:
  [ubuntu 19.04]All .desktop configuration files are opening in text
  editor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme

[Omar Rigoberto Hernandez Sapiens]

Same issue.

Looks like it's the snap version of communitheme-dark.

Switched to communitheme using gnome-tweaks and got the solid-white
background back, though switching back to thedark version and the
transparent background is still there.

Note: First, I tried Mihai Banu (m-banu94) solution and then returned to
snap communitheme (not wayland)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767541

Title:
  Transparent background of calculator in ubuntu 18.04 using
  communitheme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output

[Hui Wang]

** 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/1824259

Title:
  Headphone jack switch sense is inverted: plugging in headphones
  disables headphone output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829447] Re: Fast bootup on fresh install 18.04.2 with kernel 4.18

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-signed-hwe (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/1829447

Title:
  Fast bootup on fresh install 18.04.2 with kernel 4.18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1829447/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827967] Re: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor

[Hui Wang]

** 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/1827967

Title:
  There are 4 HDMI/Displayport audio output listed in sound setting
  without attach any HDMI/DP monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1827967/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827972] Re: The noise keeps occurring when Headset is plugged in on a Dell machine

[Hui Wang]

** 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/1827972

Title:
  The noise keeps occurring when Headset is plugged in on a Dell machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1827972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1819413] Re: [ICL] S0ix Enabling

[AceLan Kao]

Those commits doesn't affect the power consumption on Intel ICL-Y
SDP(alpha), so I'm not sure if they help on power consumption on real
products.

** Description changed:

  Description:
  
  S0ix-states represent the residency in the Intel® SoC idle standby power 
states.
  The S0ix states shut off part of the SoC when they are not in use. The S0ix
  states are triggered when specific conditions within the SoC have been 
achieved,
  for example: certain components are in low power states. The SoC consumes the
  least amount of power in the deepest (for example, S0i3) state.
  
  S0ix is triggered by two paths:
  (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
  on Android device or command manually triggered on any Linux based distros;
  
  (2) by runtime PM, i.e no system activities with display off.
  
  S0ix should simply work in theory with trigger path (1) if we have the device
  drivers ready. On GLK, we require the below PCI device drivers with system PM
  support. ACPI device requirements are WIP.
  
   I2C designware PCI driver
   USB XHCI PCI ID
   Intel trace Hub[NPK) PCI ID
   SPI BXT PCI ID
   SCSI UFS BXT PCI host ID
   Graphics
   Audio
   PWM
   HSUART
   Security engine
  
  S0ix with trigger path (2) require work as defined below.
   All the above device drivers need to support runtime PM (already defined in 
the same LCK above)
   PCI root port to support runtime PM
  
  Both paths will require intel_idle driver support for S0ix support.
  
  238f9c11351f8af8534ae0318b4d9acc77b09ee8
  
  8aba056a4ea6da18186025a335a96b2f071e69d3
  
  6769fdbe27d782dfee5e459e25b44baacc7c8459
  
  cfb55af9add9c19806300fdb31f4cd25e67c6d1a
  
  4a5861f714293767980e4948c9a7c9e5e09c9b94
  
  2a13096ac7da07a1bfc9d91fc4a982020e7ded2b
  
  cd89e92b7399a69512b8d855a2dd145c47399bf8
  
  d6827015e671cd17871c9b7a0fabe06c044f7470
  
  0e68eeea9894feeba2edf7ec63e4551b87f39621
  
  e50af8332785355de3cb40d9f5e8c45dbfc86f53
  
  Target Kernel: 5.1
  Target Release: 19.10
  
  SRU Justification
  [Impact]
  Requires patches to make new INTEL CPU IceLake support s0ix
  [Fix]
  The patch list is provided by Intel
     238f9c11351f platform/x86: intel_pmc_core: Quirk to ignore XTAL
  shutdown
     8aba056a4ea6 platform/x86: intel_pmc_core: Add Package cstates residency 
info
     6769fdbe27d7 platform/x86: intel_pmc_core: Add ICL platform support
     cfb55af9add9 platform/x86: intel_pmc_core: Convert to INTEL_CPU_FAM6 macro
     4a5861f71429 platform/x86: intel_pmc_core: Avoid a u32 overflow
     2a13096ac7da platform/x86: intel_pmc_core: Include Reserved IP for LTR
     cd89e92b7399 platform/x86: intel_pmc_core: Fix file permissions for 
ltr_show
     d6827015e671 platform/x86: intel_pmc_core: Fix PCH IP name
     0e68eeea9894 platform/x86: intel_pmc_core: Fix PCH IP sts reading
     e50af8332785 platform/x86: intel_pmc_core: Handle CFL regmap properly
  
  Below commit fix 238f9c11351f ("platform/x86: intel_pmc_core: Quirk to ignore 
XTAL shutdown")
     9ae11e237d95 platform/x86: intel_pmc_core: Mark local function static
  
  [Test]
  Verified on Intel ICL-Y SDP with fwts s2idle test 30 times, the system is 
still working.
  
  [Regression Risk]
+ Low. Those patches are all small changes, and most of them are adding IDs, 
should be safe to include them.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819413

Title:
  [ICL] S0ix Enabling

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1819413/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1701047] Re: Renaming of conf file fails

[Gunnar Hjalmarsson]

** Also affects: fonts-telu-extra (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fonts-telu-extra (Ubuntu)
   Importance: Undecided => Medium

** Changed in: fonts-telu-extra (Ubuntu)
   Status: New => In Progress

** Changed in: fonts-telu-extra (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: fonts-telu-extra (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: fonts-telu-extra (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: fonts-telu-extra (Ubuntu Bionic)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Description changed:

  [Impact]
  The fix of  wasn't accomplished properly. 
Renamings of conf files weren't addressed in maintainer scripts, upgrades from 
previous versions fail in this respect, and the package system generates 
warning messages.
  
  The problem has been reported in Debian, and the purpose of this bug
  report is to keep track of the progress.
  
  [Justification]
  This config file is broken in xenial and will still be broken on upgrade to 
bionic, which means the fonts in question will not be available to the system 
as intended if the user has upgraded.
  
  [Test case]
  For each of
  - fonts-beng-extra
  - fonts-deva-extra
  - fonts-gujr-extra
  - fonts-guru-extra
- - fonts-orya-extra:
+ - fonts-orya-extra
+ - fonts-telu-extra:
  
  * Purge the package if installed and clean up possible leftovers
-   due to the issue.
+   due to the issue.
  
  * Install the Xenial version of the package and find that the symlink
-   in /etc/fonts/conf.d incorrectly points to a directory.
+   in /etc/fonts/conf.d incorrectly points to a directory.
  
  * Install the version in bionic-release and find that the attempt
-   to fix the issue fails
+   to fix the issue fails
  
  * Install the version in bionic-proposed and find that it fixes the
-   issue and that the symlink now correctly points to the conf file.
+   issue and that the symlink now correctly points to the conf file.
  
  [Regression potential]
  Because this modifies maintainer scripts there is possibility of introducing 
a regression that will cause the package to fail to unpack.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701047

Title:
  Renaming of conf file fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-beng-extra/+bug/1701047/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1819413] Re: [ICL] S0ix Enabling

[AceLan Kao]

** Description changed:

  Description:
  
  S0ix-states represent the residency in the Intel® SoC idle standby power 
states.
  The S0ix states shut off part of the SoC when they are not in use. The S0ix
  states are triggered when specific conditions within the SoC have been 
achieved,
  for example: certain components are in low power states. The SoC consumes the
  least amount of power in the deepest (for example, S0i3) state.
  
  S0ix is triggered by two paths:
  (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
  on Android device or command manually triggered on any Linux based distros;
  
  (2) by runtime PM, i.e no system activities with display off.
  
  S0ix should simply work in theory with trigger path (1) if we have the device
  drivers ready. On GLK, we require the below PCI device drivers with system PM
  support. ACPI device requirements are WIP.
  
   I2C designware PCI driver
   USB XHCI PCI ID
   Intel trace Hub[NPK) PCI ID
   SPI BXT PCI ID
   SCSI UFS BXT PCI host ID
   Graphics
   Audio
   PWM
   HSUART
   Security engine
  
  S0ix with trigger path (2) require work as defined below.
   All the above device drivers need to support runtime PM (already defined in 
the same LCK above)
   PCI root port to support runtime PM
  
  Both paths will require intel_idle driver support for S0ix support.
  
  238f9c11351f8af8534ae0318b4d9acc77b09ee8
  
  8aba056a4ea6da18186025a335a96b2f071e69d3
  
  6769fdbe27d782dfee5e459e25b44baacc7c8459
  
  cfb55af9add9c19806300fdb31f4cd25e67c6d1a
  
  4a5861f714293767980e4948c9a7c9e5e09c9b94
  
  2a13096ac7da07a1bfc9d91fc4a982020e7ded2b
  
  cd89e92b7399a69512b8d855a2dd145c47399bf8
  
  d6827015e671cd17871c9b7a0fabe06c044f7470
  
  0e68eeea9894feeba2edf7ec63e4551b87f39621
  
  e50af8332785355de3cb40d9f5e8c45dbfc86f53
  
  Target Kernel: 5.1
  Target Release: 19.10
+ 
+ SRU Justification
+ [Impact]
+ Requires patches to make new INTEL CPU IceLake support s0ix
+ [Fix]
+ The patch list is provided by Intel
+238f9c11351f platform/x86: intel_pmc_core: Quirk to ignore XTAL 
+ shutdown
+8aba056a4ea6 platform/x86: intel_pmc_core: Add Package cstates residency 
info
+6769fdbe27d7 platform/x86: intel_pmc_core: Add ICL platform support
+cfb55af9add9 platform/x86: intel_pmc_core: Convert to INTEL_CPU_FAM6 macro
+4a5861f71429 platform/x86: intel_pmc_core: Avoid a u32 overflow
+2a13096ac7da platform/x86: intel_pmc_core: Include Reserved IP for LTR
+cd89e92b7399 platform/x86: intel_pmc_core: Fix file permissions for 
ltr_show
+d6827015e671 platform/x86: intel_pmc_core: Fix PCH IP name
+0e68eeea9894 platform/x86: intel_pmc_core: Fix PCH IP sts reading
+e50af8332785 platform/x86: intel_pmc_core: Handle CFL regmap properly
+ 
+ The following 2 commit should be required, too.
+ff7c634b4f7b x86/CPU: Add Icelake model number
+9ae11e237d95 platform/x86: intel_pmc_core: Mark local function static
+ 
+ [Test]
+ Verified on Intel ICL-Y SDP with fwts s2idle test 30 times, the system is 
still working.
+ 
+ [Regression Risk]

** Description changed:

  Description:
  
  S0ix-states represent the residency in the Intel® SoC idle standby power 
states.
  The S0ix states shut off part of the SoC when they are not in use. The S0ix
  states are triggered when specific conditions within the SoC have been 
achieved,
  for example: certain components are in low power states. The SoC consumes the
  least amount of power in the deepest (for example, S0i3) state.
  
  S0ix is triggered by two paths:
  (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
  on Android device or command manually triggered on any Linux based distros;
  
  (2) by runtime PM, i.e no system activities with display off.
  
  S0ix should simply work in theory with trigger path (1) if we have the device
  drivers ready. On GLK, we require the below PCI device drivers with system PM
  support. ACPI device requirements are WIP.
  
   I2C designware PCI driver
   USB XHCI PCI ID
   Intel trace Hub[NPK) PCI ID
   SPI BXT PCI ID
   SCSI UFS BXT PCI host ID
   Graphics
   Audio
   PWM
   HSUART
   Security engine
  
  S0ix with trigger path (2) require work as defined below.
   All the above device drivers need to support runtime PM (already defined in 
the same LCK above)
   PCI root port to support runtime PM
  
  Both paths will require intel_idle driver support for S0ix support.
  
  238f9c11351f8af8534ae0318b4d9acc77b09ee8
  
  8aba056a4ea6da18186025a335a96b2f071e69d3
  
  6769fdbe27d782dfee5e459e25b44baacc7c8459
  
  cfb55af9add9c19806300fdb31f4cd25e67c6d1a
  
  4a5861f714293767980e4948c9a7c9e5e09c9b94
  
  2a13096ac7da07a1bfc9d91fc4a982020e7ded2b
  
  cd89e92b7399a69512b8d855a2dd145c47399bf8
  
  d6827015e671cd17871c9b7a0fabe06c044f7470
  
  0e68eeea9894feeba2edf7ec63e4551b87f39621
  
  e50af8332785355de3cb40d9f5e8c45dbfc86f53
  
  Target Kernel: 5.1
  Target Release: 19.10
  
  SRU 

[Bug 1813134] Re: cp_abort in powerpc/context_switch from ubunut_kernel_selftests failed on Bionic P9

[Po-Hsu Lin]

Test no longer exist.

** 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/1813134

Title:
  cp_abort in powerpc/context_switch from ubunut_kernel_selftests failed
  on Bionic P9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813134/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825195] Re: qemu dropped osxsave/ospke feature triggering upgrade issues

[Launchpad Bug Tracker]

This bug was fixed in the package libvirt - 5.0.0-1ubuntu4

---
libvirt (5.0.0-1ubuntu4) eoan; urgency=medium

  * d/p/ubuntu/lp-1825195-*.patch: fix issues with old guests that defined
the never functional osxsave and ospke features (LP: #1825195).
  * d/p/series: reorder ubuntu Delta
  * d/p/ubuntu-aa/lp-1815910-allow-vhost-net.patch: avoid apparmor issues
with vhost-net/vhost-vsock/vhost-scsi hotplug (LP: #1815910)
  * d/p/ubuntu-aa/lp-1829223-virt-aa-helper-allow-vhost-scsi.patch fix
vhost-scsi hotplug in virt-aa-helper (LP: #1829223)

libvirt (5.0.0-1ubuntu3) eoan; urgency=medium

  * SECURITY UPDATE: Add support for md-clear functionality
- debian/patches/ubuntu/md-clear.patch: Define md-clear CPUID bit in
  src/cpu_map/x86_features.xml.
- CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091

 -- Christian Ehrhardt   Thu, 16 May
2019 10:42:09 +0200

** Changed in: libvirt (Ubuntu Eoan)
   Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12126

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12127

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12130

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11091

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825195

Title:
  qemu dropped osxsave/ospke feature triggering upgrade issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1825195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829223] Re: vhost-scsi triggers virt-aa-helper error

[Launchpad Bug Tracker]

This bug was fixed in the package libvirt - 5.0.0-1ubuntu4

---
libvirt (5.0.0-1ubuntu4) eoan; urgency=medium

  * d/p/ubuntu/lp-1825195-*.patch: fix issues with old guests that defined
the never functional osxsave and ospke features (LP: #1825195).
  * d/p/series: reorder ubuntu Delta
  * d/p/ubuntu-aa/lp-1815910-allow-vhost-net.patch: avoid apparmor issues
with vhost-net/vhost-vsock/vhost-scsi hotplug (LP: #1815910)
  * d/p/ubuntu-aa/lp-1829223-virt-aa-helper-allow-vhost-scsi.patch fix
vhost-scsi hotplug in virt-aa-helper (LP: #1829223)

libvirt (5.0.0-1ubuntu3) eoan; urgency=medium

  * SECURITY UPDATE: Add support for md-clear functionality
- debian/patches/ubuntu/md-clear.patch: Define md-clear CPUID bit in
  src/cpu_map/x86_features.xml.
- CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091

 -- Christian Ehrhardt   Thu, 16 May
2019 10:42:09 +0200

** Changed in: libvirt (Ubuntu)
   Status: Triaged => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12126

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12127

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12130

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11091

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829223

Title:
  vhost-scsi triggers virt-aa-helper error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1829223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815910] Re: Apparmor blocks access to /dev/vhost-net

[Launchpad Bug Tracker]

This bug was fixed in the package libvirt - 5.0.0-1ubuntu4

---
libvirt (5.0.0-1ubuntu4) eoan; urgency=medium

  * d/p/ubuntu/lp-1825195-*.patch: fix issues with old guests that defined
the never functional osxsave and ospke features (LP: #1825195).
  * d/p/series: reorder ubuntu Delta
  * d/p/ubuntu-aa/lp-1815910-allow-vhost-net.patch: avoid apparmor issues
with vhost-net/vhost-vsock/vhost-scsi hotplug (LP: #1815910)
  * d/p/ubuntu-aa/lp-1829223-virt-aa-helper-allow-vhost-scsi.patch fix
vhost-scsi hotplug in virt-aa-helper (LP: #1829223)

libvirt (5.0.0-1ubuntu3) eoan; urgency=medium

  * SECURITY UPDATE: Add support for md-clear functionality
- debian/patches/ubuntu/md-clear.patch: Define md-clear CPUID bit in
  src/cpu_map/x86_features.xml.
- CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091

 -- Christian Ehrhardt   Thu, 16 May
2019 10:42:09 +0200

** Changed in: libvirt (Ubuntu Eoan)
   Status: Triaged => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12126

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12127

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12130

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11091

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815910

Title:
  Apparmor blocks access to /dev/vhost-net

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-compute/+bug/1815910/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1302777] Re: Bluetooth turns itself off continuously.

[Daniel van Vugt]

JaSaunders,

Ubuntu 14.04 reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer release and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is still a
paid support option:

  https://www.ubuntu.com/esm

---

Grashdur,

We released a fix that might help you just today, so please try that:

  https://launchpad.net/ubuntu/+source/gnome-bluetooth/3.28.0-2ubuntu0.2

If that doesn't help then please open a new bug by running:

  ubuntu-bug bluez



** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302777

Title:
  Bluetooth turns itself off continuously.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1302777/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829400] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829400

Title:
  [Intel Core 2 Duo T7250] screen loop after suspension.  Kernel 4.15
  fails but 4.4.0 works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829400/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

[Daniel van Vugt]

Modesetting provides vsync and avoids tearing in all cases except in
some edge cases:

  * Multi-monitor
  * Xrandr scaling
  * Other broken packages like this bug

But those are just bugs. One of them is fixed here and the rest should
be fixed eventually in:

  https://gitlab.freedesktop.org/xorg/xserver/merge_requests/24

You can call it "TearFree" if you like, but one of the reasons
modesetting doesn't contain an option by that name is that it aims to
never tear. So an option by the name "TearFree" isn't required. If it
does tear then that's just a bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801071

Title:
  XPresentPixmap() BadWindow, recompiling fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxpresent/+bug/1801071/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829400] Re: [Intel Core 2 Duo T7250] screen loop after suspension. Kernel 4.15 fails but 4.4.0 works.

[Daniel van Vugt]

Thanks for the bug report.

Please try to find the two closest kernel versions where one works and
one doesn't. You can download them from:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

** Summary changed:

- screen loop after suspension
+ [Intel Core 2 Duo T7250] screen loop after suspension.  Kernel 4.15 fails but 
4.4.0 works.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829400

Title:
  [Intel Core 2 Duo T7250] screen loop after suspension.  Kernel 4.15
  fails but 4.4.0 works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829400/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829430] Re: [nouveau] Xorg freeze

[Daniel van Vugt]

Thanks for the bug report.

1. If you have any gnome-shell extensions (other than the default Ubuntu
ones) then please uninstall them and retest. We find a large number of
bugs are caused by Gnome extensions.

2. Your kernel log mentions a few errors from the nouveau kernel driver:

[  274.310794] nouveau :01:00.0: bus: MMIO read of  FAULT at 619444 
[ IBUS ]
[  274.959650] nouveau :01:00.0: bus: MMIO read of  FAULT at 619444 
[ IBUS ]
[  294.627149] nouveau :01:00.0: bus: MMIO read of  FAULT at 619444 
[ IBUS ]
[  305.108717] nouveau :01:00.0: bus: MMIO read of  FAULT at 619444 
[ IBUS ]

but we can't know for sure if those are related to what you see.

Please try installing the proprietary Nvidia driver instead, as it
usually provides better stability:

  sudo apt install nvidia-driver-418

I am confident one of those two suggestions will solve the problem.
Please tell us which (if any) works.


** Summary changed:

- Xorg freeze
+ [nouveau] Xorg freeze

** Tags added: nouveau

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: 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/1829430

Title:
  [nouveau] Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1829430/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829185] Re: linux-hwe: 4.18.0-21.22~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1829186
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 16. May 2019 15:35 UTC
  reason:
-   promote-to-proposed: Holding -- builds not complete in ppa
+   promote-to-proposed: Pending -- builds not complete in ppa 
signed:retry-needed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829185

Title:
  linux-hwe: 4.18.0-21.22~18.04.1 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829185/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

[Mark Haiman]

I am seeing a similar problem.

Linux Mint 18.3 XFCE, Lenovo Thinkpad T60 i686 / ATI Radeon RV515 GPU

After upgrade to kernel 4.15.0-48, I get a black screen and frozen
keyboard once the boot splash screen exits, when the login screen should
appear.  There is no mouse pointer, and I can't escape with ctrl-alt-f1,
ctrl-alt-backspace, etc.  If I leave the system running for a while,
there is occasional disk activity, and syslog entries with later time
stamps, indicating that the kernel is still running, but the X server is
frozen.

Same thing with latest kernel 4.15.0-50.

I can boot into the previous kernel 4.15.0-47 with no problems.

If I boot into run level 3 (terminal only, no GUI) by editing the Grub
kernel command line, the system will boot, but enters the same frozen
state if I then start the GUI with 'sudo service lightdm start' (which
works fine with the previous 4.15.0-47 kernel).

If I add "nomodeset" to the kernel command line, the system will boot
into the GUI.  In this case Xorg.0.log shows that the X server unloads
the Radeon driver (which will not run without KMS) and loads the
fallback VESA driver instead.  I.e., on my computer the bug affects the
Radeon driver but not the VESA driver.  (However, this is not a solution
for me because the VESA driver doesn't handle my 1400x1050 screen
resolution correctly.)

One other thing - the bug happens maybe 9 times out of 10 but not every
time.  On the occasional successful boot, once the GUI comes up without
freezing, everything seems to work OK.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829292] Re: exim4 doesn't run the local_scan function after upgrade to 19.04

[Bryce Harrington]

** Description changed:

- It seems like after upgrade to 19.04 that exim is not running the
- local_scan function (in my case the sa-exim /usr/lib/exim4/local_scan
- /sa-exim.so)
+ [Impact]
+ Regression causing breakage of spam filtering for Exim4 users when using 
sa-exim for spamassassin integration.
+ 
+ 
+ [Test Case]
+ TBD
+ 
+ [Regression Potential]
+ Low.  The 'local_scan' function was removed due to concerns it might allow 
rewriting of emails in invalid situations.  However, this risk has been equally 
present in previous exim4 releases thus does not create any new issues, just 
restores behavior to what it has been in the past.
+ 
+ This is the only major change in debian right now (the only other change
+ being a README note).
+ 
+ 
+ [Discussion]
+ Upstream dropped support for a 'local_scan' function in 4.92, that sa-exim 
requires; Debian restored support for this capability in 4.92-7, but disco is 
shipping 4.92-4ubuntu1 without the restored support.
+ 
+ The reason upstream dropped the support was out of concern that changes
+ in how emails are handled internally will break rewriting in certain
+ circumstances.  Unfortunately this breaks compatibility with sa-exim,
+ which uses local_scan to do spamassassin checking to reject spam emails
+ pre-acceptance.
+ 
+ 
+ [Original Report]
+ It seems like after upgrade to 19.04 that exim is not running the local_scan 
function (in my case the sa-exim /usr/lib/exim4/local_scan/sa-exim.so)
  
  So I now don't have the spam-scan I am used to(I have enabled scanning
  by the way of an RCPT_ACL for now)
  
  Hope this can fixed despite sa-exim being very old
  
  Description:Ubuntu 19.04
  Release:19.04
  
  exim4-daemon-heavy:
-   Installed: 4.92-4ubuntu1
-   Candidate: 4.92-4ubuntu1
-   Version table:
-  *** 4.92-4ubuntu1 500
- 500 http://dk.archive.ubuntu.com/ubuntu disco/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 4.92-4ubuntu1
+   Candidate: 4.92-4ubuntu1
+   Version table:
+  *** 4.92-4ubuntu1 500
+ 500 http://dk.archive.ubuntu.com/ubuntu disco/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  I expect to see in /var/log/exim4/mainlog lines like this as I saw before:
  2019-05-12 20:01:54 1hPsnJ-000285-Jj SA: Debug: check succeeded, running spamc
  2019-05-12 20:02:01 1hPsnJ-000285-Jj SA: Action: scanned but message isn't 
spam: score=2.5 required=5.0 (scanned in 7/7 secs | Message-Id: 
duxufv23y44bfkuepz1f4naeoavbh7xtz_es_rsbndc.erur4y-b0k2tn61ykllctsv6z3yzr3hqkm9umv94...@devotestream.icu).
 From  (host=NULL [185.254.236.42]) for 
  
  I don't see that after upgrading to 19.04 this saturday

** Changed in: exim4 (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: exim4 (Ubuntu Disco)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** Changed in: exim4 (Ubuntu Disco)
Milestone: None => disco-updates

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829292

Title:
  exim4 doesn't run the local_scan function after upgrade to 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1829292/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

[Zhanglei Mao]

For #44, in the following testing, if disable hibmc_drm loading, then it
works fine and would not be hang.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940

Title:
  Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI
  boot mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828116] Re: Password works uppercase and lowercase

[Seth Arnold]

It's almost certainly unrelated to your report, but check out these
errors in your logs:

May 16 08:16:11 hostname /usr/lib/gdm3/gdm-x-session[1820]: 
/usr/bin/prime-supported: 38: /usr/bin/prime-supported: cannot create 
/var/log/prime-supported.log: Permission denied
May 16 08:16:11 hostname /usr/lib/gdm3/gdm-x-session[1820]: 
/sbin/prime-offload: 30: /sbin/prime-offload: cannot create 
/var/log/prime-offload.log: Permission denied

These may be indicative of further problems elsewhere in your video
drivers.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828116

Title:
  Password works uppercase and lowercase

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1828116/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829098] Re: package mysql-server-5.7 5.7.26-0ubuntu0.18.10.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess was killed by signal (Terminated)

[Felipe Sitta]

Hi.

Turns out I identified the root of this problem.

The cause was the "skip-grant-tables" on mysqld.cnf file.

I use this so I can bypass a permission error on a fresh installed
mysql. I just didn't knew I had to remove it after I changed the admin
password.

Removed the line and the process followed as intended.

I think this issue can be closed. Thanks for the attention.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829098

Title:
  package mysql-server-5.7 5.7.26-0ubuntu0.18.10.1 failed to
  install/upgrade: installed mysql-server-5.7 package post-installation
  script subprocess was killed by signal (Terminated)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1829098/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766068] Re: Using Zsh, it doesn't show an error message when command not found

[Bug Watch Updater]

** Changed in: command-not-found (Debian)
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766068

Title:
  Using Zsh, it doesn't show an error message when command not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1766068/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829450] [NEW] test_systemd_fsck_with_plymouth_failure passes but marked expected failure

[Dan Streetman]

Public bug reported:

[impact]

this test case was marked as expected failure in the past to try to
ignore failures, but it now passes and so causes autopkgtest failures.

[test case]

run autopkgtest and check for the
'test_systemd_fsck_with_plymouth_failure' test, e.g.:

test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest)
Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... 
bash: line 1:   786 Killed  
/tmp/autopkgtest.84SCbj/build.1op/src/debian/tests/systemd-fsckd 2> >(tee -a 
/tmp/autopkgtest.84SCbj/systemd-fsckd-stderr >&2) > >(tee -a 
/tmp/autopkgtest.84SCbj/systemd-fsckd-stdout)
autopkgtest [16:47:57]: test process requested reboot with marker 
test_systemd_fsck_with_plymouth_failure:0
Connection to 10.44.40.6 closed by remote host.
autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds...
test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest)
Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... 
unexpected success

--
Ran 1 test in 17.952s

FAILED (unexpected successes=1)

[regression potential]

low; test case expectation fix only.

** Affects: systemd (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/1829450

Title:
  test_systemd_fsck_with_plymouth_failure passes but marked expected
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820130] Re: modem-manager-gui assert failure: munmap_chunk(): invalid pointer

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: modem-manager-gui (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/1820130

Title:
  modem-manager-gui assert failure: munmap_chunk(): invalid pointer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1820130/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1743792] Re: kernel panic on ioctl(TUNSETIFF) with a dev name with '/'

[Tyler Hicks]

For anyone coming here for information on CVE-2018-7191,
0ad646c81b2182f7fa67ec0c8c825e0ee165696d is the fix for the CVE and
5c25f65fd1e42685f7ccd80e0621829c105785d9 is a bugfix for the fix.

The other commit mentioned, 93161922c658c714715686cd0cf69b090cb9bf1d, is
unrelated to CVE-2018-7191.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743792

Title:
  kernel panic on ioctl(TUNSETIFF) with a dev name with '/'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743792/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1829173
- phase: Ready for Packaging
- phase-changed: Wednesday, 15. May 2019 11:31 UTC
+ phase: Packaging
+ phase-changed: Friday, 17. May 2019 00:03 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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829168

Title:
  linux-gcp: 5.0.0-1007.7 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829447] [NEW] Fast bootup on fresh install 18.04.2 with kernel 4.18

[lotuspsychje]

Public bug reported:

Ubuntu 18.04.2 LTS up to date @ 17/5/2019 with kernel: 4.18.0-20-generic


I had ubuntu 18.04.2 installed with kernel 4.15(from the start 18.04.0) and 
experienced a very slow systemd bootup
and compared it with exact the same system on a fresh install 18.04.2 with 
kernel 4.18
wich was extremely faster.

Installing the HWE kernel 4.18 over the 4.15 system did not fix the slow boot, 
i had to fresh install
18.04.2 with kernel 4.18 and now it boots fast again:

lotuspsychje@RootBoX:~$ systemd-analyze
Startup finished in 2.948s (kernel) + 22.106s (userspace) = 25.055s
graphical.target reached after 22.098s in userspace

what could be the bottleneck for the 4.15 users?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.18.0-20-generic 4.18.0-20.21~18.04.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 17 01:51:02 2019
InstallationDate: Installed on 2019-05-16 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829447

Title:
  Fast bootup on fresh install 18.04.2 with kernel 4.18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1829447/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829448] [NEW] desktop icons vanish with libre office writer file save

[peterzay]

Public bug reported:

Procedure to reproduce this bug:
- odt file resides on desktop
- double click to edit
- save
- many but not all desktop icons vanish
- click X to close writer window
- vanished desktop icons reappear

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libreoffice-core 1:6.2.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 16 20:05:52 2019
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2019-04-18 (28 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829448

Title:
  desktop icons vanish with libre office writer file save

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1829448/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1743792] Re: kernel panic on ioctl(TUNSETIFF) with a dev name with '/'

[Seth Arnold]

Thanks for commenting on this issue. I'm sorry we lost track of proper
public attribution for the discovery.

Yes, you may use this CVE publicly. (And thanks for asking.)

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743792

Title:
  kernel panic on ioctl(TUNSETIFF) with a dev name with '/'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743792/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 5.0.0-1007.7 -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/1829168

Title:
  linux-gcp: 5.0.0-1007.7 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829156] Re: Chrome multimedia keys doesn't work after screen lock 18.04

[Sebastien Bacher]

Button on the keyboard? Also you wrote "other programs like vlc & stock
video player." did that miss some words, or could you explain what it
means?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829156

Title:
  Chrome multimedia keys doesn't work after screen lock 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1829156/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825378] Re: systemd-networkd doesn't set wireguard peer endpoint

[John Doe]

I don't have access to the affected systems at the moment, but the test
case and your summary looks correct.

Thanks for taking a look at this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825378

Title:
  systemd-networkd doesn't set wireguard peer endpoint

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825378/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823038] Re: Neutron-keepalived-state-change fails to check initial router state

[OpenStack Infra]

Reviewed:  https://review.opendev.org/657849
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=aacd11ab9f8f24291f369d23662b0cb6b3fe43e3
Submitter: Zuul
Branch:master

commit aacd11ab9f8f24291f369d23662b0cb6b3fe43e3
Author: Rodolfo Alonso Hernandez 
Date:   Fri May 10 10:58:08 2019 +

Remove rootwrap configuration from neutron-keepalived-state-change

New IP command introduced by Ie3fe825d65408fc969c478767b411fe0156e9fbc
requires only privsep initialization. This patch removes the prisep
error FailedToDropPrivileges when executed under neutron-rootwrap.

Closes-Bug: #1823038

Change-Id: I6cde3c9dae7ffdccce49e88c3c79d1c379f291cf


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823038

Title:
  Neutron-keepalived-state-change fails to check initial router state

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1823038/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829445] Re: package libgtk-3-common 3.18.9-1ubuntu3.3 failed to install/upgrade: package libgtk-3-common is already installed and configured

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829445

Title:
  package libgtk-3-common 3.18.9-1ubuntu3.3 failed to install/upgrade:
  package libgtk-3-common is already installed and configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1829445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829445] [NEW] package libgtk-3-common 3.18.9-1ubuntu3.3 failed to install/upgrade: package libgtk-3-common is already installed and configured

[kesia ramalho soier]

Public bug reported:

nao consigo baixar arquivos para instalar o windows

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgtk-3-common 3.18.9-1ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Thu May 16 15:51:47 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DuplicateSignature:
 package:libgtk-3-common:3.18.9-1ubuntu3.3
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
 dpkg: error processing package ubuntu-mono (--configure):
  package ubuntu-mono is already installed and configured
ErrorMessage: package libgtk-3-common is already installed and configured
InstallationDate: Installed on 2019-04-15 (31 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: dpkg
Title: package libgtk-3-common 3.18.9-1ubuntu3.3 failed to install/upgrade: 
package libgtk-3-common is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dpkg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829445

Title:
  package libgtk-3-common 3.18.9-1ubuntu3.3 failed to install/upgrade:
  package libgtk-3-common is already installed and configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1829445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction

[Paul Larson]

Strange, that link seems to suggest it is in proposed already, but when I try 
to run 'do-release-upgrade -p -f DistUpgradeViewNonInteractive', I don't seem 
to get that. Do I need to do some other manual step to get it first, or do I 
need it from xenial instead since that's where I'm coming from? Even though I 
used -p, proposed doesn't seem to be on in /etc/apt/source.list
(after I got the error from above again, I killed the upgrader and checked this)
$ apt-cache policy ubuntu-release-upgrader-core
ubuntu-release-upgrader-core:
  Installed: 1:18.04.32
  Candidate: 1:18.04.32
  Version table:
 *** 1:18.04.32 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages
100 /var/lib/dpkg/status
 1:18.04.17 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796193

Title:
  DistUpgradeViewNonInteractive crashes / requires interaction

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826845] Re: Unable to build sysdig module on 5.0.0-13.14~18.04.2 linux-hwe-edge kernel

[Connor Kuehl]

** Description changed:

  [ Impact ]
  
   * The DKMS package fails to install on 5.0 kernels.
  
  [ Test Case ]
  
   * Install the 'sysdig-dkms' package. It should build and install
  without any compilation failures.
  
  [ Proposed Fix ]
  
   * Port the following patches:
     - 
https://github.com/draios/sysdig/commit/2c8f0263382bf64800faec5fba5cc3e005d9fb1e.patch
     - 
https://github.com/draios/sysdig/commit/3248bf70d677abe6f60bb9f8275a774600ed77e8.patch
  
  Note: No real context adjustments required, offset updates were required
  to apply the patch to fixup the syscall table; "quilt refresh" updated
  offsets on the patch that was already in the package.
  
  [ Regression Potential ]
  
   * Low. These changes are conditionally compiled.
  
  [ Testing ]
  
  The following instructions were used to test these changes on the 4.15
  kernel that Bionic 18.04 ships with as well as the 5.0 kernel that is
  included in the HWE edge package on an amd64 environment.
  
  - Create a Bionic 18.04 VM
  - Enable the "-proposed" repository and install the 
linux-generic-hwe-18.04-edge package or install the .debs from here: 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+packages?field.name_filter=linux-hwe-edge_filter=published_filter=bionic
  - Install "sysdig-dkms" and confirm that installation fails because the 
module cannot be compiled
  - Remove the failed install "sudo apt remove sysdig-dkms"
- - Pull the sources with "pull-lp-source sysdig"
+ - Pull the sources with "pull-lp-source sysdig bionic"
  - Apply the debdiff with "debdiff-apply < path-to-file.debdiff"
  - Build the package with "debuild -b -uc -us"
  - Install the package produced from the previous step with "sudo dpkg -i 
path-to-file.deb"
  - Verify the installation completed successfully. You can also check to see 
if it appears with "sudo dkms status"
  
  ---
  
  ubuntu_sysdig_smoke_test failed because the module cannot be built on
  Bionic 5.0.0 kernel:
  
   Error! Bad return status for module build on kernel: 5.0.0-13-generic 
(x86_64)
   Consult /var/lib/dkms/sysdig/0.19.1/build/make.log for more information.
   Setting up libjsoncpp1:amd64 (1.7.4-3) ...
   Setting up sysdig (0.19.1-1ubuntu1) ...
   Processing triggers for libc-bin (2.27-3ubuntu1) ...
  'dkms status -m sysdig | grep installed'
  'cat /var/lib/dkms/sysdig/*/build/make.log'
   DKMS make.log for sysdig-0.19.1 for kernel 5.0.0-13-generic (x86_64)
   Thu Apr 25 14:14:16 UTC 2019
   make: Entering directory '/usr/src/linux-headers-5.0.0-13-generic'
   CC [M] /var/lib/dkms/sysdig/0.19.1/build/main.o
   CC [M] /var/lib/dkms/sysdig/0.19.1/build/dynamic_params_table.o
   CC [M] /var/lib/dkms/sysdig/0.19.1/build/flags_table.o
   CC [M] /var/lib/dkms/sysdig/0.19.1/build/ppm_events.o
   CC [M] /var/lib/dkms/sysdig/0.19.1/build/ppm_fillers.o
   CC [M] /var/lib/dkms/sysdig/0.19.1/build/event_table.o
   CC [M] /var/lib/dkms/sysdig/0.19.1/build/syscall_table.o
   CC [M] /var/lib/dkms/sysdig/0.19.1/build/ppm_cputime.o
   /var/lib/dkms/sysdig/0.19.1/build/main.c: In function ‘page_fault_probe’:
   /var/lib/dkms/sysdig/0.19.1/build/main.c:2045:2: warning: ISO C90 forbids 
mixed declarations and code [-Wdeclaration-after-statement]
   struct event_data_t event_data;
   ^~
   /var/lib/dkms/sysdig/0.19.1/build/ppm_events.c: In function 
‘ppm_copy_from_user’:
   /var/lib/dkms/sysdig/0.19.1/build/ppm_events.c:99:48: error: macro 
"access_ok" passed 3 arguments, but takes just 2
   if (likely(ppm_access_ok(VERIFY_READ, from, n)))
   ^
   In file included from ./include/linux/export.h:45:0,
   from ./include/linux/linkage.h:7,
   from ./arch/x86/include/asm/cache.h:5,
   from ./include/linux/cache.h:6,
   from ./include/linux/time.h:5,
   from ./include/linux/compat.h:10,
   from /var/lib/dkms/sysdig/0.19.1/build/ppm_events.c:21:
   /var/lib/dkms/sysdig/0.19.1/build/ppm_events.c:59:23: error: ‘access_ok’ 
undeclared (first use in this function); did you mean ‘access_flags’?
   #define ppm_access_ok access_ok
   ^
   ./include/linux/compiler.h:76:40: note: in definition of macro ‘likely’
   # define likely(x) __builtin_expect(!!(x), 1)
   ^
   /var/lib/dkms/sysdig/0.19.1/build/ppm_events.c:99:13: note: in expansion of 
macro ‘ppm_access_ok’
   if (likely(ppm_access_ok(VERIFY_READ, from, n)))
   ^
   /var/lib/dkms/sysdig/0.19.1/build/ppm_events.c:59:23: note: each undeclared 
identifier is reported only once for each function it appears in
   #define ppm_access_ok access_ok
   ^
   ./include/linux/compiler.h:76:40: note: in definition of macro ‘likely’
   # define likely(x) __builtin_expect(!!(x), 1)
   ^
   /var/lib/dkms/sysdig/0.19.1/build/ppm_events.c:99:13: note: in expansion of 
macro ‘ppm_access_ok’
   if (likely(ppm_access_ok(VERIFY_READ, from, n)))
   ^
   /var/lib/dkms/sysdig/0.19.1/build/ppm_events.c: In function 
‘ppm_strncpy_from_user’:
   /var/lib/dkms/sysdig/0.19.1/build/ppm_events.c:130:54: error: macro 
"access_ok" passed 3 

[Bug 1829200] Re: linux-gcp: 4.15.0-1033.35 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

** 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 1829196 (xenial/linux-gcp)
  
  -- swm properties --
  kernel-stable-master-bug: 1829219
- phase: Ready for Packaging
- phase-changed: Wednesday, 15. May 2019 15:05 UTC
+ phase: Packaging
+ phase-changed: Thursday, 16. May 2019 22:37 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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829200

Title:
  linux-gcp: 4.15.0-1033.35 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829200/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829017] Re: [SRU] Enable support for Train Cloud Archive

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.98.2

---
software-properties (0.98.2) eoan; urgency=medium

  * cloudarchive: Enable support for the Train Ubuntu Cloud Archive on
18.04 (LP: #1829017).

 -- Corey Bryant   Tue, 14 May 2019 09:51:17
-0400

** Changed in: software-properties (Ubuntu Eoan)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829017

Title:
  [SRU] Enable support for Train Cloud Archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829017/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829200] Re: linux-gcp: 4.15.0-1033.35 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1033.35 -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/1829200

Title:
  linux-gcp: 4.15.0-1033.35 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829200/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829216] Re: linux-hwe: 4.15.0-51.55~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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 1829215 (linux-hwe-edge)
  
  -- swm properties --
  kernel-stable-master-bug: 1829219
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 16. May 2019 11:07 UTC
  reason:
-   promote-to-proposed: Holding -- builds not complete in ppa
+   promote-to-proposed: Pending -- builds not complete in ppa 
signed:retry-needed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829216

Title:
  linux-hwe: 4.15.0-51.55~16.04.1 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829216/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828116] Re: Password works uppercase and lowercase

[G S]

** Attachment added: "journalctl"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1828116/+attachment/5264391/+files/journal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828116

Title:
  Password works uppercase and lowercase

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1828116/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828116] Re: Password works uppercase and lowercase

[G S]

If it's too short, I'll paste the full log.

> Does it happen with simple password? like if you "sudo passwd "
and set "one" does it log in using "ONE"?

Yes

> "dpkg -l | grep pam"

ii  libpam-cap:amd64   1:2.25-1.2   
amd64POSIX 1003.1e capabilities (PAM module)
ii  libpam-gnome-keyring:amd64 3.28.0.2-1ubuntu1.18.04.1
amd64PAM module to unlock the GNOME keyring upon login
ii  libpam-modules:amd64   1.1.8-3.6ubuntu2.18.04.1 
amd64Pluggable Authentication Modules for PAM
ii  libpam-modules-bin 1.1.8-3.6ubuntu2.18.04.1 
amd64Pluggable Authentication Modules for PAM - helper 
binaries
ii  libpam-runtime 1.1.8-3.6ubuntu2.18.04.1 
all  Runtime support for the PAM library
ii  libpam-systemd:amd64   237-3ubuntu10.21 
amd64system and service manager - PAM module
ii  libpam0g:amd64 1.1.8-3.6ubuntu2.18.04.1 
amd64Pluggable Authentication Modules library
ii  thunderbird1:60.6.1+build2-0ubuntu0.18.04.1 
amd64Email, RSS and newsgroup client with integrated spam 
filter

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828116

Title:
  Password works uppercase and lowercase

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1828116/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829437] [NEW] apt purge apache2 doesn't delete /etc/apache2

[marvin]

Public bug reported:

Expected:
After removing apache2 via 'apt remove --purge ^apache2*' all files and 
directory should be purged from the system.

What happend:
After purging of apache2 /etc/apache2 still exists.
The only file, that still exists is within /etc/apache2 is: 
/etc/apache2/conf-available/javascript-common.conf 

This probably prevents the removal of /etc/apache2

Reproduce:
fresh install Ubuntu bionic
apt update
apt install apache2
apt remove --purge ^apache2*
ls /etc/apache2

Versions:
System:
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic

Apache:
Package: apache2 
Version: 2.4.29-1ubuntu4.6
Priority: optional
Section: web
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian Apache Maintainers 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug

** Affects: apache2 (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- apt purge apache2 doesn't deletes /etc/apache2
+ apt purge apache2 doesn't delete /etc/apache2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829437

Title:
  apt purge apache2 doesn't delete /etc/apache2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1829437/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829364] Re: Will not play sound via HDMI unless you run pavucontrol first

[Jarno Suni]

When pavucontrol is not running, it depends on sample rate of playback,
whether or not the sound is audible:

$ speaker-test -r 48000
not audible

$ speaker-test -r 47999
audible

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829364

Title:
  Will not play sound via HDMI unless you run pavucontrol first

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829028] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From cls...@us.ibm.com 2019-05-16 17:37 EDT---
This issue will be handle with a salesforce ticket so rejecting.

Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829028

Title:
  Ubuntu 18.04 - EEH error on Mellanox CX5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1829028/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs