date:20171031

[Group.of.nepali.translators] [Bug 1552241] Re: libvirt-bin apparmor settings for usb host device

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package libvirt - 3.6.0-1ubuntu6

---
libvirt (3.6.0-1ubuntu6) artful; urgency=medium

  * d/p/ubuntu-aa/0037-virt-aa-helper...: grant locking permission on append
files (LP: #1726804)
  * d/p/ubuntu-aa/0038-virt-aa-helper-fix-paths-for-usb-hostdevs.patch:
fix path generation for USB host devices (LP: #1552241)
  * d/p/ubuntu-aa/0039-virt-aa-helper-fix-libusb-access-to-udev-usb-data.patch:
generate valid rules on usb passthrough (LP: #1686324)

 -- Christian Ehrhardt   Tue, 24 Oct
2017 14:30:34 +0200

** Changed in: libvirt (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/1552241

Title:
  libvirt-bin apparmor settings for usb host device

Status in libvirt package in Ubuntu:
  Fix Committed
Status in libvirt source package in Xenial:
  New
Status in libvirt source package in Zesty:
  New
Status in libvirt source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * A while ago qemu switched to libusb, since then qemu fails to scan for 
 usb devices. Thereby it fails to use them for passthrough.

   * This

   * Fix by back-porting small upstream change

  [Test Case]

   * Create a VM Guest (e.g. via uvtool)
   * Create a XMl file desrcibing a usb hostdev from your System (check lsusb 
for IDs)
   * See the c#3 for XML examples
   * Then add that to your guest with
 $ virsh attach-device  

   * Without the fix you'll see apparmor blocks and a fail to generate the rules
   * With the fix it works

  [Regression Potential]

   * The change "only" allows to access a few more files udev populates. In 
 those it is still restricted to just USB types - that seems safe to me.

   * If no USB devices are used in the guest config (or via hot-add) then it 
 is not initialized and thereby the rules not needed.

   * But if users use USB Host devices they now can work due to the fix. And 
 "suddenly working" is not a regression but a fix.

  [Other Info]
   
   * I waited to be accepted upstream to be more confident which is 
 partially why this took so long but provides some extra confidence.

   * This was long in discussion here since the suggestions always had a bit 
 of a very open blanket apparmor rule, but we now found a minimal one to 
 work and that was upstreamable.

  ---

  
  This fix is for Ubuntu Xenial

  The following file needs some fixes in order to work for usb host device 
access:
  /etc/apparmor.d/abstractions/libvirt-qemu

  The line is wrong:
    /sys/devices/**/usb[0-9]*/** r,
  correct is:
    /sys/devices/*/*/usb[0-9]*/** r,

  This line is missing:
    /run/udev/data/** r,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1552241/+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 1686324] Re: usb hostdev passthrough generates the wrong apparmor rules

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package libvirt - 3.6.0-1ubuntu6

---
libvirt (3.6.0-1ubuntu6) artful; urgency=medium

  * d/p/ubuntu-aa/0037-virt-aa-helper...: grant locking permission on append
files (LP: #1726804)
  * d/p/ubuntu-aa/0038-virt-aa-helper-fix-paths-for-usb-hostdevs.patch:
fix path generation for USB host devices (LP: #1552241)
  * d/p/ubuntu-aa/0039-virt-aa-helper-fix-libusb-access-to-udev-usb-data.patch:
generate valid rules on usb passthrough (LP: #1686324)

 -- Christian Ehrhardt   Tue, 24 Oct
2017 14:30:34 +0200

** Changed in: libvirt (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/1686324

Title:
  usb hostdev passthrough generates the wrong apparmor rules

Status in libvirt package in Ubuntu:
  Fix Committed
Status in libvirt source package in Xenial:
  New
Status in libvirt source package in Zesty:
  New
Status in libvirt source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * USB Host devices fail to add statically

   * The reason is that libvirt has not yet initialized usb devices

   * Fix by back-porting small upstream change

  [Test Case]

   * Create a VM Guest (e.g. via uvtool)
   * Shut down the guest
   * virsh edit 
   * Add a usb hostdev from your System (check lsusb for IDs)
   * See the original description below for XML examples
   * Starting the guest will create a wrong rule
   "/dev/bus/usb/000/000" rw,
 And due to that fails to start.

  [Regression Potential]

   * The change is small and only makes certain values available to
  libvirt

   * The only thing I could think of regressing is if that 
 virHostdevFindUSBDevice would crash on some systems, but then it would 
 fail later on in the lifecycle even without the patch - so we should be 
 safe IMHO.

  [Other Info]
   
   * I waited to be accepted upstream to be more confident which is 
 partially why this took so long but provides some extra confidence.

  
  ---

  
  Libvirt-aa-helper seems to have a bug when adding usb passthrough devices 
statically.

  On hotplug with:
  $ cat sandisk-usb.xml
  
  
  
  
  
  
  

  $ virsh attach-device z-test1 sandisk-usb.xml

  It generates correctly:
  "/dev/bus/usb/003/003" rw,

  But if adding the same XML part to the guest xml itself it generates:
  "/dev/bus/usb/000/000" rw,

  And as a follow on issue the guest start fails with:
  libusb: error [_get_usbfs_fd] libusb couldn't open USB device 
/dev/bus/usb/003/003: Permission denied
  Due to:
  apparmor="DENIED" operation="open" 
profile="libvirt-adc578cb-905f-41fc-9be2-9fb81f6a6073" 
name="/dev/bus/usb/003/003" pid=22879 comm="qemu-system-x86" 
requested_mask="wr" denied_mask="wr" fsuid=123 ouid=123

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1686324/+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 1729034] Re: don't short-circuit update-grub kernel postinst hook in containers

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package livecd-rootfs - 2.479

---
livecd-rootfs (2.479) bionic; urgency=medium

  * Purge initramfs-tools from minimized images.
  * Make sure to remove any initramfs that was generated in a minimized
image.
  * divert /usr/bin/systemd-detect-virt as part of the grub diversions, so
that the grub kernel postinst hook is operational when we're building
in a container.  LP: #1729034.

 -- Steve Langasek   Tue, 31 Oct 2017
09:58:35 -0700

** Changed in: livecd-rootfs (Ubuntu)
   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/1729034

Title:
  don't short-circuit update-grub kernel postinst hook in containers

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  LP: #1060404 was addressed by making the update-grub kernel postinst hook a 
no-op when running in containers.

  We now do all of our livefs builds in containers in Launchpad; this
  means livefses no longer get a grub config automatically generated
  with the correct contents when installing a kernel in the target, as
  they did previously.

  The change for LP: #1060404 was described by Colin as a "temporary
  fix".

  We know that update-grub itself now succeeds in the launchpad buildd
  containers, because we have several points in livefs builds where we
  are invoking it directly and it does what we expect.  And in any
  containers where update-grub does not work, these same livefs builds
  will fail anyway.

  [Test case]
  Run through a standard set of xenial image builds with livecd-rootfs in 
launchpad, including the private cloud image builds.  Confirm that the builds 
are successful and that the resulting images list the correct contents in 
/boot/grub/grub.cfg.

  [Regression potential]
  If something else relied on container detection in order to modify its 
behavior, and is called between the addition and removal of the 
systemd-detect-virt diversion, it could now behave incorrectly in a container 
and cause build failures.  This is an entirely hypothetical scenario, since all 
current consumers of (un)divert_grub, and pending users of it, have it very 
narrowly scoped such that they're only doing update-grub / kernel install 
operations in between.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1729034/+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 1727373] Re: SRU of LXCFS 2.0.8 (upstream bugfix release)

2017-10-31 Thread Stéphane Graber

And uploaded bionic, zesty and xenial now.

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

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

Title:
  SRU of LXCFS 2.0.8 (upstream bugfix release)

Status in lxcfs package in Ubuntu:
  Fix Released
Status in lxcfs source package in Trusty:
  New
Status in lxcfs source package in Xenial:
  In Progress
Status in lxcfs source package in Zesty:
  In Progress
Status in lxcfs source package in Artful:
  In Progress

Bug description:
  LXCFS upstream released LXCFS 2.0.8 as a bugfix release with following 
changelog:
   - bindings: Add mountpoint for unified hierarchy
   - bindings: Calculate uptime via proc//stat
   - bindings: Revert virtualization of 'btime' field due to regressions in ps
   - doc: Update README
   - init: Add cgroupfs-mount to Should-Start/Stop sysvinit LSB headers
   - lib: Add common fallback dlopen for liblxcfs.so
   - lib: Fix the installation directory for liblxcfs to ${libdir}/lxcfs
   - pam: Add a 'all' option for -c
   - pam: Chown cgroup.procs file on unified hierarchy
   - pam: Report back when we find a unified hierarchy
   - tests: Fix invalid comparison
   - uptime: Fix a problem with subsequent reads

  
  Just like Ubuntu itself, upstream releases long term support releases, as is 
2.0 and then periodic point releases including all the accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1727373/+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 1728152] Re: EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package cloud-init -
17.1-27-geb292c18-0ubuntu1

---
cloud-init (17.1-27-geb292c18-0ubuntu1) bionic; urgency=medium

  * New upstream snapshot.
- EC2: Limit network config to fallback nic, fix local-ipv4 only
  instances. (LP: #1728152)
- Gentoo: Use "rc-service" rather than "service".
  [ckonstanski] (LP: #1727121)

 -- Chad Smith   Tue, 31 Oct 2017 12:51:10
-0600

** Changed in: cloud-init (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not
  assigned public IPv4 address

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Zesty:
  In Progress
Status in cloud-init source package in Artful:
  In Progress
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Support for configuration of IPV6 addresses on the primary network
  interface in EC2 changed behavior of the automatic network configuration.
  This changed behavior in 2 ways:
  a.) Instances with only a private ipv4 address would not get *any* ipv4
  address.

  b.) Instances with multiple NICs attached at boot would get all NICs
  configured. Previously only the primary network interface would be
  configured by cloud-init.

  'b' is not necessarily a bug for Artful.  A new release can bring new
  behavior.  However, the change of behavior was not intended and not desired
  for an SRU.  In an effort to keep this behavior consistent across 16.04+
  we will be changing the behavior of Artful to only configure the primary
  network interface.

  [Test Case]
  To verify this code is fixed for all cases involved:

  1. Verify that instances without public ipv4 get an ipv4 address.
   * Launch an instance on EC2 without a public IPV4 address.
   * Verify the instance has its Ipv4 address configured via ssh and
 checking 'ip' output.

  2. Verify no regression is done to public systems.
   * Launch an instance on EC2 with a public IPV4 address.
   * Verify the instance has its ipv4 address configured.

  3. Verify only the primary NIC is configured (17.10 only)
   * Launch an instance on EC2 with multiple  nics configured.
   * Verify that only the primary nic has configuration by default.

  For each of the above, verification entails inspection of
  network config (/etc/network/interfaces.d/* or /etc/netplan/)
  and also network state ('ip a' output).

  [Regression Potential]
  Regression in this area of code is certainly limited to EC2,
  and most likely limited to network configuration.

  Complete failure would show itself as no networking at all and
  a WARNING or stack trace on the console logs.

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

  === End SRU Template ===

  With the following cloud-init configuration:
  system_info:
    network:
  renderers: ['netplan', 'eni', 'sysconfig']

  network:
    version: 2
    ethernets:
  id0:
  match:
  name: e*
  dhcp4: true
  dhcp6: true

  with version  17.1-18-gd4f70470-0ubuntu1 on ami-36a8754c, it writes out the 
following network configuration:
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp6: true
  match:
  macaddress: 02:14:13:66:8a:66
  set-name: ens3

  

  This instance is in a (default) VPC with a private IPv4 address and no
  public IPv4 addresses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1728152/+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 1709920] Re: criu is not built for arm64

2017-10-31 Thread David Britton

This isn't something that's in plan right now.

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

** Changed in: criu (Ubuntu Zesty)
   Status: New => Won't Fix

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

Title:
  criu is not built for arm64

Status in criu package in Ubuntu:
  Fix Released
Status in criu source package in Xenial:
  Won't Fix
Status in criu source package in Zesty:
  Won't Fix
Status in criu package in Debian:
  Fix Released

Bug description:
  The criu package has source code for arch/aarch64, but arm64 is not
  listed in the control file so LP does not attempt to build it.

  At least for artful, adding arm64 to the supported list in
  debian/control is sufficient for the build to succeed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/criu/+bug/1709920/+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 1716359] Re: Unplugging headset with audio panel open mutes internal mic

2017-10-31 Thread Brian Murray

Hello Will, or anyone else affected,

Accepted unity-control-center into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unity-control-center/15.04.0+16.04.20170214-0ubuntu2 in a few hours,
and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

** Changed in: unity-control-center (Ubuntu)
   Status: In Progress => Invalid

** Changed in: unity-control-center (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  Unplugging headset with audio panel open mutes internal mic

Status in OEM Priority Project:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Invalid
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  
  Impact
  ==
  This is required by OEM team.

  Test Case
  =
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

  Make sure the internal mic is not muted.

  Regression Potential
  ===
  - Make sure that plugging/unplugging headphones does the correct thing.
  - Make sure that manually selecting an headphone actually switch mic.
  - Please also check that output sound works too.

  Original Bug Report
  ===
  This bug was reported by our OEM team, I'm opening this public bug.

  The internal microphone is muted after he headset is unplugged when the 
System Settings is running.
  We can not reproduce this bug when closed the System Settings window before 
unplugged the headset.

  Reproduce steps:
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1716359/+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 1477455] Re: Incorrect instructions leave automatic updates blocked when /boot is full

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package update-manager - 1:16.04.10

---
update-manager (1:16.04.10) xenial; urgency=medium

  * UpdateManager/UpdatesAvailable.py: Provide instructions when mount points
have insufficient free space for the upgrade to complete. (LP: #1477455)
  * test_update_origin.py: fix the extended origin matcher test as it was
making wrong assumptions, not checking if packages actually had ANY package
in -security. This should fix the current autopkgtest failures.
(LP: #1717360)

 -- Brian Murray   Wed, 20 Sep 2017 14:39:17 -0700

** Changed in: update-manager (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/1477455

Title:
  Incorrect instructions leave automatic updates blocked when /boot is
  full

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in update-manager source package in Zesty:
  Fix Released
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]
  A system's /boot mount point can fill up for many reasons and 
update-manager's free space check will cause update-manager to exit. A generic 
error message is presented which does not provide specific information to 
remedy the situation and subsequently can leave systems insecure.

  [Test Case]
  0) Ensure your system does not have the latest kernel installed
  1) Create a file to be used as a /boot partition (dd if=/dev/zero 
of=fake-boot bs=1024 count=204800)
  2) mkfs -t ext3 fake-boot
  3) copy your real /boot somewhere
  4) sudo mount -t ext3 fake-boot /boot
  5) copy the files from step 3 to /boot
  6) fill up /boot so there is less 60MB free space
  7) run update-manager
  8) Click "Install Now"

  With the current version of update-manager you'll see an error message
  with instructions to "empty your trash and remove temporary packages."
  With the version of update-manager in -proposed you'll receive a
  message regarding using "sudo apt autoremove".

  [Regression Potential]
  We are just changing the strings used in the error message, which will 
introduce untranslated strings but that is better than leaving people with 
systems that cannot update.

  Original Description
  
  What happens:

  Default installations regularly fail package updates when /boot fills
  up. While the ultimate cause of this bug lies elsewhere, update-
  manager gives the user incorrect instructions when the failure occurs:

  "Not enough free disk space The upgrade needs a total of 104 M free
  space on disk '/boot'. Please free at least an additional 85.6 M of
  disk space on '/boot'. Empty your trash and remove temporary packages
  of former installations using 'sudo apt-get clean'."

  These instructions do not work, and software updates from this point
  on fail. The user is left vulnerable, unless they have knowledgeable
  assistance or are technically capable enough to research and fix the
  problem themselves.

  What should happen:

  update-manager should provide valid instructions for dealing with this
  well known problem, or better yet perform the operation itself. It is
  responsible for keeping  the users machine up to date, and needs to
  handle this and similar failures.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: update-manager 1:15.04.7
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 23 15:35:46 2015
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'706'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'701'
   b'com.ubuntu.update-manager' b'launch-time' b'1437636623'
  InstallationDate: Installed on 2015-03-13 (131 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: allSourcePackage: update-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-16 (128 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1477455/+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 1717360] Re: test_update_origin.py test failure

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package update-manager - 1:16.04.10

---
update-manager (1:16.04.10) xenial; urgency=medium

  * UpdateManager/UpdatesAvailable.py: Provide instructions when mount points
have insufficient free space for the upgrade to complete. (LP: #1477455)
  * test_update_origin.py: fix the extended origin matcher test as it was
making wrong assumptions, not checking if packages actually had ANY package
in -security. This should fix the current autopkgtest failures.
(LP: #1717360)

 -- Brian Murray   Wed, 20 Sep 2017 14:39:17 -0700

** Changed in: update-manager (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/1717360

Title:
  test_update_origin.py test failure

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Trusty:
  Triaged
Status in update-manager source package in Xenial:
  Fix Released
Status in update-manager source package in Zesty:
  Fix Released

Bug description:
  The test_update_origin.py test is experiencing a failure. While this
  was fixed in Artful, it has not been in Zesty, Xenial, or Trusty and
  should be since the failures end up appearing when other packages are
  tested (e.g. xorg-server) too.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-xenial/xenial/amd64/u/update-
  manager/20170913_045020_c1f35@/log.gz

  Here's the fix:

  https://bazaar.launchpad.net/~ubuntu-core-dev/update-
  manager/main/revision/2792

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1717360/+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 1717360] Re: test_update_origin.py test failure

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package update-manager - 1:17.04.8

---
update-manager (1:17.04.8) zesty; urgency=medium

  * UpdateManager/UpdatesAvailable.py: Provide instructions when mount points
have insufficient free space for the upgrade to complete. (LP: #1477455)
  * test_update_origin.py: fix the extended origin matcher test as it was
making wrong assumptions, not checking if packages actually had ANY package
in -security. This should fix the current autopkgtest failures.
(LP: #1717360)

 -- Brian Murray   Wed, 20 Sep 2017 14:36:07 -0700

** Changed in: update-manager (Ubuntu Zesty)
   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/1717360

Title:
  test_update_origin.py test failure

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Trusty:
  Triaged
Status in update-manager source package in Xenial:
  Fix Released
Status in update-manager source package in Zesty:
  Fix Released

Bug description:
  The test_update_origin.py test is experiencing a failure. While this
  was fixed in Artful, it has not been in Zesty, Xenial, or Trusty and
  should be since the failures end up appearing when other packages are
  tested (e.g. xorg-server) too.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-xenial/xenial/amd64/u/update-
  manager/20170913_045020_c1f35@/log.gz

  Here's the fix:

  https://bazaar.launchpad.net/~ubuntu-core-dev/update-
  manager/main/revision/2792

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1717360/+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 1721882] Re: Generic instructions for dealing with full partitions don't help much

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-release-upgrader - 1:16.04.23

---
ubuntu-release-upgrader (1:16.04.23) xenial; urgency=medium

  * DistUpgrade/DistUpgradeController.py: Provide better instructions when an
upgrade is aborted due to a lack of free space in a partition.
(LP: #1721882)

 -- Brian Murray   Fri, 13 Oct 2017 11:55:09 -0700

** Changed in: ubuntu-release-upgrader (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/1721882

Title:
  Generic instructions for dealing with full partitions don't help much

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Released
Status in ubuntu-release-upgrader source package in Zesty:
  Fix Released
Status in ubuntu-release-upgrader source package in Artful:
  Fix Released

Bug description:
  This a parallel to bug 1477455 regarding update-manager and a full
  /boot partition.

  [Impact]
  ubuntu-release-upgrader provides generic instructions if a system being 
upgrade is calculated to not have enough free space for the upgrade to succeed. 
The instructions include using apt clean and emptying trash. This message won't 
help if you have a separate boot partition that is low on free space though.

  [Test Case]
  1) Create a file to be used as a /boot partition (dd if=/dev/zero 
of=fake-boot bs=1024 count=204800)
  2) mkfs -t ext3 fake-boot
  3) copy your real /boot somewhere
  4) sudo mount -t ext3 fake-boot /boot
  5) copy the files from step 3 to /boot
  6) fill up /boot so there is less 30MB free space
  7) run 'do-release-upgrade -p' (-p is for proposed)

  With the current version of ubuntu-release-upgrader you'll see an
  error message with instructions to "empty your trash and remove
  temporary packages." With the version of ubuntu-release-upgrader in
  -proposed you'll receive a message regarding using "sudo apt
  autoremove".

  [Regression Potential]
  We are just changing the strings used in the error message, which will 
introduce untranslated strings but that is better than leaving people with 
systems that cannot update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1721882/+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 1721882] Re: Generic instructions for dealing with full partitions don't help much

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-release-upgrader - 1:17.04.10

---
ubuntu-release-upgrader (1:17.04.10) zesty; urgency=medium

  * DistUpgrade/DistUpgradeController.py: Provide better instructions when an
upgrade is aborted due to a lack of free space in a partition.
(LP: #1721882)

 -- Brian Murray   Fri, 13 Oct 2017 11:40:57 -0700

** Changed in: ubuntu-release-upgrader (Ubuntu Zesty)
   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/1721882

Title:
  Generic instructions for dealing with full partitions don't help much

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Released
Status in ubuntu-release-upgrader source package in Zesty:
  Fix Released
Status in ubuntu-release-upgrader source package in Artful:
  Fix Released

Bug description:
  This a parallel to bug 1477455 regarding update-manager and a full
  /boot partition.

  [Impact]
  ubuntu-release-upgrader provides generic instructions if a system being 
upgrade is calculated to not have enough free space for the upgrade to succeed. 
The instructions include using apt clean and emptying trash. This message won't 
help if you have a separate boot partition that is low on free space though.

  [Test Case]
  1) Create a file to be used as a /boot partition (dd if=/dev/zero 
of=fake-boot bs=1024 count=204800)
  2) mkfs -t ext3 fake-boot
  3) copy your real /boot somewhere
  4) sudo mount -t ext3 fake-boot /boot
  5) copy the files from step 3 to /boot
  6) fill up /boot so there is less 30MB free space
  7) run 'do-release-upgrade -p' (-p is for proposed)

  With the current version of ubuntu-release-upgrader you'll see an
  error message with instructions to "empty your trash and remove
  temporary packages." With the version of ubuntu-release-upgrader in
  -proposed you'll receive a message regarding using "sudo apt
  autoremove".

  [Regression Potential]
  We are just changing the strings used in the error message, which will 
introduce untranslated strings but that is better than leaving people with 
systems that cannot update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1721882/+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 1729034] Re: don't short-circuit update-grub kernel postinst hook in containers

2017-10-31 Thread Steve Langasek

** Also affects: livecd-rootfs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Fix Committed

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

Title:
  don't short-circuit update-grub kernel postinst hook in containers

Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in livecd-rootfs source package in Xenial:
  New

Bug description:
  LP: #1060404 was addressed by making the update-grub kernel postinst
  hook a no-op when running in containers.

  We now do all of our livefs builds in containers in Launchpad; this
  means livefses no longer get a grub config automatically generated
  with the correct contents when installing a kernel in the target, as
  they did previously.

  The change for LP: #1060404 was described by Colin as a "temporary
  fix".

  We know that update-grub itself now succeeds in containers, because we
  have several points in livefs builds where we are invoking it directly
  and it does what we expect.

  We should check that running update-grub in a stock lxd container
  works as expected, and that this isn't due to some sort of launchpad
  sauce.  Provided it does work, we should remove the container check
  from the kernel postinst hook.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1729034/+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 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package cracklib2 - 2.9.2-1ubuntu1

---
cracklib2 (2.9.2-1ubuntu1) xenial; urgency=medium

  * Migrate triggers to interest-noawait to avoid trigger-cycles (Closes:
#859307, LP: #1681231)

 -- Brian Murray   Fri, 20 Oct 2017 17:07:36 -0700

** Changed in: cracklib2 (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/1681231

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Fix Released
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Fix Released
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.

  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.

  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaries-common and verify that the trigger is called

  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed, confirm 
that a distribution upgrade to next supported release succeeds.

  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.

  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.

  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+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 1688508] Re: libvirt-guests.sh fails to shutdown guests in parallel

2017-10-31 Thread Eric Desrochers

** Also affects: libvirt (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Also affects: libvirt (Ubuntu Zesty)
   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/1688508

Title:
  libvirt-guests.sh fails to shutdown guests in parallel

Status in libvirt:
  In Progress
Status in libvirt package in Ubuntu:
  Triaged
Status in libvirt source package in Xenial:
  New
Status in libvirt source package in Zesty:
  New
Status in libvirt source package in Artful:
  New

Bug description:
  On a brand new installation of Ubuntu Server 16.04.2 LTS the libvirt-
  guests.sh script fails to shutdown my VMs if run with
  PARALLEL_SHUTDOWN > 0, instead running forever thereby preventing me
  from shutting down my system. I debugged the script with 'set -x' and
  found out that the problem lies in the `check_guests_shutdown()`
  function (line 337). If a guest is shutdown, it runs eval_gettext() to
  print that the state of the guest cannot be determined. This is used
  as a return value on line 428, causing the script to interpret the
  error message as a list of VM IDs and trying to shutdown these. This
  of course fails again and the cycle continues. For now I have
  commented out the eval_gettext line and the script works fine again.

  My libvirt version is 1.3.1-1ubuntu10.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1688508/+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 1107935] Re: Support for WPA Enterprise wireless networks

2017-10-31 Thread Dimitri John Ledkov

** Also affects: network-manager-applet (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: network-manager-applet (Ubuntu)
   Status: New => Fix Released

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

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  New
Status in ubiquity source package in Xenial:
  In Progress

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to 
the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or 
credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look 
for in general failure to connect to a secured wireless network when the 
authentication settings are correct (pre-shared key is correct), or in cases of 
connecting to an unsecured network.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+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 1724060] Re: linux-azure: 4.11.0-1014.14 -proposed tracker

2017-10-31 Thread Brad Figg

The package has been published and the bug is being set to Fix Released


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

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

** Description changed:

  This bug is for tracking the 4.11.0-1014.14 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
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Tuesday, 31. October 2017 15:01 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 4.11.0-1014.14 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
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Tuesday, 31. October 2017 15:01 UTC
- kernel-stable-phase:Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-azure: 4.11.0-1014.14 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.11.0-1014.14 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
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724060/+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 1724021] Re: linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker

2017-10-31 Thread Brad Figg

The package has been published and the bug is being set to Fix Released


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

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

** Description changed:

  This bug is for tracking the 4.13.0-16.19~16.04.3 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
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Tuesday, 31. October 2017 15:03 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 4.13.0-16.19~16.04.3 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
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Tuesday, 31. October 2017 15:03 UTC
- kernel-stable-phase:Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
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:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.13.0-16.19~16.04.3 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
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724021/+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 1726809] Re: Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package nvidia-graphics-drivers-384 -
384.90-0ubuntu4

---
nvidia-graphics-drivers-384 (384.90-0ubuntu4) bionic; urgency=medium

  * debian/rules,
debian/templates/nvidia-graphics-drivers.links.in,
debian/templates/nvidia-graphics-drivers.links32.in:
- Ship the correct (non GLVND) libGL and libEGL libraries (LP: #1726809).

 -- Alberto Milone   Mon, 30 Oct 2017
16:01:58 +0100

** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   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/1726809

Title:
  Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json

Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-384 source package in Zesty:
  Fix Committed
Status in nvidia-graphics-drivers-384 source package in Artful:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Vulkan support is broken because the packages ship a mix of GLVND and non 
GLVND GL and EGL libraries.

  [Test Case]
  1) Enable the -proposed repository, install the new nvidia-384 package, and 
reboot.

  2) Install the utilities to check that the correct libraries can be
  found:

  sudo apt install vulkan-utils mesa-utils-extra

  3) Run and attach the output of the following commands (which should
  execute with no errors):

  vulkaninfo

  es2_info

  [Regression Potential]
  Low, as the libraries are the same that are installed by the upstream NVIDIA 
installer when the non-GLVND parameter is used.

  
  The Vulkan nvidia_icd.json included with the nvidia-384 package has the wrong 
"library_path" set, meaning that no Vulkan apps can run. For example, running 
"vulkaninfo" gives the following:

  ERROR: [loader] Code 0 : loader_scanned_icd_add: Attempt to retrieve either 
'vkGetInstanceProcAddr' or 'vk_icdGetInstanceProcAddr' from ICD libGL.so.1 
failed.
  Cannot create Vulkan instance.
  /build/vulkan-8TJjRa/vulkan-1.0.61.1+dfsg1/demos/vulkaninfo.c:698: failed 
with VK_ERROR_INCOMPATIBLE_DRIVER

  Furthermore, none of our (Feral Interactive) Vulkan games are able to
  run when this driver package is installed.

  The library path is set to "libGL.so.1", however since this package
  includes the GLVND version of the NVIDIA driver, that library is not a
  valid Vulkan ICD (it is the GLVND dispatch library). The correct ICD
  library path when using GLVND is "libGLX_nvidia.so.0" (this is what
  you get when you install the driver manually with NVIDIA's installer).

  This is seen with nvidia-384_384.90-0ubuntu0.17.04.1_amd64.

  The nvidia-384 package from the graphics-drivers PPA (version
  384.90-0ubuntu0~gpu17.04.1) does not have this problem. However, as of
  today, the version from the main repository seems to be getting
  installed as an update in preference to the PPA version, which causes
  breakage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1726809/+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 1719624] Re: [Hyper-V] linux-azure cifs mount error caused by missing nls_utf8.ko module

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-azure - 4.11.0-1014.14

---
linux-azure (4.11.0-1014.14) xenial; urgency=low

  * linux-azure: 4.11.0-1014.14 -proposed tracker (LP: #1724060)

  * [Hyper-V] linux-azure cifs mount error caused by missing  nls_utf8.ko module
(LP: #1719624)
- [config] azure: move nls_utf8.ko to linux-image package

 -- Thadeu Lima de Souza Cascardo   Mon, 16 Oct
2017 17:24:42 -0200

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

Title:
  [Hyper-V] linux-azure cifs mount error caused by missing  nls_utf8.ko
  module

Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Released

Bug description:
  While mounting the share with CIFS/version=2.1/charset=utf8 ansible
  breaks with an error.

  Error "Can not access a needed shared library"...

  Testing with ISO-8859 charset works. utf8 does not.

  ls -ltr /lib/modules/4.11.0-1011-azure/kernel/fs/nls/ 
  total 12
  -rw-r--r-- 1 root root 9094 Sep 19 19:49 nls_iso8859-1.ko

  It looks like the nls_utf8.ko module was not included in this kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1719624/+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 1722719] Re: HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

2017-10-31 Thread Andy Whitcroft

** Also affects: linux (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/1722719

Title:
  HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New

Bug description:
  [Impact]
  Alps touchpad with ID 0x120A + trackpoint will not be used for mass 
production machines.
  Touchpad 0x120A w/o trackpoint still reports it has a trackpoint, this will 
confuse userspace apps.

  [Fix]
  Reverts commit fcaa4a07d2a4b541e91da7a55d8b3331f96d1865, so 0x120A device is 
no longer a MT_CLS_WIN_8_DUAL device.

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  Minimal.
  This patch is for a single device in a specific driver.

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1722719/+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 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

2017-10-31 Thread Andy Whitcroft

** Also affects: linux (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/1709282

Title:
  Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

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

Bug description:
  Very similar to this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763

  == the Problem ==
  Listening to sound on a vmware machine, hosted by Ubuntu, the devices 
freezes, and cannot listen to sound anymore, i have to connect/disconnect the 
device. 
  After i disconnect i get the logs:
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get 
freq at ep 0x81
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! 
Unlikely big volume range (=8192), cval->res is probably wrong.
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU 
[Sidetone Playback Volume] ch = 1, val = 0/8192/1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics 
Plantronics C520-M as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 
0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics 
Plantronics C520-M] on usb-:00:14.0-1/input3
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd

  = The solution ==

  It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.

  
  version signature: Ubuntu 4.10.0-28.32-generic 4.10.17

  Thanks!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mihai.cin...@3pillar.corp   2208 F...m pulseaudio
   /dev/snd/controlC0:  mihai.cin...@3pillar.corp   2208 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861
  InstallationDate: Installed on 2017-06-22 (47 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Precision 3510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 
i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 
i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.4
  dmi.board.name: 00D283
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282/+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 1708499] Re: usb 3-1: 2:1: cannot get freq at ep 0x1

2017-10-31 Thread Andy Whitcroft

** Also affects: linux (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/1708499

Title:
  usb 3-1: 2:1: cannot get freq at ep 0x1

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

Bug description:
  Hello,

  dmesg:
  [   74.344674] usb 3-1: 2:1: cannot get freq at ep 0x1
  [  138.403001] usb 3-1: 2:1: cannot get freq at ep 0x1
  [  247.864869] usb 3-1: 2:1: cannot get freq at ep 0x1

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  caravena   1452 F pulseaudio
   /dev/snd/controlC0:  caravena   1452 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Aug  3 13:18:46 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-07-05 (28 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708499/+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 1724021] Re: linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-hwe-edge - 4.13.0-16.19~16.04.3

---
linux-hwe-edge (4.13.0-16.19~16.04.3) xenial; urgency=low

  * linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker (LP:
#1724021)

  * Miscellaneous Ubuntu changes
- [Debian] Remove build dep on libnuma-dev for s390x, again

linux-hwe-edge (4.13.0-16.19~16.04.1) xenial; urgency=low

  * linux-hwe-edge: 4.13.0-16.19~16.04.1 -proposed tracker (LP:
#1723246)

  * 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl
graphics driver (LP: #1711358)
- qxl: fix framebuffer unpinning

  * [Bug] USB controller failed to respond on Denverton after loading
intel_th_pci module (LP: #1715833)
- SAUCE: PCI: Disable broken RTIT_BAR of Intel TH

  * CVE-2017-5123
- waitid(): Add missing access_ok() checks

 -- Seth Forshee   Mon, 16 Oct 2017 12:20:46
-0500

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

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

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

Title:
  linux-hwe-edge: 4.13.0-16.19~16.04.3 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.13.0-16.19~16.04.3 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
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724021/+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 1724021] Re: linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker

2017-10-31 Thread Brad Figg

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

** Description changed:

  This bug is for tracking the 4.13.0-16.19~16.04.3 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
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Promoted to security
+ kernel-stable-phase-changed:Tuesday, 31. October 2017 14:33 UTC

** Description changed:

  This bug is for tracking the 4.13.0-16.19~16.04.3 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
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Promoted to security
- kernel-stable-phase-changed:Tuesday, 31. October 2017 14:33 UTC

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

Title:
  linux-hwe-edge: 4.13.0-16.19~16.04.3 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.13.0-16.19~16.04.3 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
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724021/+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 1723246] Re: linux-hwe-edge: 4.13.0-16.19~16.04.1 -proposed tracker

2017-10-31 Thread Launchpad Bug Tracker

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

This bug was fixed in the package linux-hwe-edge - 4.13.0-16.19~16.04.3

---
linux-hwe-edge (4.13.0-16.19~16.04.3) xenial; urgency=low

  * linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker (LP:
#1724021)

  * Miscellaneous Ubuntu changes
- [Debian] Remove build dep on libnuma-dev for s390x, again

linux-hwe-edge (4.13.0-16.19~16.04.1) xenial; urgency=low

  * linux-hwe-edge: 4.13.0-16.19~16.04.1 -proposed tracker (LP:
#1723246)

  * 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl
graphics driver (LP: #1711358)
- qxl: fix framebuffer unpinning

  * [Bug] USB controller failed to respond on Denverton after loading
intel_th_pci module (LP: #1715833)
- SAUCE: PCI: Disable broken RTIT_BAR of Intel TH

  * CVE-2017-5123
- waitid(): Add missing access_ok() checks

 -- Seth Forshee   Mon, 16 Oct 2017 12:20:46
-0500

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

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

** Changed in: linux-hwe-edge (Ubuntu Xenial)
   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/1723246

Title:
  linux-hwe-edge: 4.13.0-16.19~16.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.13.0-16.19~16.04.1 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 --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1723246/+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 1724060] Re: linux-azure: 4.11.0-1014.14 -proposed tracker

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-azure - 4.11.0-1014.14

---
linux-azure (4.11.0-1014.14) xenial; urgency=low

  * linux-azure: 4.11.0-1014.14 -proposed tracker (LP: #1724060)

  * [Hyper-V] linux-azure cifs mount error caused by missing  nls_utf8.ko module
(LP: #1719624)
- [config] azure: move nls_utf8.ko to linux-image package

 -- Thadeu Lima de Souza Cascardo   Mon, 16 Oct
2017 17:24:42 -0200

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

Title:
  linux-azure: 4.11.0-1014.14 -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:
  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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.11.0-1014.14 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
  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/1724060/+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 1724865] Re: broadcom-sta 6.30.223.271-3~16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2017-10-31 Thread Timo Aaltonen

** Also affects: broadcom-sta (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/1724865

Title:
  broadcom-sta 6.30.223.271-3~16.04.1 ADT test failure with linux-hwe-
  edge 4.13.0-16.19~16.04.3

Status in broadcom-sta package in Ubuntu:
  In Progress
Status in broadcom-sta source package in Xenial:
  New

Bug description:
  [Impact]

  Currently the DKMS package broadcom-sta fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11 
hwe-edge
  and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud 
kernels
  as well.

  [Test Case]

  Install the broadcom-sta package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since the new
  changes are conditionally compiled based on the kernel version.

  Besides that the new package was tested with the following kernels in an amd64
  environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original Description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/broadcom-sta/20171018_120722_62eb1@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/broadcom-sta/20171018_121214_62eb1@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1724865/+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 1716359] Re: Unplugging headset with audio panel open mutes internal mic

2017-10-31 Thread Sebastien Bacher

** Also affects: unity-control-center (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/1716359

Title:
  Unplugging headset with audio panel open mutes internal mic

Status in OEM Priority Project:
  Confirmed
Status in unity-control-center package in Ubuntu:
  In Progress
Status in unity-control-center source package in Xenial:
  New

Bug description:
  
  Impact
  ==
  This is required by OEM team.

  Test Case
  =
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

  Make sure the internal mic is not muted.

  Regression Potential
  ===
  - Make sure that plugging/unplugging headphones does the correct thing.
  - Make sure that manually selecting an headphone actually switch mic.
  - Please also check that output sound works too.

  Original Bug Report
  ===
  This bug was reported by our OEM team, I'm opening this public bug.

  The internal microphone is muted after he headset is unplugged when the 
System Settings is running.
  We can not reproduce this bug when closed the System Settings window before 
unplugged the headset.

  Reproduce steps:
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1716359/+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 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

2017-10-31 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-drivers-common - 1:0.4.24

---
ubuntu-drivers-common (1:0.4.24) bionic; urgency=medium

  * gpu-manager.{c|py}:
- Add support for forcing the dGPU on on hybrid systems.
  Creating an empty file named "force-dgpu-on"
  in the /usr/share/gpu-manager.d directory will force the dGPU
  on in power saving mode (LP: #1728547).

 -- Alberto Milone   Mon, 30 Oct 2017
10:25:02 +0100

** Changed in: ubuntu-drivers-common (Ubuntu)
   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/1728547

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  In Progress
Status in ubuntu-drivers-common source package in Zesty:
  In Progress
Status in ubuntu-drivers-common source package in Artful:
  In Progress

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-10-31 Thread Łukasz Zemczak

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

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

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

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

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress
Status in sysdig package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in sysdig source package in Xenial:
  New

Bug description:
  [SRU sysdig XENIAL for 4.11 and 4.13 kernel support]

  sysdig DKMS fails to build because of API changes in 4.11, 4.13

  [FIX]

  Apply the following upstream sysdig commits for various kernel compat
  fixes:

  - [5fef96] Fix for kernel < 3.9 with CPU_ACCOUNTING_NATIVE disabled.
  - [29c40f] Fix cputime for kernel 3.8 and 2.6.18
  - [4596f0] Make sure to unlock mutex during error paths
  - [460f6e] Update probe module for kernel 4.11 (#829)

  [TEST]
  from kernel team autotests:

  sudo autotest/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  Without the fixes, these will fail. With the fixes, the regression
  tests pass. Run this 4.4, 4.8, 4.11 azure and 4.13-hwe kernels, must
  pass on all three kernel versions.

  [REGRESSION POTENTIAL]
  This affects just the sysdig driver. Could break on pre-4.13 older kernels, 
so needs regression checking on supported kernel versions.

  -

  azure : 4.11.0-1014.14

    == sysdig smoke test to trace dd, cat, read and writes ==
    Limiting raw capture file to 16384 blocks
    Try 1 of 10
    Could not find start of capture message, maybe sysdig didn't start?
    Raw capture file is 0 Mbytes
    Converted events file is 0 Mbytes
    Try 2 of 10
    Could not find start of capture message, maybe sysdig didn't start?
    Raw capture file is 0 Mbytes
    Converted events file is 0 Mbytes
    Try 3 of 10
    Could not find start of capture message, maybe sysdig didn't start?
    Raw capture file is 0 Mbytes
    Converted events file is 0 Mbytes
    Try 4 of 10
    Could not find start of capture message, maybe sysdig didn't start?
    Raw capture file is 0 Mbytes
    Converted events file is 0 Mbytes
    Try 5 of 10
    Could not find start of capture message, maybe sysdig didn't start?
    Raw capture file is 0 Mbytes
    Converted events file is 0 Mbytes
    Try 6 of 10
    Could not find start of capture message, maybe sysdig didn't start?
    Raw capture file is 0 Mbytes
    Converted events file is 0 Mbytes
    Try 7 of 10
    Could not find start of capture message, maybe sysdig didn't start?
    Raw capture file is 0 Mbytes
    Converted events file is 0 Mbytes
    Try 8 of 10
    Could not find start of capture message, maybe sysdig didn't start?
    Raw capture file is 0 Mbytes
    Converted events file is 0 Mbytes
    Try 9 of 10
    Could not find start of capture message, maybe sysdig didn't start?
    Raw capture file is 0 Mbytes
    Converted events file is 0 Mbytes
    Try 10 of 10
    Could not find start of capture message, maybe sysdig didn't start?
    Raw capture file is 0 Mbytes
    Converted events file is 0 Mbytes
    Found:
    0 sysdig events
    0 context switches
    0 reads from /dev/zero by dd
    0 writes to /dev/null by dd
    FAILED (trace at least 25 context switches)
    FAILED (trace at least 25 reads of /dev/zero by dd)
    FAILED (trace at least 25 writes to /dev/null by dd)

  Summary: 0 passed, 3 failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1718578] Re: Support setting I2C_TIMEOUT via ioctl for i2c-designware

2017-10-31 Thread Kai-Heng Feng

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

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

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

Title:
  Support setting I2C_TIMEOUT via ioctl for i2c-designware

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

Bug description:
  SRU Justification

  [Impact]
  The timeout value in i2c-designware is hardcoded. Userspace tool may want to 
change the timeout value via ioctl I2C_TIMEOUT, but it doesn't work for 
i2c-designware.

  [Test Case]
  Change the timeout value via ioctl I2C_TIMEOUT. Nothing happened.
  With the patch, timeout value for i2c-designware will be updated correctly.

  [Regression Potential]
  Minimal. The change only applies to a specific driver, i2c-designware. Also, 
it has minimal code change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718578/+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 1724021] Re: linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker

2017-10-31 Thread Po-Hsu Lin

No bug tagged with verification-needed.

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

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux-hwe-edge: 4.13.0-16.19~16.04.3 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-16.19~16.04.3 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
  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/1724021/+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 1552241] Re: libvirt-bin apparmor settings for usb host device

[Group.of.nepali.translators] [Bug 1686324] Re: usb hostdev passthrough generates the wrong apparmor rules

[Group.of.nepali.translators] [Bug 1729034] Re: don't short-circuit update-grub kernel postinst hook in containers

[Group.of.nepali.translators] [Bug 1727373] Re: SRU of LXCFS 2.0.8 (upstream bugfix release)

[Group.of.nepali.translators] [Bug 1728152] Re: EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address

[Group.of.nepali.translators] [Bug 1709920] Re: criu is not built for arm64

[Group.of.nepali.translators] [Bug 1716359] Re: Unplugging headset with audio panel open mutes internal mic

[Group.of.nepali.translators] [Bug 1477455] Re: Incorrect instructions leave automatic updates blocked when /boot is full

[Group.of.nepali.translators] [Bug 1717360] Re: test_update_origin.py test failure

[Group.of.nepali.translators] [Bug 1717360] Re: test_update_origin.py test failure

[Group.of.nepali.translators] [Bug 1721882] Re: Generic instructions for dealing with full partitions don't help much

[Group.of.nepali.translators] [Bug 1721882] Re: Generic instructions for dealing with full partitions don't help much

[Group.of.nepali.translators] [Bug 1729034] Re: don't short-circuit update-grub kernel postinst hook in containers

[Group.of.nepali.translators] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Group.of.nepali.translators] [Bug 1688508] Re: libvirt-guests.sh fails to shutdown guests in parallel

[Group.of.nepali.translators] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Group.of.nepali.translators] [Bug 1724060] Re: linux-azure: 4.11.0-1014.14 -proposed tracker

[Group.of.nepali.translators] [Bug 1724021] Re: linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker

[Group.of.nepali.translators] [Bug 1726809] Re: Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json

[Group.of.nepali.translators] [Bug 1719624] Re: [Hyper-V] linux-azure cifs mount error caused by missing nls_utf8.ko module

[Group.of.nepali.translators] [Bug 1722719] Re: HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

[Group.of.nepali.translators] [Bug 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

[Group.of.nepali.translators] [Bug 1708499] Re: usb 3-1: 2:1: cannot get freq at ep 0x1

[Group.of.nepali.translators] [Bug 1724021] Re: linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker

[Group.of.nepali.translators] [Bug 1724021] Re: linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker

[Group.of.nepali.translators] [Bug 1723246] Re: linux-hwe-edge: 4.13.0-16.19~16.04.1 -proposed tracker

[Group.of.nepali.translators] [Bug 1724060] Re: linux-azure: 4.11.0-1014.14 -proposed tracker

[Group.of.nepali.translators] [Bug 1724865] Re: broadcom-sta 6.30.223.271-3~16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Group.of.nepali.translators] [Bug 1716359] Re: Unplugging headset with audio panel open mutes internal mic

[Group.of.nepali.translators] [Bug 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

[Group.of.nepali.translators] [Bug 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

[Group.of.nepali.translators] [Bug 1718578] Re: Support setting I2C_TIMEOUT via ioctl for i2c-designware

[Group.of.nepali.translators] [Bug 1724021] Re: linux-hwe-edge: 4.13.0-16.19~16.04.3 -proposed tracker

33 matches

Site Navigation

Mail list logo

Footer information