[Group.of.nepali.translators] [Bug 2059556] Re: xenial/linux-aws: 4.4.0-1168.183 -proposed tracker

[Timo Aaltonen]

** Changed in: kernel-sru-workflow/new-review
   Status: Triaged => In Progress

** Changed in: kernel-sru-workflow/new-review
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in kernel-sru-workflow/new-review
 Status explanation: unset => from:

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-aws

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-aws
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-aws --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15928529 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15928530
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-aws/4.4.0-1168.183 \
linux-meta-aws/4.4.0.1168.172 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2059556

Title:
  xenial/linux-aws: 4.4.0-1168.183 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws source package in Xenial:
  New

Bug description:
  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 --
  built:
from: e1118f3e7d1fef69
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11791
  kernel-stable-master-bug: 2059563
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Friday, 12. April 2024 14:08 UTC
  reason:
boot-testing: Stalled -s testing FAILED
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.4.0-1168.183
meta: 4.4.0.1168.172
  ~~:
announce:
  swm-transition-crankable: 2024-04-11 11:42:41.585183
clamps:
  new-review: e1118f3e7d1fef69
  self: 4.4.0-1168.183
  sru-review: e1118f3e7d1fef69
tracker:
  last-message: '2024-04-12 14:15:22.175547+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2059556/+subscriptions


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 2059581] Re: xenial/linux-oracle: 4.15.0-1130.141~16.04.1 -proposed tracker

[Timo Aaltonen]

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-oracle

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-oracle
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> signing:pro/3 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-oracle --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914669 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914670 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914675 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914671
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-oracle/4.15.0-1130.141~16.04.1 \
linux-meta-oracle/4.15.0.1130.141~16.04.1 \
linux-generate-oracle/4.15.0-1130.141~16.04.1 \
  --to signing:pro/3 --to-suite xenial
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-signed-oracle/4.15.0-1130.141~16.04.1/signing \
  --to signing:pro/3 --to-suite xenial
copy \
  --from signing:pro/3 --from-suite xenial --sources \
linux-oracle/4.15.0-1130.141~16.04.1 \
linux-meta-oracle/4.15.0.1130.141~16.04.1 \
linux-signed-oracle/4.15.0-1130.141~16.04.1 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial
delete \
  --from signing:pro/3 --from-suite xenial --sources \
linux-oracle/4.15.0-1130.141~16.04.1 \
linux-meta-oracle/4.15.0.1130.141~16.04.1 \
linux-generate-oracle/4.15.0-1130.141~16.04.1 \
linux-signed-oracle/4.15.0-1130.141~16.04.1

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2059581

Title:
  xenial/linux-oracle: 4.15.0-1130.141~16.04.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Triaged
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle source package in Xenial:
  New

Bug description:
  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 --
  built:
from: a4e5680be0a5d9a1
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11817
  kernel-stable-master-bug: 2059582
  packages:
generate: linux-generate-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 08. April 2024 08:43 UTC
  reason:
sru-review: Stalled -s ready for review (built)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1130.141~16.04.1
meta: 4.15.0.1130.141~16.04.1
signed: 4.15.0-1130.141~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-04-05 14:11:54.140233
clamps:
  new-review: a4e5680be0a5d9a1
  self: 4.15.0-1130.141~16.04.1
  sru-review: a4e5680be0a5d9a1
tracker:
  last-message: '2024-04-05 18:45:15.892235+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-signing-jobs/task00/+bu

[Group.of.nepali.translators] [Bug 2059577] Re: xenial/linux-gcp: 4.15.0-1161.178~16.04.1 -proposed tracker

[Timo Aaltonen]

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-gcp

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-gcp
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> signing:pro/3 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-gcp --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914953 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914954 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914968 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914955
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-gcp/4.15.0-1161.178~16.04.1 \
linux-meta-gcp/4.15.0.1161.178~16.04.1 \
linux-generate-gcp/4.15.0-1161.178~16.04.1 \
  --to signing:pro/3 --to-suite xenial
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-signed-gcp/4.15.0-1161.178~16.04.1/signing \
  --to signing:pro/3 --to-suite xenial
copy \
  --from signing:pro/3 --from-suite xenial --sources \
linux-gcp/4.15.0-1161.178~16.04.1 \
linux-meta-gcp/4.15.0.1161.178~16.04.1 \
linux-signed-gcp/4.15.0-1161.178~16.04.1 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial
delete \
  --from signing:pro/3 --from-suite xenial --sources \
linux-gcp/4.15.0-1161.178~16.04.1 \
linux-meta-gcp/4.15.0.1161.178~16.04.1 \
linux-generate-gcp/4.15.0-1161.178~16.04.1 \
linux-signed-gcp/4.15.0-1161.178~16.04.1

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2059577

Title:
  xenial/linux-gcp: 4.15.0-1161.178~16.04.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Triaged
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp source package in Xenial:
  New

Bug description:
  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 --
  built:
from: 2c6503b0ed511d3c
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11813
  kernel-stable-master-bug: 2059578
  packages:
generate: linux-generate-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 08. April 2024 08:43 UTC
  reason:
sru-review: Stalled -s ready for review (built)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1161.178~16.04.1
meta: 4.15.0.1161.178~16.04.1
signed: 4.15.0-1161.178~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-04-05 15:54:47.079741
clamps:
  new-review: 2c6503b0ed511d3c
  self: 4.15.0-1161.178~16.04.1
  sru-review: 2c6503b0ed511d3c
tracker:
  last-message: '2024-04-05 21:45:09.295837+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2059577/+subscriptions

[Group.of.nepali.translators] [Bug 2059566] Re: xenial/linux-aws-hwe: 4.15.0-1167.180~16.04.1 -proposed tracker

[Timo Aaltonen]

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-aws-hwe

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-aws-hwe
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> signing:pro/3 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-aws-hwe --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914427 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914429 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914520 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15914431
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-aws-hwe/4.15.0-1167.180~16.04.1 \
linux-meta-aws-hwe/4.15.0.1167.180~16.04.1 \
linux-generate-aws-hwe/4.15.0-1167.180~16.04.1 \
  --to signing:pro/3 --to-suite xenial
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-signed-aws-hwe/4.15.0-1167.180~16.04.1/signing \
  --to signing:pro/3 --to-suite xenial
copy \
  --from signing:pro/3 --from-suite xenial --sources \
linux-aws-hwe/4.15.0-1167.180~16.04.1 \
linux-meta-aws-hwe/4.15.0.1167.180~16.04.1 \
linux-signed-aws-hwe/4.15.0-1167.180~16.04.1 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial
delete \
  --from signing:pro/3 --from-suite xenial --sources \
linux-aws-hwe/4.15.0-1167.180~16.04.1 \
linux-meta-aws-hwe/4.15.0.1167.180~16.04.1 \
linux-generate-aws-hwe/4.15.0-1167.180~16.04.1 \
linux-signed-aws-hwe/4.15.0-1167.180~16.04.1

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2059566

Title:
  xenial/linux-aws-hwe: 4.15.0-1167.180~16.04.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Triaged
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws-hwe source package in Xenial:
  New

Bug description:
  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 --
  built:
from: afda4cd6b3686d6e
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11802
  kernel-stable-master-bug: 2059567
  packages:
generate: linux-generate-aws-hwe
main: linux-aws-hwe
meta: linux-meta-aws-hwe
signed: linux-signed-aws-hwe
  phase: Testing
  phase-changed: Friday, 05. April 2024 19:32 UTC
  reason:
boot-testing: Stalled -s testing FAILED
sru-review: Stalled -s ready for review (built)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1167.180~16.04.1
meta: 4.15.0.1167.180~16.04.1
signed: 4.15.0-1167.180~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-04-04 16:54:08.762970
clamps:
  new-review: afda4cd6b3686d6e
  self: 4.15.0-1167.180~16.04.1
  sru-review: afda4cd6b3686d6e
tracker:
  last-message: '2024-04-05 17:45:13.846193+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.ne

[Group.of.nepali.translators] [Bug 2059560] Re: xenial/linux-kvm: 4.4.0-1131.141 -proposed tracker

[Timo Aaltonen]

** Changed in: kernel-sru-workflow/new-review
   Status: Triaged => In Progress

** Changed in: kernel-sru-workflow/new-review
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in kernel-sru-workflow/new-review
 Status explanation: unset => from:

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-kvm

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-kvm
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-kvm --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15910731 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15910732
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-kvm/4.4.0-1131.141 \
linux-meta-kvm/4.4.0.1131.128 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2059560

Title:
  xenial/linux-kvm: 4.4.0-1131.141 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Triaged
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm source package in Xenial:
  New

Bug description:
  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 --
  built:
from: 54c27f6c5b64654e
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11795
  kernel-stable-master-bug: 2059563
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 04. April 2024 19:16 UTC
  reason:
sru-review: Stalled -s ready for review (built)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.4.0-1131.141
meta: 4.4.0.1131.128
  ~~:
announce:
  swm-transition-crankable: 2024-04-04 10:46:16.696387
clamps:
  new-review: 54c27f6c5b64654e
  self: 4.4.0-1131.141
  sru-review: 54c27f6c5b64654e
tracker:
  last-message: '2024-04-04 17:45:33.372653+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2059560/+subscriptions


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 2059569] Re: xenial/linux-azure: 4.15.0-1176.191~16.04.1 -proposed tracker

[Timo Aaltonen]

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-azure

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-azure
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> signing:pro/3 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-azure --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15910861 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15910863 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15910956 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15910864
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-azure/4.15.0-1176.191~16.04.1 \
linux-meta-azure/4.15.0.1176.191~16.04.1 \
linux-generate-azure/4.15.0-1176.191~16.04.1 \
  --to signing:pro/3 --to-suite xenial
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-signed-azure/4.15.0-1176.191~16.04.1/signing \
  --to signing:pro/3 --to-suite xenial
copy \
  --from signing:pro/3 --from-suite xenial --sources \
linux-azure/4.15.0-1176.191~16.04.1 \
linux-meta-azure/4.15.0.1176.191~16.04.1 \
linux-signed-azure/4.15.0-1176.191~16.04.1 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial
delete \
  --from signing:pro/3 --from-suite xenial --sources \
linux-azure/4.15.0-1176.191~16.04.1 \
linux-meta-azure/4.15.0.1176.191~16.04.1 \
linux-generate-azure/4.15.0-1176.191~16.04.1 \
linux-signed-azure/4.15.0-1176.191~16.04.1

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2059569

Title:
  xenial/linux-azure: 4.15.0-1176.191~16.04.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Triaged
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure source package in Xenial:
  New

Bug description:
  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 --
  built:
from: 6a55c883f8fb3eb1
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11805
  kernel-stable-master-bug: 2059571
  packages:
generate: linux-generate-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 04. April 2024 22:52 UTC
  reason:
sru-review: Stalled -s ready for review (built)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1176.191~16.04.1
meta: 4.15.0.1176.191~16.04.1
signed: 4.15.0-1176.191~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-04-03 20:31:19.212491
clamps:
  new-review: 6a55c883f8fb3eb1
  self: 4.15.0-1176.191~16.04.1
  sru-review: 6a55c883f8fb3eb1
tracker:
  last-message: '2024-04-04 20:15:16.551723+00:00'

To manage notifications about this bug go to:
https://bugs

[Group.of.nepali.translators] [Bug 2059583] Re: xenial/linux-hwe: 4.15.0-224.236~16.04.1 -proposed tracker

[Timo Aaltonen]

** Changed in: kernel-sru-workflow/new-review
   Status: Triaged => In Progress

** Changed in: kernel-sru-workflow/new-review
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in kernel-sru-workflow/new-review
 Status explanation: unset => from:

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-hwe

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-hwe
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> signing:pro/3 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-hwe --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15907979 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15907980 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15907984 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15907981
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-hwe/4.15.0-224.236~16.04.1 \
linux-meta-hwe/4.15.0.224.236~16.04.1 \
linux-generate-hwe/4.15.0-224.236~16.04.1 \
  --to signing:pro/3 --to-suite xenial
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-signed-hwe/4.15.0-224.236~16.04.1/signing \
  --to signing:pro/3 --to-suite xenial
copy \
  --from signing:pro/3 --from-suite xenial --sources \
linux-hwe/4.15.0-224.236~16.04.1 \
linux-meta-hwe/4.15.0.224.236~16.04.1 \
linux-signed-hwe/4.15.0-224.236~16.04.1 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial
delete \
  --from signing:pro/3 --from-suite xenial --sources \
linux-hwe/4.15.0-224.236~16.04.1 \
linux-meta-hwe/4.15.0.224.236~16.04.1 \
linux-generate-hwe/4.15.0-224.236~16.04.1 \
linux-signed-hwe/4.15.0-224.236~16.04.1

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2059583

Title:
  xenial/linux-hwe: 4.15.0-224.236~16.04.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Triaged
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-hwe source package in Xenial:
  New

Bug description:
  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 --
  built:
from: 948bf9913515ed7a
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11818
  kernel-stable-master-bug: 2059584
  packages:
generate: linux-generate-hwe
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 04. April 2024 03:56 UTC
  reason:
sru-review: Stalled -s ready for review (built)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-224.236~16.04.1
meta: 4.15.0.224.236~16.04.1
signed: 4.15.0-224.236~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-04-02 16:53:38.237871
clamps:
  new-review: 948bf9913515ed7a
  self: 4.15.0-224.236~16.04.1
 

[Group.of.nepali.translators] [Bug 2055900] Re: xenial/linux-aws: 4.4.0-1167.182 -proposed tracker

[Timo Aaltonen]

** Changed in: kernel-sru-workflow/sru-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2055900

Title:
  xenial/linux-aws: 4.4.0-1167.182 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws source package in Xenial:
  New

Bug description:
  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 --
  auto-prepare:
cycle: s2024.01.08
previous-cycle: s2024.01.08
  built:
from: 9c4b8e23065beefb
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11468
  kernel-stable-master-bug: 2055907
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Monday, 18. March 2024 19:16 UTC
  reason:
boot-testing: Stalled -s testing FAILED
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.4.0-1167.182
meta: 4.4.0.1167.171
  ~~:
announce:
  swm-transition-crankable: 2024-03-18 10:11:27.996384
  swm-transition-peer-reviewable: 2024-03-18 12:49:35.811314
clamps:
  new-review: 9c4b8e23065beefb
  self: 4.4.0-1167.182
  sru-review: 9c4b8e23065beefb
tracker:
  last-message: '2024-03-18 19:30:09.127809+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2055900/+subscriptions


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 2055900] Re: xenial/linux-aws: 4.4.0-1167.182 -proposed tracker

[Timo Aaltonen]

** Changed in: kernel-sru-workflow/new-review
   Status: Triaged => In Progress

** Changed in: kernel-sru-workflow/new-review
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in kernel-sru-workflow/new-review
 Status explanation: unset => from:

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-aws

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-aws
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-aws --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15864939 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15864940
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-aws/4.4.0-1167.182 \
linux-meta-aws/4.4.0.1167.171 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2055900

Title:
  xenial/linux-aws: 4.4.0-1167.182 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Triaged
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws source package in Xenial:
  New

Bug description:
  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 --
  auto-prepare:
cycle: s2024.01.08
previous-cycle: s2024.01.08
  built:
from: 9c4b8e23065beefb
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11468
  kernel-stable-master-bug: 2055907
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Monday, 18. March 2024 19:16 UTC
  reason:
boot-testing: Stalled -s testing FAILED
sru-review: Stalled -s ready for review (built)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.4.0-1167.182
meta: 4.4.0.1167.171
  ~~:
announce:
  swm-transition-crankable: 2024-03-18 10:11:27.996384
  swm-transition-peer-reviewable: 2024-03-18 12:49:35.811314
clamps:
  new-review: 9c4b8e23065beefb
  self: 4.4.0-1167.182
  sru-review: 9c4b8e23065beefb
tracker:
  last-message: '2024-03-18 19:30:09.127809+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2055900/+subscriptions


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 2055921] Re: xenial/linux-gcp: 4.15.0-1160.177~16.04.1 -proposed tracker

[Timo Aaltonen]

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-gcp

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-gcp
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> signing:pro/3 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-gcp --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15859783 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15859784 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15859795 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15859785
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-gcp/4.15.0-1160.177~16.04.1 \
linux-meta-gcp/4.15.0.1160.150 \
linux-generate-gcp/4.15.0-1160.177~16.04.1 \
  --to signing:pro/3 --to-suite xenial
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-signed-gcp/4.15.0-1160.177~16.04.1/signing \
  --to signing:pro/3 --to-suite xenial
copy \
  --from signing:pro/3 --from-suite xenial --sources \
linux-gcp/4.15.0-1160.177~16.04.1 \
linux-meta-gcp/4.15.0.1160.150 \
linux-signed-gcp/4.15.0-1160.177~16.04.1 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial
delete \
  --from signing:pro/3 --from-suite xenial --sources \
linux-gcp/4.15.0-1160.177~16.04.1 \
linux-meta-gcp/4.15.0.1160.150 \
linux-generate-gcp/4.15.0-1160.177~16.04.1 \
linux-signed-gcp/4.15.0-1160.177~16.04.1

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2055921

Title:
  xenial/linux-gcp: 4.15.0-1160.177~16.04.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Triaged
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp source package in Xenial:
  New

Bug description:
  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 --
  built:
from: 976741fec59a0c50
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11490
  kernel-stable-master-bug: 2055922
  packages:
generate: linux-generate-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Saturday, 16. March 2024 07:10 UTC
  reason:
sru-review: Stalled -s ready for review (built)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1160.177~16.04.1
meta: 4.15.0.1160.150
signed: 4.15.0-1160.177~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-03-14 18:25:24.422612
clamps:
  new-review: 976741fec59a0c50
  self: 4.15.0-1160.177~16.04.1
  sru-review: 976741fec59a0c50
tracker:
  last-message: '2024-03-15 18:45:07.621330+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2055921/+subscriptions


___
Mailing lis

[Group.of.nepali.translators] [Bug 2055925] Re: xenial/linux-oracle: 4.15.0-1129.140~16.04.1 -proposed tracker

[Timo Aaltonen]

** Changed in: kernel-sru-workflow/new-review
   Status: Triaged => In Progress

** Changed in: kernel-sru-workflow/new-review
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in kernel-sru-workflow/new-review
 Status explanation: unset => from:

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-oracle

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-oracle
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> signing:pro/3 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-oracle --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15857318 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15857319 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15857332 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15857320
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-oracle/4.15.0-1129.140~16.04.1 \
linux-meta-oracle/4.15.0.1129.110 \
linux-generate-oracle/4.15.0-1129.140~16.04.1 \
  --to signing:pro/3 --to-suite xenial
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-signed-oracle/4.15.0-1129.140~16.04.1/signing \
  --to signing:pro/3 --to-suite xenial
copy \
  --from signing:pro/3 --from-suite xenial --sources \
linux-oracle/4.15.0-1129.140~16.04.1 \
linux-meta-oracle/4.15.0.1129.110 \
linux-signed-oracle/4.15.0-1129.140~16.04.1 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial
delete \
  --from signing:pro/3 --from-suite xenial --sources \
linux-oracle/4.15.0-1129.140~16.04.1 \
linux-meta-oracle/4.15.0.1129.110 \
linux-generate-oracle/4.15.0-1129.140~16.04.1 \
linux-signed-oracle/4.15.0-1129.140~16.04.1

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2055925

Title:
  xenial/linux-oracle: 4.15.0-1129.140~16.04.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Triaged
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle source package in Xenial:
  New

Bug description:
  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 --
  built:
from: ae1f577763306700
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11494
  kernel-stable-master-bug: 2055926
  packages:
generate: linux-generate-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 14. March 2024 23:06 UTC
  reason:
sru-review: Stalled -s ready for review (built)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1129.140~16.04.1
meta: 4.15.0.1129.110
signed: 4.15.0-1129.140~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-03-14 10:54:32.323347
clamps:
  new-review: ae1f5777633

[Group.of.nepali.translators] [Bug 2055910] Re: xenial/linux-aws-hwe: 4.15.0-1166.179~16.04.1 -proposed tracker

[Timo Aaltonen]

** Changed in: canonical-signing-jobs/task00
   Importance: Undecided => Medium

** Changed in: canonical-signing-jobs/task00
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in canonical-signing-jobs/task00
 Importance explanation: unset => xenial:linux-aws-hwe

** Changed in canonical-signing-jobs/task00
 Status explanation: unset => # title kernel xenial:linux-aws-hwe
# route ppa:canonical-kernel-esm/ubuntu/ppa2 -> signing:pro/3 -> 
ppa:canonical-kernel-esm/ubuntu/proposed2
validate \
  --exclude xenial:linux-aws-hwe --publications \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15857285 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15857286 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15857309 \
~canonical-kernel-esm/+archive/ubuntu/ppa2/+sourcepub/15857287
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-aws-hwe/4.15.0-1166.179~16.04.1 \
linux-meta-aws-hwe/4.15.0.1166.149 \
linux-generate-aws-hwe/4.15.0-1166.179~16.04.1 \
  --to signing:pro/3 --to-suite xenial
copy \
  --from ppa:canonical-kernel-esm/ubuntu/ppa2 --from-suite xenial --sources \
linux-signed-aws-hwe/4.15.0-1166.179~16.04.1/signing \
  --to signing:pro/3 --to-suite xenial
copy \
  --from signing:pro/3 --from-suite xenial --sources \
linux-aws-hwe/4.15.0-1166.179~16.04.1 \
linux-meta-aws-hwe/4.15.0.1166.149 \
linux-signed-aws-hwe/4.15.0-1166.179~16.04.1 \
  --to ppa:canonical-kernel-esm/ubuntu/proposed2 --to-suite xenial
delete \
  --from signing:pro/3 --from-suite xenial --sources \
linux-aws-hwe/4.15.0-1166.179~16.04.1 \
linux-meta-aws-hwe/4.15.0.1166.149 \
linux-generate-aws-hwe/4.15.0-1166.179~16.04.1 \
linux-signed-aws-hwe/4.15.0-1166.179~16.04.1

** Changed in: canonical-signing-jobs/task00
   Status: New => Triaged

** Changed in: kernel-sru-workflow/new-review
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2055910

Title:
  xenial/linux-aws-hwe: 4.15.0-1166.179~16.04.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Triaged
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Triaged
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws-hwe source package in Xenial:
  New

Bug description:
  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 --
  auto-prepare:
cycle: s2024.01.08
previous-cycle: s2024.01.08
  built:
from: a19cae626e7e5c13
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11479
  kernel-stable-master-bug: 2055911
  packages:
generate: linux-generate-aws-hwe
main: linux-aws-hwe
meta: linux-meta-aws-hwe
signed: linux-signed-aws-hwe
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 15. March 2024 00:11 UTC
  reason:
sru-review: Stalled -s ready for review (built)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1166.179~16.04.1
meta: 4.15.0.1166.149
signed: 4.15.0-1166.179~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-03-14 11:21:09.212507
clamps:
  new-review: a19cae626e7e5c13
  self: 4.15.0-1166.179~16.04.1
  sru-review: a19cae626e7e5c13
tracker:
  last-message: '2024-03-14 19:45:07.727514+00:00'

To manage notifications about this bug go to:
ht

[Group.of.nepali.translators] [Bug 2044657] Re: Multiple data corruption issues in zfs

[Timo Aaltonen]

** Changed in: zfs-linux (Ubuntu Lunar)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2044657

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  Incomplete
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1581076] Re: Xorg segfaults on start-up on Big Endian PPC hardware

[Timo Aaltonen]

** Changed in: xorg-server-lts-xenial (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: xorg-server-lts-xenial (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1581076

Title:
  Xorg segfaults on start-up on Big Endian PPC hardware

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-lts-xenial package in Ubuntu:
  Invalid
Status in xorg-server-lts-xenial source package in Trusty:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server-lts-xenial source package in Xenial:
  Invalid

Bug description:
  On my Big Endian PowerPC machine, Xorg segfaults when starting. I have
  been able to confirm that this does not happen when building Xorg from
  upstream source, and then further confirmed that the source of the
  segfault appears to be caused by a non-upstreamed, ubuntu specific
  patch.

  When building the xorg-server-1.18.3 deb from source, I commented out
  the following patches from debian/patches/series to try to isolate the
  source of the crash. With the following patches not-applied, and the
  resulting .deb package built, the segfault on start does not occur.

  08_xfree86_fix_ia64_inx_outx.diff
  105_nvidia_autodetect.patch
  168_glibc_trace_to_stderr.patch
  188_default_primary_to_first_busid.patch
  190_cache-xkbcomp_output_for_fast_start_up.patch
  191-Xorg-add-an-extra-module-path.patch
  232-xf86compatoutput-valgrind.patch
  no-nv.patch
  228_autobind_gpu.patch
  xf86-inactive-gpuscreen.patch
  config-add-no-removal.patch
  xf86-ignore-conflicting-rr-caps.patch
  fix-detach-gpu.patch
  disable-rotation-transform-gpuscreens.patch
  xmir.patch
  xmir-desktop-file-hint-flag.patch
  drm_device_keep_trying.patch
  xi2-resize-touch.patch
  xmir-fixes.diff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1581076/+subscriptions


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 2017013] Re: net: sched: Fix use after free in red_enqueue()

[Timo Aaltonen]

oem-5.14 is EOL

** Changed in: linux-oem-5.14 (Ubuntu)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2017013

Title:
  net: sched: Fix use after free in red_enqueue()

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
  Won't Fix
Status in linux-oem-5.17 package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  We can't use "skb" again after passing it to qdisc_enqueue().  This is
  basically identical to commit 2f09707 ("sch_sfb: Also store skb
  len before calling child enqueue").

  Fixes: d7f4f33 ("sch_red: update backlog as well")

  [Fix]
  Cherry picked from upstream.

  [Test case]
  Compile, boot and basic network functionality tested using ntop.

  [Potential regression]
  Low. This has been in multiple trees for a while now.

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1968016] Re: Use kernel-testing repo from launchpad for ADT tests

[Timo Aaltonen]

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.17 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Kinetic)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1968016

Title:
  Use kernel-testing repo from launchpad for ADT tests

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-oem-5.14 source package in Trusty:
  Invalid
Status in linux-oem-5.17 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-oem-5.14 source package in Xenial:
  Invalid
Status in linux-oem-5.17 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-5.14 source package in Bionic:
  Invalid
Status in linux-oem-5.17 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux-oem-5.17 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  New

Bug description:
  In ADT tests, we are still using the kernel-testing repo from
  kernel.ubuntu.com, it should be migrated to launchpad instead
  to align with our other testing repos.

  For autotest-client-tests repo change, it will needs to be handled
  in the kernel-testing repo directly, see bug 1968257.

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1999567] Re: [SRU] Bring translations from launchpad

[Timo Aaltonen]

Hello Lucas, or anyone else affected,

Accepted update-notifier into kinetic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.192.59.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: update-notifier (Ubuntu Kinetic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

** Changed in: update-notifier (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1999567

Title:
  [SRU] Bring translations from launchpad

Status in update-notifier package in Ubuntu:
  Invalid
Status in update-notifier source package in Xenial:
  New
Status in update-notifier source package in Bionic:
  New
Status in update-notifier source package in Focal:
  New
Status in update-notifier source package in Jammy:
  New
Status in update-notifier source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  In the last couple releases we have not updated the translations from  
Launchpad. We are bringing them to the source package in an effort to unblock 
this SRU release:
  https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1991030

  This is because the launchpad translations already have the "pro
  status" string properly translated.

  Not only this will unblock this SRU, but it will make the package
  aligned with the launchpad translations.

  [Test Case]
  To test this change, we will need to verify if the message:
  See https://ubuntu.com/esm or run: sudo pro status

  Is correctly translated for the languages that have added support for
  this message.

  [Regression Potential]
  Since we are bringing the translations from launchpad, there could be 
translations done directly in the package that are now missed. Although this is 
unlikely, since the translations on Launchpad are better maintained them the 
ones in the package.

  Note that update-notifier is not using language pack (reasons in
  https://launchpad.net/bugs/562900) so it relies on translations
  updates to be included in the source. We used to do such 'export
  translations for launchpad and include them in the vcs' but that
  hadn't been done since 2013 which means none of the strings added in
  the last years for ua and now ubuntu pro have a working translation
  today, such the risk of regression a translated string there is rather
  inexistant

  [Other Info]
  We have some gray areas regarding the verification of this bug. The target 
message:

  See https://ubuntu.com/esm or run: sudo pro status

  Is not translated into all Ubuntu releases, like Xenial. For those releases, 
we are then just updating the translations using the Launchpad
  language packs.

  Therefore, we might need future SRUs just to update the translation of
  new messages into these releases.

  Additionally, we are still searching for a good way to just verify
  translation updates in the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1999567/+subscriptions


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1983035] Please test proposed package

[Timo Aaltonen]

Hello Michael, or anyone else affected,

Accepted snapd into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/snapd/2.57.5+20.04 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: snapd (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: snapd (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1983035

Title:
  [SRU] 2.57

Status in snapd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Invalid
Status in snapd source package in Bionic:
  Fix Committed
Status in snapd source package in Focal:
  Fix Committed
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Kinetic:
  Fix Released

Bug description:
  This is a new version of snapd.

  The changelog is available here
  https://github.com/snapcore/snapd/blob/2.57/packaging/ubuntu-16.04/changelog,
  the raw git changelog is available here:
  https://github.com/snapcore/snapd/commits/2.57 (note that the debian
  changelog is auto-generated from the merges of the git commits so
  there is usually no need to look at the raw git commits).

  The snappy team released a new release that we want SRU into bionc+.
  The new process described in https://wiki.ubuntu.com/SnapdUpdates was
  used and we have done integration-tests on the snappy images,
  autopkgtests on classic and unit tests.

  GitHub Actions test runs can be found at
  https://github.com/snapcore/snapd/actions?query=branch%3Arelease%2F2.57

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1983035] Re: [SRU] 2.57

[Timo Aaltonen]

Hello Michael, or anyone else affected,

Accepted snapd into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/snapd/2.57.5+22.04 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: snapd (Ubuntu Jammy)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done verification-done-jammy
** Tags added: verification-needed verification-needed-jammy

** Changed in: snapd (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1983035

Title:
  [SRU] 2.57

Status in snapd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Invalid
Status in snapd source package in Bionic:
  Fix Committed
Status in snapd source package in Focal:
  Fix Committed
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Kinetic:
  Fix Released

Bug description:
  This is a new version of snapd.

  The changelog is available here
  https://github.com/snapcore/snapd/blob/2.57/packaging/ubuntu-16.04/changelog,
  the raw git changelog is available here:
  https://github.com/snapcore/snapd/commits/2.57 (note that the debian
  changelog is auto-generated from the merges of the git commits so
  there is usually no need to look at the raw git commits).

  The snappy team released a new release that we want SRU into bionc+.
  The new process described in https://wiki.ubuntu.com/SnapdUpdates was
  used and we have done integration-tests on the snappy images,
  autopkgtests on classic and unit tests.

  GitHub Actions test runs can be found at
  https://github.com/snapcore/snapd/actions?query=branch%3Arelease%2F2.57

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1968016] Re: Use kernel-testing repo from launchpad for ADT tests

[Timo Aaltonen]

** Changed in: linux-oem-5.17 (Ubuntu)
   Status: Fix Committed => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1968016

Title:
  Use kernel-testing repo from launchpad for ADT tests

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-oem-5.14 source package in Trusty:
  Invalid
Status in linux-oem-5.17 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-oem-5.14 source package in Xenial:
  Invalid
Status in linux-oem-5.17 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-5.14 source package in Bionic:
  Invalid
Status in linux-oem-5.17 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux-oem-5.17 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  In ADT tests, we are still using the kernel-testing repo from
  kernel.ubuntu.com, it should be migrated to launchpad instead
  to align with our other testing repos.

  For autotest-client-tests repo change, it will needs to be handled
  in the kernel-testing repo directly, see bug 1968257.

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1758800] Re: hda driver initialization takes too much time on the machine with coffeelake audio controller [8086:a348]

[Timo Aaltonen]

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

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1758800

Title:
  hda driver initialization takes too much time on the machine with
  coffeelake audio controller [8086:a348]

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [Impact]

  We have a couple of laptop and desktop computers, all of them are cfl 
platforms
  and all of them have cfl audio controller [8086:a348], and these computers 
have
  different realtek codecs on them (alc256, alc255, alc289 and ...). The hda
  driver takes too much time (3 secs - 8 secs) to initialize on these machines.
  This problem never happened on kbl, skl, bdw, ... before.

  Sometimes this can make pulseaudio can't work well.

  pulseaudio starts, but the driver (as kernel modules) initialization has not
  finished, then there is no valid sink in the pulseaudio. At this moment, some 
UI
  Apps already start using pulseaudio to play sound, but users can't hear the 
sound
  as expected. This problem never happened before, it is exposed on cfl 
platforms,
  and all cfl platforms (with audio controller 8086:a348) have this problem.

  [Fix]
  Set the polling mode can fix this problem, and this workaround is in the
  mainline kernel.

  [Test Case]
  Boot the machine and check the dmesg, from the hda log, we can see the driver
  initialization is finished within 0.1s and pulseaudio works well.

  [Regression Potential]
  No regression, this fix is only for CFL audio controller (8086:a348), and
  in theory, polling mode is safe for all audio controllers, using interrupt
  mode rather than polling mode on other platforms just wants to save polling
  overhead for CPUs, since interrupt mode can't work well on CFL platform, we
  have to use polling mode.

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1786574] Re: remove i2c-i801 from blacklist

[Timo Aaltonen]

** Changed in: hwe-next
   Status: In Progress => Fix Released

** Changed in: oem-priority
   Status: In Progress => Fix Released

** Changed in: kmod (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

** Changed in: kmod (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: kmod (Ubuntu Bionic)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1786574

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Won't Fix
Status in kmod source package in Bionic:
  Won't Fix
Status in kmod source package in Cosmic:
  Won't Fix

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1881124] Re: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210

[Timo Aaltonen]

** Changed in: hwe-next
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1881124

Title:
  I2C bus on Dell Edge Gateway stops working after upgrading to
  Ubuntu-4.4.0-180.210

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  I2C stops working after kernel upgrade:

  [   13.812210] i2c_designware 80860F41:01: Unknown Synopsys component type: 
0x
  [   13.855837] i2c_designware 80860F41:01: timeout in enabling adapter
  
  [   14.856276] i2c_designware 80860F41:01: controller timed out   

 
  [   14.856288] i2c_designware 80860F41:01: Unknown Synopsys component type: 
0x

  
  This is caused by the commit

  commit 5568c3f29fbd0ec0d9bb0f805bacc5755180c5cb
  Author: Andy Shevchenko 
  Date:   Fri Dec 4 23:49:18 2015 +0200

  Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"

  BugLink: https://bugs.launchpad.net/bugs/1878232

  commit b5f88dd1d6efc472e35ca1b21a44e662c5422088 upstream.

  The specific power domain can't be used in a way provided by the commit
  01ac170ba29a, i.e. pointer to platform device is a subject to change 
during
  unbound / bind cycle.

  This reverts commit 01ac170ba29a9903ee590e1ef2d8e6b27b49a16c.

  Fixes: 3df2da968744 (Revert "ACPI / LPSS: introduce a 'proxy' device to 
power on LPSS for DMA")
  Signed-off-by: Andy Shevchenko 
  Signed-off-by: Rafael J. Wysocki 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Ian May 
  Signed-off-by: Kleber Sacilotto de Souza 

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1630285] Re: mwifiex_pcie crashes after several bind/unbind

[Timo Aaltonen]

** Changed in: hwe-next
   Status: New => Fix Released

** Changed in: linux (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1630285

Title:
  mwifiex_pcie crashes after several bind/unbind

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in nplan source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Won't Fix
Status in nplan source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  netplan-configured systems with mwifiex interfaces crash if netplan attempts 
to unbind/bind the interface.

  [Test case]
  1) Run 'netplan apply' on a system with mwifiex_pci driver.

  The system should not crash, and the mwifiex interface should remain
  untouched.

  [Regression potential]
  Interfaces other than those affected by unbind/bind crashes or failures 
should still be unbound when 'netplan apply' is run. This affects most wireless 
interfaces, with the notable exception of mwifiex and brcmfmac. Failure to 
apply netplan configuration for a legitimate mwifiex device (wireless 
connection driven by NetworkManager renderer using netplan) would also 
constitute a regression.

  [Original bug report]
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bind

  Keep doing the bind/unbind actions, it would crash very soon.

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1715586] Re: Fix shrinking behavior in rrCheckPixmapBounding

[Timo Aaltonen]

** Changed in: xorg-server (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1715586

Title:
  Fix shrinking behavior in rrCheckPixmapBounding

Status in HWE Next:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Won't Fix

Bug description:
  [Impact]
  When using extended mode on an slave-output connected external monitor, 
RRSetCrtc calls rrCheckPixmapBounding, which shrinks the output area. It makes 
the slave-output configured to scan-out an area which completely falls outside 
of the screen-pixmap, and end up with
  a black display on the external monitor.

  We need these two commits:
  a46afee84d45fbff4e4dad9376afc95bbcc31d7c randr: rrCheckPixmapBounding: do not 
shrink the screen_pixmap
  3b624aa9a9df86dc7d48149e0f18ca223b4355f1 randr: rrCheckPixmapBounding: Do not 
substract crtc non 0 x,y from screen size

  [Test Case]
  Enable NVIDIA PRIME, plug an external monitor, and change to extended mode.

  [Regression Potential]
  There should be none, the shrinking behavior wasn't right at the first place.

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1740231] Re: Add support for Realtek WiFi device RTL8821CE [10ec:c821]

[Timo Aaltonen]

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

** Changed in: hwe-next
   Status: Confirmed => Fix Released

** Changed in: hwe-next/bionic
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1740231

Title:
  Add support for Realtek WiFi device RTL8821CE [10ec:c821]

Status in HWE Next:
  Fix Released
Status in HWE Next bionic series:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  PCI ID: 10ec:c821

  The off-tree driver is attached.

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1746411] Re: [linux-oem] Fix out of bound VBT pin on CNP

[Timo Aaltonen]

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

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1746411

Title:
  [linux-oem] Fix out of bound VBT pin on CNP

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  i915 crashed when probing for VBT pin. No graphics output after that.

  [Test Case]
  Enable Legacy ROM boot option in BIOS. Screen goes blank.
  Cherrypick fixes can solve the issue. 

  [Fix]
  Handle out of bounds pin value more appropriately.
  Patches from Jani are most refactoring, but the fix we want depends on
  them.
  Patches from Rogrigo are the fixes we want. These patches are also
  picked base on his suggestion,
  https://bugs.freedesktop.org/show_bug.cgi?id=104139#c7

  [Regression Potential]
  Low. CNL and CNP are still quite new. These commits are limited to them.

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1615381] Please test proposed package

[Timo Aaltonen]

Hello Jarno, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.15 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1615381

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  APT will try and fail to remove the currently running kernel, when booted 
into an older kernel that is not protected. May wreak some havoc if mixed with 
other operations to the point that apt goes weird and needs manual fixing up.

  [Test case]
  For the SRUs we have included an automated test case that starts with an 
empty autoremove config file, and then checks that the running kernel is 
protected at runtime.

  You can also test manually, but it's not necessary:

  - Install new kernel
  - Reboot into kernel not listed as protected in 01autoremove-kernels
  - Run autoremove

  [Where problems could occur]
  We may more easily run out of space in /boot. hirsute has new autoremoval 
code that runs completely at runtime; but that seems a bit large to SRU after 
only a few weeks in hirsute. Hence, we should protect the current kernel _in 
addition_ to the other kernels, just like unattended-upgrades and 
update-manager do. This increases the risk of filling up /boot compared to 
older apt versions, but is at the same level as unattended-upgrades and 
update-manager.

  [Original bug report]

  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 

[Group.of.nepali.translators] [Bug 1615381] Re: apt-get autoremove may remove current kernel

[Timo Aaltonen]

Hello Jarno, or anyone else affected,

Accepted apt into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.0.8 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-focal
** Tags added: verification-needed verification-needed-focal

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

** Changed in: apt (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1615381

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  APT will try and fail to remove the currently running kernel, when booted 
into an older kernel that is not protected. May wreak some havoc if mixed with 
other operations to the point that apt goes weird and needs manual fixing up.

  [Test case]
  For the SRUs we have included an automated test case that starts with an 
empty autoremove config file, and then checks that the running kernel is 
protected at runtime.

  You can also test manually, but it's not necessary:

  - Install new kernel
  - Reboot into kernel not listed as protected in 01autoremove-kernels
  - Run autoremove

  [Where problems could occur]
  We may more easily run out of space in /boot. hirsute has new autoremoval 
code that runs completely at runtime; but that seems a bit large to SRU after 
only a few weeks in hirsute. Hence, we should protect the current kernel _in 
addition_ to the other kernels, just like unattended-upgrades and 
update-manager do. This increases the risk of filling up /boot compared to 
older apt versions, but is at the same level as unattended-upgrades and 
update-manager.

  [Original bug report]

  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly 

[Group.of.nepali.translators] [Bug 1758364] Re: add audio kernel patches for Raven

[Timo Aaltonen]

** Changed in: amd
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1758364

Title:
  add audio kernel patches for Raven

Status in amd:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [impact]
  Raven platforms don't have audio support.

  Please include these patches in the OEM and HWE kernels for Raven
  platforms:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/sound/pci/hda?h=v4.14.28=ca90f34e2e80597dee73c2e8d55de364a34c112b
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/sound/pci/hda?h=v4.14.28=b177556318a731878a1e9e8a9bb28b98f7bc832c

  [test case]
  boot a kernel with the backported commits on such a system, test that audio 
works.

  [regression potential]
  none, they just add a pci-id and fix a typo

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1729442] Re: Prevent timer value 0 for MWAITX

[Timo Aaltonen]

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => Won't Fix

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

** Changed in: amd
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1729442

Title:
  Prevent timer value 0 for MWAITX

Status in amd:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  Won't Fix

Bug description:
  Newer hardware has uncovered a bug in the software implementation of
  using MWAITX for the delay function. A value of 0 for the timer is
  meant to indicate that a timeout will not be used to exit MWAITX. On
  newer hardware this can result in MWAITX never returning, resulting in
  NMI soft lockup messages being printed. On older hardware, some of the
  other conditions under which MWAITX can exit masked this issue.

  The AMD APM does not currently document this and will be updated.
  Please refer to http://marc.info/?l=kvm=148950623231140 for
  information regarding NMI soft lockup messages on an AMD Ryzen 1800X.
  This has been root-caused as a 0 passed to MWAITX causing it to wait
  indefinitely. This change has the added benefit of avoiding the
  unnecessary setup of MONITORX/MWAITX when the delay value is zero.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1770271] Re: VegaM support

[Timo Aaltonen]

** Changed in: amd
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770271

Title:
  VegaM support

Status in amd:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1877844] Re: [SRU] borgbackup version 1.1.15 and 1.0.13

[Timo Aaltonen]

Hello Steve, or anyone else affected,

Accepted borgbackup into groovy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/borgbackup/1.1.15-1~ubuntu1.20.10.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: borgbackup (Ubuntu Groovy)
   Status: Fix Released => In Progress

** Changed in: borgbackup (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

** Changed in: borgbackup (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1877844

Title:
  [SRU] borgbackup version 1.1.15 and 1.0.13

Status in borgbackup package in Ubuntu:
  Fix Released
Status in xxhash package in Ubuntu:
  Fix Released
Status in borgbackup source package in Xenial:
  Fix Committed
Status in borgbackup source package in Bionic:
  In Progress
Status in xxhash source package in Bionic:
  In Progress
Status in borgbackup source package in Focal:
  Fix Committed
Status in borgbackup source package in Groovy:
  Fix Committed
Status in xxhash source package in Groovy:
  Fix Released
Status in borgbackup package in Debian:
  Fix Released

Bug description:
  [ Impact ]
  * Data is corrupted on some specific conditions, upstream asked to backport 
1.1.15 that fixes some high ram usage and this corruption bug (not for focal, 
already fixed)

  [ Regression Potential ]
  * Really low, the package has an autopkgtestsuite that runs thousand of 
tests, and the fix is since one year part of upstream code

  [ Test Case ]
  * Backup some TB of data, and try to read the index, it should be not 
corrupted

  [ Other info ]
  Per the "important notes" section of the borg docs:

  https://borgbackup.readthedocs.io/en/stable/changes.html

  "Pre-1.1.11 potential index corruption / data loss issue
  A bug was discovered in our hashtable code, see issue #4829. The code is used 
for the client-side chunks cache and the server-side repo index.

  Although borg uses the hashtables very heavily, the index corruption
  did not happen too frequently, because it needed specific conditions
  to happen.

  Data loss required even more specific conditions, so it should be rare
  (and also detectable via borg check). [..]"

  Theoretically affects all Ubuntu releases before 20.04 (focal.)

  I know this is a universe package, but if anyone was up for an SRU
  that would be fantastic..

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1870514] Re: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon

[Timo Aaltonen]

fixed in hirsute by 1.3.7-0ubuntu5

** Changed in: containerd (Ubuntu Hirsute)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1870514

Title:
  [SRU] update containerd:amd64 1.3.3-0 stops docker daemon

Status in containerd package in Ubuntu:
  Fix Released
Status in docker.io package in Ubuntu:
  Fix Released
Status in containerd source package in Xenial:
  Fix Committed
Status in docker.io source package in Xenial:
  Fix Committed
Status in containerd source package in Bionic:
  Fix Committed
Status in docker.io source package in Bionic:
  Fix Committed
Status in containerd source package in Focal:
  Fix Committed
Status in docker.io source package in Focal:
  Fix Committed
Status in containerd source package in Groovy:
  Fix Committed
Status in docker.io source package in Groovy:
  Fix Committed
Status in containerd source package in Hirsute:
  Fix Released
Status in docker.io source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Docker uses containerd under the hood.  When containerd is upgraded it
  stops and restarts its service; docker stops when containerd stops but
  doesn’t restart.  Particularly when doing unattended upgrades, an SRU
  fix rolled out for containerd can result in unexpected and widespread
  service outages for docker.

  [Test Case]

  $ sudo apt install docker.io
  $ sudo systemctl start docker
  $ systemctl status docker | grep Active
   Active: active (running) since[...]
  $ systemctl status containerd | grep Active
   Active: active (running) since[...]

  $ docker pull ubuntu/redis:latest
  $ docker run -e REDIS_PASSWORD=1234 --network host \
  --name test-redis -d ubuntu/redis:latest
  $ telnet localhost 6379
  $ docker container logs test-redis

  $ sudo apt install --reinstall containerd
  $ systemctl status containerd | grep Active
   Active: active (running) since
  $ systemctl status docker | grep Active
   Active: inactive (dead) since [...]; 8s ago
  $ docker container logs test-redis

  [Where Problems Could Occur]

  The challenge with this issue is addressing all important corner
  cases, and as such the biggest risk is that we miss a corner case and
  fail to keep the two services running when they should.  Areas to
  watch will be failures during start/stop/restart/upgrade type
  operations.  Issues during runtime are unlikely to relate to this
  change.

  [Original Report]

  hello we have had in several vms, the problem that after updating to "
  containerd:amd64 1.3.3" the docker daemon is stopped and so are all
  running containers

  the vms run with ubuntu 18.04.1/18.04.2

  journal log during the update:

  ```
  -- Logs begin at Tue 2020-01-14 09:58:27 CET, end at Fri 2020-04-03 11:30:39 
CEST. --
  Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:09.648358396Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:09.660781933Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=\"\"" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03 
06:09:14+02:00","message":"interface enp0s3 works fine"}
  Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03 
06:09:14+02:00","message":"interface enp0s8 works fine"}
  Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:24.650166885Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:24.663239678Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=\"\"" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  Apr 03 06:09:31 server systemd[1]: Starting Daily apt upgrade and clean 
activities...
  Apr 03 06:09:39 server dockerd[1751]: time="2020-04-03T06:09:39+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:39.64981528Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  

[Group.of.nepali.translators] [Bug 1893717] Re: Add Ubuntu Advantage service apt urls to valid mirrors

[Timo Aaltonen]

Hello Chad, or anyone else affected,

Accepted ubuntu-release-upgrader into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:20.04.28 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
   Status: Won't Fix => Fix Committed

** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1893717

Title:
  Add Ubuntu Advantage service apt urls to valid mirrors

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Committed
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Committed
Status in ubuntu-release-upgrader source package in Focal:
  Fix Committed
Status in ubuntu-release-upgrader source package in Groovy:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Customers with Ubuntu Advantage services enabled on Trusty/Xenial/Bionic find 
APT config files disabled with comments after running `do-release-upgrade`.

  This requires either:
   1. manual intervention to uncomment and correct the apt suite for any 
enabled Ubuntu Advantage service stored in 
/etc/apt/sources.list.d/ubuntu-*.list.

   OR

   2. Providing AllowThirdParty=yes configuration override during do-
  release-upgrade to force upgrades of all third party ppa apt
  configuration urls.

  Adding these supported commercial URLs to mirror.cfg allows these urls to be
  treated as valid Ubuntu-proper apt URLs and would automatically update the
  apt config files for any enabled Ubuntu Advantage offering without
  manual intervention.

  [Test Case]

  # test procedure
  for release in trusty xenial bionic; do
   1. lxc launch daily image for the given $release enabling 
ubuntu-advantage-daily PPA (to allow for upgrading to viable 
ubuntu-advantage-tools deb
   2. attach the machine to ua with a token and enable any available apt-based
  services
   3. Download the -proposed tarball to locally perform a 
"do-release-upgrade"
   4. unzip that proposed tarball
   5. Add ubuntu-advantage-daily PPA to mirrors.cfg # to avoid disabling on 
upgrade
   6. and run ./${upgraderelease} upgrade on the CLI
   7. check contents of /etc/apt/sources.list.d/ubuntu-*.list to ensure all
  UA-related apt URLs are still available
   8. apt-cache policy to check that permissions to said APT repositories are 
live
  done

  # test script

  ```
  #!/bin/bash
  set -ex
  UA_TOKEN=
  cat > test-uru.yaml 

[Group.of.nepali.translators] [Bug 1890796] Re: ipsec: policy priority management is broken

[Timo Aaltonen]

** Also affects: linux-oem-5.6 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-5.6 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-oem-5.6 (Ubuntu Bionic)
   Status: New => Invalid

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1890796

Title:
  ipsec: policy priority management is broken

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in linux-hwe source package in Xenial:
  Invalid
Status in linux-oem-5.6 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in linux-hwe source package in Bionic:
  Fix Committed
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  New

Bug description:
  [Impact]

  When the user tries to update the priority field of a SP, the SP is
  not updated *AND* a new SP is created. This results to a broken IPsec
  configuration.

  This problem has been fixed in the upstream commit 4f47e8ab6ab7 ("xfrm: 
policy: match with both mark and mask on user interfaces"):
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4f47e8ab6ab7

  [Test Case]

  root@dut-vm:~# uname -a
  Linux dut-vm 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
  root@dut-vm:~# ip xfrm policy flush
  root@dut-vm:~# ip xfrm policy
  root@dut-vm:~# ip xfrm policy add src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp dir 
in action allow priority 9 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel 
reqid 1
  root@dut-vm:~# ip xfrm policy
  src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp 
  dir in priority 9 
  tmpl src 3.3.3.3 dst 4.4.4.4
  proto esp reqid 1 mode tunnel
  root@dut-vm:~# ip xfrm policy update src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp 
dir in priority 5 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel reqid 1
  root@dut-vm:~# ip xfrm policy
  src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp 
  dir in priority 5 
  tmpl src 3.3.3.3 dst 4.4.4.4
  proto esp reqid 1 mode tunnel
  src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp 
  dir in priority 9 
  tmpl src 3.3.3.3 dst 4.4.4.4
  proto esp reqid 1 mode tunnel
  root@dut-vm:~#

  => Now, there is 2 SP instead of 1.

  [Regression Potential]

  The patch affects the xfrm stack only. Thus, the potential regressions
  are limited to this area.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid

[Timo Aaltonen]

focal has -5 now

** Changed in: openssh (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: openssh (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1859013

Title:
  openssh tests use "not valid yet" certificate from 2020, which is now
  valid

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  New
Status in openssh source package in Trusty:
  New
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Disco:
  Won't Fix
Status in openssh source package in Eoan:
  Fix Committed
Status in openssh source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * regression testsuite uses 1st of January 2020 as the date in the
  future, however that is now in the past making autpkgtests fail.

  [Test Case]

   * Autopkgtest must pass

  [Regression Potential]

   * Testsuite assertion update only

  [Other Info]

  This is a staged update to be rolled up with any other openssh update
  in the future.

  fixed in debian https://tracker.debian.org/news/1092767/accepted-
  openssh-181p1-4-source-into-unstable/

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid

[Timo Aaltonen]

disco is EOL

** Changed in: openssh (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: openssh (Ubuntu Eoan)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-eoan

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1859013

Title:
  openssh tests use "not valid yet" certificate from 2020, which is now
  valid

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  New
Status in openssh source package in Trusty:
  New
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Disco:
  Won't Fix
Status in openssh source package in Eoan:
  Fix Committed
Status in openssh source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * regression testsuite uses 1st of January 2020 as the date in the
  future, however that is now in the past making autpkgtests fail.

  [Test Case]

   * Autopkgtest must pass

  [Regression Potential]

   * Testsuite assertion update only

  [Other Info]

  This is a staged update to be rolled up with any other openssh update
  in the future.

  fixed in debian https://tracker.debian.org/news/1092767/accepted-
  openssh-181p1-4-source-into-unstable/

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1856795] Re: [SRU] X2Go Client broken by libssh CVE-2019-14889 fix

[Timo Aaltonen]

Hello Mihai, or anyone else affected,

Accepted x2goclient into eoan-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/x2goclient/4.1.2.1-2ubuntu0.19.10.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: x2goclient (Ubuntu Disco)
   Status: Confirmed => Invalid

** Changed in: x2goclient (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

** Changed in: x2goclient (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1856795

Title:
  [SRU] X2Go Client broken by libssh CVE-2019-14889 fix

Status in libssh package in Ubuntu:
  Invalid
Status in x2goclient package in Ubuntu:
  Fix Released
Status in libssh source package in Xenial:
  Invalid
Status in x2goclient source package in Xenial:
  Fix Committed
Status in libssh source package in Bionic:
  Invalid
Status in x2goclient source package in Bionic:
  Fix Committed
Status in libssh source package in Disco:
  Invalid
Status in x2goclient source package in Disco:
  Invalid
Status in libssh source package in Eoan:
  Invalid
Status in x2goclient source package in Eoan:
  Fix Committed
Status in x2goclient package in Debian:
  Fix Released

Bug description:
  [Test case]
  Connect to a x2go server on a session that has file sharing or 
audo-forwarding enabled -> Error message "SCP: Warning: status code 1 received: 
scp: ~/.x2go/ssh: No such file or directory" needs to be clicked away 
with "ok".

  [Regression potential]
  Very low as the patch removes "~" from the ssh string which is the same 
as just using no path spec (":") as the default is the home dir of the logged 
in remote user.

  --

  The recent CVE fix broke SCP support in libssh, which X2Go Client
  (x2goclient) relies on.

  Sessions now fail with error messages such as "SCP: Warning: status
  code 1 received: scp: ~username/.x2go/ssh: No such file or
  directory\n". (Also note the literal "\n" there, but I guess we don't
  really need to care about that.)

  The previous version worked fine and rolling the libssh4 package back
  fixes this issue, but also leaves users vulnerable to the fixed
  security issue in its scp implementation.

  I've been looking at the debdiff, but spotting the actual changes is
  very difficult due to the reformatting that was done at the same time.
  This degraded the patch(es) into one big blob.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1828790] Re: On a Wyse system, if Intel DP is connected before the AMD one, there's a 50% chance the AMD one would have no output

[Timo Aaltonen]

and also backported to xenial

xorg-server-hwe-16.04 (2:1.19.6-1ubuntu4.1~16.04.1) xenial;
urgency=medium

  * prime-sync-refactor.diff: Fix crash on modesetting+amdgpu hybrid.
(LP: #1789913)

 -- Timo Aaltonen   Wed, 05 Sep 2018 14:31:56 +0300


** Changed in: xorg-server-hwe-16.04 (Ubuntu Xenial)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1828790

Title:
  On a Wyse system, if Intel DP is connected before the AMD one, there's
  a 50% chance the AMD one would have no output

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Xenial:
  Won't Fix
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  Summary:
  On extended SKU (AMD SKU), boot to OS with monitor connecting to Intel DP, 
then connect another monitor to AMD DP, there is a 50% chance AMD DP has no 
video output to monitor.

  Step to reproduce:
  1. Attached a 2k/4K monitor to Intel UMA DP port.
  2. Power on system and boot to desktop.
  3. Attach another 2k/4K monitor to AMD Graphics DP port.

  Expect result:
  Both monitors can display correctly

  Actually result:
  AMD DP monitor will be black screen. (Intel DP output still normal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1828790/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1828790] Re: On a Wyse system, if Intel DP is connected before the AMD one, there's a 50% chance the AMD one would have no output

[Timo Aaltonen]

this is actually fixed in bionic
xorg-server (2:1.19.6-1ubuntu4.1) bionic; urgency=medium

  * prime-sync-refactor.diff: Fix crash on modesetting+amdgpu hybrid.
(LP: #1789913)
  * sync-i965-pciids.diff: Update intel pci-id's. (LP: #1789924)

 -- Timo Aaltonen   Wed, 05 Sep 2018 14:38:25 +0300


** Changed in: xorg-server (Ubuntu Bionic)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1828790

Title:
  On a Wyse system, if Intel DP is connected before the AMD one, there's
  a 50% chance the AMD one would have no output

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Xenial:
  Won't Fix
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  Summary:
  On extended SKU (AMD SKU), boot to OS with monitor connecting to Intel DP, 
then connect another monitor to AMD DP, there is a 50% chance AMD DP has no 
video output to monitor.

  Step to reproduce:
  1. Attached a 2k/4K monitor to Intel UMA DP port.
  2. Power on system and boot to desktop.
  3. Attach another 2k/4K monitor to AMD Graphics DP port.

  Expect result:
  Both monitors can display correctly

  Actually result:
  AMD DP monitor will be black screen. (Intel DP output still normal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1828790/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)

[Timo Aaltonen]

don't mark bugs fixed when the package has only been uploaded to the SRU
queue

** Changed in: chrony (Ubuntu Disco)
   Status: Fix Released => In Progress

** Changed in: chrony (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-disco

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1836929

Title:
  chrony has migration regressions from autopkgtests (disco/eoan)

Status in chrony package in Ubuntu:
  Fix Released
Status in chrony source package in Xenial:
  Won't Fix
Status in chrony source package in Bionic:
  Won't Fix
Status in chrony source package in Cosmic:
  Won't Fix
Status in chrony source package in Disco:
  Fix Committed
Status in chrony source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * Recent changes have caused the chrony autopkgtests to fail.
     In this case upstream of chrony and the clk tests changed, which need 
 to be back under control to match what works reliably for Disco.

   * Later versions have this fixed, backport the changes to fix it in Disco
     as well

  [Test Case]

   * Let the autopkgtests run (which is part of the proposed migration
     anyway)
     Sniffs already show them completing:
     https://bileto.ubuntu.com/excuses/3759/disco.html

  [Regression Potential]

   * There is no functional change, only the self-tests as well the
     autopkgtest execution are changed.
     The one source for a regression could be that the rebuild picks
     something up that triggers a behavior change. But the PPA builds have
     not shown something (at least not something obvious)

  [Other Info]

   * This is one of the cases where the actual package as used by the user
     has no bug. I'm unsure how to proceed. Do we want to push it just to
     disco-proposed but keep it there (to avoid downloads for "nothing")?
     I know rbasak wanted to discuss that in the SRU team for the even worse
     https://bugs.launchpad.net/cloud-archive/+bug/1829823/comments/14
     To some extend this come under the same banner.
   * If this is denied from SRU for this reason I'd ask to add a force-
     badtest as a replacement to unblock proposed migration.

  ---

  Checking last eoan merge I realized that some tests were failing for
  chrony:

  
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/369588/comments/967625

  But eoan ran autopkgtests okay when the trigger was
  chrony/3.5-2ubuntu2 (this last merge):

  http://autopkgtest.ubuntu.com/packages/chrony/eoan/amd64

  Despite having failed for the previous 12 times (eoan).

  Now, for the first time, we have the same failure for disco:

  http://autopkgtest.ubuntu.com/packages/chrony/disco/amd64

  http://bit.ly/2LpMx4G

  """
  make: Leaving directory 
'/tmp/autopkgtest.pBHSAl/build.WCD/src/test/simulation/clknetsim'
  ...
  110-chronyc    PASS
  111-knownclient    FAIL
  112-port   FAIL
  121-orphan PASS
  ...
  SUMMARY:
    TOTAL  50
    PASSED 48
    FAILED 2(111-knownclient 112-port) (255 256 257 258 259 260 261 262 263 
264 265 266 267 268 269 270 271 272 273 274 255 256 257 258 259 260 261 262 263 
264 265 266 267 268 269 270 271 272 273 274 265)
  """

  And I'm able to reproduce locally:

  """
  (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ 
./111-knownclient
  Testing reply to client configured as server:
    network with 1*1 servers and 1 clients:
  non-default settings:
    client_conf=acquisitionport 123
    server_conf=server 192.168.123.2 noselect acquisitionport 123
  starting node 1: OK
  starting node 2: OK
  running simulation: OK
  checking chronyd exit:
    node 1: OK
    node 2: OK
  checking source selection:
    node 2: OK
  checking port numbers in packet log:
    node 1: BAD
    node 2: BAD
  FAIL

  AND

  (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ 
./112-port
  Testing port and acquisitionport directives:
    network with 1*1 servers and 1 clients:
  non-default settings:
  starting node 1: OK
  starting node 2: OK
  running simulation: OK
  checking chronyd exit:
    node 1: OK
    node 2: OK
  checking source selection:
    node 2: OK
  checking mean/min incoming/outgoing packet interval:
    node 1: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK
    node 2: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK
  checking clock sync time, max/rms time/freq error:
    node 2: 132 9.29e-05 1.21e-06 5.77e-05 1.01e-07 OK
  checking port numbers in packet log:
    node 1: BAD
    node 2: BAD
    network with 1*1 servers 

[Group.of.nepali.translators] [Bug 1828790] Re: On a Wyse system, if Intel DP is connected before the AMD one, there's a 50% chance the AMD one would have no output

[Timo Aaltonen]

** Also affects: xorg-server (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: xorg-server-hwe-16.04 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: xorg-server-hwe-16.04 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: xorg-server (Ubuntu Xenial)
   Status: Invalid => Won't Fix

** Changed in: xorg-server-hwe-16.04 (Ubuntu)
   Status: New => Invalid

** Changed in: xorg-server-hwe-16.04 (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: xorg-server (Ubuntu)
   Status: New => Fix Released

** Changed in: xorg-server (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: xorg-server (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1828790

Title:
  On a Wyse system, if Intel DP is connected before the AMD one, there's
  a 50% chance the AMD one would have no output

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Xenial:
  Won't Fix
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Bionic:
  Triaged
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  Summary:
  On extended SKU (AMD SKU), boot to OS with monitor connecting to Intel DP, 
then connect another monitor to AMD DP, there is a 50% chance AMD DP has no 
video output to monitor.

  Step to reproduce:
  1. Attached a 2k/4K monitor to Intel UMA DP port.
  2. Power on system and boot to desktop.
  3. Attach another 2k/4K monitor to AMD Graphics DP port.

  Expect result:
  Both monitors can display correctly

  Actually result:
  AMD DP monitor will be black screen. (Intel DP output still normal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1828790/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Timo Aaltonen]

Hello Daniel, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: netplan.io (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770082

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. 

[Group.of.nepali.translators] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Timo Aaltonen]

no need to re-test this on bionic/cosmic

** Changed in: netplan.io (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

** Changed in: netplan.io (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic 
verification-done-cosmic

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770082

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd 

[Group.of.nepali.translators] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Timo Aaltonen]

Hello Daniel, or anyone else affected,

Accepted netplan.io into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: netplan.io (Ubuntu Cosmic)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done-cosmic
** Tags added: verification-needed verification-needed-cosmic

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770082

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and 

[Group.of.nepali.translators] [Bug 1709193] Re: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

[Timo Aaltonen]

there's a new upload for trusty, for bug 1444656

closing this one

** Changed in: gnutls26 (Ubuntu Trusty)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1709193

Title:
  Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls26 source package in Trusty:
  Won't Fix
Status in gnutls28 source package in Trusty:
  Won't Fix
Status in gnutls28 source package in Xenial:
  Fix Released
Status in gnutls28 source package in Zesty:
  Fix Released
Status in gnutls28 source package in Artful:
  Fix Released
Status in gnutls28 package in Debian:
  Fix Released

Bug description:
  [Impact]

  Applications using GnuTLS OpenSSL compat layer [1] are be unable to
  use modern TLS versions (1.1 and 1.2) when relying on the
  SSLv23_{client,server}_method functions.

  There is an industry-wide push to use modern TLS versions, see [2] and
  [3] for example.

  The proposed fix changes the compat layer to use GnuTLS' "NORMAL"
  priority [4] instead of hard-coding which protocol versions and
  ciphers to enable.

  [Test Case]

  1) Setup a mail submission server that uses StartTLS
  2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay
 through the mail relay using StartTLS
  3) Send an email while capturing with tcpdump/tshark
  4) Inspect the submission connection (TCP/587) and look for the protocol
 version negotiated by the client.

  Without the fix, you should see TLSv1.0. With the fix, it should be
  TLSv1.2.

  Please see the original issue description for more details.

  [Regression Potential]

  Regression risk should be low since it's a backport of a simple fix
  that landed in Debian in April 2017.

  [References]

  1: $ apt-cache rdepends libgnutls-openssl27
  libgnutls-openssl27
  Reverse Depends:
libgnutls-dev
libgnutls-dev
zoneminder
yaskkserv
tf5
ssmtp
snowdrop
sngrep
slrnpull
slrn
sipsak
macopix-gtk2
gnss-sdr
gkrellm
freewheeling
boinctui
iputils-ping

  2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
  3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls
  4: https://gnutls.org/manual/html_node/Priority-Strings.html

  
  [Original issue description]

  sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with
  it. Here's a packet capture when ssmtp connects to
  smtp.sdeziel.info:587 that offers TLSv1.0 and higher:

  $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | 
grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)'
  Version: TLS 1.0 (0x0301)
  Handshake Protocol: Client Hello
  Version: TLS 1.0 (0x0301)
  Cipher Suites Length: 30
  Cipher Suites (15 suites)
  Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
  Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088)
  Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0044)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0087)
  Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)

  I would expect ssmtp to use TLSv1.2 and a recent cipher like the
  openssl s_client is able to do:

  $ echo | openssl s_client -connect smtp.sdeziel.info:587 -starttls smtp 
2>/dev/null | grep -E '^[[:space:]]+(Protocol|Cipher)'
  Protocol  : TLSv1.2
  Cipher: ECDHE-RSA-AES128-GCM-SHA256

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  $ apt-cache policy ssmtp libgnutls-openssl27
  ssmtp:
    Installed: 2.64-8ubuntu1
    Candidate: 2.64-8ubuntu1
    Version table:
   *** 2.64-8ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  libgnutls-openssl27:
    Installed: 3.4.10-4ubuntu1.3
    Candidate: 3.4.10-4ubuntu1.3
    Version table:
   *** 3.4.10-4ubuntu1.3 500
  500 http://archive.ubuntu.com/ubuntu 

[Group.of.nepali.translators] [Bug 1722936] Re: sssd hbac rule applicaton for AD users is inconsistent

[Timo Aaltonen]

should be fixed bionic and up

** Also affects: sssd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: sssd (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1722936

Title:
  sssd hbac rule applicaton for AD users is inconsistent

Status in sssd package in Ubuntu:
  Fix Released
Status in sssd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  From the upstream bug at https://pagure.io/SSSD/sssd/issue/3382:
  """
  In IPA-AD trust environment, sssd is intermittently failing to map AD user
  group with IPA POSIX group hence getting access denied due to HBAC rules. The 
issue gets resolved automatically after certain time, without restarting the 
sssd service. i.e:

  The IPA HBAC code used to read the group members from the the
  originalMemberOf attribute value for performance reasons. However,
  especially on IPA clients trusting an AD domain, the originalMemberOf
  attribute value is often not synchronized correctly.
  """

  
  [Test Case]
  Coming up with a simple test case is not feasable. Even upstream wasn't able 
to reliably reproduce the issue in a controlled manner. My best suggestion is 
for affected users to try the updated package and observe if the incorrect 
access denied error stops happening.

  This involves setting up an AD server, a FreeIPA one, creating trust
  between them, and nested groups and HBAC rules. Upstream's description
  of such a scenario is at
  https://github.com/SSSD/sssd/pull/309#issuecomment-318037063

  [Regression Potential]
  The patch changes how group membership in this scenario is computed. It's a 
complex setup, and we are relying on a) patch has been applied upstream and 
backported to 1.13; b) user who reported this bug confirmed it fixed the issue 
with a custom build he did; c) upstream test suite passed; d) dep8 tests (new 
with this SRU) also pass.

  [Other Info]
  The scenario where the bug happens is too complex to reproduce in a test 
case, but does happen out in the wild according to this report and also in 
upstream's bug tracker. I decided to add the DEP8 tests to this update as well 
to give extra confidence in this and future updates, even though it doesn't 
exercise this bug in particular.

  [Original Description]
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"

  sssd Version: 1.13.4-1ubuntu1.8

  I'm sometimes seeing AD users denied access to a machine due to HBAC
  access rules:

  (Tue Oct  3 04:11:09 2017) [sssd[be[nwra.com]]]
  [ipa_hbac_evaluate_rules] (0x0080): Access denied by HBAC rules

  Upstream suggest applying this commit:

  https://pagure.io/SSSD/sssd/c/88f6d8ad4eef4b4fa032fd451ad732cf8201b0bf

  That was made on the 1.13 branch but not yet released.  More here:

  https://lists.fedorahosted.org/archives/list/sssd-
  us...@lists.fedorahosted.org/message/YIHC2C6JDNQLYMW7K7IXQKKIIRMO3QER/

  I'm currently testing out a local package with this patch.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working

[Timo Aaltonen]

needs SRU template, test case etc

** Also affects: makedumpfile (Ubuntu Disco)
   Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1790788

Title:
  Customize 'crashkernel' parameter is not properly working

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  New
Status in makedumpfile source package in Cosmic:
  In Progress
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  Trying to use crashdump especially in a KVM machine.
  Installation looks fine and the reboot is triggered.
  But it does not work because the kernel does not have a 'crashkernel=' 
parameter.
  Nothing in /proc/cmdline:
  $ cat /proc/cmdline 
  root=LABEL=cloudimg-rootfs

  Issue seems to be in adding the crashkernel line in this snippet:
  # Customize crashkernel= value according to architecture
  ARCH="$(arch)"
  DEF_PRESET="384M-:128M"
  case "$ARCH" in
 s390x)
HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
if test -z "$HAS_CRASHKERNEL"; then
   sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}" 
/etc/zipl.conf
   zipl
fi
   CIO_IGNORE="$(cio_ignore -u -k)"
   sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
   sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}" 
$INITCONFFILE
  ;;
  esac

  (especially 1st sed stmt)

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1770271] Re: VegaM support

[Timo Aaltonen]

bionic has 4.18 backport now, installed with 18.04.2 image or manually
via 'linux-generic-hwe-18.04'

** Changed in: linux (Ubuntu Bionic)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770271

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1818428] Re: bdftopcf: bdf input, xtfont4.bdf, corrupt

[Timo Aaltonen]

btw, libxfont2 is backported to xenial, so you should be able to build
XTS with libxfont-dev, not libxfont1-dev

** Changed in: libxfont (Ubuntu Xenial)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1818428

Title:
  bdftopcf: bdf input, xtfont4.bdf, corrupt

Status in libxfont package in Ubuntu:
  Fix Released
Status in libxfont source package in Xenial:
  Won't Fix
Status in libxfont package in Nexenta Operating System:
  Unknown

Bug description:
  Compiling the xorg Test Suite called XTS
  (https://github.com/freedesktop/xorg-test-xts) on TravisCI (https
  ://travis-ci.org/mjtrangoni/nx-libs/jobs/501145999), I am running on
  this Bug,

  -
  /usr/bin/bdftopcf -t -o xtfont0.pcf xtfont0.bdf
  /usr/bin/bdftopcf -t -o xtfont1.pcf xtfont1.bdf
  /usr/bin/bdftopcf -t -o xtfont2.pcf xtfont2.bdf
  /usr/bin/bdftopcf -t -o xtfont3.pcf xtfont3.bdf
  /usr/bin/bdftopcf -t -o xtfont4.pcf xtfont4.bdf
  BDF Error on line 32: character 'ascii001' has out of range width, -8
  /usr/bin/bdftopcf: bdf input, xtfont4.bdf, corrupt
  Makefile:767: recipe for target 'xtfont4.pcf' failed
  ---

  Which seems to be fixed upstream,

  See RedHat Bugzilla 1241939
  (https://bugzilla.redhat.com/show_bug.cgi?id=1241939) and its upstream
  fix here (https://lists.x.org/archives/xorg-
  devel/2015-July/046914.html)

  I hope, I can get this fixed/backported soon on Ubuntu Xenial.

  Operating System Details:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04
  Codename: xenial

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1818428] Re: bdftopcf: bdf input, xtfont4.bdf, corrupt

[Timo Aaltonen]

** Also affects: libxfont (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: libxfont (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1818428

Title:
  bdftopcf: bdf input, xtfont4.bdf, corrupt

Status in libxfont package in Ubuntu:
  Fix Released
Status in libxfont source package in Xenial:
  New
Status in libxfont package in Nexenta Operating System:
  Unknown

Bug description:
  Compiling the xorg Test Suite called XTS
  (https://github.com/freedesktop/xorg-test-xts) on TravisCI (https
  ://travis-ci.org/mjtrangoni/nx-libs/jobs/501145999), I am running on
  this Bug,

  -
  /usr/bin/bdftopcf -t -o xtfont0.pcf xtfont0.bdf
  /usr/bin/bdftopcf -t -o xtfont1.pcf xtfont1.bdf
  /usr/bin/bdftopcf -t -o xtfont2.pcf xtfont2.bdf
  /usr/bin/bdftopcf -t -o xtfont3.pcf xtfont3.bdf
  /usr/bin/bdftopcf -t -o xtfont4.pcf xtfont4.bdf
  BDF Error on line 32: character 'ascii001' has out of range width, -8
  /usr/bin/bdftopcf: bdf input, xtfont4.bdf, corrupt
  Makefile:767: recipe for target 'xtfont4.pcf' failed
  ---

  Which seems to be fixed upstream,

  See RedHat Bugzilla 1241939
  (https://bugzilla.redhat.com/show_bug.cgi?id=1241939) and its upstream
  fix here (https://lists.x.org/archives/xorg-
  devel/2015-July/046914.html)

  I hope, I can get this fixed/backported soon on Ubuntu Xenial.

  Operating System Details:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04
  Codename: xenial

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1770271] Re: VegaM support

[Timo Aaltonen]

bionic has 18.2.2 now

** Changed in: mesa (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770271

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1770271] Re: VegaM support

[Timo Aaltonen]

I think we'll just fix this in bionic via the HWE stack update. Backport
to xenial would basically mean updating stock bionic kernel/mesa and
then backport those to xenial. A big patchset to the kernel is unlikely
to get approved..

** Changed in: linux (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: mesa (Ubuntu Xenial)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770271

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1780109] Re: Only Recommend rsyslog | system-log-daemon

[Timo Aaltonen]

Hello Balint, or anyone else affected,

Accepted gce-compute-image-packages into trusty-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/gce-compute-image-packages/20180905+dfsg1-0ubuntu1~14.04.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gce-compute-image-packages (Ubuntu Trusty)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done verification-done-trusty
** Tags added: verification-needed verification-needed-trusty

** Changed in: gce-compute-image-packages (Ubuntu Xenial)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done-xenial
** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1780109

Title:
  Only Recommend rsyslog | system-log-daemon

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  Fix Committed
Status in gce-compute-image-packages source package in Xenial:
  Fix Committed
Status in gce-compute-image-packages source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * gce-compute-image-packages depends on rsyslog | system-log-daemon
  while there is need for images where none of those dependencies are
  present.

   * The upload demotes the dependencies to Recommends

  [Test Case]

   * This is seen when the package is fixed:
  $ apt show gce-compute-image-packages | grep rsyslog

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  Recommends: google-cloud-sdk, rsyslog | system-log-daemo

   * google-cloud-sdk is recommended only on Xenial and Trusty

  [Regression Potential]

   * Since by default recommended packages are installed with the
  packages recommending them the change should not cause issues in image
  generation nor during package upgrades. When an image build process
  uses apt's --no-install-recommends option, that would result rsyslog
  missing from the image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1780109/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1798706] Re: Incomplete linking with boost_regex

[Timo Aaltonen]

Hello Daniel, or anyone else affected,

Accepted gce-compute-image-packages into trusty-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/gce-compute-image-packages/20180905+dfsg1-0ubuntu1~14.04.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Also affects: gce-compute-image-packages (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gce-compute-image-packages (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: gce-compute-image-packages (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-trusty

** Changed in: gce-compute-image-packages (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1798706

Title:
  Incomplete linking with boost_regex

Status in gce-compute-image-packages package in Ubuntu:
  In Progress
Status in gce-compute-image-packages source package in Trusty:
  Fix Committed
Status in gce-compute-image-packages source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification
  =

  [Impact]
  oslogin fails on Xenial and Trusty.

  In auth.log we see:

  Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to 
dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: cannot open 
shared object file: No such file or directory
  Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: 
pam_oslogin_login.so
  Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to 
dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: cannot open 
shared object file: No such file or directory
  Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: 
pam_oslogin_admin.so

  The error message is a bit deceptive - PAM tries to load the module
  from the correct location, fails, and then tries the other location
  where it is missing. It then reports the missing error rather than the
  real error.

  symlink the module into both paths leads to a much more useful error
  message:

  Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to 
dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: undefined 
symbol: 
_ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE
  Oct 18 06:45:12 dja-202158 sshd[16554]: PAM adding faulty module: 
pam_oslogin_login.so
  Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to 
dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: undefined 
symbol: 
_ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE

  [Test case]
   - set up GCE VM
   - turn on oslogin
   - attempt to log in

  [Fix]
  
debian/patches/0002-Set-LDFLAGS-at-the-end-of-the-c-command-line-right-b.patch 
re-orders the link flags to link boost_regex for oslogin. However, this didn't 
change the flags for PAM module linking. So fix that too.

  [Regression Potential]
  - fixes a regression
  - limited to oslogin, and how it is linked.

  [Other Notes]
  We still see a scary list of warnings when building, but they don't seem to 
have an impact on the common path:
  dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail13put_mem_blockEPv used by 
debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so
 found in none of the libraries
  dpkg-shlibdeps: warning: symbol 

[Group.of.nepali.translators] [Bug 1795953] Re: sru cloud-init (18.3.9-g2e62cb8a-0ubuntu1) to (18.4-0ubuntu1)

[Timo Aaltonen]

** Changed in: cloud-init (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1795953

Title:
  sru cloud-init (18.3.9-g2e62cb8a-0ubuntu1) to (18.4-0ubuntu1)

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  New
Status in cloud-init source package in Bionic:
  New

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones that affect Ubuntu are:

   - Add support for Infiniband network interfaces (IPoIB). [Mark Goddard]
   - cli: add cloud-init query subcommand to query instance metadata
   - OpenStack: Support setting mac address on bond.
    [Fabian Wiesel] (LP: #1682064)
   - EphemeralIPv4Network: Be more explicit when adding default route.
    (LP: #1792415)
   - OpenStack: support reading of newer versions of metdata.
   - OpenStack: fix bug causing 'latest' version to be used from network.
    (LP: #1792157)
   - user-data: jinja template to render instance-data.json in cloud-config
    (LP: #1791781)
   - config: disable ssh access to a configured user account
   - sysconfig: refactor sysconfig to accept distro specific templates paths
   - hyperv_reporting_handler: simplify threaded publisher
   - VMWare: Fix a network config bug in vm with static IPv4 and no gateway.
    [Pengpeng Sun] (LP: #1766538)
   - logging: Add logging config type hyperv for reporting via Azure KVP
    [Andy Liu]
   - Add oracle datasource to debian/cloud-init.templates
   - Add datasource Oracle Compute Infrastructure (OCI).
   - azure: allow azure to generate network configuration from IMDS per boot.
   - Scaleway: Add network configuration to the DataSource [Louis Bouchard]
    [Wesley Gao]
   - netplan: Correctly render macaddress on a bonds and bridges when
    provided. (LP: #1784699)
   - tools: Add 'net-convert' subcommand command to 'cloud-init devel'.
   - Use typeset or local in profile.d scripts. (LP: #1784713)
   - OpenNebula: Fix null gateway6 [Akihiko Ota] (LP: #1768547)
   - oracle: fix detect_openstack to report True on OracleCloud.com DMI data
    (LP: #1784685)
   - update_metadata re-config on every boot comments and tests not quite
    right [Mike Gerdts]
   - get_linux_distro: add support for centos6 and rawhide flavors of redhat
    (LP: #1781229)

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates

  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.

  * Automated Test Results
  
  
  
  

  * Manual Test Results
  
  
  

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  [Discussion]
  

  == End SRU Template ==

  == Complete ChangeLog ==
  - release 18.4
  - tests: allow skipping an entire cloud_test without running.
  - tests: disable lxd tests on cosmic
  - cii-tests: use unittest2.SkipTest in ntp_chrony due to new deps
  - lxd: adjust to snap installed lxd.
  - docs: surface experimental doc in instance-data.json
  - tests: fix ec2 integration tests. process meta_data instead of meta-data
  - Add support for Infiniband network interfaces (IPoIB). [Mark Goddard]
  - cli: add cloud-init query subcommand to query instance metadata
  - tools/tox-venv: update for new features.
  - pylint: ignore warning assignment-from-no-return for _write_network
  - stages: Fix bug causing datasource to have incorrect sys_cfg.
  - Remove dead-code _write_network distro implementations.
  - net_util: ensure static configs have netmask in translate_network result
    [Thomas Berger]
  - Fall back to root:root on syslog permissions if other options fail.
    [Robert Schweikert]
  - tests: Add mock for util.get_hostname. [Robert Schweikert]
  - ds-identify: doc string cleanup.
  - OpenStack: Support setting mac address on bond. [Fabian Wiesel]
  - bash_completion/cloud-init: fix shell syntax error.
  - EphemeralIPv4Network: Be more explicit when adding default route.
  - OpenStack: support reading of newer versions of metdata.
  - OpenStack: fix bug causing 'latest' version to be used from network.
  - user-data: jinja template to render instance-data.json in cloud-config
  - config: disable ssh access to a configured user account
  - tests: print failed testname 

[Group.of.nepali.translators] [Bug 1795953] Re: sru cloud-init (18.3.9-g2e62cb8a-0ubuntu1) to (18.4-0ubuntu1~18.04.1)

[Timo Aaltonen]

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1795953

Title:
  sru cloud-init (18.3.9-g2e62cb8a-0ubuntu1) to (18.4-0ubuntu1)

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  New
Status in cloud-init source package in Bionic:
  New

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones that affect Ubuntu are:

   - Add support for Infiniband network interfaces (IPoIB). [Mark Goddard]
   - cli: add cloud-init query subcommand to query instance metadata
   - OpenStack: Support setting mac address on bond.
    [Fabian Wiesel] (LP: #1682064)
   - EphemeralIPv4Network: Be more explicit when adding default route.
    (LP: #1792415)
   - OpenStack: support reading of newer versions of metdata.
   - OpenStack: fix bug causing 'latest' version to be used from network.
    (LP: #1792157)
   - user-data: jinja template to render instance-data.json in cloud-config
    (LP: #1791781)
   - config: disable ssh access to a configured user account
   - sysconfig: refactor sysconfig to accept distro specific templates paths
   - hyperv_reporting_handler: simplify threaded publisher
   - VMWare: Fix a network config bug in vm with static IPv4 and no gateway.
    [Pengpeng Sun] (LP: #1766538)
   - logging: Add logging config type hyperv for reporting via Azure KVP
    [Andy Liu]
   - Add oracle datasource to debian/cloud-init.templates
   - Add datasource Oracle Compute Infrastructure (OCI).
   - azure: allow azure to generate network configuration from IMDS per boot.
   - Scaleway: Add network configuration to the DataSource [Louis Bouchard]
    [Wesley Gao]
   - netplan: Correctly render macaddress on a bonds and bridges when
    provided. (LP: #1784699)
   - tools: Add 'net-convert' subcommand command to 'cloud-init devel'.
   - Use typeset or local in profile.d scripts. (LP: #1784713)
   - OpenNebula: Fix null gateway6 [Akihiko Ota] (LP: #1768547)
   - oracle: fix detect_openstack to report True on OracleCloud.com DMI data
    (LP: #1784685)
   - update_metadata re-config on every boot comments and tests not quite
    right [Mike Gerdts]
   - get_linux_distro: add support for centos6 and rawhide flavors of redhat
    (LP: #1781229)

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates

  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.

  * Automated Test Results
  
  
  
  

  * Manual Test Results
  
  
  

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  [Discussion]
  

  == End SRU Template ==

  == Complete ChangeLog ==
  - release 18.4
  - tests: allow skipping an entire cloud_test without running.
  - tests: disable lxd tests on cosmic
  - cii-tests: use unittest2.SkipTest in ntp_chrony due to new deps
  - lxd: adjust to snap installed lxd.
  - docs: surface experimental doc in instance-data.json
  - tests: fix ec2 integration tests. process meta_data instead of meta-data
  - Add support for Infiniband network interfaces (IPoIB). [Mark Goddard]
  - cli: add cloud-init query subcommand to query instance metadata
  - tools/tox-venv: update for new features.
  - pylint: ignore warning assignment-from-no-return for _write_network
  - stages: Fix bug causing datasource to have incorrect sys_cfg.
  - Remove dead-code _write_network distro implementations.
  - net_util: ensure static configs have netmask in translate_network result
    [Thomas Berger]
  - Fall back to root:root on syslog permissions if other options fail.
    [Robert Schweikert]
  - tests: Add mock for util.get_hostname. [Robert Schweikert]
  - ds-identify: doc string cleanup.
  - OpenStack: Support setting mac address on bond. [Fabian Wiesel]
  - bash_completion/cloud-init: fix shell syntax error.
  - EphemeralIPv4Network: Be more explicit when adding default route.
  - OpenStack: support reading of newer versions of metdata.
  - OpenStack: fix bug causing 'latest' version to be used from network.
  - user-data: jinja template to render instance-data.json in cloud-config
  - config: disable ssh access to a configured user account
  - tests: print 

[Group.of.nepali.translators] [Bug 1645911] Re: linux-firmware 1.157.5 causes sound issues after initramfs update

[Timo Aaltonen]

hmm, looks like xenial kernel didn't need any update, so closing this
task as invalid

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1645911

Title:
  linux-firmware 1.157.5 causes sound issues after initramfs update

Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  On laptops with Kaby Lake processors and Sunrise point chipsets
  (System76 Lemu7), updating to the current (1.157.5) version of the
  linux-firmware package and then updating initramfs causes sound
  issues.  This can manifest in two ways:

  1: Volume hotkeys and controls appear to work, but actual playback volume 
remains the same.
 Three HDMI devices appear in the sound-settings gui, despite no HDMI 
device connected (and only 1 HDMI port)
  2: 'Dummy Output' is the only device in the sound-settings gui, and there is 
no sound output at all.

  In both cases dmesg shows error output relating to snd_hda_codec_hdmi.

  This bug only affects Xenial, not Yakkety.  Xenial still exhibits the
  above symptoms after installing the current Yakkety linux-firmware
  package.

  I believe the issue is related to the Kaby Lake firmware.  In testing,
  I was able to remove '/lib/firmware/i915/kbl_dmc_ver1_01.bin', run
  'sudo update-initramfs -u', and reboot to get sound working correctly
  again.

  Perhaps this firmware is needed for the upcoming Union Point chipsets,
  but causes problems with the for Kaby Lake processor laptops running
  the 4.4.0 kernel and Sunrise Point chipsets.  There is either a bug in
  the new Kaby Lake firmware or it is being erroneously applied to
  inappropriate hardware.

  I have received a number of reports of users running into this bug,
  presumably anyone who updated to the latest kernel and linux-firmware
  packages at the same time.  Based on testing, next kernel update could
  trigger the bug for many more users.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1720133] Re: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer

[Timo Aaltonen]

and the patch is in -hwe-16.04 backport for xenial

** Changed in: xorg-server (Ubuntu Xenial)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1720133

Title:
  USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or
  newer

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * This impacts all Ubuntu releases which received an update of x.org
  to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10

   * End users are unable to use their USB displays unless they
  workaround the problem which currently involves disabling pageflip for
  modesetting in x.org.conf file

   * The fix which has been submitted to x.org extends blacklisting
  mechanism so the EVDI kernel module which is essential for DisplayLink
  USB 3.0 devices to work is correctly recognised by x.org. Then the
  PRIME sync is disabled in such case; The patch can be found here:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1

  [Test Case]

  1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54 
downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed 
requirements and instructions can be found here:  
  2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking 
station
  3. Plug in an external monitor (HDMI or DisplayPort) to the docking station

  Expected result: 
  The external monitor should light up and show the desktop

  Actual result: 
  The monitor remains black or shows frozen desktop.

  [Regression Potential]

   * The patchset extends number of modules for which x.org changes its
  functionality. It checks if "evdi" string is in the syspath so it is
  quite unlikely there would be any impact on anything else then USB 3.0
  displays which use EVDI module.

  [Other Info]
   
   * The patch has been applied to Ubuntu x.org source code built and tested.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1720133/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1720133] Re: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer

[Timo Aaltonen]

fixed upstream

** No longer affects: xorg-server (Ubuntu Zesty)

** No longer affects: xorg-server (Ubuntu Artful)

** Changed in: xorg-server (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1720133

Title:
  USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or
  newer

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * This impacts all Ubuntu releases which received an update of x.org
  to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10

   * End users are unable to use their USB displays unless they
  workaround the problem which currently involves disabling pageflip for
  modesetting in x.org.conf file

   * The fix which has been submitted to x.org extends blacklisting
  mechanism so the EVDI kernel module which is essential for DisplayLink
  USB 3.0 devices to work is correctly recognised by x.org. Then the
  PRIME sync is disabled in such case; The patch can be found here:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1

  [Test Case]

  1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54 
downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed 
requirements and instructions can be found here:  
  2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking 
station
  3. Plug in an external monitor (HDMI or DisplayPort) to the docking station

  Expected result: 
  The external monitor should light up and show the desktop

  Actual result: 
  The monitor remains black or shows frozen desktop.

  [Regression Potential]

   * The patchset extends number of modules for which x.org changes its
  functionality. It checks if "evdi" string is in the syspath so it is
  quite unlikely there would be any impact on anything else then USB 3.0
  displays which use EVDI module.

  [Other Info]
   
   * The patch has been applied to Ubuntu x.org source code built and tested.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1720133/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1770271] Re: VegaM support

[Timo Aaltonen]

cosmic has 4.18 already

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770271

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1742755] Re: x86: CFL missing from early quirks

[Timo Aaltonen]

is included since 4.15.0-11

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1742755

Title:
  x86: CFL missing from early quirks

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  CFL was missing from intel_early_ids[]. The PCI ID needs to be there to
  allow the memory region to be stolen, otherwise we could have RAM being
  arbitrarily overwritten if for example we keep using the UEFI framebuffer,
  depending on how BIOS has set up the e820 map.

  commit is not in 4.15 yet, needed for both bionic and linux-oem

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1789913] [NEW] X crashes when connecting to an external monitor via HDMI (I+A)

[Timo Aaltonen]

Public bug reported:

Copied from a private bug:

- Steps to see the issue:
1. Connect a monitor to UUT via HDMI port
Expected Result:
  Video outputs successfully in the monitor
Actual Result:
  X crashes into a login screen

- BIOS: 0.7.3
- AMD driver release: 18.10, 18.20RC8 and 18.20RC9

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xorg-server-hwe-16.04 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: xorg-server (Ubuntu Xenial)
 Importance: Undecided
 Status: Won't Fix

** Affects: xorg-server-hwe-16.04 (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: xorg-server (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: xorg-server-hwe-16.04 (Ubuntu Bionic)
 Importance: Undecided
 Status: Invalid

** Also affects: xorg-server-hwe-16.04 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: xorg-server-hwe-16.04 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: xorg-server-hwe-16.04 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: xorg-server-hwe-16.04 (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: xorg-server-hwe-16.04 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1789913

Title:
  X crashes when connecting to an external monitor via HDMI (I+A)

Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Xenial:
  Won't Fix
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Bionic:
  New
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  Copied from a private bug:

  - Steps to see the issue:
  1. Connect a monitor to UUT via HDMI port
  Expected Result:
Video outputs successfully in the monitor
  Actual Result:
X crashes into a login screen

  - BIOS: 0.7.3
  - AMD driver release: 18.10, 18.20RC8 and 18.20RC9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1789913/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1785280] [NEW] Transition 4.13 OEM kernel users to 4.15 HWE kernel

[Timo Aaltonen]

Public bug reported:

The artful kernel was EOL'd, and now it's time to transition the users
of 4.13 OEM kernel over to 4.15 HWE kernel on 16.04.

** Affects: linux-meta-hwe (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-meta-hwe (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: Triaged

** Also affects: linux-meta-hwe (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux-meta-hwe (Ubuntu)
   Status: New => Invalid

** Changed in: linux-meta-hwe (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: linux-meta-hwe (Ubuntu Xenial)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1785280

Title:
  Transition 4.13 OEM kernel users to 4.15 HWE kernel

Status in linux-meta-hwe package in Ubuntu:
  Invalid
Status in linux-meta-hwe source package in Xenial:
  Triaged

Bug description:
  The artful kernel was EOL'd, and now it's time to transition the users
  of 4.13 OEM kernel over to 4.15 HWE kernel on 16.04.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Timo Aaltonen]

yes it is

thanks for testing!

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: xorg-server (Ubuntu Xenial)
   Status: Confirmed => Triaged

** Changed in: xorg-server (Ubuntu Xenial)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1780664

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server source package in Xenial:
  Triaged

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb

  
  After rebooting, all the issues disappeared.

  For example I wa

[Group.of.nepali.translators] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Timo Aaltonen]

** Package changed: mesa (Ubuntu) => xorg-server (Ubuntu)

** Also affects: xorg-server (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1780664

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server source package in Xenial:
  Triaged

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb

  
  After rebooting, all the issues disappeared.

  For example I was once again able to left-click on the Firefox **three
  line/bar** menu and view the drop down list menu.  Also the KDE bottom
  menu bar retured to the normal 

[Group.of.nepali.translators] [Bug 1770271] Re: VegaM support

[Timo Aaltonen]

kernel support is in 4.18, not sure if cosmic will get that, otherwise
these should be backported there too

mesa changes are in 18.1

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

** Changed in: mesa (Ubuntu)
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770271

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack

[Timo Aaltonen]

** Changed in: xserver-xorg-video-amdgpu-hwe-16.04 (Ubuntu)
   Status: New => Invalid

** No longer affects: xserver-xorg-video-amdgpu (Ubuntu)

** No longer affects: xserver-xorg-video-amdgpu (Ubuntu Xenial)

** No longer affects: xserver-xorg-video-ati (Ubuntu)

** No longer affects: xserver-xorg-video-ati (Ubuntu Xenial)

** No longer affects: xserver-xorg-video-intel (Ubuntu)

** No longer affects: xserver-xorg-video-intel (Ubuntu Xenial)

** Changed in: xserver-xorg-video-ati-hwe-16.04 (Ubuntu)
   Status: New => Invalid

** Changed in: xserver-xorg-video-intel-hwe-16.04 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1772632

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-6.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1775152] Re: Fix "Unable to handle kernel paging request" in AMD MP2 driver

[Timo Aaltonen]

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1775152

Title:
  Fix "Unable to handle kernel paging request" in AMD MP2 driver

Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  ===SRU Justification===
  [Impact]
  Touchpad doesn't work after boot. Roughly 1/10 fail rate.

  [Test]
  With the patch, I no longer see the issue in 30 times reboot.

  [Fix]
  Factor out the pointer in the union, so the pointer value won't get changed 
by other union member.

  [Regression Potential]
  Low. It's specific to a single driver, which only enabled in OEM-A kernel.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1774126] Re: linux-oem: 4.13.0-1030.33 -proposed tracker

[Timo Aaltonen]

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1774126

Title:
  linux-oem: 4.13.0-1030.33 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1774124
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack

[Timo Aaltonen]

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Invalid

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: New => Invalid

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1772632

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in llvm-toolchain-6.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

[Timo Aaltonen]

** Changed in: linux-oem (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux-oem (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1769980

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Committed
Status in wireless-regdb source package in Xenial:
  Fix Committed
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Committed
Status in wireless-regdb source package in Bionic:
  Fix Committed

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

  ---

  wireless-regdb SRU Justification

  Impact: New regulatory requirements in the EU necessitate updating our
  wireless regulatory database.

  Fix: New upstream release.

  Test Case: Minimal testing would be to reload the regdb (can be done
  with iw built from git or by rebooting) and verifying that you are
  able to change regulatory domains (e.g., sudo iw reg set US; iw reg
  get).

  Regression Potential: Minimal. Biggest risk would be the inability to
  load the new database due to the changes in signing, however testing
  will confirm that appropriate key is present.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1771919] Re: Support Realtek Bluetooth [0bda:c024]

[Timo Aaltonen]

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1771919

Title:
  Support Realtek Bluetooth [0bda:c024]

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  The driver rtk-btusb is already in ubuntu/rtl8821ce-bt. All we need to
  support this device is to add the ID to the driver and blacklist it in
  btusb.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack

[Timo Aaltonen]

** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-ati (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1772632

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in llvm-toolchain-6.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1772632] [NEW] Backport packages for 16.04.5 HWE stack

[Timo Aaltonen]

Public bug reported:

[Impact]

*** hwe-16.04 refresh for 16.04.4 ***

A minor update, only xserver sync, some driver updates plus a newer
Mesa.

Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

[Test case]

upgrade from/to stock & old hwe stack, test desktop usage

[Regression potential]

libdrm:
Slim to none, changes from 2.4.83 to 2.4.91
- amdgpu: new pci-ids, bugfixes, tests
- intel: new pci-ids
- drm: leak fixes, manpage updates
- exynos, etnaviv, freedreno, android: fixes, new stuff

wayland-protocols:
None, just adds a few protocol definitions (xml files)

llvm-toolchain-6.0:
None, a new package

libclc:
I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

xorg-server:
Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
- security fixes
- backported bugfixes to glamor, modesetting driver, xwayland etc

mesa:
New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

[Other info]

build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

** Affects: libclc (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: libdrm (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: llvm-toolchain-6.0 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: xorg-server-hwe-16.04 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: libclc (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: libdrm (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: llvm-toolchain-6.0 (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: mesa (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: xorg-server-hwe-16.04 (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Also affects: mesa (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: llvm-toolchain-6.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libdrm (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libclc (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libclc (Ubuntu)
   Status: New => Invalid

** Changed in: libdrm (Ubuntu)
   Status: New => Invalid

** Changed in: llvm-toolchain-6.0 (Ubuntu)
   Status: New => Invalid

** Changed in: mesa (Ubuntu)
   Status: New => Invalid

** Also affects: xorg-server-hwe-16.04 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server-hwe-16.04 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1772632

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in llvm-toolchain-6.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other 

[Group.of.nepali.translators] [Bug 1770565] Re: [i915_bpo] Fix flickering issue after panel change

[Timo Aaltonen]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

** Changed in: linux (Ubuntu)
 Assignee: Timo Aaltonen (tjaalton) => (unassigned)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770565

Title:
  [i915_bpo] Fix flickering issue after panel change

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Triaged

Bug description:
  [Impact]
  A certain OEM laptop changed the panel type/vendor, and the change regressed 
the driver causing a flickering image. The ODM has tools to measure various 
values of the driver/panel combination, and determined that some voltage levels 
were way too low to pass the spec. The process to bisect the commits took 
weeks, so while it's technically possible that this issue was fixed by a single 
commit (drm/i915: Ignore OpRegion panel type except on select machines), we've 
also kept another 10 commits which upstream thought should help (and did, they 
improved the measured values but not enough).

  So, this backport carries all 11 commits from 4.8/4.9 that the ODM
  verified to pass the tests.

  [Test case]
  Needs to be tested with the ODM tools to be sure.

  [Regression potential]
  There is some, but apart from the necessary refactoring the rest are bugfixes 
to match the HW specs, so this should in fact fix a lot more than just this 
certain machine.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1769182] Re: ./configure --enable-arm needed for ARM events

[Timo Aaltonen]

cosmic got this

** Changed in: rasdaemon (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: rasdaemon (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1769182

Title:
  ./configure --enable-arm needed for ARM events

Status in rasdaemon package in Ubuntu:
  Fix Released
Status in rasdaemon source package in Xenial:
  In Progress
Status in rasdaemon source package in Artful:
  In Progress
Status in rasdaemon source package in Bionic:
  Fix Committed
Status in rasdaemon package in Debian:
  Fix Released

Bug description:
  [Impact]
  The UEFI 2.6 spec added support for ARM processor errors and errors
  that have unrecognized CPER section types. rasdaemon needs to support ARM 
kernel trace events. To enable arm events we need to configure rasdaemon 
package with --enable-arm 

  [Test]
  debian/rules needs --enable-arm to enable arm events. I have a test build of 
the rasdaemon package in ppa:centriq-team/lp1741978-rasdaemon. I tested this on 
an a QDF2400 system. Here are the results for bionic, artful and xenial.

  --- bionic ---
  ubuntu@awrep3:~$ sudo service rasdaemon status
  ● rasdaemon.service - RAS daemon to log the RAS events
 Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor 
preset
 Active: active (running) since Mon 2018-04-23 15:25:18 UTC; 17s ago
   Main PID: 3369 (rasdaemon)
  Tasks: 1 (limit: 7065)
 CGroup: /system.slice/rasdaemon.service
 └─3369 /usr/sbin/rasdaemon -f -r

  Apr 23 15:25:18 awrep3 rasdaemon[3369]: ras:arm_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: Enabled event ras:arm_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't parse /proc/cpuinfo: missing 
[vend
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't register mce handler
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't get traces from ras:aer_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mc_event events
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording aer_event events
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording extlog_event 
events
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mce_record events
  Apr 23 15:25:19 awrep3 rasdaemon[3369]: rasdaemon: Recording arm_event events

  ubuntu@awrep3:~$ grep rasdaemon /var/log/syslog 
  Apr 23 15:25:18 awrep3 rasdaemon: ras:mc_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon: ras:mc_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:mc_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:mc_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:aer_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:aer_event
  Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:mc_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:aer_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: Can't write to set_event
  Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: Can't write to set_event
  Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:arm_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:mc_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:arm_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:arm_event
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't parse /proc/cpuinfo: 
missing [vendor_id] [cpu family] [model] [cpu MHz] [flags]
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't register mce handler
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't get 
ras:extlog_mem_event traces. Perhaps this feature is not supported on your 
system.
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't get traces from 
ras:aer_event
  Apr 23 15:25:18 awrep3 rasdaemon: ras:aer_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Listening to events for 
cpus 0 to 45
  Apr 23 15:25:18 awrep3 rasdaemon: Can't write to set_event
  Apr 23 15:25:18 awrep3 rasdaemon: ras:aer_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:aer_event
  Apr 23 15:25:18 awrep3 rasdaemon: Can't write to set_event
  Apr 23 15:25:18 awrep3 rasdaemon: ras:arm_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon: ras:arm_event event enabled
  Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:arm_event
  Apr 23 15:25:18 awrep3 rasdaemon: Can't parse /proc/cpuinfo: missing 
[vendor_id] [cpu family] [model] [cpu MHz] [flags]
  Apr 23 15:25:18 awrep3 rasdaemon: Can't register mce handler
  Apr 23 15:25:18 awrep3 rasdaemon: Can't get traces from ras:aer_event
  Apr 23 15:25:18 awrep3 

[Group.of.nepali.translators] [Bug 1657682] Re: Support latest Redpine WLAN/BT RS9113 driver

[Timo Aaltonen]

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

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1657682

Title:
  Support latest Redpine WLAN/BT RS9113 driver

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New

Bug description:
  Support latest Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel.

  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures. The impact
  is also restricted to { SDIO_DEVICE(0x041B, 0x9330) } chipsets.

  For linux-oem (4.15) bionic series:
  ~~
  To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways. Most of the
  patches are already upstream (either Accepted or under review) and being
  tracked here:
  https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A

  SAUCE patches have been tested by Canonical CE-QA (based on
  Ubuntu-4.15.0-16.17) and HWE is working with the Redpine to get them
  upstreamed to linux-wireless. For now, to meet the project schedule, we'll
  have to carry them in linux-oem.

  The impact is limited to the Redpine RS9113 Wifi+BT with following VID/PID
  { SDIO_DEVICE(0x041B, 0x9330) }.

  This bug is used for tracking purposes, please do not triage.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1766197] Re: Update btusb reset-resume quirk to decrease power usage

[Timo Aaltonen]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1766197

Title:
  Update btusb reset-resume quirk to decrease power usage

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  USB reset-resume quirk prevents the device from runtime suspending,
  which increases power usage.

  [Test]
  With the patch, the power consumption decreases 0.5W.
  The tested machine doesn't need the quirk to make btusb work.

  [Fix]
  Update the btusb reset-resume quirk with a DMI based version, which can
  be more specific.

  [Regression Potential]
  Low.
  Everthing is in mainline, and I haven't seen any new report about this
  issue for some time.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1766477] Re: Change the location for one of two front mics on a lenovo thinkcentre machine

[Timo Aaltonen]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1766477

Title:
  Change the location for one of two front mics on a lenovo thinkcentre
  machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Incomplete
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem source package in Bionic:
  New

Bug description:
  [Impact]
  On one of Lenovo thinkcenter machines we have, there are two microphone jacks
  on the front panel, but only one of them can work after we plug a micrphone in
  them.

  [Fix]
  Because two microphones are located in front panels, the alsa driver will 
assign
  the same jack name to them, but pulseaudio can't handle two jacks with the 
same
  name.

  After applying this FIXUP, they will have different mixer name,
  then pulseaudio can handle them correctly.

  
  [Test Case]
  After booting up, plug micrphone into any one of the two audio jacks, the 
microphone
  works very well.

  [Regression Potential]
  Very low, since this patch is specific to the thinkcenter machine with 
subsystem id
  0x17aa3138.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1764684] Re: Fix an issue that some PCI devices get incorrectly suspended

[Timo Aaltonen]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1764684

Title:
  Fix an issue that some PCI devices get incorrectly suspended

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  Some PCI device are not power managed by system firmware get runtime 
suspended incorrectly. In this case it's an xHC device, which can't be woken up 
by plugging USB device.

  [Test]
  With the patch, the xHC no longer get put to suspend incorrectly. USB devices 
can work on the xHC now.

  [Fix]
  We need to check if the device is power managed by system firmware, also if 
it supports PME from D3hot.

  [Regression Potential]
  Low.
  It fixes a regression caused by the PM core refactor.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu

[Timo Aaltonen]

** Also affects: linux-meta-oem (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-meta-oem (Ubuntu)
   Status: New => Invalid

** Changed in: linux-meta-oem (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1738259

Title:
  need to ensure microcode updates are available to all bare-metal
  installs of Ubuntu

Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  Invalid
Status in linux-meta-oem package in Ubuntu:
  Invalid
Status in linux-meta source package in Precise:
  New
Status in linux-meta source package in Trusty:
  Fix Committed
Status in linux-meta source package in Xenial:
  Fix Committed
Status in linux-meta-hwe source package in Xenial:
  Fix Committed
Status in linux-meta-hwe-edge source package in Xenial:
  Fix Committed
Status in linux-meta-lts-xenial source package in Xenial:
  Fix Committed
Status in linux-meta-oem source package in Xenial:
  Fix Committed
Status in linux-meta source package in Zesty:
  Invalid
Status in linux-meta source package in Artful:
  Fix Committed
Status in linux-meta source package in Bionic:
  Triaged

Bug description:
  From time to time, CPU vendors release updates to microcode that can
  be loaded into the CPU from the OS.  For x86, we have these updates
  available in the archive as amd64-microcode and intel-microcode.

  Sometimes, these microcode updates have addressed security issues with
  the CPU.  They almost certainly will again in the future.

  We should ensure that all users of Ubuntu on baremetal x86 receive
  these security updates, and have them applied to the CPU in early boot
  where at all feasible.

  Because these are hardware-dependent packages which we don't want to
  install except on baremetal (so: not in VMs or containers), the
  logical place to pull them into the system is via the kernel, so that
  only the kernel baremetal flavors pull them in.  This is analogous to
  linux-firmware, which is already a dependency of the linux-
  image-{lowlatency,generic} metapackages, and whose contents are
  applied to the hardware by the kernel similar to microcode.

  So, please update the linux-image-{lowlatency,generic} metapackages to
  add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
  and the corresponding hwe metapackages also.

  Please time this change to coincide with the next updates of the
  microcode packages in the archive.

  I believe we will also need to promote the *-microcode packages to
  main from restricted as part of this (again, by analogy with linux-
  firmware).

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1645591] Re: Driver for Exar USB UART

[Timo Aaltonen]

** Changed in: linux-oem (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1645591

Title:
  Driver for Exar USB UART

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  Fix Released
Status in linux-oem source package in Yakkety:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  Driver can be found at
  https://www.exar.com/design-tools/software-drivers

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1727228] Re: ath9k can't connect to wifi AP

[Timo Aaltonen]

** Changed in: linux-oem (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1727228

Title:
  ath9k can't connect to wifi AP

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  iwlist scan can search the available wifi APs, but can't get connected.

  On new Intel platforms like ApolloLake, legacy interrupt mechanism
  (INTx) is not supported, so WLAN modules are not working because
  interrupts are missing.

  The affected and listed platforms are
  Dell Inspiron 24-3460
  Dell Inspiron 14-3473
  Dell Inspiron 3472
  Dell Inspiron 3576
  Dell Vostro 3262
  Dell Vostro 15-3572
  Dell Vostro 3578

  [Fix]
  Qualcomm provided a MSI patch for ath9k, and it fixes the issue.

  [Test Case]
  Tested on the machines mentioned above, and they all work well.

  [Regression Potential]
  There shouldn't  be any regression potential. These are newly enabled 
machines and quirks are applied based on DMI_PRODUCT_NAME to only use MSI on 
such machines.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1685133] Re: Fix RX fail issue on Exar USB serial driver after resume from S3/S4

[Timo Aaltonen]

** Changed in: linux-oem (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1685133

Title:
  Fix RX fail issue on Exar USB serial driver after resume from S3/S4

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  Resolution of LP: #1645591 added support for Exar USB UART devices in
  Ubuntu Xenial kernel. However, the devices fail to RX data after
  system resumes from suspend-to-ram(S3) and suspend-to-disk(S4). This
  bug is to track the integration of the driver released by the vendor
  to fix this issue.

  Changelog:
  
  Version 1B, 11/6/2015
  Fixed Bug: The conditional logic to support kernel 3.9 was incorrect(line 396 
in xr_usb_serial_common.c).
  
  Version 1A, 1/9/2015
  This driver will work with any USB UART function in these Exar devices:
  XR21V1410/1412/1414
  XR21B1411
  XR21B1420/1422/1424
  XR22801/802/804

  Exar serial devices are typically enuremated as /dev/ttyXRUSB[0-3]

  This bug is used for tracking purposes, please do not triage.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1759188] Re: [8086:3e92] display becomes blank after S3

[Timo Aaltonen]

** Changed in: linux-oem (Ubuntu Bionic)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759188

Title:
  [8086:3e92] display becomes blank after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  The display becomes black after S3 with the following error messages.

  [   38.304449] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 
0050 w(1)
  [   38.304462] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK on first 
message, retry
  [   38.306726] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 
0050 w(1)
  [   38.306733] [drm:drm_do_probe_ddc_edid [drm]] drm: skipping non-existent 
adapter i915 gmbus dpd
  [   38.311251] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode 
HDMI ID: DP-HDMI ADAPTOR\004 (err 0)
  [   38.313538] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode 
adaptor ID: 44 (err 0)
  [   38.313554] [drm:intel_hdmi_set_edid [i915]] DP dual mode adaptor (type 1 
HDMI) detected (max TMDS clock: 165000 kHz)
  [   38.313557] [drm:drm_helper_hpd_irq_event [drm_kms_helper]] 
[CONNECTOR:115:HDMI-A-1] status updated from disconnected to disconnected

  [Fix]
  This commit pointed out by Timo fixes the issue.

  [Regression Potential]
  Should be low, although the change applies broadly.
  From the patch description, it explains it should be safe.
  > This workaround was designed to minimize the impact only
  > to save the bad case with that link rates. But HW engineers
  > indicated that it should be safe to apply broadly, although
  > they were expecting the DPLL0 link rate to be unchanged on
  > runtime.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1756700] Re: Ryzen/Raven Ridge USB ports do not work

[Timo Aaltonen]

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1756700

Title:
  Ryzen/Raven Ridge USB ports do not work

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux-oem source package in Bionic:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1690362] Re: Exar usb-serial doesn't restore baud rate after resume from S3/S4

[Timo Aaltonen]

** Changed in: linux-oem (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1690362

Title:
  Exar usb-serial doesn't restore baud rate after resume from S3/S4

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  Resume from suspend-to-ram and suspend-to-disk should restore data 
send/receive over Exar usb-serial ports. The XR21V1412 ports were using the 
hardware power-on default of 9600bps
  after resume from S3/S4. This patch re-initializes the baud rate and fixes 
the re-connection issues after resume from S3/S4.

  This bug is to track the integration of the driver released by the
  vendor to fix this issue.

  Changelog:

  Version 1B, 11/6/2015
  Fixed Bug: The conditional logic to support kernel 3.9 was incorrect(line 396 
in xr_usb_serial_common.c).

  Version 1A, 1/9/2015
  This driver will work with any USB UART function in these Exar devices:
  XR21V1410/1412/1414
  XR21B1411
  XR21B1420/1422/1424
  XR22801/802/804

  Exar serial devices are typically enuremated as /dev/ttyXRUSB[0-3]

  This bug is used for tracking purposes, please do not triage.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1759303] Re: Update Aquantia driver to fix various issues

[Timo Aaltonen]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux-oem (Ubuntu)
   Status: New => Fix Released

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759303

Title:
  Update Aquantia driver to fix various issues

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  ===SRU Justification===
  [Impact]
  According to commit log, there are lots of issues got fixed for Aquantia 
driver since v4.13.

  [Test]
  It's a request from costumer.
  Unless Aquantia provides a reproducer, we need Aquantia to verify it.

  [Fix]
  Update Aquantia driver to 2.0.2.1, basically keep the driver in sync with 
Linux kernel v4.16.

  [Regression Potential]
  Low. The driver is the same one as in v4.16, so it should be well tested by 
Aquantia.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1764684] Re: Fix an issue that some PCI devices get incorrectly suspended

[Timo Aaltonen]

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Triaged

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1764684

Title:
  Fix an issue that some PCI devices get incorrectly suspended

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  New
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  Some PCI device are not power managed by system firmware get runtime 
suspended incorrectly. In this case it's an xHC device, which can't be woken up 
by plugging USB device.

  [Test]
  With the patch, the xHC no longer get put to suspend incorrectly. USB devices 
can work on the xHC now.

  [Fix]
  We need to check if the device is power managed by system firmware, also if 
it supports PME from D3hot.

  [Regression Potential]
  Low.
  It fixes a regression caused by the PM core refactor.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1766398] Re: set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630

[Timo Aaltonen]

** Also affects: linux-oem (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Critical
 Assignee: Hui Wang (hui.wang)
   Status: New

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: linux-oem (Ubuntu Artful)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1766398

Title:
  set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New

Bug description:
  [Impact]
  On this Dell machine (codename: turtle bay), the microphone always shows up
  in the sound-setting even there is no microphone plugged in.

  [Fix]

  Without this fix, the pin will be regarded as microphone, and the jack name
  is "Mic Phantom", it is always on in the pulseaudio even nothing is plugged
  into the jack. So the UI is confusing to users since the microphone always
  shows up in the UI even there is no microphone plugged.

  After adding this flag, the jack name is "Headset Mic Phantom", then
  the pulseaudio can handle its detection correctly.

  
  [Test Case]
  After booting up the system, and without plugging anything in the audio combo
  jack, there is nothing in the input tab of sound-setting, then plug a headset
  in the jack, the what-did-you-plug-in dialogue pops up, users can select 
headset
  mic from UI, and headset-mic shows up in the sound-setting, we can record 
sound
  via headset-mic

  
  [Regression Potential]
  Very low, since this patch is specific for ALC255_FIXUP_DELL_HEADSET_MIC 
which is
  only used by Dell precision 3630 by now.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1766477] Re: Chang the location for one of two front mics on a lenovo thinkcentre machine

[Timo Aaltonen]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Critical
 Assignee: Hui Wang (hui.wang)
   Status: New

** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Changed in: linux-oem (Ubuntu Artful)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1766477

Title:
  Chang the location for one of two front mics on a lenovo thinkcentre
  machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New

Bug description:
  [Impact]
  On one of Lenovo thinkcenter machines we have, there are two microphone jacks
  on the front panel, but only one of them can work after we plug a micrphone in
  them.

  [Fix]
  Because two microphones are located in front panels, the alsa driver will 
assign
  the same jack name to them, but pulseaudio can't handle two jacks with the 
same
  name.

  After applying this FIXUP, they will have different mixer name,
  then pulseaudio can handle them correctly.

  
  [Test Case]
  After booting up, plug micrphone into any one of the two audio jacks, the 
microphone
  works very well.

  [Regression Potential]
  Very low, since this patch is specific to the thinkcenter machine with 
subsystem id
  0x17aa3138.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1764684] Re: Fix an issue that some PCI devices get incorrectly suspended

[Timo Aaltonen]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1764684

Title:
  Fix an issue that some PCI devices get incorrectly suspended

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  Some PCI device are not power managed by system firmware get runtime 
suspended incorrectly. In this case it's an xHC device, which can't be woken up 
by plugging USB device.

  [Test]
  With the patch, the xHC no longer get put to suspend incorrectly. USB devices 
can work on the xHC now.

  [Fix]
  We need to check if the device is power managed by system firmware, also if 
it supports PME from D3hot.

  [Regression Potential]
  Low.
  It fixes a regression caused by the PM core refactor.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1766197] Re: Update btusb reset-resume quirk to decrease power usage

[Timo Aaltonen]

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1766197

Title:
  Update btusb reset-resume quirk to decrease power usage

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem source package in Xenial:
  New

Bug description:
  [Impact]
  USB reset-resume quirk prevents the device from runtime suspending,
  which increases power usage.

  [Test]
  With the patch, the power consumption decreases 0.5W.
  The tested machine doesn't need the quirk to make btusb work.

  [Fix]
  Update the btusb reset-resume quirk with a DMI based version, which can
  be more specific.

  [Regression Potential]
  Low.
  Everthing is in mainline, and I haven't seen any new report about this
  issue for some time.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1595889] Re: Bind9 service does not source OPTIONS from /etc/default/bind9

[Timo Aaltonen]

fixed in bionic at least

** Changed in: bind9 (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1595889

Title:
  Bind9 service does not source OPTIONS from /etc/default/bind9

Status in bind9 package in Ubuntu:
  Fix Released
Status in bind9 source package in Xenial:
  New
Status in bind9 source package in Zesty:
  New

Bug description:
  Ubuntu 16.06 x86_64

  Doesn't work OPTIONS from /etc/default/bind9

  $sudo service bind9 stop
  $cat /etc/default/bind9
   # run resolvconf?
   RESOLVCONF=no
   # startup options for the server
   OPTIONS="-u bind -4"

  $ sudo service bind9 start
  $ ps ax | grep named
   1112 ?Ssl0:00 /usr/sbin/named -f -u bind

  Where option "-4"?

  In Ubuntu 14.04 this good work!

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

[Timo Aaltonen]

** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux-oem (Ubuntu Artful)
   Status: New => Invalid

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

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

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: linux-oem (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1762693

Title:
  No network with e1000e driver on 4.13.0-38-generic

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  New
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  e1000e stops working since 4.13.0-38-generic/4.13.0-1022-oem.
  The regression was introduced by patches in LP: #1730550.

  [Fix]
  Commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 fixes the issue.
  e1000e now reports correct link status.

  [Test]
  With the extra commit, the e1000e starts to working again.

  [Regression Potential]
  Low.
  It says:
  Fixes: 19110cfbb34d ("e1000e: Separate signaling for link check/link up")
  So it's pretty clear this patch is to fix the regression.

  It's in upstream linux-stable, so only Arftul needs this patch.

  ===Original Bug Report===
  When my computer boots with the most recent kernel 4.13.0-38-generic, I don't 
have a working network connection. ethtool reports that my network interface 
doesn't have a connection:

  martin@dogmeat ~ % cat ethtool.txt
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: Unknown!
  Duplex: Unknown! (255)
  Port: Twisted Pair
  PHYAD: 2
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown (auto)
  Supports Wake-on: pumbg
  Wake-on: g
  Current message level: 0x0007 (7)
     drv probe link
  Link detected: no

  dmesg contains suspicious e1000e error messages:

  martin@dogmeat ~ % tail -n 40 dmesg.txt
  [   20.211715] Could not find valid key in user session keyring for sig 
specified in mount option: [459a10809c211381]
  [   20.211716] One or more global auth toks could not properly register; rc = 
[-2]
  [   20.211717] Error parsing options; rc = [-2]
  [   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   51.244686] ahci :00:17.0: port does not support device sleep
  [   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   88.800521] 

[Group.of.nepali.translators] [Bug 1763296] Re: linux-oem: 4.13.0-1024.26 -proposed tracker

[Timo Aaltonen]

** Changed in: kernel-sru-workflow/verification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux-oem (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1763296

Title:
  linux-oem: 4.13.0-1024.26 -proposed tracker

Status in Kernel SRU Workflow:
  New
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-1024.26 upload package. This bug
  will contain status and testing results related to that upload.

  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: 1761456
  phase: Packaging

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1763296] [NEW] linux-oem: 4.13.0-1024.26 -proposed tracker

[Timo Aaltonen]

Public bug reported:

This bug is for tracking the 4.13.0-1024.26 upload package. This bug
will contain status and testing results related to that upload.

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: 1761456
phase: Packaging

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem (Ubuntu Xenial)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** 

[Group.of.nepali.translators] [Bug 1763271] Re: [8086:3e92] display becomes blank after S3

[Timo Aaltonen]

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1763271

Title:
  [8086:3e92] display becomes blank after S3

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  The display becomes black after S3 with the following error messages.

  dmesg:
  [ 60.546305] [drm:intel_dp_start_link_train [i915]] Link Training failed at 
link rate = 54, lane count = 4

  Xorg.0.log:
  [ 60.748] (EE) modeset(0): failed to set mode: Invalid argument
  [ 60.748] (WW) modeset(0): hotplug event: connector 48's link-state is BAD, 
tried resetting the current mode. You may be left with a black screen if this 
fails...

  [Fix]
  Looks like link training fallback fails sometimes with eDP, we need this 
commit to fix the issue.

  commit a306343bcd7df89d9d45a601929e26866e7b7a81 (refs/bisect/bad)
  Author: Manasi Navare 
  Date: Thu Oct 12 12:13:38 2017 -0700

  drm/i915/edp: Do not do link training fallback or prune modes on
  EDP

  [Regression Potential]
  Should be low.
  To avoid conflicts, we introduce 4 commits, I'll try explaining them below

  a306343 drm/i915/edp: Do not do link training fallback or prune modes on EDP
     This is the fix commit and the behavior only changes when DP is eDP, it 
does nothing if DP is eDP. Should be fine to not do link training fallback and 
not emit Hotplug Uevent to userspace to start modeset, since its eDP, the 
display is fixed.

  1853a9d drm/i915/dp: make is_edp non-static and rename to intel_dp_is_edp
  7b91bf7 drm/i915/dp: rename intel_dp_is_edp to intel_dp_is_port_edp
     Above 2 commits do function name renaming only.

  dc911f5 drm/i915/edp: Allow alternate fixed mode for eDP if available.
     Change the prototype of function "intel_panel_init()" and adding one extra 
argument, should have small impact on the display.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp