[Group.of.nepali.translators] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-09-19 Thread Mathew Hodson 
** Changed in: kbd (Ubuntu Cosmic)
   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/520546

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

     On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration

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

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844388
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 20:05 UTC
+ phase: Testing
+ phase-changed: Friday, 20. September 2019 01:45 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842580
  variant: debs

-- 
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/1844387

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  Confirmed

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844388
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Friday, 20. September 2019 01:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842580
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844387/+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 1844393] Re: xenial/linux-azure: 4.15.0-1060.65 -proposed tracker

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844403
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 20:10 UTC
+ phase: Testing
+ phase-changed: Friday, 20. September 2019 01:41 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842587
  trackers:
trusty/linux-azure: bug 1844392
xenial/linux-azure-edge: bug 1844391
xenial/linux-azure/azure-kernel: bug 1844390
  variant: debs

-- 
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/1844393

Title:
  xenial/linux-azure: 4.15.0-1060.65 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844403
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 20. September 2019 01:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842587
  trackers:
trusty/linux-azure: bug 1844392
xenial/linux-azure-edge: bug 1844391
xenial/linux-azure/azure-kernel: bug 1844390
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844393/+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 1844391] Re: xenial/linux-azure-edge: 4.15.0-1060.65 -proposed tracker

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844393
  packages:
meta: linux-meta-azure-edge
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 20:12 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 19. September 2019 22:51 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842584
  variant: debs

-- 
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/1844391

Title:
  xenial/linux-azure-edge: 4.15.0-1060.65 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure-edge package in Ubuntu:
  Invalid
Status in linux-azure-edge source package in Xenial:
  Confirmed

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844393
  packages:
meta: linux-meta-azure-edge
  phase: Ready for Testing
  phase-changed: Thursday, 19. September 2019 22:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842584
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844391/+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 1844406] Re: xenial/linux-aws: 4.4.0-1095.106 -proposed tracker

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844416
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 20:25 UTC
+ phase: Testing
+ phase-changed: Thursday, 19. September 2019 22:46 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842597
  trackers:
xenial/linux-aws/aws-kernel: bug 1844405
  variant: debs

-- 
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/1844406

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844416
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 19. September 2019 22:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842597
  trackers:
xenial/linux-aws/aws-kernel: bug 1844405
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844406/+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 1844412] Re: xenial/linux-snapdragon: 4.4.0-1127.135 -proposed tracker

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844416
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 20:31 UTC
+ phase: Testing
+ phase-changed: Thursday, 19. September 2019 22:46 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842603
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1844411
  variant: debs

-- 
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/1844412

Title:
  xenial/linux-snapdragon: 4.4.0-1127.135 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844416
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 19. September 2019 22:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842603
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1844411
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844412/+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 1844401] Re: xenial/linux-hwe: 4.15.0-65.74~16.04.1 -proposed tracker

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844403
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 08:01 UTC
+ phase: Testing
+ phase-changed: Thursday, 19. September 2019 21:47 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842593
  trackers:
xenial/linux-deeplens: bug 1844400
xenial/linux-hwe-edge: bug 1844399
  variant: debs

-- 
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/1844401

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Xenial:
  Confirmed

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844403
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Testing
  phase-changed: Thursday, 19. September 2019 21:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842593
  trackers:
xenial/linux-deeplens: bug 1844400
xenial/linux-hwe-edge: bug 1844399
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844401/+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 1844413] Re: xenial/linux-fips: 4.4.0-1022.27 -proposed tracker

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844416
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 20:35 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 19. September 2019 21:36 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
+   promote-signing-to-proposed: Pending -- ready for review
  replaces: bug 1842605
  variant: debs

-- 
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/1844413

Title:
  xenial/linux-fips: 4.4.0-1022.27 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
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 verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844416
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 19. September 2019 21:36 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review
  replaces: bug 1842605
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844413/+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 1844400] Re: xenial/linux-deeplens: 4.15.0-1009.9 -proposed tracker

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844401
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 20:16 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 19. September 2019 20:36 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   certification-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842592
  variant: debs

-- 
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/1844400

Title:
  xenial/linux-deeplens: 4.15.0-1009.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844401
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Ready for Testing
  phase-changed: Thursday, 19. September 2019 20:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842592
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844400/+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 1621901] Re: impitool lacks support for ipv6 addresses

2019-09-19 Thread Adam Collard 
This bug has not seen any activity in the last 6 months, so it is being
automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

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

Title:
  impitool lacks support for ipv6 addresses

Status in MAAS:
  Invalid
Status in ipmitool package in Ubuntu:
  Fix Released
Status in ipmitool source package in Xenial:
  New
Status in ipmitool source package in Yakkety:
  New
Status in ipmitool package in Debian:
  Fix Released

Bug description:
  # sudo ipmitool lan print
  Set in Progress : Set Complete
  Auth Type Support   :
  Auth Type Enable: Callback :
  : User :
  : Operator :
  : Admin:
  : OEM  :
  IP Address Source   : Static Address
  IP Address  : 0.0.0.0
  Subnet Mask : 0.0.0.0
  MAC Address : 14:58:d0:47:70:28
  SNMP Community String   :
  BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled
  Default Gateway IP  : 0.0.0.0
  802.1q VLAN ID  : Disabled
  802.1q VLAN Priority: 0
  Cipher Suite Priv Max   : Not Available
  Bad Password Threshold  : Not Available
  #

  The iLo in question is configured with a static IPv6 address (though SLAAC 
made no difference), and is quite reachable:
  ssh -l lamont 2001:...::cb
  lamont@2001:...::cb's password:
  User:lamont logged-in to kearns.example.com(0.0.0.0 / 
FE80::1658:D0FF:FE47:7028)
  iLO 4 Standard 2.03 at  Nov 07 2014
  Server Name:
  Server Power: On

  In fact, I can't seem to get the iLo to tell me its IPv6 address (other
  than link-local) at the ssh prompt -- only at via web ui.

  Please fix ipmitool to return the ipv6 address of the iLo, if any, in
  addition to any IPv4 address.

  lamont

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1621901/+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 1655440] Re: "unconfigured" NIC can still get IPv6 addresses via RA

2019-09-19 Thread Adam Collard 
This bug has not seen any activity in the last 6 months, so it is being
automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

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

Title:
  "unconfigured" NIC can still get IPv6 addresses via RA

Status in curtin:
  Invalid
Status in MAAS:
  Invalid
Status in netplan:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in nplan source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Some users omit configuration for some interfaces, and expect that the lack 
of configuration translates to "no IP address" on the interface, as per netplan 
documentation.

  [Test case]
  /!\ Requires an IPv6-capable network.
  1) Update nplan.
  2) Ensure the nplan configure includes the 'accept-ra: no' option.
  3) Run 'netplan apply'
  4) Verify that there is no IPv6 address set for the interface where 
'accept-ra: no is set; using 'ip -6 addr'.

  [Regression potential]
  Incorrect configuration of the IPv6 addresses on a device would consistute a 
regression: for instance, getting an IPv6 SLAAC address when 'accept-ra: no' is 
set; or no IPv6 address when RAs are being received and 'accept-ra' is not set. 
Furthermore, possible regressions may look like incorrect IPv6 configuration or 
missing options on IPv6 or IPv4 setups, in the form of not retrieving an IP 
address or getting the wrong IP.

  ---

  TL;DR A MAAS NIC that is set to "unconfigured" (or "link up") will get
  no IPv4 address, but it might still get an IPv6 address via router
  advertisements (RA), if there is such a service in that network
  segment.

  Whether this is a bug or not is up for discussion. That's the point of
  this ticket, actually, so that this discussion can be had and be
  recorded.

  We found out about this when we couldn't get any connectivity to
  instances of an openstack cloud deployed by the autopilot.

  After much debugging, we found that the problem was with the br-data
  bridge on the neutron-gateway node: it didn't have the external NIC
  (eth1) as part of the bridge.

  The neutron-gateway charm, before adding any NIC to a bridge, performs
  certain checks to see if it's really unused. One of these checks looks
  for IP addresses on the NIC, both IPv4 and IPv6. In MAAS, that node
  had eth1 set to "unconfigured", so that eth1 is just "up", but has no
  IP (v4) address. Turns out this NIC had gotten an IPv6 ULA from an
  openwrt router in that network segment. That was enough for the charm
  to not add it to the br-data bridge, thus breaking connectivity to
  openstack instances that were later brought up.

  We shut down the RA service on the openwrt router and then everything
  worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1655440/+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 1844399] Re: xenial/linux-hwe-edge: 4.15.0-65.74~16.04.1 -proposed tracker

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844401
  packages:
meta: linux-meta-hwe-edge
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 08:22 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 19. September 2019 14:01 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842591
  variant: debs

-- 
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/1844399

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Confirmed

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844401
  packages:
meta: linux-meta-hwe-edge
  phase: Ready for Testing
  phase-changed: Thursday, 19. September 2019 14:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842591
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844399/+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 1827202] Re: Apport hook may expose sensitive information

2019-09-19 Thread Christian Ehrhardt  
This fix is in 5.128-0ubuntu1 in Eoan

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

** Changed in: byobu (Ubuntu)
 Assignee: Paride Legovini (legovini) => (unassigned)

** Tags removed: server-next

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

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

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

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

** Changed in: byobu (Ubuntu Bionic)
   Status: New => Won't Fix

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

** Changed in: byobu (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: byobu (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: byobu (Ubuntu Disco)
   Importance: Undecided => Low

-- 
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/1827202

Title:
  Apport hook may expose sensitive information

Status in byobu:
  Invalid
Status in byobu package in Ubuntu:
  Fix Released
Status in byobu source package in Xenial:
  Won't Fix
Status in byobu source package in Bionic:
  Won't Fix
Status in byobu source package in Disco:
  Won't Fix

Bug description:
  OVERVIEW
  

  Author: Sander Bos
  Author's e-mail address: sbos _at_ sbosnet _dot_ nl
  Author's website: 
  CVE identifier: requested
  Date: 2019-04-19
  Report version: 2


  SUMMARY
  ---

  The Ubuntu "byobu" package contains a security vulnerability which may
  lead to disclosure of private as well as sensitive information in case
  a bug or crash report file gets created by the user or in case the
  application crashes, with this report file then being uploaded to an
  external crash report database, all through the Ubuntu "Apport" crash
  report framework.

  The vulnerability is specific to the Ubuntu (and Debian) byobu package
  (and potentially derivate OS packages, for example Linux Mint), and not
  present in the upstream application itself (although it is in fact part
  of the upstream source code repository).


  DESCRIPTION
  ---

  "Byobu" [1, 2] is a text-based window manager, terminal multiplexer,
  and integrated DevOps environment which can act as an enhancement to
  the GNU Screen and tmux applications.  It was initially developed for
  Ubuntu, and is nowadays available in many GNU/Linux distributions as
  well as macOS and some BSD operating systems.

  The Ubuntu "byobu" package adds a file "debian/source_byobu.py" [3] to
  the program.  This file acts as a so-called "package hook" for the Ubuntu
  "Apport" crash report framework [4].  When a Byobu process crashes,
  or when the user manually creates a bug report file for the program,
  a local crash or bug report file gets created.  This report file may be
  amended with additional information, as defined by the package hook file.
  The resulting report file may then be uploaded to an external bug report
  database like Launchpad [5] or the Ubuntu Error Tracker [6].

  The vulnerability lies in the fact that the debian/source_byobu.py package
  hook file includes the user's ~/.screenrc file (line numbers prepended):

   10 def add_info(report):
  [...]
   13 attach_file_if_exists(report, path.expanduser('~/.screenrc'), 
'ScreenRC')

  This file however is a user's private dot file, which should therefore
  probably not be attached to the report at all to begin with.  Specifically
  though the file may contain actual sensitive information, including but
  not limited to passwords, user names, and host names.

  Thus, private and / or sensitive user information may end up in external
  bug databases and (potentially public) bug reports.  This applies
  specifically in case the system on which the application crashed is
  configured to automatically upload Apport crash reports without asking
  the user's permission or requiring any user intervention at all.

  The vulnerability is specific to the Ubuntu (and Debian) byobu package
  (and potentially derivate OS packages, for example Linux Mint), and not
  present in the upstream application itself.


  VULNERABILITY IMPACT
  

  The general vulnerability impact type of this vulnerability is disclosure
  of sensitive information potentially including but not limited to
  passwords, user names, and host names.

  The leakage of such sensitive information from the ~/.screenrc file is
  the core of this security vulnerability.  However, even when the file
  does not (or would never) include sensitive information like passwords,
  sending out a user dot file like ~/.screenrc could still be considered
  a privacy infringement on itself.

  The following are examples of GNU Screen commands which may be included
  in ~/

[Group.of.nepali.translators] [Bug 1822503] Re: ClamAV needs updated to reflect security fixes

2019-09-19 Thread Leonidas S. Barbosa 
In precise/esm these CVE were fixed update/released in 0.100.3+dfsg-
1ubuntu0.12.04.1

** Changed in: clamav (Ubuntu Precise)
   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/1822503

Title:
  ClamAV needs updated to reflect security fixes

Status in clamav package in Ubuntu:
  Fix Released
Status in clamav source package in Precise:
  Fix Released
Status in clamav source package in Trusty:
  Fix Released
Status in clamav source package in Xenial:
  Fix Released
Status in clamav source package in Bionic:
  Fix Released
Status in clamav source package in Cosmic:
  Fix Released
Status in clamav source package in Disco:
  Fix Released

Bug description:
  lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  apt-cache policy clamav
  clamav:
Installed: 0.100.2+dfsg-1ubuntu0.18.04.1
Candidate: 0.100.2+dfsg-1ubuntu0.18.04.1

  
  The current version of ClamAV for 18.04.2 LTS is 
0.100.2+dfsg-1ubuntu0.18.04.1. The current stable version of ClamAV is 0.101.2. 
There have been patches released for 0.101.2 and 0.100.3 that fix security 
related bugs as shown below:

  ClamAV 0.101.2

  ClamAV 0.101.2 is a patch release to address a handful of security
  related bugs.

  This patch release is being released alongside the 0.100.3 patch so that users
  who are unable to upgrade to 0.101 due to libclamav API changes are protected.

  This release includes 3 extra security related bug fixes that do not apply to
  prior versions.  In addition, it includes a number of minor bug fixes and
  improvements.

  - Fixes for the following vulnerabilities affecting 0.101.1 and prior:
- CVE-2019-1787:
  An out-of-bounds heap read condition may occur when scanning PDF
  documents. The defect is a failure to correctly keep track of the number
  of bytes remaining in a buffer when indexing file data.
- CVE-2019-1789:
  An out-of-bounds heap read condition may occur when scanning PE files
  (i.e. Windows EXE and DLL files) that have been packed using Aspack as a
  result of inadequate bound-checking.
- CVE-2019-1788:
  An out-of-bounds heap write condition may occur when scanning OLE2 files
  such as Microsoft Office 97-2003 documents. The invalid write happens when
  an invalid pointer is mistakenly used to initialize a 32bit integer to
  zero. This is likely to crash the application.

  - Fixes for the following vulnerabilities affecting 0.101.1 and 0.101.0 only:
- CVE-2019-1786:
  An out-of-bounds heap read condition may occur when scanning malformed PDF
  documents as a result of improper bounds-checking.
- CVE-2019-1785:
  A path-traversal write condition may occur as a result of improper input
  validation when scanning RAR archives. Issue reported by aCaB.
- CVE-2019-1798:
  A use-after-free condition may occur as a result of improper error
  handling when scanning nested RAR archives. Issue reported by David L.

  - Fixes for the following assorted bugs:
- Added checks to prevent shifts from causing undefined behavior in HTML
  normalizer, UPX unpacker, ARJ extractor, CPIO extractor, OLE2 parser,
  LZW decompressor used in the PDF parser, Xz decompressor, and UTF-16 to
  ASCII transcoder.
- Added checks to prevent integer overflow in UPX unpacker.
- Fix for minor memory leak in OLE2 parser.
- Fix to speed up PDF parser when handling truncated (or malformed) PDFs.
- Fix for memory leak in ARJ decoder failure condition.
- Fix for potential memory and file descriptor leak in HTML normalization 
code.

  - Removed use of problematic feature that converted file descriptors to
file paths. The feature was intended to improve performance when scanning
file types, notably RAR archives, for which the API requires a file path.
This feature caused issues in environments where the ClamAV engine is run
in a low-permissions or sandboxed process. RAR archives are still supported
with this change, but performance may suffer slightly if the file path is 
not
provided in calls to `cl_scandesc_callback()`.
- Added filename and tempfile names to scandesc calls in clamd.
- Added general scan option `CL_SCAN_GENERAL_UNPRIVILEGED` to treat the scan
  engine as unprivileged, meaning that the scan engine will not have read
  access to the file. Provided file paths are for logging purposes only.
- Added ability to create a temp file when scanning RAR archives when the
  process does not have read access to the file path provided (i.e.
  unprivileged is set, or an access check fails).

  ClamAV 0.100.3

  ClamAV 0.100.3 is a patch release to address a few security related
  bugs.

  This patch release is being released alongside the 0.101.2 patch so that users

[Group.of.nepali.translators] [Bug 1844654] Re: Remove from archive

2019-09-19 Thread Steve Langasek 
Removed and blacklisted.

Removing packages from eoan:
virtualbox-ext-pack 6.0.12-1 in eoan
virtualbox-ext-pack 6.0.12-1 in eoan amd64
virtualbox-ext-pack 6.0.12-1 in eoan arm64
virtualbox-ext-pack 6.0.12-1 in eoan armhf
virtualbox-ext-pack 6.0.12-1 in eoan i386
virtualbox-ext-pack 6.0.12-1 in eoan ppc64el
virtualbox-ext-pack 6.0.12-1 in eoan s390x
Comment: Installer package for undistributable software; has unacceptable 
autopkgtests that trigger installation of encumbered software; LP: #1844654
1 package successfully removed.


** Changed in: virtualbox-ext-pack (Ubuntu Eoan)
   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/1844654

Title:
  Remove from archive

Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  New
Status in virtualbox-ext-pack source package in Bionic:
  New
Status in virtualbox-ext-pack source package in Disco:
  New
Status in virtualbox-ext-pack source package in Eoan:
  Fix Released

Bug description:
  virtualbox-ext-pack is *not* free software and therefore it should not
  be in the archive. This is a request to do the following:

  * Remove virtualbox-ext-pack from the archive for all releases
  * Ensure no version of the package is in proposed and remove if it is
  * Blacklist the package from syncing from Debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1844654/+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 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment

2019-09-19 Thread Adam Collard 
This bug has not seen any activity in the last 6 months, so it is being
automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

** Changed in: maas
   Status: Incomplete => Expired

-- 
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/1607345

Title:
  Collect all logs needed to debug curtin/cloud-init for each deployment

Status in cloud-init:
  Confirmed
Status in MAAS:
  Expired
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Zesty:
  Won't Fix

Bug description:
  Re-opening this bug as confirmed because the previous SRU content
  released only provided only 'cloud-init collect-logs'. A command line
  tool which tars all cloud-init install logs and artifacts for triage.

  However, those fixes did not provide any configuration options for
  MAAS to request that those logs are automatically published to MAAS
  upon error.

  
  Cloud-init should provide cloud-config which allows consumers to specify an 
endpoint and oauth credentials to which cloud-init will automatically POST all 
compressed cloud-init log artifacts.

  
  === Original Description ===
  According to https://bugs.launchpad.net/maas/+bug/1604962/comments/12, these 
logs are needed to debug curtin/cloud-init issues but aren't collected 
automatically by MAAS:

  - /var/log/cloud-init*
  - /run/cloud-init*
  - /var/log/cloud
  - /tmp/install.log

  We need these to be automatically collected by MAAS so we can
  automatically collect them as artifacts in the case of failures in
  OIL.  curtin/cloud-init issues can be race conditions that are
  difficult to reproduce manually, so we need to grab the logs required
  to debug the first time it happens.

  === Begin SRU Template ===
  [Impact]
  ubuntu-bug cloud-init now collects cloud-init-related information for a 
bug-report

  [Test Case]

  # Launch instance under test
  $ for release in xenial zesty;
    do
  ref=$release-proposed;
  lxc-proposed-snapshot --proposed --publish $release $ref;
  lxc launch $ref $name;
  sleep 10;
  lxc exec $name ubuntu-bug cloud-init  # And follow the prompts to report 
a bogus bug
    done

  [Regression Potential]
  Worst case scenario is the apport wrapper doesn't work and the developer has 
to file a bug manually instead.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=ca2730e2ac86b05f7e6

  === End SRU Template ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1607345/+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 1844379] Re: xenial/linux-aws-hwe: 4.15.0-1051.53~16.04.1 -proposed tracker

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844380
  packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 08:11 UTC
+ phase: Testing
+ phase-changed: Thursday, 19. September 2019 10:41 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842572
  variant: debs

-- 
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/1844379

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws-hwe package in Ubuntu:
  Invalid
Status in linux-aws-hwe source package in Xenial:
  Confirmed

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844380
  packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
  phase: Testing
  phase-changed: Thursday, 19. September 2019 10:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842572
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844379/+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 1844407] Re: xenial/linux-kvm: 4.4.0-1059.66 -proposed tracker

2019-09-19 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844416
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Promote to Proposed
- phase-changed: Thursday, 19. September 2019 08:35 UTC
+ phase: Testing
+ phase-changed: Thursday, 19. September 2019 10:46 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  replaces: bug 1842598
  variant: debs

-- 
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/1844407

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844416
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Thursday, 19. September 2019 10:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1842598
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844407/+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 1827346] Re: Power: Fail to set delay time when the value is 90 minutes

2019-09-19 Thread Launchpad Bug Tracker 
This bug was fixed in the package gnome-control-center -
1:3.28.2-0ubuntu0.18.04.5

---
gnome-control-center (1:3.28.2-0ubuntu0.18.04.5) bionic; urgency=medium

  * debian/patches/git_monitor_configuration.patch:
- display: backport fix for the apply button not being displayed in
  some cases (lp: #1823857)
  * debian/patches/git_suspend_value.patch:
- really suspend after 90 minutes when that value is selected
  (lp: #1827346)

 -- Sebastien Bacher   Wed, 29 May 2019 16:37:03
+0200

** Changed in: gnome-control-center (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/1827346

Title:
  Power: Fail to set delay time when the value is 90 minutes

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project bionic series:
  Fix Committed
Status in OEM Priority Project xenial series:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Xenial:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Released
Status in gnome-control-center source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Fail to set delay time when the value is 90 minutes.

  In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not
  5400 (90*60). When setting the delay time to 90 minutes, the UI will
  show "80 minutes" after reopening "All Settings". (Please refer to the
  photo in #1 and #2)

  [Test Case]

  1) Go to [All Settings][Power][Automatic suspend]

  2) Set delay time to 90 minutes (On Battery Power or Plugged in)

  3) Close [All Settings]

  4) Reopen [All Settings][Power][Automatic suspend]

  5) Check if the value is 90 minutes.

  [Regression Potential]

  Low. The value of 90 minutes is wrong. Just correct the value to 5400.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1827346/+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