[Group.of.nepali.translators] [Bug 1733276] Re: Cannot resize partitions on NVME devices due to bad device name parsing

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package partman-partitioning - 110ubuntu4.2

---
partman-partitioning (110ubuntu4.2) xenial; urgency=medium

  * Make get_real_device() both simpler and more generic.
(LP: #1733276) (Closes: #820818).

 -- Eric Desrochers   Mon, 05 Feb 2018
12:04:22 -0500

** Changed in: partman-partitioning (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: partman-partitioning (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/1733276

Title:
  Cannot resize partitions on NVME devices due to bad device name
  parsing

Status in partman-partitioning:
  Fix Released
Status in partman-partitioning package in Ubuntu:
  Fix Released
Status in partman-partitioning source package in Trusty:
  Fix Released
Status in partman-partitioning source package in Xenial:
  Fix Released
Status in partman-partitioning source package in Zesty:
  Won't Fix
Status in partman-partitioning source package in Artful:
  Fix Released
Status in partman-partitioning source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  It is not possible to resize NVME partitions in the Ubiquity installer.
  NVME devices have an unusual device format, specifically e.g. /dev/nvme0n1p1 
that has two 'sections' that potentially look like partitions.

  Based on the error message, it seems that this device name is being
  parsed incorrectly and it attempts to use the device path /dev/nvme0n1
  instead of /dev/nvme0n1p1

  ** See attachment (screenshot) took in action, illustrating the problem:
  - resize.png
  - resize_impossible.png
  - console_log.png

  [Test Case]

  To test component(s) in -proposed
  
  https://wiki.ubuntu.com/Testing/EnableProposed
  [Section: Installation testing using -proposed]

  In order to install successfully from these images, you will normally
  need to tell the installer to fetch its own components from -proposed
  as well, which is not the default. To do this, add the following boot
  parameter:

  apt-setup/proposed=true
  

  You can test this using qemu and a virtual NVME device. If you toggle
  the same device/partition between a virtual SCSI/IDE and an NVME
  device - the issue appears and disappears.

  Commands you can use to replicate the issue - unpack netboot.tar.gz
  into the local directory and then

  dd if=/dev/zero of=nvme.disk bs=1M count=16384

  NVME:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device 
nvme,drive=drv0,serial=foo -enable-kvm -smp 2 -m 1024 -kernel 
xenial/ubuntu-installer/amd64/linux -initrd 
xenial/ubuntu-installer/amd64/initrd.gz

  SCSI:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drv0,id=virtio-disk0,bootindex=1
 -enable-kvm -smp 2 -m 1024 -kernel ubuntu-installer/amd64/linux -initrd 
ubuntu-installer/amd64/initrd.gz

  ** See attachment (screenshot) took in action, illustrating how the installer 
should react with the fix :
  xenial_with_fix1.png
  xenial_with_fix2.png
  xenial_with_fix3.png
  xenial_console_with_fix.png

  [Regression Potential]

   * Low risk of regression, with this patch, partman, will be more robust and 
align with what disk_name() in the kernel does 
(linux.git/tree/block/partition-generic.c). It is sufficient to check
  whether the last character is a digit.

  * The patch may also fixes (or at least prevent for the future) other
  potential similar devices issue and not only explicitly fixing and/or
  benefit NVMe device types.

  [Other Info]

  * Debian upstream bug :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820818

  * Debian upstream fix :
  
https://anonscm.debian.org/cgit/d-i/partman-partitioning.git/commit/?id=01087125e07a7b22da589e8116f9ef7a26275006

  * Commit [01087125]
  Make get_real_device() both simpler and more generic (See: #820818).
  Looking at the implementation of the disk_name() function in the kernel
  (linux.git/tree/block/partition-generic.c), it is sufficient to check
  whether the last character is a digit.

  * $ git describe --contains 01087125e07a7b22da589e8116f9ef7a26275006
  116~2

  * $ rmadison partman-partitioning
   partman-partitioning | 85ubuntu2| precise/main/debian-installer
   partman-partitioning | 99ubuntu1| trusty/main/debian-installer
   partman-partitioning | 110ubuntu4.1 | xenial-updates/main/debian-installer
   partman-partitioning | 114ubuntu2   | zesty/main/debian-installer
   partman-partitioning | 114ubuntu2   | artful/main/debian-installer
   partman-partitioning | 120ubuntu1   | bionic/main/debian-installer

  [Original Description]

  It is not possible to resize NVME partitions in the Ubiquity
  installer.  This appears to 

[Group.of.nepali.translators] [Bug 1733276] Re: Cannot resize partitions on NVME devices due to bad device name parsing

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package partman-partitioning - 99ubuntu2

---
partman-partitioning (99ubuntu2) trusty; urgency=medium

  * Make get_real_device() both simpler and more generic.
(LP: #1733276) (Closes: #820818).

 -- Eric Desrochers   Tue, 06 Feb 2018
12:08:28 -0500

** Changed in: partman-partitioning (Ubuntu Artful)
   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/1733276

Title:
  Cannot resize partitions on NVME devices due to bad device name
  parsing

Status in partman-partitioning:
  Fix Released
Status in partman-partitioning package in Ubuntu:
  Fix Released
Status in partman-partitioning source package in Trusty:
  Fix Released
Status in partman-partitioning source package in Xenial:
  Fix Released
Status in partman-partitioning source package in Zesty:
  Won't Fix
Status in partman-partitioning source package in Artful:
  Fix Released
Status in partman-partitioning source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  It is not possible to resize NVME partitions in the Ubiquity installer.
  NVME devices have an unusual device format, specifically e.g. /dev/nvme0n1p1 
that has two 'sections' that potentially look like partitions.

  Based on the error message, it seems that this device name is being
  parsed incorrectly and it attempts to use the device path /dev/nvme0n1
  instead of /dev/nvme0n1p1

  ** See attachment (screenshot) took in action, illustrating the problem:
  - resize.png
  - resize_impossible.png
  - console_log.png

  [Test Case]

  To test component(s) in -proposed
  
  https://wiki.ubuntu.com/Testing/EnableProposed
  [Section: Installation testing using -proposed]

  In order to install successfully from these images, you will normally
  need to tell the installer to fetch its own components from -proposed
  as well, which is not the default. To do this, add the following boot
  parameter:

  apt-setup/proposed=true
  

  You can test this using qemu and a virtual NVME device. If you toggle
  the same device/partition between a virtual SCSI/IDE and an NVME
  device - the issue appears and disappears.

  Commands you can use to replicate the issue - unpack netboot.tar.gz
  into the local directory and then

  dd if=/dev/zero of=nvme.disk bs=1M count=16384

  NVME:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device 
nvme,drive=drv0,serial=foo -enable-kvm -smp 2 -m 1024 -kernel 
xenial/ubuntu-installer/amd64/linux -initrd 
xenial/ubuntu-installer/amd64/initrd.gz

  SCSI:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drv0,id=virtio-disk0,bootindex=1
 -enable-kvm -smp 2 -m 1024 -kernel ubuntu-installer/amd64/linux -initrd 
ubuntu-installer/amd64/initrd.gz

  ** See attachment (screenshot) took in action, illustrating how the installer 
should react with the fix :
  xenial_with_fix1.png
  xenial_with_fix2.png
  xenial_with_fix3.png
  xenial_console_with_fix.png

  [Regression Potential]

   * Low risk of regression, with this patch, partman, will be more robust and 
align with what disk_name() in the kernel does 
(linux.git/tree/block/partition-generic.c). It is sufficient to check
  whether the last character is a digit.

  * The patch may also fixes (or at least prevent for the future) other
  potential similar devices issue and not only explicitly fixing and/or
  benefit NVMe device types.

  [Other Info]

  * Debian upstream bug :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820818

  * Debian upstream fix :
  
https://anonscm.debian.org/cgit/d-i/partman-partitioning.git/commit/?id=01087125e07a7b22da589e8116f9ef7a26275006

  * Commit [01087125]
  Make get_real_device() both simpler and more generic (See: #820818).
  Looking at the implementation of the disk_name() function in the kernel
  (linux.git/tree/block/partition-generic.c), it is sufficient to check
  whether the last character is a digit.

  * $ git describe --contains 01087125e07a7b22da589e8116f9ef7a26275006
  116~2

  * $ rmadison partman-partitioning
   partman-partitioning | 85ubuntu2| precise/main/debian-installer
   partman-partitioning | 99ubuntu1| trusty/main/debian-installer
   partman-partitioning | 110ubuntu4.1 | xenial-updates/main/debian-installer
   partman-partitioning | 114ubuntu2   | zesty/main/debian-installer
   partman-partitioning | 114ubuntu2   | artful/main/debian-installer
   partman-partitioning | 120ubuntu1   | bionic/main/debian-installer

  [Original Description]

  It is not possible to resize NVME partitions in the Ubiquity
  installer.  This appears to affect multiple filesystem types including
  NTFS and ext4.

  NVME devices have an unusual device format, 

[Group.of.nepali.translators] [Bug 1727699] Re: SSL issue upgrading postfix

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package postfix - 3.1.0-3ubuntu0.3

---
postfix (3.1.0-3ubuntu0.3) xenial; urgency=medium

  * Only run post 3.0 master.cf fixup if upgrading from version before
the fix. (LP: #1727699)
This is a pick of 37b37e93 from Debian packaging repo at
https://git.launchpad.net/postfix

 -- Christian Ehrhardt   Tue, 02 Jan
2018 13:48:25 +0100

** Changed in: postfix (Ubuntu Xenial)
   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/1727699

Title:
  SSL issue upgrading postfix

Status in postfix package in Ubuntu:
  Fix Released
Status in postfix source package in Xenial:
  Fix Released
Status in postfix package in Debian:
  Fix Released

Bug description:
  [Impact]

   * On upgrade depending on config postfix might mess with said config as 
 it mis-detects being an upgrade from postfix-2.

   * This was fixes in Debian later on, this cherry picks the fix

  [Test Case]

   * have a config with
  submission inet  n   -   -   -   -   smtpd
 And then upgrade (reinstall), example:
 - apt install postfix
 - change the line to the above in /etc/postfix/master.cf
   (that was essentially removing a comment and y -> -)
 - apt install --reinstall postfix
 This will have changed the config:
   - on upgrade you see
 setting explicit chroot on /etc/postfix:submission/inet/chroot
   - the value now is
 submission inet  n   -   y   -   -   smtpd

  
  [Regression Potential] 

   * Upgrades behave slightly different, but in the way we want. We can 
 break down into two things:
 1. only if coming from the right former versions (wanted)
 2. if the upgrade is done it is done in a safer way (wanted)

  [Other Info]
   
   * In a perfect world the version compare would be against the first 
 ubuntu 3.x version, but taking the cherry pick as-is appears much 
 cleaner for review and also there was never anything released (nor 
 seems it remotely likely to be) that would fall in the gap between 
 the first Debian / Ubuntu postfix 3 version.


  

  issue upgrading posfix on Ubuntu 16.04.3 LTS

  in file master.cf, line submission=

  the upgrade procedure has changed the field chroot to 'y', but it was
  '-'. 'y' is wrong

  #pre upgrade it was
  submission inet  n   -   -   -   -   smtpd

  #then it become
  submission inet  n   -   y   -   -   smtpd

  the 'y' is wrong

  http://www.postfix.org/master.5.html

  sais "Chroot (default: Postfix >= 3.0: n, Postfix <3.0: y)"

  with 'y' the server rejects all SSL smtp mails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1727699/+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 1637984] Re: Disks shows all mounted snaps

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-disk-utility -
3.18.3.1-1ubuntu1.1

---
gnome-disk-utility (3.18.3.1-1ubuntu1.1) xenial; urgency=medium

  * debian/patches/hide-snaps.patch:
- Don't list snaps loop mount as disks/devices since that's confusing
  (lp: #1637984)

 -- Andrea Azzarone   Wed, 07 Feb 2018
16:01:32 +0100

** Changed in: gnome-disk-utility (Ubuntu Xenial)
   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/1637984

Title:
  Disks shows all mounted snaps

Status in GNOME Disks:
  Fix Released
Status in gnome-disk-utility package in Ubuntu:
  Fix Released
Status in udisks2 package in Ubuntu:
  Fix Committed
Status in gnome-disk-utility source package in Xenial:
  Fix Released
Status in udisks2 source package in Xenial:
  Won't Fix
Status in gnome-disk-utility source package in Artful:
  Fix Released
Status in udisks2 source package in Artful:
  Won't Fix
Status in gnome-disk-utility source package in Bionic:
  Fix Released
Status in udisks2 source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  In 16.04 and later any installed snaps show as loop devices in Disks.

  * Test Case
  - install a snap
  - open gnome-disks
  -> the snap shouldn't be listed on the left pane as a device

  * Regression potential
  Check that all your existing disks are still listed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1637984/+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 1745531] Re: [SRU] Reinforce hostname preseed regex

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package debian-installer -
20101020ubuntu318.43

---
debian-installer (20101020ubuntu318.43) trusty; urgency=medium

  * Include $efi_name in shim filename. (LP: #1743787)
  * Rebuild to pick up the latest change in preseed. (LP: #1745531)

 -- Eric Desrochers   Fri, 19 Jan 2018
09:20:25 -0500

** Changed in: preseed (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/1745531

Title:
  [SRU] Reinforce hostname preseed regex

Status in debian-installer package in Ubuntu:
  In Progress
Status in preseed package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Fix Released
Status in preseed source package in Trusty:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released
Status in preseed source package in Xenial:
  Fix Released
Status in debian-installer source package in Artful:
  Fix Released
Status in preseed source package in Artful:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in preseed source package in Bionic:
  Fix Released

Bug description:
  [Special notes]

  Rebuilding debian-installer will be necessary in order to get a new
  mini.iso (Minimal ISO image of Ubuntu) containing this particular fix.

  Despite the fact that a full ISO are no longer built for some of the
  affected stable releases, one can use what is called a minimal ISO
  image (mini.iso) of Ubuntu. This mini.iso uses a text-based installer,
  resulting in a smaller image. The minimal ISO image will download
  packages from online archives at installation time instead of
  providing them on the install media itself.

  [Impact]

  This is the same issue reported in 
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202
  However that is marked as 'Fix Released' and the issue is still occurring so 
it seems best to just open a new bug according to Eric's comment.

  The present hostname preseed regex looks like:

  if ! echo "$RET" | grep -q 'ubuntu'; then
     ...
     /bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
     ...
  fi

  There are still multiple problems with them according to Peter's
  comment
  (https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/comments/64)
  and Mathieu's comment
  (https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/comments/93).

  - The default hostname is 'ubuntu', and is the value you will get if
  nothing is preseeded -- we *do* need to skip it in this case, although
  the grep may need to be more precise. A name like 'ubuntuxenial'
  should match this grep.

  - The sed needs to be fixed to more appropriately catch for the exact
  string, rather than any substring -- ie. it should not match
  'ipv6-allnodes' if the name received from DHCP was 'node'. It should
  only match and replace for 'node'.

  So the fix will try to:

  1) Keep the if statement and add the -w option to grep to be more robust
  2) Modify the sed cmd with word boundaries (\b) to be more robust as well.

  [Test Case]

  Install Ubuntu using a preseed[1] file[2] and add the following line in the 
preseed recipe :
  d-i netcfg/hostname string 

  Change the HOSTNAME to see if the hostname in /etc/hosts can be
  updated correctly.

  [1] - url=http:///
  [2] - https://help.ubuntu.com/lts/installation-guide/example-preseed.txt

  [Regression Potential]

   * none expected, the actual changes are as follows:

  -if ! echo "$RET" | grep -q 'ubuntu'; then
  +if ! echo "$RET" | grep -qw 'ubuntu'; then
  ...
  - /bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
  + /bin/sed -i "s/\b${CURRENT_HOSTNAME}\b/${NETCFG_HOSTNAME}/g" 
/etc/hosts

  In other words, we simply make it more robust to select only pattern
  containing matches that form whole word... catching 'ubuntu' hostname
  as-is but not catching pattern where ubuntu is part of the user chosen
  hostname as follow :

  "sometextubuntu"
  "sometextubuntusometext"
  "ubuntusometext"
  ...

  [Original Description]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1745531/+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 1745531] Re: [SRU] Reinforce hostname preseed regex

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package preseed - 1.71ubuntu1.2

---
preseed (1.71ubuntu1.2) xenial; urgency=medium

  * Fix for netcfg/hostname, if set, to take precedence. (LP: #1745531)
- Modify debian/network-preseed.postinst to make it more robust

 -- Hua Zhang   Thu, 25 Jan 2018 15:16:39
+0800

** Changed in: debian-installer (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/1745531

Title:
  [SRU] Reinforce hostname preseed regex

Status in debian-installer package in Ubuntu:
  In Progress
Status in preseed package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Fix Released
Status in preseed source package in Trusty:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released
Status in preseed source package in Xenial:
  Fix Released
Status in debian-installer source package in Artful:
  Fix Released
Status in preseed source package in Artful:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in preseed source package in Bionic:
  Fix Released

Bug description:
  [Special notes]

  Rebuilding debian-installer will be necessary in order to get a new
  mini.iso (Minimal ISO image of Ubuntu) containing this particular fix.

  Despite the fact that a full ISO are no longer built for some of the
  affected stable releases, one can use what is called a minimal ISO
  image (mini.iso) of Ubuntu. This mini.iso uses a text-based installer,
  resulting in a smaller image. The minimal ISO image will download
  packages from online archives at installation time instead of
  providing them on the install media itself.

  [Impact]

  This is the same issue reported in 
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202
  However that is marked as 'Fix Released' and the issue is still occurring so 
it seems best to just open a new bug according to Eric's comment.

  The present hostname preseed regex looks like:

  if ! echo "$RET" | grep -q 'ubuntu'; then
     ...
     /bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
     ...
  fi

  There are still multiple problems with them according to Peter's
  comment
  (https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/comments/64)
  and Mathieu's comment
  (https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/comments/93).

  - The default hostname is 'ubuntu', and is the value you will get if
  nothing is preseeded -- we *do* need to skip it in this case, although
  the grep may need to be more precise. A name like 'ubuntuxenial'
  should match this grep.

  - The sed needs to be fixed to more appropriately catch for the exact
  string, rather than any substring -- ie. it should not match
  'ipv6-allnodes' if the name received from DHCP was 'node'. It should
  only match and replace for 'node'.

  So the fix will try to:

  1) Keep the if statement and add the -w option to grep to be more robust
  2) Modify the sed cmd with word boundaries (\b) to be more robust as well.

  [Test Case]

  Install Ubuntu using a preseed[1] file[2] and add the following line in the 
preseed recipe :
  d-i netcfg/hostname string 

  Change the HOSTNAME to see if the hostname in /etc/hosts can be
  updated correctly.

  [1] - url=http:///
  [2] - https://help.ubuntu.com/lts/installation-guide/example-preseed.txt

  [Regression Potential]

   * none expected, the actual changes are as follows:

  -if ! echo "$RET" | grep -q 'ubuntu'; then
  +if ! echo "$RET" | grep -qw 'ubuntu'; then
  ...
  - /bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
  + /bin/sed -i "s/\b${CURRENT_HOSTNAME}\b/${NETCFG_HOSTNAME}/g" 
/etc/hosts

  In other words, we simply make it more robust to select only pattern
  containing matches that form whole word... catching 'ubuntu' hostname
  as-is but not catching pattern where ubuntu is part of the user chosen
  hostname as follow :

  "sometextubuntu"
  "sometextubuntusometext"
  "ubuntusometext"
  ...

  [Original Description]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1745531/+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 1745531] Re: [SRU] Reinforce hostname preseed regex

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package debian-installer -
20101020ubuntu451.19

---
debian-installer (20101020ubuntu451.19) xenial; urgency=medium

  * No change rebuild to pick up the latest change in preseed (LP:
#1745531)

 -- Zhang Hua   Tue, 16 Jan 2018 21:58:04
+0800

** Changed in: debian-installer (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: preseed (Ubuntu Xenial)
   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/1745531

Title:
  [SRU] Reinforce hostname preseed regex

Status in debian-installer package in Ubuntu:
  In Progress
Status in preseed package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Fix Released
Status in preseed source package in Trusty:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released
Status in preseed source package in Xenial:
  Fix Released
Status in debian-installer source package in Artful:
  Fix Released
Status in preseed source package in Artful:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in preseed source package in Bionic:
  Fix Released

Bug description:
  [Special notes]

  Rebuilding debian-installer will be necessary in order to get a new
  mini.iso (Minimal ISO image of Ubuntu) containing this particular fix.

  Despite the fact that a full ISO are no longer built for some of the
  affected stable releases, one can use what is called a minimal ISO
  image (mini.iso) of Ubuntu. This mini.iso uses a text-based installer,
  resulting in a smaller image. The minimal ISO image will download
  packages from online archives at installation time instead of
  providing them on the install media itself.

  [Impact]

  This is the same issue reported in 
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202
  However that is marked as 'Fix Released' and the issue is still occurring so 
it seems best to just open a new bug according to Eric's comment.

  The present hostname preseed regex looks like:

  if ! echo "$RET" | grep -q 'ubuntu'; then
     ...
     /bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
     ...
  fi

  There are still multiple problems with them according to Peter's
  comment
  (https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/comments/64)
  and Mathieu's comment
  (https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/comments/93).

  - The default hostname is 'ubuntu', and is the value you will get if
  nothing is preseeded -- we *do* need to skip it in this case, although
  the grep may need to be more precise. A name like 'ubuntuxenial'
  should match this grep.

  - The sed needs to be fixed to more appropriately catch for the exact
  string, rather than any substring -- ie. it should not match
  'ipv6-allnodes' if the name received from DHCP was 'node'. It should
  only match and replace for 'node'.

  So the fix will try to:

  1) Keep the if statement and add the -w option to grep to be more robust
  2) Modify the sed cmd with word boundaries (\b) to be more robust as well.

  [Test Case]

  Install Ubuntu using a preseed[1] file[2] and add the following line in the 
preseed recipe :
  d-i netcfg/hostname string 

  Change the HOSTNAME to see if the hostname in /etc/hosts can be
  updated correctly.

  [1] - url=http:///
  [2] - https://help.ubuntu.com/lts/installation-guide/example-preseed.txt

  [Regression Potential]

   * none expected, the actual changes are as follows:

  -if ! echo "$RET" | grep -q 'ubuntu'; then
  +if ! echo "$RET" | grep -qw 'ubuntu'; then
  ...
  - /bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
  + /bin/sed -i "s/\b${CURRENT_HOSTNAME}\b/${NETCFG_HOSTNAME}/g" 
/etc/hosts

  In other words, we simply make it more robust to select only pattern
  containing matches that form whole word... catching 'ubuntu' hostname
  as-is but not catching pattern where ubuntu is part of the user chosen
  hostname as follow :

  "sometextubuntu"
  "sometextubuntusometext"
  "ubuntusometext"
  ...

  [Original Description]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1745531/+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 1637984] Re: Disks shows all mounted snaps

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-disk-utility - 3.26.1-0ubuntu1.1

---
gnome-disk-utility (3.26.1-0ubuntu1.1) artful; urgency=medium

  * debian/patches/hide-snaps.patch:
- Don't list snaps loop mount as disks/devices since that's confusing
  (lp: #1637984)

 -- Andrea Azzarone   Wed, 07 Feb 2018
15:39:32 +0100

** Changed in: gnome-disk-utility (Ubuntu Artful)
   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/1637984

Title:
  Disks shows all mounted snaps

Status in GNOME Disks:
  Fix Released
Status in gnome-disk-utility package in Ubuntu:
  Fix Released
Status in udisks2 package in Ubuntu:
  Fix Committed
Status in gnome-disk-utility source package in Xenial:
  Fix Released
Status in udisks2 source package in Xenial:
  Won't Fix
Status in gnome-disk-utility source package in Artful:
  Fix Released
Status in udisks2 source package in Artful:
  Won't Fix
Status in gnome-disk-utility source package in Bionic:
  Fix Released
Status in udisks2 source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  In 16.04 and later any installed snaps show as loop devices in Disks.

  * Test Case
  - install a snap
  - open gnome-disks
  -> the snap shouldn't be listed on the left pane as a device

  * Regression potential
  Check that all your existing disks are still listed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1637984/+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 1670408] Re: apparmor base abstraction needs backport of rev 3658 to fix several denies (tor, ntp, ...)

2018-02-14 Thread ChristianEhrhardt
** Changed in: apparmor (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: tor (Ubuntu)
   Status: Invalid => 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/1670408

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+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 1743156] Re: [regression] 4.4.0-110 doesn't load AMD microcode

2018-02-14 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  [regression] 4.4.0-110 doesn't load AMD microcode

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  When booting my AMD system with 4.4.0-109.132, the microcode is
  updated:

  root@ocelot:~# journalctl -k | grep microcode
  Jan 13 15:26:36 ocelot kernel: microcode: CPU0: patch_level=0x0500010d
  Jan 13 15:26:36 ocelot kernel: microcode: CPU1: patch_level=0x0500010d
  Jan 13 15:26:36 ocelot kernel: microcode: Microcode Update Driver: v2.01 
, Peter Oruba
  Jan 13 15:26:36 ocelot kernel: microcode: CPU0: new patch_level=0x05000119
  Jan 13 15:26:36 ocelot kernel: microcode: CPU1: new patch_level=0x05000119

  However, with 4.4.0-110.133, no microcode is loaded:

  root@ocelot:~# journalctl -k | grep microcode
  # nothing

  Extra information on the system:

  root@ocelot:~# sed -n '1,/^$/ p' /proc/cpuinfo 
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 20
  model : 2
  model name: AMD C-60 APU with Radeon(tm) HD Graphics
  stepping  : 0
  microcode : 0x5000119
  cpu MHz   : 800.000
  cache size: 512 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 6
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni 
monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch ibs skinit wdt cpb hw_pstate kaiser vmmcall arat npt 
lbrv svm_lock nrip_save pausefilter
  bugs  : fxsave_leak sysret_ss_attrs
  bogomips  : 1999.97
  TLB size  : 1024 4K pages
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management: ts ttp tm stc 100mhzsteps hwpstate cpb

  root@ocelot:~# lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  root@ocelot:~# apt-cache policy amd64-microcode
  amd64-microcode:
Installed: 2.20160316.1
Candidate: 2.20160316.1
Version table:
   *** 2.20160316.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-110-generic 4.4.0-110.133
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 13 15:26 seq
   crw-rw 1 root audio 116, 33 Jan 13 15:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sat Jan 13 15:30:51 2018
  HibernationDevice: RESUME=UUID=cfe87834-be9d-4a32-93d1-3f2b655e58af
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  PciMultimedia:
   
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=9696399d-3bed-4126-b203-7672f2ea0576 ro hugepages=3072 kaslr 
nmi_watchdog=0 possible_cpus=2 pti=on transparent_hugepage=never vsyscall=none
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0502
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: C60M1-I
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Group.of.nepali.translators] [Bug 1728742] Re: curtin dname for bcache uses unstable devname instead of UUID

2018-02-14 Thread Ryan Harper
** Bug watch added: Debian Bug tracker #890446
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890446

** Also affects: bcache-tools (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890446
   Importance: Unknown
   Status: Unknown

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

Title:
  curtin dname for bcache uses unstable devname instead of UUID

Status in bcache-tools:
  New
Status in curtin:
  New
Status in bcache-tools package in Ubuntu:
  In Progress
Status in bcache-tools source package in Trusty:
  Confirmed
Status in bcache-tools source package in Xenial:
  Confirmed
Status in bcache-tools source package in Artful:
  Confirmed
Status in bcache-tools source package in Bionic:
  In Progress
Status in bcache-tools package in Debian:
  Unknown

Bug description:
  Bcache device names like /dev/bcache0 are unstable.  Bcache does not
  use any predictable ordering when assembling bcache devices, so on
  systems with multiple bcache devices, a symlink to /dev/bcache0 may
  end up pointing do a different device.

  the bcache dname symlink should point to the /dev/bcache/by-
  uuid/ which matches the backing device UUID that's set at
  creation time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bcache-tools/+bug/1728742/+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 1746114] Re: Move xenial to fwupd 0.8.x branch

2018-02-14 Thread Mario Limonciello
@kabirdkng, the fwupd_0.8.3-0ubuntu2 has not yet been accepted into
xenial.  It's awaiting an archive administrator to perform this action.

** Changed in: fwupd (Ubuntu Xenial)
   Status: Opinion => In Progress

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

Title:
  Move xenial to fwupd 0.8.x branch

Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd source package in Xenial:
  In Progress

Bug description:
  [Impact]
   * Upstream has declared that 0.7.x is EOL
     - No further security updates will be performed for it.
   * Many crashers were fixed in 0.8.x.
   * Upstream can better maintain fwupd ecosystem wide if Ubuntu (the last ones 
using 0.7.x release) move to 0.8.x or newer.
   * Latest upstream release is 1.0.4 release, but moving to 0.9.x or 1.0.x is 
difficult due to many dependencies not present in Ubuntu 16.04.
   * Upstream spun this point release specifically for getting Ubuntu xenial on 
a newer maintainable version.
  https://groups.google.com/forum/#!topic/fwupd/R6UyaCtWbqo

  New Features:
   - Add --version option to fwupdmgr (Richard Hughes)

  Bugfixes:
   - Add a delay when calling update_prepare (Mario Limonciello)
   - Block owned Dell TPM updates (#339) (Mario Limonciello)
   - Catch invalid Dell dock component requests (Mario Limonciello)
   - Disable the dell plugin if libsmbios fails (Mario Limonciello)
   - Do not re-download firmware that exists in the cache (Richard Hughes)
   - Ensure the 8bitdo version is set in non-bootloader mode (Richard Hughes)
   - Fix a logic error with testing for a dell system (Mario Limonciello)
   - Fix compile with newer versions of GUdev (Richard Hughes)
   - Fix crash with dock connected but UEFI capsule off (Mario Limonciello)
   - Use new VID for 8bitdo (Richard Hughes)

  [Test Case]
   * Use fwupdmgr to check for and apply a firmware update
   * Use gnome-software to check for and apply a firmware update

  [Regression Potential]
   * This is a point release of the 0.8.x release which has been deemed stable.
   * Potential regressions would more likely exist in gnome-software which uses 
fwupd's interfaces to perform firmware updates.
   * If a regression were to occur, gnome-software may crash or not display a 
firmware update anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1746114/+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 1746114] Re: Move xenial to fwupd 0.8.x branch

2018-02-14 Thread kabir hossain
not working .. theres showing unable to download firmware update from
"fwupd"

** Changed in: fwupd (Ubuntu Xenial)
   Status: Fix Committed => Opinion

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

Title:
  Move xenial to fwupd 0.8.x branch

Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd source package in Xenial:
  Opinion

Bug description:
  [Impact]
   * Upstream has declared that 0.7.x is EOL
     - No further security updates will be performed for it.
   * Many crashers were fixed in 0.8.x.
   * Upstream can better maintain fwupd ecosystem wide if Ubuntu (the last ones 
using 0.7.x release) move to 0.8.x or newer.
   * Latest upstream release is 1.0.4 release, but moving to 0.9.x or 1.0.x is 
difficult due to many dependencies not present in Ubuntu 16.04.
   * Upstream spun this point release specifically for getting Ubuntu xenial on 
a newer maintainable version.
  https://groups.google.com/forum/#!topic/fwupd/R6UyaCtWbqo

  New Features:
   - Add --version option to fwupdmgr (Richard Hughes)

  Bugfixes:
   - Add a delay when calling update_prepare (Mario Limonciello)
   - Block owned Dell TPM updates (#339) (Mario Limonciello)
   - Catch invalid Dell dock component requests (Mario Limonciello)
   - Disable the dell plugin if libsmbios fails (Mario Limonciello)
   - Do not re-download firmware that exists in the cache (Richard Hughes)
   - Ensure the 8bitdo version is set in non-bootloader mode (Richard Hughes)
   - Fix a logic error with testing for a dell system (Mario Limonciello)
   - Fix compile with newer versions of GUdev (Richard Hughes)
   - Fix crash with dock connected but UEFI capsule off (Mario Limonciello)
   - Use new VID for 8bitdo (Richard Hughes)

  [Test Case]
   * Use fwupdmgr to check for and apply a firmware update
   * Use gnome-software to check for and apply a firmware update

  [Regression Potential]
   * This is a point release of the 0.8.x release which has been deemed stable.
   * Potential regressions would more likely exist in gnome-software which uses 
fwupd's interfaces to perform firmware updates.
   * If a regression were to occur, gnome-software may crash or not display a 
firmware update anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1746114/+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 1749143] Re: BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad address

2018-02-14 Thread Joseph Salisbury
I'll mark this bug as "Fix Released" since the linux-
image-4.4.0-116-generic kernel solves it.  If the bug re-appears, change
the status back to "Confirmed".

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Hello,

  We test the -proposed packages before our ±25000 user servers get a
  chance to download it when it's in stable and we have an issue since
  the package linux-image-4.4.0-113-generic and linux-
  image-4.4.0-115-generic.

  We tried on KVM virtual machines

  To reproduce the problem, execute:

  # fping -t50 -r2 127.0.0.1
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1 is unreachable

  We have no problem with ping:

  # ping -c 1 127.0.0.1
  PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
  64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.046 ms
  
  --- 127.0.0.1 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.046/0.046/0.046/0.000 ms

  fping is working fine under kernel 4.4.0-112:

  # fping -t50 -r2 127.0.0.1
  127.0.0.1 is alive

  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 févr. 13 16:40 seq
   crw-rw 1 root audio 116, 33 févr. 13 16:40 timer
  AplayDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/eolebase--vg-swap_1
  IwConfig: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-115-generic 
root=/dev/mapper/hostname--vg-root ro rootdelay=90
  ProcVersionSignature: Ubuntu 4.4.0-115.139-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-115-generic N/A
   linux-backports-modules-4.4.0-115-generic  N/A
   linux-firmware 1.157.16
  RfKill: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Tags:  xenial
  Uname: Linux 4.4.0-115-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+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 1747890] Re: Update the source code location in the debian package for cloud kernels

2018-02-14 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux-aws (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-gke (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-azure (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-gcp (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-kvm (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-azure-edge (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/1747890

Title:
  Update the source code location in the debian package for cloud
  kernels

Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure-edge source package in Xenial:
  New
Status in linux-gcp source package in Xenial:
  New
Status in linux-gke source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-azure-edge source package in Bionic:
  New
Status in linux-gcp source package in Bionic:
  New
Status in linux-gke source package in Bionic:
  New
Status in linux-kvm source package in Bionic:
  New

Bug description:
  Currently we have a single git repository for each cloud kernel, which
  is used for xenial. With bionic, we will need to split those repos by
  series.

  For instance, linux-azure repository will move from:

  git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/

  To:

  
git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/xenial
  
git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/bionic

  Gcs-Git tag in the debian/control file needs to be updated
  accordingly.

  The same is valid for meta packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1747890/+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 1749094] Re: linux-raspi2: 4.4.0-1085.93 -proposed tracker

2018-02-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   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/1749094

Title:
  linux-raspi2: 4.4.0-1085.93 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-02-14 Thread Chris Wayne
+1 to promote, results here: https://trello.com/c/Y9LW1c2P/199-pc-
kernel-440-116140-104

** Changed in: kernel-sru-workflow/snap-certification-testing
   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/1749089

Title:
  linux: 4.4.0-116.140 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa 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:
  Confirmed

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

  backports: bug 1749090 (linux-aws), bug 1749091 (linux-lts-xenial)
  derivatives: bug 1749092 (linux-kvm), bug 1749093 (linux-aws), bug 1749094 
(linux-raspi2), bug 1749095 (linux-euclid), bug 1749096 (linux-snapdragon), bug 
1749097 (linux-gke)
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-02-14 Thread Chris Wayne
+1 for promotion, results here: https://trello.com/c/ZljPY3vV/197
-dragonboard-kernel-440-108792-43

** Changed in: kernel-sru-workflow/snap-certification-testing
   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/1749096

Title:
  linux-snapdragon: 4.4.0-1087.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
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 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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749096/+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 1749094] Re: linux-raspi2: 4.4.0-1085.93 -proposed tracker

2018-02-14 Thread Chris Wayne
+1 to promote snap, results here:
https://trello.com/c/3GbGyg3T/198-pi2-kernel-440-108593-50

** Changed in: kernel-sru-workflow/snap-certification-testing
   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/1749094

Title:
  linux-raspi2: 4.4.0-1085.93 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749094/+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 1728742] Re: curtin dname for bcache uses unstable devname instead of UUID

2018-02-14 Thread Scott Moser
** Also affects: bcache-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: bcache-tools (Ubuntu)
   Status: New => Confirmed

** Changed in: bcache-tools (Ubuntu)
   Importance: Undecided => Medium

** Changed in: bcache-tools (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: bcache-tools (Ubuntu)
 Assignee: (unassigned) => Ryan Harper (raharper)

** Also affects: bcache-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: bcache-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: bcache-tools (Ubuntu Bionic)
   Importance: Medium
 Assignee: Ryan Harper (raharper)
   Status: In Progress

** Also affects: bcache-tools (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: bcache-tools (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: bcache-tools (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: bcache-tools (Ubuntu Artful)
   Status: New => Confirmed

** Changed in: bcache-tools (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: bcache-tools (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: bcache-tools (Ubuntu Artful)
   Importance: Undecided => Medium

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

Title:
  curtin dname for bcache uses unstable devname instead of UUID

Status in bcache-tools:
  New
Status in curtin:
  New
Status in bcache-tools package in Ubuntu:
  In Progress
Status in bcache-tools source package in Trusty:
  Confirmed
Status in bcache-tools source package in Xenial:
  Confirmed
Status in bcache-tools source package in Artful:
  Confirmed
Status in bcache-tools source package in Bionic:
  In Progress

Bug description:
  Bcache device names like /dev/bcache0 are unstable.  Bcache does not
  use any predictable ordering when assembling bcache devices, so on
  systems with multiple bcache devices, a symlink to /dev/bcache0 may
  end up pointing do a different device.

  the bcache dname symlink should point to the /dev/bcache/by-
  uuid/ which matches the backing device UUID that's set at
  creation time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bcache-tools/+bug/1728742/+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 1749283] Re: configured stats_temp_directory does not get created after reboot

2018-02-14 Thread Mario Splivalo
** Bug watch added: Debian Bug tracker #890427
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890427

** Also affects: postgresql-common (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890427
   Importance: Unknown
   Status: Unknown

** Tags added: sts-sponsor

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

Title:
  configured stats_temp_directory does not get created after reboot

Status in postgresql-common package in Ubuntu:
  In Progress
Status in postgresql-common source package in Xenial:
  In Progress
Status in postgresql-common source package in Artful:
  In Progress
Status in postgresql-common source package in Bionic:
  In Progress
Status in postgresql-common package in Debian:
  Unknown

Bug description:
  Default postgres installation in Ubuntu (and Debian) configures
  stats_temp_directory inside /var/run/postgresql:

  $ grep stats_temp /etc/postgresql/10/main/postgresql.conf 
  stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp'

  However, this directory is not created after reboot.

  In most cases this is not a problem as systemd starts postgres via
  pg_ctlcluster, a "multiversion/cluster aware pg_ctl wrapper", and
  pg_ctlcluster will create missing directories before starting
  postgres.

  But in cases where systemd is not starting postgres this is a problem.
  Specifically, when postgres is controlled by pacemaker (using postgres 
resource agent for pacemaker) it is started using pg_ctl wrapper. pg_ctl won't 
create missing directories and therefore postgres fails to start.

  The simplest solution for this issue is to have systemd recreate
  missing directories via /usr/lib/tmpfiles.d/postgresql.conf file.

  Currently only /var/run/postgresql and /var/log/postgresql are created
  using systemd-tmpfiles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1749283/+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 1749332] Re: [Hyper-V] Fixes for Network Direct InfiniBand/RDMA driver

2018-02-14 Thread Kleber Sacilotto de Souza
** Also affects: linux-azure (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/1749332

Title:
  [Hyper-V] Fixes for Network Direct InfiniBand/RDMA driver

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Xenial:
  New

Bug description:
  This LP encapsulates three fixes for the IB/RDMA drivers for Network
  Direct in Azure. Patches are attached for ND142 and ND144 hosts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1749332/+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 1741227] Re: apparmor denial to several paths to binaries

2018-02-14 Thread ChristianEhrhardt
Bionic - ok
SRU Template - ok
Debdiff for X/T checked - ok
Tested A upload from ppa - ok.
(This issue in particular doesn't apply to Xenial, so dropping this task)

** No longer affects: ntp (Ubuntu Xenial)

** Changed in: ntp (Ubuntu Artful)
   Status: Triaged => In Progress

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1743300] Re: libguestfs not work anymore with 4.13.0-26-generic #29~16.04.2-Ubuntu

2018-02-14 Thread Eric Desrochers
** Also affects: supermin (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: supermin (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: supermin (Ubuntu Xenial)
 Assignee: (unassigned) => Nivedita Singhvi (niveditasinghvi)

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

** Changed in: supermin (Ubuntu Xenial)
   Status: New => In Progress

** Tags removed: sts-sponsor
** Tags added: sts

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

Title:
  libguestfs not work anymore with 4.13.0-26-generic #29~16.04.2-Ubuntu

Status in supermin package in Ubuntu:
  Fix Released
Status in supermin source package in Xenial:
  In Progress

Bug description:
  (Updated Description/Summary)

  Summary
  ==
  * This is a bug in the supermin package v5.1.14 in Xenial.
  * This bug affects supermin versions < v5.1.18 when using a
    kernel that is v4.13-based or later.
  * This bug was caused by an update to the mainline v4.13 kernel
    which broke supermin due to the way supermin handled symlinks.

  Impact
  
  * The bug results in total loss of functionality in supermin
    and users of supermin such as guestfish, libguestfs-test-tool,
    others. i.e. it is a regression in functionality for managing
    virtual appliances.
  * This bug does not affect Bionic, Artful or Trusty (See Comment #14).

  Test Case & Reproduction
  ===
  * This bug manifests in different ways based on the caller / use case
    but is reliable and consistent in its reproduction.
    See original description and Comment #12, for trivial repro cases.

  Fix
  
  * The fix for the Xenial version includes a backport of 2 upstream
    fixes to the file ext2fs-c.c (the fix for the symlink breakage
    is contained in this file). See comment #13 for details.
  * A separate PPA test package for Xenial is available to test with
    (See comment #13).
  * This fix has been tested successfully on Xenial and shown to fix the
    reported and related breakages as listed in this bug (Comment #12).

  Regression Potential
  =
  * Regression Potential: there might be some bugs in some edge cases
    that have not been tested or some environment that is not typical
    causing some new issue which might affect the creation of the virtual
    appliances and their management/manipulation via tools in the
    libguestfs-tools package (e.g. guestfish).

  
  The attached debdiff is intended to create a rev of the current Xenial
  package version supermin_5.1.14-2ubuntu1 to supermin_5.1.14-2ubuntu1.1.

  

  Original Description
  =
  after upgrade to 4.13.0-26-generic #29~16.04.2-Ubuntu all the virt-* tools 
not work anymore

  running the libguestfs-test-tool shows that the qemu kernel crashes
  [0.755354] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [0.755354]
  [0.756619] CPU: 0 PID: 1 Comm: init Not tainted 4.13.0-26-generic 
#29~16.04.2-Ubuntu
  [0.757893] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [0.759157] Call Trace:
  [0.759444]  dump_stack+0x63/0x8b
  [0.760847]  panic+0xe4/0x23d
  [0.761184]  do_exit+0xae6/0xaf0
  [0.761547]  ? dput+0x34/0x1f0
  [0.762292]  do_group_exit+0x43/0xb0
  [0.762690]  SyS_exit_group+0x14/0x20
  [0.76]  entry_SYSCALL_64_fastpath+0x1e/0x81
  [0.764221] RIP: 0033:0x451579
  [0.764799] RSP: 002b:7ffda4fe3768 EFLAGS: 0246 ORIG_RAX: 
00e7
  [0.766275] RAX: ffda RBX: 01415cb3 RCX: 
00451579
  [0.767056] RDX: 0008 RSI: 0001 RDI: 
0001
  [0.768290] RBP: 01415c30 R08: 003c R09: 
00e7
  [0.769451] R10: ffd0 R11: 0246 R12: 

  [0.770651] R13: 0044b82fa09b5a53 R14:  R15: 
01415c30
  [0.772563] Kernel Offset: 0x3cc0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [0.774729] Rebooting in 1 seconds..
  libguestfs: error: appliance closed the connect

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Jan 15 07:03:40 2018
  InstallationDate: Installed on 2017-07-14 (184 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go 

[Group.of.nepali.translators] [Bug 1748662] Re: [Hyper-V] Drivers: hv: vmbus: Fix ring buffer signaling

2018-02-14 Thread Stefan Bader
** Also affects: linux-azure (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/1748662

Title:
  [Hyper-V] Drivers: hv: vmbus: Fix ring buffer signaling

Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Xenial:
  New

Bug description:
  Fix bugs in signaling the Hyper-V host when freeing space in the
  host->guest ring buffer:

  1. The interrupt_mask must not be used to determine whether to signal
 on the host->guest ring buffer
  2. The ring buffer write_index must be read (via hv_get_bytes_to_write)
 *after* pending_send_sz is read in order to avoid a race condition
  3. Comparisons with pending_send_sz must treat the "equals" case as
 not-enough-space
  4. Don't signal if the pending_send_sz feature is not present. Older
 versions of Hyper-V that don't implement this feature will poll.

  Fixes: 03bad714a161 ("vmbus: more host signalling avoidance")

  This patch is on its way upstream but has not yet been accepted into
  char-misc. It should apply to 4.4+ kernels that have taken
  03bad714a161

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1748662/+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 1670408] Re: Missing apparmor rules cause tor to fail to start

2018-02-14 Thread ChristianEhrhardt
Correctly added a bug task for ntp to also be affected.
Dropping Artful (EOL)

** Also affects: ntp (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: apparmor (Ubuntu Yakkety)

** Changed in: apparmor (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: ntp (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/1670408

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Invalid
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+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 1722313] Re: Enable auditing in util-linux.

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.30.1-0ubuntu4.1

---
util-linux (2.30.1-0ubuntu4.1) artful; urgency=medium

  * Add --with-audit to rules file and libaudit-dev to build depenedencies.
The hwclock needs audit defined in order to create audit records when
time is changed. (LP: #1722313)

 -- Joy Latten   Sun, 05 Nov 2017 18:14:49
-0600

** Changed in: util-linux (Ubuntu Artful)
   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/1722313

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Zesty:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.

  Only the hwclock and the login commands within util-linux package have
  source code for auditing. But that source code is disabled by default
  and requires the config option, --with-audit to enable it. The login
  command is not built nor shipped in util-linux. Ubuntu uses the login
  command from shadow instead. Thus, only hwclock command would be
  affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged to /var/log/audit/audit.log,
  if auditd daemon is running. Otherwise, if the auditd is not running,
  like most log messages, it will get logged to /var/log/kern.log and|or
  /var/log/syslog if these services are enabled.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+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 1722313] Re: Enable auditing in util-linux.

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.27.1-6ubuntu3.4

---
util-linux (2.27.1-6ubuntu3.4) xenial; urgency=medium

  * Add --with-audit to rules file and libaudit-dev to build depenedencies.
The hwclock needs audit defined in order to create audit records when
time is changed. (LP: #1722313)

 -- Joy Latten   Fri, 03 Nov 2017 17:46:07
-0500

** Changed in: util-linux (Ubuntu Xenial)
   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/1722313

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Zesty:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.

  Only the hwclock and the login commands within util-linux package have
  source code for auditing. But that source code is disabled by default
  and requires the config option, --with-audit to enable it. The login
  command is not built nor shipped in util-linux. Ubuntu uses the login
  command from shadow instead. Thus, only hwclock command would be
  affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged to /var/log/audit/audit.log,
  if auditd daemon is running. Otherwise, if the auditd is not running,
  like most log messages, it will get logged to /var/log/kern.log and|or
  /var/log/syslog if these services are enabled.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+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 1748807] Re: headset mic can't be detected on two Dell machines

2018-02-14 Thread Stefan Bader
** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

Title:
  headset mic can't be detected on two Dell machines

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
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:
  New
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  One machine is with the codec alc289, the other one is with the codec
  alc256.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1748807/+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 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware - 1.157.16

---
linux-firmware (1.157.16) xenial; urgency=medium

  * Connection issue in Bluetooth SPP mode between a Dell Edge Gateway 3000
and an HC-05 BT module attached to Arduino Uno (LP: #1738773)
- UBUNTU: linux-firmware: update firmware images for Redpine 9113 chipset

  * QCA6174 stops working on newer kernels after second group rekeying
(LP: #1743279)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00051-QCARMSWP-1

 -- Seth Forshee   Thu, 18 Jan 2018 07:29:44
-0600

** Changed in: linux-firmware (Ubuntu Xenial)
   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/1743279

Title:
  QCA6174 stops working on newer kernels after second group rekeying

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
  WiFi would stop working after every 20 minutes or so. The problem
  initially seems related to some DNS services crashing because of what
  happend in browsers and other software that usually rely on DNS but
  I've noticed I couldn't ping my router and other local devices for
  which I knew the IP addresses. The connection is still presented as
  being connected, but it just doesn't work.

  After googling a lot, I came across this question on askubuntu.com

  https://askubuntu.com/questions/967355/wifi-unstable-
  after-17-10-update

  Which led me to this bug report on Debian's bug tracker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184

  Which led me to this bug in upstream:

  http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html

  I've tested the proposed fixes myself and I can confirm they work.

  What causes the WiFi to stop working is a bug related to the group
  rekeying routines.

  It seems it only happens in >4.12 kernels, hence why I've only had
  problems after 4.13 was pushed as the current rolling HWE kernel for
  16.04.3.

  kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1
  of the firmware-6.bin file, which is the current one present in
  upstream.

  Updating the firmware-6.bin (and board-2.bin, optionally) to any
  version equal or later than that fixes the issue completely.

  -

  SRU Justification:
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in 
numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, 
silently stops working after the second group rekeying, which is usually few 
minutes after the user has connected to a WiFi network. The connection status 
remains unchanged but there's no connectivity at all. This effectively 
disconnects the user without notifying it of what's occurred.

  Additionally, this happens for the only HWE kernel that's been patched
  against the recent Meltdown vulnerability, leaving the user without
  the option of using a recent kernel and a secure kernel at the same
  time.

  [Test Case]
  After applying the required firmwares, check if the connectivity is 
unaffected after the second group rekeying, which can be checked with

  $ cat /var/log/syslog | grep wpa_.*rekeying

  [How to fix it]

  Update the firmware-6.bin file to version
  WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.

  [Regression Potential]
  The new firmware overwrites the old one, but since it's been in upstream 
since October 2017, it should be good.

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-firmware:
    Instalado: 1.157.14
    Candidato: 1.157.14
    Tabela de versão:
   *** 1.157.14 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+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 

[Group.of.nepali.translators] [Bug 1738773] Re: Connection issue in Bluetooth SPP mode between a Dell Edge Gateway 3000 and an HC-05 BT module attached to Arduino Uno

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware - 1.157.16

---
linux-firmware (1.157.16) xenial; urgency=medium

  * Connection issue in Bluetooth SPP mode between a Dell Edge Gateway 3000
and an HC-05 BT module attached to Arduino Uno (LP: #1738773)
- UBUNTU: linux-firmware: update firmware images for Redpine 9113 chipset

  * QCA6174 stops working on newer kernels after second group rekeying
(LP: #1743279)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00051-QCARMSWP-1

 -- Seth Forshee   Thu, 18 Jan 2018 07:29:44
-0600

** Changed in: linux-firmware (Ubuntu Xenial)
   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/1738773

Title:
  Connection issue in Bluetooth SPP mode between a Dell Edge Gateway
  3000 and an HC-05 BT module attached to Arduino Uno

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  SRU Justification

  Impact: Connection issue in Bluetooth SPP mode between a Dell Edge
  Gateway 3000 and an HC-05 BT module attached to Arduino Uno

  Fix: Updated firmware from Redpine containing a fix for the issue.

  Regression Potential: Below stress tests are conducted to ensure there is no 
regression with updated firmware
  BT mouse + BT keyboard
  BT mouse + BLE keyboard
  BT keyboard + BLE mouse
  BLE keyboard + BLE mouse
  BT mouse or keyboard + Wifi connected
  BT mouse + BT keyboard + WiFi connected
  BLE mouse + BLE keyboard + WiFi Connected
  BT mouse + BLE keyboard + Wifi connected
  BLE mouse + BT keyboard + Wifi connected
  (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + Wifi Scan
  (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + BT inquiry + 
BLE scan
  BT file transfer from mobile + WiFi connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738773/+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 1555904] Re: opal-prd not installed by default on ppc64el systems

2018-02-14 Thread Dimitri John Ledkov
** Also affects: debian-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: hw-detect (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/1555904

Title:
  opal-prd not installed by default on ppc64el systems

Status in The Ubuntu-power-systems project:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  New
Status in hw-detect source package in Xenial:
  New

Bug description:
  Just tried an install with current 16.04 network media, using standard
  server package selections, and it looks like opal-prd isn't installed
  by default:

   [jk@fstn ~]$ dpkg -l opal-prd
   dpkg-query: no packages found matching opal-prd

  This is required for RAS-type functions on OpenPOWER machines; and has
  a similar role to something like acpid, on x86.

  I'm not sure whether filing this against the skiboot package is best,
  or whether this should be moved to something installer-related. Happy
  to shift if necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1555904/+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 1748161] Re: improve britney hints for postgres MREs

2018-02-14 Thread ChristianEhrhardt
** Package changed: postgresql-9.5 (Ubuntu) => postgresql-common
(Ubuntu)

** Also affects: postgresql-common (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: postgresql-common (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: postgresql-common (Ubuntu)
   Status: New => Fix Released

** Changed in: postgresql-common (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: postgresql-common (Ubuntu Xenial)
   Status: New => 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/1748161

Title:
  improve britney hints for postgres MREs

Status in britney:
  New
Status in postgresql-common package in Ubuntu:
  Fix Released
Status in postgresql-common source package in Trusty:
  Triaged
Status in postgresql-common source package in Xenial:
  Triaged

Bug description:
  On every postgres MRE we mention some regular failing tests.
  Those were mostly caused by changes in the environment and fixes were done 
for later Ubuntu releases but not SRUable.
  We should not ask the release team to force them on every SRU but cover those 
where it is correct with badtest entries.

  So this is about collecting this information and adapting hints for
  britney accordingly.

  Due to changes from lxc -> lxd (documented by pitti and carried on since then)
  - trusty
- postgresql-9.3/armhf
  - Xenial
- postgresql-9.5/armhf
- mimeo/armhf

  FYI - there are also some long term always fail cases.
  Often had just 1-2 good runs on old pgsql versions and hen never again - 
resolved in latter releases. Those packages are in universe only and are 
already covered by hints.
  - Xenial
- pgfincore, see [1]
- orafce, see [2]
- postgresql-plproxy, see [3]
- pgpool2, since pgpool2/3.4.3-1 see [4] as an example

  Some others are known flaky tests are there as well, but I don't want to 
overrid all those to keep their coverage.
  E.g. dbconfig-common failed on artful due to mysql (but one can see in the 
log postgres is good which for this update is the important part).

  But for those above that are due to the LXC/LXD change there is no reason to 
bump it on every MRE.
  It won't change - so lets propose them unversioned to not need this over and 
over again.

  [1]: http://autopkgtest.ubuntu.com/packages/pgfincore/xenial/amd64
  [2]: http://autopkgtest.ubuntu.com/packages/orafce/xenial/amd64
  [3]: http://autopkgtest.ubuntu.com/packages/postgresql-plproxy/xenial/amd64
  [4]: http://autopkgtest.ubuntu.com/packages/pgpool2/xenial/amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/britney/+bug/1748161/+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 1749389] Re: ntpdate lock apparmor deny

2018-02-14 Thread ChristianEhrhardt
Missed the right format in changelog :-/, but this is fixed in Bionic by
https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p10+dfsg-5ubuntu7

** Changed in: ntp (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/1749389

Title:
  ntpdate lock apparmor deny

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged
Status in ntp source package in Artful:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no 
 issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w 
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the 
 changes poses a security risk so regression potential on it's own 
 should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would 
 e.g. no more be freed up or the action behind the locking would cause 
 issues.

  [Other Info]
   
   * n/a

  
  On start/restart nto has an error in apparmor due to the locking it tries to 
avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1749089] Re: linux: 4.4.0-116.140 -proposed tracker

2018-02-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-certification-testing
   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/1749089

Title:
  linux: 4.4.0-116.140 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa 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:
  Confirmed

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

  backports: bug 1749090 (linux-aws), bug 1749091 (linux-lts-xenial)
  derivatives: bug 1749092 (linux-kvm), bug 1749093 (linux-aws), bug 1749094 
(linux-raspi2), bug 1749095 (linux-euclid), bug 1749096 (linux-snapdragon), bug 
1749097 (linux-gke)
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749089/+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 1748478] Re: linux-gcp: 4.13.0-1011.15 -proposed tracker

2018-02-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

** Changed in: kernel-sru-workflow/snap-release-to-edge
   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/1748478

Title:
  linux-gcp: 4.13.0-1011.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

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: 1748743
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-02-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-certification-testing
   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/1749096

Title:
  linux-snapdragon: 4.4.0-1087.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
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 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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-02-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

** Changed in: kernel-sru-workflow/snap-release-to-edge
   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/1749093

Title:
  linux-aws: 4.4.0-1052.61 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
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 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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749093/+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 1749094] Re: linux-raspi2: 4.4.0-1085.93 -proposed tracker

2018-02-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-certification-testing
   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/1749094

Title:
  linux-raspi2: 4.4.0-1085.93 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749094/+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 1749095] Re: linux-euclid: 4.4.0-9025.27 -proposed tracker

2018-02-14 Thread Kleber Sacilotto de Souza
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Invalid

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

** Changed in: kernel-sru-workflow/regression-testing
   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/1749095

Title:
  linux-euclid: 4.4.0-9025.27 -proposed tracker

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

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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-02-14 Thread Kleber Sacilotto de Souza
** Changed in: kernel-sru-workflow/regression-testing
   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/1749096

Title:
  linux-snapdragon: 4.4.0-1087.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
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 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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749096/+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 1749095] Re: linux-euclid: 4.4.0-9025.27 -proposed tracker

2018-02-14 Thread Kleber Sacilotto de Souza
** Changed in: kernel-sru-workflow/certification-testing
   Status: Invalid => 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/1749095

Title:
  linux-euclid: 4.4.0-9025.27 -proposed tracker

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

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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749095/+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 1749094] Re: linux-raspi2: 4.4.0-1085.93 -proposed tracker

2018-02-14 Thread Kleber Sacilotto de Souza
** Changed in: kernel-sru-workflow/regression-testing
   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/1749094

Title:
  linux-raspi2: 4.4.0-1085.93 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-02-14 Thread Kleber Sacilotto de Souza
** Changed in: kernel-sru-workflow/certification-testing
   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/1749092

Title:
  linux-kvm: 4.4.0-1019.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
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 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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-02-14 Thread Kleber Sacilotto de Souza
** Changed in: kernel-sru-workflow/certification-testing
   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/1749093

Title:
  linux-aws: 4.4.0-1052.61 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
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 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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749093/+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 1741189] Re: New bugfix release 17.2.8

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 17.2.8-0ubuntu0~16.04.1

---
mesa (17.2.8-0ubuntu0~16.04.1) xenial; urgency=medium

  * New upstream bugfix release. (LP: #1741189)

 -- Timo Aaltonen   Thu, 18 Jan 2018 16:19:31 +0200

** Changed in: mesa (Ubuntu Xenial)
   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/1741189

Title:
  New bugfix release 17.2.8

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.4:

  Mesa 17.2.5 is now available.

  In this release we have:

  In Mesa Core a GL error related to the ARB_ES3_1_compatibility spec
  noticed with the GFXBench 5 Aztec Ruins has been corrected. 

  The GLSL compiler is not giving a linker error for mismatching uniform
  precision with GLSL ES 1.00 any more. This enables, specially, several
  Android applications which violate this rule, like Forge of Empires,
  for example.

  The SPIR-V compiler has corrected an assert triggered when support for
  the simple memory model was claimed.

  NIR has also received a correction related with
  gl_SubGroupG{e,t}MaskARB.

  The Intel drivers, specially i965, have received several fixes,
  including a plug for a memory leak and another one in the compiler to
  avoid GPU hangs on Broxton.

  The gallium i915g driver for Intel has also seen an important
  correction.

  AMD drivers, mostly radv, have also received several fixes, including a
  correction for a DCC corruption that was visible with Rust, breaking an
  endless loop in r600, avoiding a GPU hang with vulkan dota2 in VR mode
  and a plug for a memory leak.

  Broadcom's vc4 has gotten a fix to compile out some non-debug code that
  shouldn't be there for the release build.

  

  Mesa 17.2.6 is now available.

  In this release we have:

  In Mesa Core we have included a correction to keep a program alive when
  re-linking and prevent an use-after-free.

  The GLSL compiler has received several fixes, including one to prevent
  a SIGSEV when calling an undeclared subroutine in certain conditions
  and another to mark the xfb buffers as active only if a variable uses
  them.

  The SPIR-V compiler has corrected a couple of issues involving the
  usage of separate images and texture/samplers.

  The Intel drivers include many new fixes, specially for i965. Several 
  are focused on improving SIMD32 and little-core. It also includes a fix
  for a GPU hang which was detected while playing HW accelerated video
  with mpv.

  The AMD drivers have also received some care. radv has seen plugged 2
  memory leaks while r600 has gotten a fix through reversing the tess
  factor components for isolines.

  The swr driver has corrected two performance regressions, one for the
  avx512 platforms and the other for the avx/avx2 platforms.

  In the ddebug gallium driver we have a fix for an use-after-free.

  On the EGL side, the Wayland platform of the the DRI2 drivers has
  received a fix to prevent crashing in ancient systems.

  GLX has also received corrections to prevent a couple of errors when
  creating and binding a context in DRI3 and DRISW, respectively.

  From build and integration point of view, we have added some few more
  fixes, including one to allow building libglvnd when EGL is present but
  not GLX, another to enable building targets which don't need X11, such
  as omx and va, when XCB is not present, and another one to be able to
  specify the prefix installation for the OpenCL icd file.

  

  Mesa 17.2.7 is now available.

  In this release we have:

  The current queue consists of a variety of fixes, with a sizeable hunk in the
  shared GLSL codebase.

  Whereas for individual drivers - i965 has a crash fix for when playing various
  Valve games, r600 and nouveau have tweaks in their compiler backends. Fast
  clears on radeonsi and RADV are better now, while the VAAPI encoding is 
playing
  nicely with GStreamer.

  The WGL state tracker and SWR driver have also seen minor
  improvements.

  To top of up - Mesa should build fine with the latest glibc 2.17.

  

  Mesa 17.2.8 is now available.

  In this release we have:

  The SPIR-V compiler has seen corrected a possible SEGFAULT.

  The Intel i965 driver includes a correction for Haswell involving
  doubles management. 

  The AMD drivers have also received some fixes. A couple have gone for
  radv and radeon's VCE while r600 has seen corrected some glitches
  detected with This War of Mine.

  Gallium has also received a patch fixing a problem affecting the VMware
  driver and the st/nine state tracker.

  The endianness detection in 

[Group.of.nepali.translators] [Bug 1741227] Re: apparmor denial to several paths to binaries

2018-02-14 Thread ChristianEhrhardt
Hi Tony,
yeah this is so far only fixed in Bionic (18.04) onwards.
It it not really an issue other than a log message itself (it is not needed for 
the opt parsing).
It occurs "only" on NTP start/restart (since it is arg parsing) so it is not 
that frequent that it would fill up the log or similar secondary issues.

All that makes it a hard case for the SRU policy [1] to make this change in 
releases.
Until then everybody who bothers about the log message can add:
   /usr/local/{,s}bin/  r,
to
   /etc/apparmor.d/usr.sbin.ntpd

I'm adding X/A bug tasks and set won't fix to mark that more explicitly.

I'm happy to discuss if one thinks this case would qualify fot the SRU
policy - the change itself is easy enough to be done.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates

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

** Also affects: ntp (Ubuntu Artful)
   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/1741227

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged
Status in ntp source package in Artful:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1749094] Re: linux-raspi2: 4.4.0-1085.93 -proposed tracker

2018-02-14 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   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/1749094

Title:
  linux-raspi2: 4.4.0-1085.93 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-02-14 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   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/1749096

Title:
  linux-snapdragon: 4.4.0-1087.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
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 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: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749096/+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